Narrative:

On may/thu/97, I was giving instruction in a C172 with a primary, pre-solo student. While on the ground, I was showing the student the use of the transponder. In addition to the normal VFR code (1200), I set the transponder to 7500, 7600, and 7700 respectively, in order to show the proper emergency codes. After displaying the 7700 code, I became distracted and did not set the transponder back to 1200. The following day, I flew with a different student. While on the ground, I realized the transponder was set to 7700. I then recycled the transponder back to 1200 (VFR). I believe that the transponder was on long enough that it alerted ATC to the code. While in the air, I was called by unicom to check my transponder. Portland ATC had contacted the FBO to determine that I was the aircraft with the 7700 code. I believe that even though I reset the transponder, ATC had already been alerted and the 7700 code remained on their screen. In-flight I contacted portland approach to confirm my transponder code. They informed me that the code was intermittent between 1200 and 7700. Therefore, the initial code of 7700 was enough to remain in the system. The factors that led to this problem were the inability of myself to recognize the 7700 code and change it to 1200 while the transponder had no power. My actions showed improper use of the checklist and poor instruction to my student. Adhering to the checklist and staying alert will prevent this occurring in the future. I am sorry for the inconvenience it caused.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 ACFT ON TRAINING FLT INADVERTENTLY HAD XPONDER CODE 7700 SET AND DIDN'T NOTICE UNTIL APCH CTLR ALERTED HIM VIA UNICOM.

Narrative: ON MAY/THU/97, I WAS GIVING INSTRUCTION IN A C172 WITH A PRIMARY, PRE-SOLO STUDENT. WHILE ON THE GND, I WAS SHOWING THE STUDENT THE USE OF THE XPONDER. IN ADDITION TO THE NORMAL VFR CODE (1200), I SET THE XPONDER TO 7500, 7600, AND 7700 RESPECTIVELY, IN ORDER TO SHOW THE PROPER EMER CODES. AFTER DISPLAYING THE 7700 CODE, I BECAME DISTRACTED AND DID NOT SET THE XPONDER BACK TO 1200. THE FOLLOWING DAY, I FLEW WITH A DIFFERENT STUDENT. WHILE ON THE GND, I REALIZED THE XPONDER WAS SET TO 7700. I THEN RECYCLED THE XPONDER BACK TO 1200 (VFR). I BELIEVE THAT THE XPONDER WAS ON LONG ENOUGH THAT IT ALERTED ATC TO THE CODE. WHILE IN THE AIR, I WAS CALLED BY UNICOM TO CHK MY XPONDER. PORTLAND ATC HAD CONTACTED THE FBO TO DETERMINE THAT I WAS THE ACFT WITH THE 7700 CODE. I BELIEVE THAT EVEN THOUGH I RESET THE XPONDER, ATC HAD ALREADY BEEN ALERTED AND THE 7700 CODE REMAINED ON THEIR SCREEN. INFLT I CONTACTED PORTLAND APCH TO CONFIRM MY XPONDER CODE. THEY INFORMED ME THAT THE CODE WAS INTERMITTENT BTWN 1200 AND 7700. THEREFORE, THE INITIAL CODE OF 7700 WAS ENOUGH TO REMAIN IN THE SYS. THE FACTORS THAT LED TO THIS PROB WERE THE INABILITY OF MYSELF TO RECOGNIZE THE 7700 CODE AND CHANGE IT TO 1200 WHILE THE XPONDER HAD NO PWR. MY ACTIONS SHOWED IMPROPER USE OF THE CHKLIST AND POOR INSTRUCTION TO MY STUDENT. ADHERING TO THE CHKLIST AND STAYING ALERT WILL PREVENT THIS OCCURRING IN THE FUTURE. I AM SORRY FOR THE INCONVENIENCE IT CAUSED.

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.