Manager David Wartofsky Fires Back At TSA
Editor's Note: Yesterday, November 1st, the TSA
slammed Potomac Airfield closed, with a brief and statement which
we provided without further comment. Here is Potomac Airfield's
response by manager David Wartofsky (below), which we'll run in the
same manner.
We do not know the cause of this closure at this time. (The TSA
statement did not make it clear). We are investigating and will
comment soon. Take it away, David Wartofsky:
TSA WALKING AWAY FROM IMPROVED AIRSPACE SECURITY BY CLOSING
POTOMAC AIRFIELD IN MARYLAND
Airspace security in the national capital area is provided by
multiple agencies. Rather than address the more significant
long-standing problems, unfortunately in this case, TSA has chosen
the least effective route.
To improve security overhead, instead of more effectively
dealing with real airspace issues, which are addressed through
operational security measures, TSA has chosen to lock a few
aircraft on the ground; even more remarkably, aircraft only
operated by pilots already cleared by TSA, The United States Secret
Service, and other agencies.
Meanwhile TSA allows pilots having less secure procedures to
continue to operate.
While Potomac Airfield has continually improved security,
through improving plans approved by TSA, and by incorporating
security measures already in place for other operators in the
National Capital Area, TSA has withdrawn its approval for reasons
that are not clear.
Potomac Airfield security plans have been developed in
consultation with all relevant agencies responsible to enhance
airspace security, including United States Secret Service, Customs,
DOD, FAA, and others, yet TSA for some reason feels this is
inadequate.
By TSA removing its approval, TSA has chosen to not support
enhanced security.
In review of information provided by TSA and other agencies, no
agency has identified any physical threat; particularly from the
pilots already approved by TSA, USSS and others, who operate from
the Potomac Airfield.
The procedures developed by Potomac Airfield, to more
effectively screen and eliminate any real potential threat, go
unnoticed by TSA.
TSA's current action is further evidence that TSA, in this
instance, does not understand enhancing airspace security through
more effective operational procedures.
TSA also does not understand the impact to legitimate
private-sector users; shown by their similar efforts to 're-open'
DCA to general aviation, as recently reported by the press.
Regardless, TSA continues to allow pilots not having assured
in-cockpit control to operate, while grounding those pilots with
the most effective operational security protocols.
Potomac understands that Congressional inquiries are under way
considering TSA's handling of this particular matter.
Potomac also plans to request clarification from the Executive
office about their sincerity in decisions post 911, to re-open
national security airspace to legitimate private sector users.
Potomac understands that TSA's statutory authority is to
coordinate with other government agencies.
It is not clear that TSA coordinated with any Executive agencies
in this action.