[JYO] A message from the President of AOPA

Passed on for those of of you that are not (yet) AOPA members....

Ed
AOPA Member since 1978
- - - -

Dear AOPA member...

I was gratified by the recent attendance of more than 300 pilot/members to 
the Baltimore Pilot Town Meeting last week. At that meeting, I did not 
present a "canned" speech, but spoke very openly about the current situation 
involving the airspace around the nation's capital, the area where attendees 
to the meeting and myself "live and fly"; or as the line goes, "live to fly." 

As you know, the AOPA staff is constantly working issues in Washington that 
you never hear about. We often solve problems BEFORE they become public, and 
for this reason they never appear as problems for pilots. That's our job.

Since last November, however, your association staff including myself, have 
been acutely aware of "chatter." It started as rumors, but is now escalating 
well beyond that stage. At last week's meeting, I shared with the local 
pilots what we have been hearing, and feel it only fair that those members 
not in attendance have the same information.

Since 9/11, but particularly since late last year, Washington, D.C., airspace 

has been under increased scrutiny from the highest levels of government. I am 

sure much of this is because the nation continues to gather threat 
information from the terrorist community, and our government prepares for a 
possible hostile confrontation with Iraq. To put it bluntly, security 
officials are very concerned that the terrorists are not easily deterred and 
that they are intent on again attacking the nation's capital, utilizing some 
form of aviation. 

Even though it has not been officially announced as I write this message, the 

hoped for changes to the Special Flight Rules Area (SFAR 94) aren't likely to 

occur. This is the SFAR, set to expire February 13th, that prohibits GA 
operations within a 15-nm radius of the DCA VOR. It has very specific meaning 

to the pilots and businesses at the "DC-3" airports: Potomac, Hyde and 
College Park. In spite of our efforts, including a petition and Congressional 

support, this rule will be extended for two additional years, with an 
official of TSA stating, "This is the best case."

For several months we have been aware of the formation of the National 
Capital Region Airspace Security Working Group, tasking numerous agencies 
with developing stricter airspace regulations around Washington, D.C. As we 
reported on the AOPA website last week, the government has established the 
National Capital Region Command Center (NCRCC), staffed 24/7 to prevent SFAR 
94 airspace incursions. All of this is complicated by airspace violations by 
general aviation pilots that break the confidence of those who are deciding 
our fate. The U.S. Customs Air Marine Interdiction Branch is patrolling the 
skies in a law enforcement/public safety role. This past weekend, there were 
two intercepts made by this new unit. To make matters worse, both were 
brought down at AOPA's home airport, Frederick, MD.

All of what I have previously stated is fact or will soon be fact. Now to the 

continuing "chatter" which is somewhat disturbing. These established groups 
and agencies are discussing possible implementation of additional D.C. 
airspace restrictions. The range of the restrictions would greatly expand the 

scope of the current 15-nm radius SFAR 94. Least restrictive would be the 
vertical expansion of the Washington-Baltimore Class B airspace from the 
surface to 10,000 ft, with no VFR operations. Next, rumors abound that from 
the outer ring of the Class B to the Mode C Veil outer boundary, creating a 
full 30-nm ring around IAD, DCA and BWI a "squawk and talk" requirement would 

be implemented (discrete transponder code and communications), along with no 
flight training. The worst we have heard is a draconian 55-mile 'no-fly' zone 

around Washington, DC. This would mean absolutely no Part 91 and no Part 135 
operations. Period.

Don't kill the messenger, and don't think AOPA is sitting on its hands 
accepting any of this. Believe me, with our national headquarters in the 
area, we are keenly aware and concerned about potential restrictions on our 
members. Our staff continues to press Department of Homeland Security 
officials to not unfairly target general aviation. We have stepped up our 
meetings with TSA, FAA, Dept. of Defense, U.S. Customs, Secretary Ridge, 
other senior Department of Homeland Security staff, as well as Congress. We 
have compiled economic impact data on all general aviation airports within a 
55-mile radius of Washington and we are pressing for "reason" in a situation 
that has the potential to become extremely "unreasonable." As soon as we have 

something more specific, we'll obviously turn to our elected officials in 
Congress to intercede, and reach out to you with a call to action. 

Once again, while we usually fight these battles silently, and behind the 
scenes, without involving you in the rumors, gossip, and back-and-forth 
dialogue, as President of your association and a local pilot, I think you 
should be aware of this information. 

Phil Boyer

Other related posts: