Narrative:

I flew from mtn to oxb in a beechcraft sundowner (BE23) for a planned day trip. My intentions were to departure ocean city for the return trip to essex skypark (W48). Friday morning I called flight service and filed an 'ADIZ' flight plan for an intended transition W48 to mtn, a short 6 mi flight. Flight service seemed a bit confused with my request. He stated that an ADIZ flight plan was for an intended flight into, or out of, an ADIZ and wanted to know where my exit or entrance point might be. The briefer I talked to said he could not accept my flight plan as I was neither entering into nor exiting an ADIZ area. I explained that I was at an airport just 6 mi away from mtn airport already inside the ADIZ. He went on to say something to the effect of since I was already inside the ADIZ, he wasn't sure of the exact procedure to use. I told him I would like to file my original ADIZ flight plan with a proposed departure time of XA45. This was the end of the conversation. I was not given any type of squawk code or phone number(south) to call prior to takeoff. Having successfully communicated on the ground with potomac approach just a few hours earlier, I was pretty confident I could get them again. When I arrived to the airport early that morning, the FBO was not open. My ride had already dropped me off at the airport. I attempted several times to contact potomac approach on the same frequency I had successfully communicated with them on just 4 hours earlier. No luck. I tried to call potomac approach via my cell phone, but at this airport at that time of the morning, I was unable to get a signal from my cell phone. I exited the aircraft and walked around a bit looking for a pay phone, but could not find one. I figured since I had already filed the ADIZ flight plan for a departure from this airport at this time of day, I could take off, stay in the pattern, get my squawk code, and finish my planned short return flight. Immediately upon reaching the downwind leg of the approach pattern, I contacted potomac approach and advised them of my intentions. The controller immediately snapped back that I had 'busted the ADIZ' and asked me what my destination was. After a bit of hesitation, he gave me a squawk code and told me to fly direct mtn airport and to advise him when I was ready to write down a contact number. I wrote down the contact number and landed at mtn airport. The potomac approach facility supervisor informed me that he was required to submit this information to the FSDO. My mistake was not going 'down-the-road' to make a phone call and obtain a discrete squawk code prior to departure. I carry with me on my kneeboard an advisory form I obtained from pilot organization on ADIZ operations. I remembered one particular line in this checklist that stated 'do not leave the vicinity of the airport without ATC approval and radio contact.' my erroneous thinking was to 'stay in the pattern' until I could work out a release back to mtn airport. The chain of events that led up to this poor decision on my part was: 1) confusion between myself and the FSS briefer. The difficulty in getting an ADIZ flight plan filed, and the attendant not giving me either a squawk code or contact information left me a bit puzzled and confused on my procedure. 2) no communications with ATC prior to departure. I found myself with no immediate option to contact ATC on the ground. In hindsight, I should have packed things up and walked to an area that either had a phone or where a good signal could be obtained on my cell phone. I know now that contacting ATC 'in the air' prior to departing the air traffic area was not an acceptable option. Since the incident, I have been in direct contact with a flight instructor. He and I have thoroughly reviewed ADIZ operations.

Google
 

Original NASA ASRS Text

Title: PLT OF BE23 FAILED TO OBTAIN ADIZ CLRNC AND CODE PRIOR TO TKOF FOR SHORT FLT FROM W48 TO MTN. A POORLY CONDUCTED BRIEFING FROM AN ILL INFORMED FSS BRIEFER CONTRIBUTED TO THIS RPTR'S DILEMMA.

