Major Fail: TSA Agents Don’t Know What ‘DC’ Stands For

More embarrassment for the TSA this week ahead of one of the busiest travel weekends of the year.

Recent reports have surfaced on multiple occasions in which residents of Washington, DC, have been disallowed to board their flights until their IDs were double-checked.

The culprit? Officials in Washington recently replaced ‘Washington, DC’ on driver’s licenses with ‘District of Columbia’.

That now has TSA agents thoroughly confused because they’ve “never heard of the District of Columbia before.”

No, we’re not kidding.

This comes on the heels of a bombshell audit after the agency failed screening test by as much as 95% of the time.

Insert double-facepalm.

Here’s more from Daily Caller…

Transportation Security Administration officers continue to be confused about their nation’s capital.

District of Columbia Del. Eleanor Holmes Norton sent a letter Tuesday to TSA Administrator David Pekoske Wednesday about a Washington, D.C. resident who had issues at the Newark International Airport with her driver’s license.

Holmes Norton said that a TSA officer denied that the I.D. was valid and had to consult with colleagues before allowing the D.C. resident to catch her flight.

“As I am sure you can imagine, it can be humiliating for a U.S. citizen to be delayed because a federal government does not recognize the name of the District of Columbia,” Del. Holmes Norton wrote in her letter.

A Washington journalist tweeted in 2014 that a TSA agent in Orlando “never heard of ‘District of Columbia.’ Demanded passport because he didn’t believe my driver’s license was from US!?”

D.C. officials replaced “Washington D.C.” with “the District of Columbia” in 2014, which Del. Holmes Norton credited with the TSA’s troubles. This year, officials decided to return to the “Washington D.C.” labeling.

You Might Also Like