Brady Landing Air Park, NC

 

Title:  TSA Airport Inspections?

Subject: Strange-behaving Car in the Brady Landing Airpark today

Just before noon today I was on the motorcycle, following a black SUV on Maple Rd.  It began driving very slowly and then turned into the new street leading into the Airpark.  The driver was stopping frequently, looking into the Airpark and talking on a cell phone.  I pulled up beside him and asked if he was lost or was looking for somebody’s house.  He replied that he was just trying to get to the Airpark to take pictures of the airport’s fence and gates.  That got my attention and when I asked him why he wanted to do that he grinned and said he was a Department of Homeland Security inspector.  I asked to see his ID and he obliged and then said “I wish every place I visit was as security-conscious as you guys, stopping on the road to ask a stranger snooping around the airport what he is doing there”.  He then drove down to the taxiway gate and took pictures of that and of our “wait for the gate” signs and our “no trespassing” and “watch for airplanes” neighborhood entry signs.

He then came back by the house and we talked for almost an hour.  I answered his questions about Airpark ops, gave him copies of the Airpark Handbook and pointed out the security-related sections, and gave him a copy of the latest gate procedures.  He seemed very pleased with what he saw.

Turns out DHS inspected Currituck’s airport this morning, the E. City airport yesterday and was going to Manteo’s airport later this afternoon.

I don’t know how the Currituck airport itself fared in the inspection but I think our Airpark did fine.  Airport access and security remains a major focal point for DHS and FAA.  If you see unfamiliar cars or people in the Airpark, it pays to stop them and ask “Can I help you?”

Mack McKinney

 

200 OK

OK

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.