Narrative: I FLEW FROM MTN TO OXB IN A BEECHCRAFT SUNDOWNER (BE23) FOR A PLANNED DAY TRIP. MY INTENTIONS WERE TO DEP OCEAN CITY FOR THE RETURN TRIP TO ESSEX SKYPARK (W48). FRIDAY MORNING I CALLED FLT SVC AND FILED AN 'ADIZ' FLT PLAN FOR AN INTENDED TRANSITION W48 TO MTN, A SHORT 6 MI FLT. FLT SVC SEEMED A BIT CONFUSED WITH MY REQUEST. HE STATED THAT AN ADIZ FLT PLAN WAS FOR AN INTENDED FLT INTO, OR OUT OF, AN ADIZ AND WANTED TO KNOW WHERE MY EXIT OR ENTRANCE POINT MIGHT BE. THE BRIEFER I TALKED TO SAID HE COULD NOT ACCEPT MY FLT PLAN AS I WAS NEITHER ENTERING INTO NOR EXITING AN ADIZ AREA. I EXPLAINED THAT I WAS AT AN ARPT JUST 6 MI AWAY FROM MTN ARPT ALREADY INSIDE THE ADIZ. HE WENT ON TO SAY SOMETHING TO THE EFFECT OF SINCE I WAS ALREADY INSIDE THE ADIZ, HE WASN'T SURE OF THE EXACT PROC TO USE. I TOLD HIM I WOULD LIKE TO FILE MY ORIGINAL ADIZ FLT PLAN WITH A PROPOSED DEP TIME OF XA45. THIS WAS THE END OF THE CONVERSATION. I WAS NOT GIVEN ANY TYPE OF SQUAWK CODE OR PHONE NUMBER(S) TO CALL PRIOR TO TKOF. HAVING SUCCESSFULLY COMMUNICATED ON THE GND WITH POTOMAC APCH JUST A FEW HRS EARLIER, I WAS PRETTY CONFIDENT I COULD GET THEM AGAIN. WHEN I ARRIVED TO THE ARPT EARLY THAT MORNING, THE FBO WAS NOT OPEN. MY RIDE HAD ALREADY DROPPED ME OFF AT THE ARPT. I ATTEMPTED SEVERAL TIMES TO CONTACT POTOMAC APCH ON THE SAME FREQ I HAD SUCCESSFULLY COMMUNICATED WITH THEM ON JUST 4 HRS EARLIER. NO LUCK. I TRIED TO CALL POTOMAC APCH VIA MY CELL PHONE, BUT AT THIS ARPT AT THAT TIME OF THE MORNING, I WAS UNABLE TO GET A SIGNAL FROM MY CELL PHONE. I EXITED THE ACFT AND WALKED AROUND A BIT LOOKING FOR A PAY PHONE, BUT COULD NOT FIND ONE. I FIGURED SINCE I HAD ALREADY FILED THE ADIZ FLT PLAN FOR A DEP FROM THIS ARPT AT THIS TIME OF DAY, I COULD TAKE OFF, STAY IN THE PATTERN, GET MY SQUAWK CODE, AND FINISH MY PLANNED SHORT RETURN FLT. IMMEDIATELY UPON REACHING THE DOWNWIND LEG OF THE APCH PATTERN, I CONTACTED POTOMAC APCH AND ADVISED THEM OF MY INTENTIONS. THE CTLR IMMEDIATELY SNAPPED BACK THAT I HAD 'BUSTED THE ADIZ' AND ASKED ME WHAT MY DEST WAS. AFTER A BIT OF HESITATION, HE GAVE ME A SQUAWK CODE AND TOLD ME TO FLY DIRECT MTN ARPT AND TO ADVISE HIM WHEN I WAS READY TO WRITE DOWN A CONTACT NUMBER. I WROTE DOWN THE CONTACT NUMBER AND LANDED AT MTN ARPT. THE POTOMAC APCH FACILITY SUPVR INFORMED ME THAT HE WAS REQUIRED TO SUBMIT THIS INFO TO THE FSDO. MY MISTAKE WAS NOT GOING 'DOWN-THE-ROAD' TO MAKE A PHONE CALL AND OBTAIN A DISCRETE SQUAWK CODE PRIOR TO DEP. I CARRY WITH ME ON MY KNEEBOARD AN ADVISORY FORM I OBTAINED FROM PLT ORGANIZATION ON ADIZ OPS. I REMEMBERED ONE PARTICULAR LINE IN THIS CHKLIST THAT STATED 'DO NOT LEAVE THE VICINITY OF THE ARPT WITHOUT ATC APPROVAL AND RADIO CONTACT.' MY ERRONEOUS THINKING WAS TO 'STAY IN THE PATTERN' UNTIL I COULD WORK OUT A RELEASE BACK TO MTN ARPT. THE CHAIN OF EVENTS THAT LED UP TO THIS POOR DECISION ON MY PART WAS: 1) CONFUSION BTWN MYSELF AND THE FSS BRIEFER. THE DIFFICULTY IN GETTING AN ADIZ FLT PLAN FILED, AND THE ATTENDANT NOT GIVING ME EITHER A SQUAWK CODE OR CONTACT INFO LEFT ME A BIT PUZZLED AND CONFUSED ON MY PROC. 2) NO COMS WITH ATC PRIOR TO DEP. I FOUND MYSELF WITH NO IMMEDIATE OPTION TO CONTACT ATC ON THE GND. IN HINDSIGHT, I SHOULD HAVE PACKED THINGS UP AND WALKED TO AN AREA THAT EITHER HAD A PHONE OR WHERE A GOOD SIGNAL COULD BE OBTAINED ON MY CELL PHONE. I KNOW NOW THAT CONTACTING ATC 'IN THE AIR' PRIOR TO DEPARTING THE ATA WAS NOT AN ACCEPTABLE OPTION. SINCE THE INCIDENT, I HAVE BEEN IN DIRECT CONTACT WITH A FLT INSTRUCTOR. HE AND I HAVE THOROUGHLY REVIEWED ADIZ OPS.

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.