Narrative:

I am a police officer and a pilot with over 15 yrs of experience in aviation. I have also been requested by other government interdiction agencies to stop and detain pilots who have allegedly violated this airspace and landed at montgomery county airpark, md. At XA00 hours, I proceeded to file a VFR flight plan from gai to oxb. This was the first time I had filed VFR in a year. The flight down to oxb was conducted without incident. At XD00 hours, I proceeded to file a return flight plan which had an original departure time of XF30 local time. Jyo FSS was contacted for an amended departure time of XG30 local. At XG15 hours, I proceeded to runway 20. After attempts were made to obtain a clearance through clearance delivery and millville FSS, I contacted patuxent approach (127.95) to obtain a clearance. Patuxent allowed a transition through R4006 and handed me off to pct approach. After several calls to pct and then no answer from pct, I proceeded to obtain more frequencies for pct. Pct approach was heard speaking with several aircraft, but did not respond to any transmission made by me. After 20 mins of attempting to gain a squawk code, higher altitude and now 42KM east of dca at 2500 ft, controller finally answered me and admitted he had been ignoring me. He angrily advised to remain clear of class B and the 'zone' and stated he would call me. The controller refused to acknowledge me for a request for higher altitude. After a few turns in holding 10 KM east of bay bridge airport, a different controller gave me a squawk code and allowed me to enter the corridor to gai. While en route, the controller advised me to call upon landing. Later, the ARTCC supervisor advised a pilot deviation report will be initiated. A controller had reported a violation of airspace within the 30 KM of class B airspace. Since I had remained clear of the 15 KM radius of dca and clear of class B airspace, I was unaware of any penetration or incursion. A VFR sectional depicted a 15 KM radius of dca. However, on 03/thur/03, the airspace in this corridor has been extended to 30 KM. I was unaware of this until this writing. Sometime after 03/thur/03 a sign had been posted on the front door of the primary FBO. This sign notifies 60% of the pilots at gai. However, the other 40% of pilots go through a coded gate on the northwest side of the field. I feel this error was made by me in failing to know the exact border of the new zone and the refusal of communication by ATC. I have some suggestions which should improve the safety of travel from gai and through the dca corridor. A VFR sectional should highlight the new airspace change covering the entire 30 KM of class B airspace. No pilot should be ignored by ATC. I feel controllers are habitually ignoring general aviation aircraft. At gai, a sign should be posted on the gate leading to personal and club aircraft indicating this new airspace. The AWOS should indicate the range of this new airspace rather than just a squawk code for transition.

Google
 

Original NASA ASRS Text

Title: SR20 PLT, POLICE OFFICER, FOUND OUT HOW UNWORKABLE ATTEMPTING TO GET CLRNC INTO DC ADIZ. THE PLT PENETRATED THE ADIZ AFTER THE PCT APCH CTLR AND THE NHK MILFAC CTLR REFUSED TO RESPOND TO PLTS COM REQUEST.

