Narrative:

It appears that I operated an aircraft using the wrong transponder code. The event occurred within the 30 mi limit of dca requiring a working transponder and below the limits of the washington class B airspace. I flew the aircraft from approximately XA30 to XB50 on aug/xa/97 in the local traffic area at W32 performing practice takeoffs and lndgs. After attending a meeting for 2 hours at the airport, I checked the aircraft before flying again. I found that the transponder was set to code XXXX instead of 1200. I was the last person flying and apparently had flown the aircraft in the traffic pattern with the wrong transponder code. The airport is located 4.5 mi from adw AFB and less than 10 mi from dca. The traffic pattern at W32 is below and not included in the washington class B airspace. The problem was discovered during a careful and complete preflight check for the second flight of the day. Apparently, the first preflight check of the day omitted checking the transponder code even though I was careful to set the transponder to 'altitude' (mode C) before each takeoff and to turn it to 'standby' after each landing. Contributing factors would include limited flight experience in the last 120 days and the transponder not included on the preflight checklist. Corrective actions will include adding the transponder code to the 'before takeoff' checklist for both aircraft that I fly. Also, I will develop the habit of touching the transponder face plate to insure that I read the code displayed. This event demonstrates how easy it is to 'think you are careful' when in fact, an important step was omitted.

Related reports:

Google
 

Original NASA ASRS Text

Title: THE PLT OF AN MO2J DISCOVERED DURING THE SECOND PREFLT OF THE DAY THAT THE FIRST FLT HAD BEEN FLOWN WITH THE WRONG CODE IN THE XPONDER.

Narrative: IT APPEARS THAT I OPERATED AN ACFT USING THE WRONG XPONDER CODE. THE EVENT OCCURRED WITHIN THE 30 MI LIMIT OF DCA REQUIRING A WORKING XPONDER AND BELOW THE LIMITS OF THE WASHINGTON CLASS B AIRSPACE. I FLEW THE ACFT FROM APPROX XA30 TO XB50 ON AUG/XA/97 IN THE LCL TFC AREA AT W32 PERFORMING PRACTICE TKOFS AND LNDGS. AFTER ATTENDING A MEETING FOR 2 HRS AT THE ARPT, I CHKED THE ACFT BEFORE FLYING AGAIN. I FOUND THAT THE XPONDER WAS SET TO CODE XXXX INSTEAD OF 1200. I WAS THE LAST PERSON FLYING AND APPARENTLY HAD FLOWN THE ACFT IN THE TFC PATTERN WITH THE WRONG XPONDER CODE. THE ARPT IS LOCATED 4.5 MI FROM ADW AFB AND LESS THAN 10 MI FROM DCA. THE TFC PATTERN AT W32 IS BELOW AND NOT INCLUDED IN THE WASHINGTON CLASS B AIRSPACE. THE PROB WAS DISCOVERED DURING A CAREFUL AND COMPLETE PREFLT CHK FOR THE SECOND FLT OF THE DAY. APPARENTLY, THE FIRST PREFLT CHK OF THE DAY OMITTED CHKING THE XPONDER CODE EVEN THOUGH I WAS CAREFUL TO SET THE XPONDER TO 'ALT' (MODE C) BEFORE EACH TKOF AND TO TURN IT TO 'STANDBY' AFTER EACH LNDG. CONTRIBUTING FACTORS WOULD INCLUDE LIMITED FLT EXPERIENCE IN THE LAST 120 DAYS AND THE XPONDER NOT INCLUDED ON THE PREFLT CHKLIST. CORRECTIVE ACTIONS WILL INCLUDE ADDING THE XPONDER CODE TO THE 'BEFORE TKOF' CHKLIST FOR BOTH ACFT THAT I FLY. ALSO, I WILL DEVELOP THE HABIT OF TOUCHING THE XPONDER FACE PLATE TO INSURE THAT I READ THE CODE DISPLAYED. THIS EVENT DEMONSTRATES HOW EASY IT IS TO 'THINK YOU ARE CAREFUL' WHEN IN FACT, AN IMPORTANT STEP WAS OMITTED.

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.