Narrative:

After landing at maryland airport (2w5) at XA52, I closed out my DVFR flight plan with elkins FSS and refiled for an XC30 estimated time of departure. At approximately XC30, I started the engine and attempted to contact potomac approach/departure control for an assigned transponder code for exiting the ADIZ. I was unsuccessful in my attempt but, since I had been assigned a code while airborne on the inbound flight, I assumed the process would be the same in reverse for my departure. I was aware that codes were required by telephone assignment for the so-called 'DC3' but, since 2w5 is not one of those 3 airports, I assumed the code could be picked up once airborne, just as clrncs from untowered fields frequently are. I was unaware of any requirement to obtain a transponder code and contact frequency, on the ground, at this airport, prior to takeoff. Subsequently, I took off at approximately XC40, turning within 2 NM of the airport, so that I would remain in the immediate vicinity while contacting potomac departure. I was nearly overhead the airport when contact was established and potomac advised me to land immediately and obtain a code. I did as instructed, landing within 1 min of being so instructed. After landing, I went to the FBO office, where I found the correct phone number for the TRACON. I called, and my error was acknowledged by an unidented female person, who gave me a transponder code and frequency 118.95, and she told me that was all I needed. I then returned to my plane and strapped in. As I was doing that, an unidented gentleman walked out of the FBO office, cell phone in hand, and handed it to me. The caller was from united states customs, and when I told him what had happened, and that I had now been given a code and frequency, he said that I was good to go. After taking off, and contacting potomac departure control, I was told to call ATC regarding a possible pilot flight violation, upon landing at my destination. I subsequently landed, called FSS to close my flight plan, and then called the number given. I spoke to a gentleman who asked me a few questions regarding the incident, and who then informed me that I would probably be hearing from flight standards at some future time. He also suggested that I file this NASA report. Since I had never flown into the washington, dc, ADIZ before, I had attempted to research the entire flight very carefully prior to initial takeoff, and I truly believed that I was satisfying all requirements for the flight. I regret my error. I have certainly learned from this experience, and I will not make such an error again!

Related reports:

Google
 

Original NASA ASRS Text

Title: A GA PLT IN HIS VAN'S RV6A ATTEMPTS A VFR DEP WITHOUT A VALID XPONDER CODE ASSIGNMENT FROM PCT PRIOR TO TKOF FROM 2W5, MD.

Narrative: AFTER LNDG AT MARYLAND ARPT (2W5) AT XA52, I CLOSED OUT MY DVFR FLT PLAN WITH ELKINS FSS AND REFILED FOR AN XC30 ESTIMATED TIME OF DEP. AT APPROX XC30, I STARTED THE ENG AND ATTEMPTED TO CONTACT POTOMAC APCH/DEP CTL FOR AN ASSIGNED XPONDER CODE FOR EXITING THE ADIZ. I WAS UNSUCCESSFUL IN MY ATTEMPT BUT, SINCE I HAD BEEN ASSIGNED A CODE WHILE AIRBORNE ON THE INBOUND FLT, I ASSUMED THE PROCESS WOULD BE THE SAME IN REVERSE FOR MY DEP. I WAS AWARE THAT CODES WERE REQUIRED BY TELEPHONE ASSIGNMENT FOR THE SO-CALLED 'DC3' BUT, SINCE 2W5 IS NOT ONE OF THOSE 3 ARPTS, I ASSUMED THE CODE COULD BE PICKED UP ONCE AIRBORNE, JUST AS CLRNCS FROM UNTOWERED FIELDS FREQUENTLY ARE. I WAS UNAWARE OF ANY REQUIREMENT TO OBTAIN A XPONDER CODE AND CONTACT FREQ, ON THE GND, AT THIS ARPT, PRIOR TO TKOF. SUBSEQUENTLY, I TOOK OFF AT APPROX XC40, TURNING WITHIN 2 NM OF THE ARPT, SO THAT I WOULD REMAIN IN THE IMMEDIATE VICINITY WHILE CONTACTING POTOMAC DEP. I WAS NEARLY OVERHEAD THE ARPT WHEN CONTACT WAS ESTABLISHED AND POTOMAC ADVISED ME TO LAND IMMEDIATELY AND OBTAIN A CODE. I DID AS INSTRUCTED, LNDG WITHIN 1 MIN OF BEING SO INSTRUCTED. AFTER LNDG, I WENT TO THE FBO OFFICE, WHERE I FOUND THE CORRECT PHONE NUMBER FOR THE TRACON. I CALLED, AND MY ERROR WAS ACKNOWLEDGED BY AN UNIDENTED FEMALE PERSON, WHO GAVE ME A XPONDER CODE AND FREQ 118.95, AND SHE TOLD ME THAT WAS ALL I NEEDED. I THEN RETURNED TO MY PLANE AND STRAPPED IN. AS I WAS DOING THAT, AN UNIDENTED GENTLEMAN WALKED OUT OF THE FBO OFFICE, CELL PHONE IN HAND, AND HANDED IT TO ME. THE CALLER WAS FROM UNITED STATES CUSTOMS, AND WHEN I TOLD HIM WHAT HAD HAPPENED, AND THAT I HAD NOW BEEN GIVEN A CODE AND FREQ, HE SAID THAT I WAS GOOD TO GO. AFTER TAKING OFF, AND CONTACTING POTOMAC DEP CTL, I WAS TOLD TO CALL ATC REGARDING A POSSIBLE PLT FLT VIOLATION, UPON LNDG AT MY DEST. I SUBSEQUENTLY LANDED, CALLED FSS TO CLOSE MY FLT PLAN, AND THEN CALLED THE NUMBER GIVEN. I SPOKE TO A GENTLEMAN WHO ASKED ME A FEW QUESTIONS REGARDING THE INCIDENT, AND WHO THEN INFORMED ME THAT I WOULD PROBABLY BE HEARING FROM FLT STANDARDS AT SOME FUTURE TIME. HE ALSO SUGGESTED THAT I FILE THIS NASA RPT. SINCE I HAD NEVER FLOWN INTO THE WASHINGTON, DC, ADIZ BEFORE, I HAD ATTEMPTED TO RESEARCH THE ENTIRE FLT VERY CAREFULLY PRIOR TO INITIAL TKOF, AND I TRULY BELIEVED THAT I WAS SATISFYING ALL REQUIREMENTS FOR THE FLT. I REGRET MY ERROR. I HAVE CERTAINLY LEARNED FROM THIS EXPERIENCE, AND I WILL NOT MAKE SUCH AN ERROR AGAIN!

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.