Narrative:

Called FSS on landline with elkins FSS to request a VFR ADIZ clearance from fdk to gai. We called on the ground for clearance delivery, picked up our code, departed fdk, climbed to 2500 ft MSL, contacted approach control and were told to proceed on course to gai, 'report airport in sight.' proceeding towards gai, reported gai in sight, and frequency change to CTAF approved, we were told to remain on the squawk code until on the ground. At this point we realized the transponder was on 'standby' and immediately turned it to 'altitude.' we landed and were told by CTAF to contact the TRACON. They informed us that we were 2 mi inside the ADIZ before we activated the beacon. Contributing factors included my nervousness in successfully completing my instrument check ride (an FAA examiner was my right seat copilot) and overreacting to following the departure instructions given by the examiner. Corrective actions include better CRM. I should have engaged my examiner in the checklist process and asked him to verify that the beacon was on 'altitude.' I have modified my checklist to include 'check transponder squawking altitude' twice so that I have 2 opportunities to confirm that it is transmitting the code.

Google
 

Original NASA ASRS Text

Title: WHILE INBOUND TO GAI IN THE DC ADIZ, PLT AND FAA EXAMINER ABOARD PA28 BOTH FAIL TO NOTE THAT, ALTHOUGH THE PROPER DISCRETE CODE WAS SELECTED, THE XPONDER WAS IN THE STANDBY MODE RATHER THAN ALT AS REQUIRED.

Narrative: CALLED FSS ON LANDLINE WITH ELKINS FSS TO REQUEST A VFR ADIZ CLRNC FROM FDK TO GAI. WE CALLED ON THE GND FOR CLRNC DELIVERY, PICKED UP OUR CODE, DEPARTED FDK, CLBED TO 2500 FT MSL, CONTACTED APCH CTL AND WERE TOLD TO PROCEED ON COURSE TO GAI, 'RPT ARPT IN SIGHT.' PROCEEDING TOWARDS GAI, RPTED GAI IN SIGHT, AND FREQ CHANGE TO CTAF APPROVED, WE WERE TOLD TO REMAIN ON THE SQUAWK CODE UNTIL ON THE GND. AT THIS POINT WE REALIZED THE XPONDER WAS ON 'STANDBY' AND IMMEDIATELY TURNED IT TO 'ALT.' WE LANDED AND WERE TOLD BY CTAF TO CONTACT THE TRACON. THEY INFORMED US THAT WE WERE 2 MI INSIDE THE ADIZ BEFORE WE ACTIVATED THE BEACON. CONTRIBUTING FACTORS INCLUDED MY NERVOUSNESS IN SUCCESSFULLY COMPLETING MY INST CHK RIDE (AN FAA EXAMINER WAS MY R SEAT COPLT) AND OVERREACTING TO FOLLOWING THE DEP INSTRUCTIONS GIVEN BY THE EXAMINER. CORRECTIVE ACTIONS INCLUDE BETTER CRM. I SHOULD HAVE ENGAGED MY EXAMINER IN THE CHKLIST PROCESS AND ASKED HIM TO VERIFY THAT THE BEACON WAS ON 'ALT.' I HAVE MODIFIED MY CHKLIST TO INCLUDE 'CHK XPONDER SQUAWKING ALT' TWICE SO THAT I HAVE 2 OPPORTUNITIES TO CONFIRM THAT IT IS XMITTING THE CODE.

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.