Narrative:

I inadvertently violated the washington dc ADIZ by 3 or 4 NM this morning. This is especially embarrassing because I am based at an airport, gai, which is within the ADIZ, and I am very well familiar with security procedures for going into and out of the ADIZ. The immediate reason for my error was my failure to remember/realize/clarify that the southern border of the ADIZ, which I violated, does not coincide with the dc class B airspace, as it does on the northern side, where I make nearly all my flts. As with many aviation incidents there was a cascading series of errors and problems. I left manteo, mqi, this morning approximately XA45 on a VFR flight, destination gai. Before departure, I filed an ADIZ entry plan, as is required. I stated the entry point as the brv VOR, and the proposed entry time as XC15, with altitude 2500 ft. About 10 mins after takeoff, I contacted norfolk approach for clearance through their class C. They gave me a squawk, then handed me off to subsequent controllers for flight following. I remained on a code, with flight following, until I was about 15 NM southeast of the brv VOR. At that point, the richmond approach controller told me: a) I was leaving his radar coverage, B) I should squawk VFR, and C) in 10 mi I should contact potomac on 119.85. My VFR sectional also showed 119.85 as the potomac frequency for approachs near brv. Starting about 6 NM southeast of brv VOR, and continuing when I passed brv and went about 4 NM northeast of the VOR, I repeatedly tried to raise potomac on 119.85. I called 6 or 8 times, each time saying my tail number and 'ADIZ clearance.' I could hear other traffic on the frequency but never got a reply. As I neared the quantico air base, nyg, I realized that I would start to have ADIZ and class B trouble. I tried the next frequency shown on the chart, 124.65, and immediately made contact. At this same time, I circled southward -- and climbed from 2500-2700 ft, to stay above the 2500 ft ceiling of quantico's space. The potomac controller on 124.65 told me to contact quantico. He told me I was inside the ADIZ, and I should proceed south and re-contact him. 2 or 3 mins later, he called me with a squawk and told me that I was now cleared to enter. The rest of the flight was uneventful. On landing, I was told by the FBO that potomac TRACON wanted me to contact them. I was fundamentally to blame here for not clarifying that the ADIZ border extended farther south than the class B. The main culprit was complacency. I have made probably 100 xings of the northern ADIZ border, and I did not inform myself of the difference. The compounding factors were my difficulty in making contact on 119.85. A big surprise to me is that, my database in my GPS which is current through dec/thu/03 (1 week after the incident), shows the class B border but not the ADIZ border. So I turned south before I came to the class B (I turned about 2 NM south of quantico) but not before I was in the ADIZ. I do not know what sort of enforcement action this might lead to. It certainly has concentrated my mind on becoming completely familiar with security requirements.

Related reports:

Google
 

Original NASA ASRS Text

Title: SR20 PLT PENETRATES DC ADIZ FROM VICINITY OF BRV VORTAC AND NYG AIRBASE.