Narrative: I AM A POLICE OFFICER AND A PLT WITH OVER 15 YRS OF EXPERIENCE IN AVIATION. I HAVE ALSO BEEN REQUESTED BY OTHER GOVERNMENT INTERDICTION AGENCIES TO STOP AND DETAIN PLTS WHO HAVE ALLEGEDLY VIOLATED THIS AIRSPACE AND LANDED AT MONTGOMERY COUNTY AIRPARK, MD. AT XA00 HRS, I PROCEEDED TO FILE A VFR FLT PLAN FROM GAI TO OXB. THIS WAS THE FIRST TIME I HAD FILED VFR IN A YEAR. THE FLT DOWN TO OXB WAS CONDUCTED WITHOUT INCIDENT. AT XD00 HRS, I PROCEEDED TO FILE A RETURN FLT PLAN WHICH HAD AN ORIGINAL DEP TIME OF XF30 LCL TIME. JYO FSS WAS CONTACTED FOR AN AMENDED DEP TIME OF XG30 LCL. AT XG15 HRS, I PROCEEDED TO RWY 20. AFTER ATTEMPTS WERE MADE TO OBTAIN A CLRNC THROUGH CLRNC DELIVERY AND MILLVILLE FSS, I CONTACTED PATUXENT APCH (127.95) TO OBTAIN A CLRNC. PATUXENT ALLOWED A TRANSITION THROUGH R4006 AND HANDED ME OFF TO PCT APCH. AFTER SEVERAL CALLS TO PCT AND THEN NO ANSWER FROM PCT, I PROCEEDED TO OBTAIN MORE FREQUENCIES FOR PCT. PCT APCH WAS HEARD SPEAKING WITH SEVERAL ACFT, BUT DID NOT RESPOND TO ANY XMISSION MADE BY ME. AFTER 20 MINS OF ATTEMPTING TO GAIN A SQUAWK CODE, HIGHER ALT AND NOW 42KM E OF DCA AT 2500 FT, CTLR FINALLY ANSWERED ME AND ADMITTED HE HAD BEEN IGNORING ME. HE ANGRILY ADVISED TO REMAIN CLR OF CLASS B AND THE 'ZONE' AND STATED HE WOULD CALL ME. THE CTLR REFUSED TO ACKNOWLEDGE ME FOR A REQUEST FOR HIGHER ALT. AFTER A FEW TURNS IN HOLDING 10 KM E OF BAY BRIDGE ARPT, A DIFFERENT CTLR GAVE ME A SQUAWK CODE AND ALLOWED ME TO ENTER THE CORRIDOR TO GAI. WHILE ENRTE, THE CTLR ADVISED ME TO CALL UPON LNDG. LATER, THE ARTCC SUPVR ADVISED A PLT DEVIATION RPT WILL BE INITIATED. A CTLR HAD RPTED A VIOLATION OF AIRSPACE WITHIN THE 30 KM OF CLASS B AIRSPACE. SINCE I HAD REMAINED CLR OF THE 15 KM RADIUS OF DCA AND CLR OF CLASS B AIRSPACE, I WAS UNAWARE OF ANY PENETRATION OR INCURSION. A VFR SECTIONAL DEPICTED A 15 KM RADIUS OF DCA. HOWEVER, ON 03/THUR/03, THE AIRSPACE IN THIS CORRIDOR HAS BEEN EXTENDED TO 30 KM. I WAS UNAWARE OF THIS UNTIL THIS WRITING. SOMETIME AFTER 03/THUR/03 A SIGN HAD BEEN POSTED ON THE FRONT DOOR OF THE PRIMARY FBO. THIS SIGN NOTIFIES 60% OF THE PLTS AT GAI. HOWEVER, THE OTHER 40% OF PLTS GO THROUGH A CODED GATE ON THE NW SIDE OF THE FIELD. I FEEL THIS ERROR WAS MADE BY ME IN FAILING TO KNOW THE EXACT BORDER OF THE NEW ZONE AND THE REFUSAL OF COMMUNICATION BY ATC. I HAVE SOME SUGGESTIONS WHICH SHOULD IMPROVE THE SAFETY OF TRAVEL FROM GAI AND THROUGH THE DCA CORRIDOR. A VFR SECTIONAL SHOULD HIGHLIGHT THE NEW AIRSPACE CHANGE COVERING THE ENTIRE 30 KM OF CLASS B AIRSPACE. NO PLT SHOULD BE IGNORED BY ATC. I FEEL CTLRS ARE HABITUALLY IGNORING GENERAL AVIATION ACFT. AT GAI, A SIGN SHOULD BE POSTED ON THE GATE LEADING TO PERSONAL AND CLUB ACFT INDICATING THIS NEW AIRSPACE. THE AWOS SHOULD INDICATE THE RANGE OF THIS NEW AIRSPACE RATHER THAN JUST A SQUAWK CODE FOR TRANSITION.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.