Narrative:

On feb/sun/04, I flew round-trip from my base airport (W00) to lku with a full stop at lku county. I filed 2 ADIZ flight plans before I departed W00, 1 flight plan for the outbound trip and 1 for the return trip. Just before departure, I called and got my transponder code which I activated on departure. The flight went well. I took off shortly thereafter and headed back toward brv VOR. A few mi before reaching brv, I began trying to contact ATC on 124.65. I tried runway 30R 4 times. Each time I gave my tail number location at brv, and requested a squawk code since I had already filed my ADIZ flight plan. On the last call, I was told that the transmission was broken and to contact 119.3. I immediately went to that frequency and idented myself, gave location at brooke VOR and asked for a squawk. I was told to contact 126.75, which I did. I then went through the same process except by that time I was a few mi northeast of brv. I was given a squawk code. About 2 mins later, ATC asked me to contact by phone, because of a possible ADIZ violation. From my first attempt to contact ATC till I received my squawk code was about 5 mins. If I was inside the ADIZ, then I was just barely inside. I am an instrument rated commercial pilot and fly fairly frequently. I am familiar with the ADIZ procedures, although I just moved to the area from out of state, and this was the 6TH or 7TH time that I have flown into or out of ADIZ. Although I knew where the ADIZ boundary was, it was not shown on the sectional chart that I was using. The problem arose from not being able to get my squawk code from ATC and being given 3 different frequencys to call. Contributing factors were not having the ADIZ marked on the sectional chart. Corrective action will be to have a chart with me next time that has the exact boundary on it and to circle brv VOR until I have the code. I have over 800 hours total flight time on my own airplane, and am a very careful pilot. If I did violate the ADIZ, it was certainly an accident and not on purpose.

Google
 

Original NASA ASRS Text

Title: PLT OF PA28 ENTERS DC ADIZ WHILE ATTEMPTING UNSUCCESSFULLY TO GET APPROPRIATE CLRNC FROM PCT.

Narrative: ON FEB/SUN/04, I FLEW ROUND-TRIP FROM MY BASE ARPT (W00) TO LKU WITH A FULL STOP AT LKU COUNTY. I FILED 2 ADIZ FLT PLANS BEFORE I DEPARTED W00, 1 FLT PLAN FOR THE OUTBOUND TRIP AND 1 FOR THE RETURN TRIP. JUST BEFORE DEP, I CALLED AND GOT MY XPONDER CODE WHICH I ACTIVATED ON DEP. THE FLT WENT WELL. I TOOK OFF SHORTLY THEREAFTER AND HEADED BACK TOWARD BRV VOR. A FEW MI BEFORE REACHING BRV, I BEGAN TRYING TO CONTACT ATC ON 124.65. I TRIED RWY 30R 4 TIMES. EACH TIME I GAVE MY TAIL NUMBER LOCATION AT BRV, AND REQUESTED A SQUAWK CODE SINCE I HAD ALREADY FILED MY ADIZ FLT PLAN. ON THE LAST CALL, I WAS TOLD THAT THE XMISSION WAS BROKEN AND TO CONTACT 119.3. I IMMEDIATELY WENT TO THAT FREQ AND IDENTED MYSELF, GAVE LOCATION AT BROOKE VOR AND ASKED FOR A SQUAWK. I WAS TOLD TO CONTACT 126.75, WHICH I DID. I THEN WENT THROUGH THE SAME PROCESS EXCEPT BY THAT TIME I WAS A FEW MI NE OF BRV. I WAS GIVEN A SQUAWK CODE. ABOUT 2 MINS LATER, ATC ASKED ME TO CONTACT BY PHONE, BECAUSE OF A POSSIBLE ADIZ VIOLATION. FROM MY FIRST ATTEMPT TO CONTACT ATC TILL I RECEIVED MY SQUAWK CODE WAS ABOUT 5 MINS. IF I WAS INSIDE THE ADIZ, THEN I WAS JUST BARELY INSIDE. I AM AN INST RATED COMMERCIAL PLT AND FLY FAIRLY FREQUENTLY. I AM FAMILIAR WITH THE ADIZ PROCS, ALTHOUGH I JUST MOVED TO THE AREA FROM OUT OF STATE, AND THIS WAS THE 6TH OR 7TH TIME THAT I HAVE FLOWN INTO OR OUT OF ADIZ. ALTHOUGH I KNEW WHERE THE ADIZ BOUNDARY WAS, IT WAS NOT SHOWN ON THE SECTIONAL CHART THAT I WAS USING. THE PROB AROSE FROM NOT BEING ABLE TO GET MY SQUAWK CODE FROM ATC AND BEING GIVEN 3 DIFFERENT FREQS TO CALL. CONTRIBUTING FACTORS WERE NOT HAVING THE ADIZ MARKED ON THE SECTIONAL CHART. CORRECTIVE ACTION WILL BE TO HAVE A CHART WITH ME NEXT TIME THAT HAS THE EXACT BOUNDARY ON IT AND TO CIRCLE BRV VOR UNTIL I HAVE THE CODE. I HAVE OVER 800 HRS TOTAL FLT TIME ON MY OWN AIRPLANE, AND AM A VERY CAREFUL PLT. IF I DID VIOLATE THE ADIZ, IT WAS CERTAINLY AN ACCIDENT AND NOT ON PURPOSE.

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.