Narrative: I INADVERTENTLY VIOLATED THE WASHINGTON DC ADIZ BY 3 OR 4 NM THIS MORNING. THIS IS ESPECIALLY EMBARRASSING BECAUSE I AM BASED AT AN ARPT, GAI, WHICH IS WITHIN THE ADIZ, AND I AM VERY WELL FAMILIAR WITH SECURITY PROCS FOR GOING INTO AND OUT OF THE ADIZ. THE IMMEDIATE REASON FOR MY ERROR WAS MY FAILURE TO REMEMBER/REALIZE/CLARIFY THAT THE SOUTHERN BORDER OF THE ADIZ, WHICH I VIOLATED, DOES NOT COINCIDE WITH THE DC CLASS B AIRSPACE, AS IT DOES ON THE NORTHERN SIDE, WHERE I MAKE NEARLY ALL MY FLTS. AS WITH MANY AVIATION INCIDENTS THERE WAS A CASCADING SERIES OF ERRORS AND PROBS. I LEFT MANTEO, MQI, THIS MORNING APPROX XA45 ON A VFR FLT, DEST GAI. BEFORE DEP, I FILED AN ADIZ ENTRY PLAN, AS IS REQUIRED. I STATED THE ENTRY POINT AS THE BRV VOR, AND THE PROPOSED ENTRY TIME AS XC15, WITH ALT 2500 FT. ABOUT 10 MINS AFTER TKOF, I CONTACTED NORFOLK APCH FOR CLRNC THROUGH THEIR CLASS C. THEY GAVE ME A SQUAWK, THEN HANDED ME OFF TO SUBSEQUENT CTLRS FOR FLT FOLLOWING. I REMAINED ON A CODE, WITH FLT FOLLOWING, UNTIL I WAS ABOUT 15 NM SE OF THE BRV VOR. AT THAT POINT, THE RICHMOND APCH CTLR TOLD ME: A) I WAS LEAVING HIS RADAR COVERAGE, B) I SHOULD SQUAWK VFR, AND C) IN 10 MI I SHOULD CONTACT POTOMAC ON 119.85. MY VFR SECTIONAL ALSO SHOWED 119.85 AS THE POTOMAC FREQ FOR APCHS NEAR BRV. STARTING ABOUT 6 NM SE OF BRV VOR, AND CONTINUING WHEN I PASSED BRV AND WENT ABOUT 4 NM NE OF THE VOR, I REPEATEDLY TRIED TO RAISE POTOMAC ON 119.85. I CALLED 6 OR 8 TIMES, EACH TIME SAYING MY TAIL NUMBER AND 'ADIZ CLRNC.' I COULD HEAR OTHER TFC ON THE FREQ BUT NEVER GOT A REPLY. AS I NEARED THE QUANTICO AIR BASE, NYG, I REALIZED THAT I WOULD START TO HAVE ADIZ AND CLASS B TROUBLE. I TRIED THE NEXT FREQ SHOWN ON THE CHART, 124.65, AND IMMEDIATELY MADE CONTACT. AT THIS SAME TIME, I CIRCLED SOUTHWARD -- AND CLBED FROM 2500-2700 FT, TO STAY ABOVE THE 2500 FT CEILING OF QUANTICO'S SPACE. THE POTOMAC CTLR ON 124.65 TOLD ME TO CONTACT QUANTICO. HE TOLD ME I WAS INSIDE THE ADIZ, AND I SHOULD PROCEED S AND RE-CONTACT HIM. 2 OR 3 MINS LATER, HE CALLED ME WITH A SQUAWK AND TOLD ME THAT I WAS NOW CLRED TO ENTER. THE REST OF THE FLT WAS UNEVENTFUL. ON LNDG, I WAS TOLD BY THE FBO THAT POTOMAC TRACON WANTED ME TO CONTACT THEM. I WAS FUNDAMENTALLY TO BLAME HERE FOR NOT CLARIFYING THAT THE ADIZ BORDER EXTENDED FARTHER S THAN THE CLASS B. THE MAIN CULPRIT WAS COMPLACENCY. I HAVE MADE PROBABLY 100 XINGS OF THE NORTHERN ADIZ BORDER, AND I DID NOT INFORM MYSELF OF THE DIFFERENCE. THE COMPOUNDING FACTORS WERE MY DIFFICULTY IN MAKING CONTACT ON 119.85. A BIG SURPRISE TO ME IS THAT, MY DATABASE IN MY GPS WHICH IS CURRENT THROUGH DEC/THU/03 (1 WK AFTER THE INCIDENT), SHOWS THE CLASS B BORDER BUT NOT THE ADIZ BORDER. SO I TURNED S BEFORE I CAME TO THE CLASS B (I TURNED ABOUT 2 NM S OF QUANTICO) BUT NOT BEFORE I WAS IN THE ADIZ. I DO NOT KNOW WHAT SORT OF ENFORCEMENT ACTION THIS MIGHT LEAD TO. IT CERTAINLY HAS CONCENTRATED MY MIND ON BECOMING COMPLETELY FAMILIAR WITH SECURITY REQUIREMENTS.

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.