Narrative:

I received the following clearance from smo ground: fly runway heading; upon reaching the lax VORTAC 315 degree radial right turn to a heading of 270 degree radar vector to smo VOR. I read back the departure procedure and took 5 mins to set up my avionics for the departure procedure and to explain it to my student so that he could fly. He punched in the transponder code (I do not remember the exact code; but it did end with a zero).just after takeoff smo tower advised that he was not receiving my squawk. The gtx-327 transponder is designed to automatically switch from standby mode to altitude mode after reaching 30 KIAS. I reached down and hit the 'altitude' button on the transponder and asked the tower for confirmation of the code received. His reply was negative; but he handed me over to socal departure anyway. I told my student to continue flying the departure procedure while I handled the radios and troubleshot the transponder. Immediately after checking in with socal and fixing the transponder I was told to turn to heading 270 degrees and expedite for traffic. I took the controls and turned to 270 degrees. I looked over at the HSI and saw that we had just flown through the course. Once situated so cal gave me a number to call for a possible pilot deviation. Not knowing what deviation occurred; I asked the reason. He informed me that a loss of separation occurred between me and a B737 due to my overshooting the 315 degree radial from lax. The distraction due to the transponder issue is what led to the deviation. I will explain what happened with the transponder. Going from a code of 1200 to XXX my student assumed that he only needed to punch in the first 3 digits (the last already being zero). As a result; the gtx-327 displayed all 4 digits of the correct code; yet the unit was holding for the last digit to be entered. Even after I hit the 'altitude' button; it was still on standby waiting for the fourth digit to be entered. Not until I tried to re-enter the code did I realize the problem and then was able to solve it. The distraction with the transponder could have been prevented had we programmed it correctly before takeoff. More vigilance on my part could have caught the mistake. To reduce the confusion with the transponder display; the gtx-327 could be modified so that the 4 digits on the display disappear with the initiation of punching in a new code. As it is; the digits just stay on the display until you type over each individual number. Another possibility is for the gtx-327 to function normally with the old code until a complete new code is entered; as opposed to freezing up while waiting for a new code to be entered completely. This would have at least put us in radar contact with a 1200 code; as opposed to flying in IMC without radar contact. If that was a function; tower and socal could have caught the deviation before it became a safety of flight issue. Finally; there is a lot going on in the cockpit during a lesson; let alone a lesson in lax airspace on an actual IFR flight. The tower controller was only trying to help by making sure he was able to establish radar contact. I do understand the importance of radar contact in this environment and I am not projecting the blame for the incident onto the controller. However; considering the difficulty of the departure procedure; knowing that I was giving a lesson (this I mentioned to him on the ground); and the proximity to another aircraft that just departed lax; it would have been better if the tower controller had not brought my attention to the transponder issue and then given me a frequency change before we were given enough time to be out of harm's way. If the concern was that I might get too close to the other traffic; the controller should have confirmed my altitude and position verbally; not the functioning of my transponder.

Google
 

Original NASA ASRS Text

Title: SR-22 INSTRUCTOR AND STUDENT DEPARTING SMO EXPERIENCE LOSS OF SEPARATION WITH A B737 WHEN THEY BECOME PREOCCUPIED WITH AN EQUIP PROB AND MISS A TURN ON DEP.

Narrative: I RECEIVED THE FOLLOWING CLRNC FROM SMO GND: FLY RWY HDG; UPON REACHING THE LAX VORTAC 315 DEG RADIAL R TURN TO A HDG OF 270 DEG RADAR VECTOR TO SMO VOR. I READ BACK THE DEP PROC AND TOOK 5 MINS TO SET UP MY AVIONICS FOR THE DEP PROC AND TO EXPLAIN IT TO MY STUDENT SO THAT HE COULD FLY. HE PUNCHED IN THE XPONDER CODE (I DO NOT REMEMBER THE EXACT CODE; BUT IT DID END WITH A ZERO).JUST AFTER TKOF SMO TWR ADVISED THAT HE WAS NOT RECEIVING MY SQUAWK. THE GTX-327 XPONDER IS DESIGNED TO AUTOMATICALLY SWITCH FROM STANDBY MODE TO ALT MODE AFTER REACHING 30 KIAS. I REACHED DOWN AND HIT THE 'ALT' BUTTON ON THE XPONDER AND ASKED THE TWR FOR CONFIRMATION OF THE CODE RECEIVED. HIS REPLY WAS NEGATIVE; BUT HE HANDED ME OVER TO SOCAL DEP ANYWAY. I TOLD MY STUDENT TO CONTINUE FLYING THE DEP PROC WHILE I HANDLED THE RADIOS AND TROUBLESHOT THE XPONDER. IMMEDIATELY AFTER CHKING IN WITH SOCAL AND FIXING THE XPONDER I WAS TOLD TO TURN TO HDG 270 DEGS AND EXPEDITE FOR TFC. I TOOK THE CTLS AND TURNED TO 270 DEGS. I LOOKED OVER AT THE HSI AND SAW THAT WE HAD JUST FLOWN THROUGH THE COURSE. ONCE SITUATED SO CAL GAVE ME A NUMBER TO CALL FOR A POSSIBLE PLTDEV. NOT KNOWING WHAT DEV OCCURRED; I ASKED THE REASON. HE INFORMED ME THAT A LOSS OF SEPARATION OCCURRED BTWN ME AND A B737 DUE TO MY OVERSHOOTING THE 315 DEG RADIAL FROM LAX. THE DISTR DUE TO THE XPONDER ISSUE IS WHAT LED TO THE DEV. I WILL EXPLAIN WHAT HAPPENED WITH THE XPONDER. GOING FROM A CODE OF 1200 TO XXX MY STUDENT ASSUMED THAT HE ONLY NEEDED TO PUNCH IN THE FIRST 3 DIGITS (THE LAST ALREADY BEING ZERO). AS A RESULT; THE GTX-327 DISPLAYED ALL 4 DIGITS OF THE CORRECT CODE; YET THE UNIT WAS HOLDING FOR THE LAST DIGIT TO BE ENTERED. EVEN AFTER I HIT THE 'ALT' BUTTON; IT WAS STILL ON STANDBY WAITING FOR THE FOURTH DIGIT TO BE ENTERED. NOT UNTIL I TRIED TO RE-ENTER THE CODE DID I REALIZE THE PROB AND THEN WAS ABLE TO SOLVE IT. THE DISTR WITH THE XPONDER COULD HAVE BEEN PREVENTED HAD WE PROGRAMMED IT CORRECTLY BEFORE TKOF. MORE VIGILANCE ON MY PART COULD HAVE CAUGHT THE MISTAKE. TO REDUCE THE CONFUSION WITH THE XPONDER DISPLAY; THE GTX-327 COULD BE MODIFIED SO THAT THE 4 DIGITS ON THE DISPLAY DISAPPEAR WITH THE INITIATION OF PUNCHING IN A NEW CODE. AS IT IS; THE DIGITS JUST STAY ON THE DISPLAY UNTIL YOU TYPE OVER EACH INDIVIDUAL NUMBER. ANOTHER POSSIBILITY IS FOR THE GTX-327 TO FUNCTION NORMALLY WITH THE OLD CODE UNTIL A COMPLETE NEW CODE IS ENTERED; AS OPPOSED TO FREEZING UP WHILE WAITING FOR A NEW CODE TO BE ENTERED COMPLETELY. THIS WOULD HAVE AT LEAST PUT US IN RADAR CONTACT WITH A 1200 CODE; AS OPPOSED TO FLYING IN IMC WITHOUT RADAR CONTACT. IF THAT WAS A FUNCTION; TWR AND SOCAL COULD HAVE CAUGHT THE DEV BEFORE IT BECAME A SAFETY OF FLT ISSUE. FINALLY; THERE IS A LOT GOING ON IN THE COCKPIT DURING A LESSON; LET ALONE A LESSON IN LAX AIRSPACE ON AN ACTUAL IFR FLT. THE TWR CTLR WAS ONLY TRYING TO HELP BY MAKING SURE HE WAS ABLE TO ESTABLISH RADAR CONTACT. I DO UNDERSTAND THE IMPORTANCE OF RADAR CONTACT IN THIS ENVIRONMENT AND I AM NOT PROJECTING THE BLAME FOR THE INCIDENT ONTO THE CTLR. HOWEVER; CONSIDERING THE DIFFICULTY OF THE DEP PROC; KNOWING THAT I WAS GIVING A LESSON (THIS I MENTIONED TO HIM ON THE GND); AND THE PROX TO ANOTHER ACFT THAT JUST DEPARTED LAX; IT WOULD HAVE BEEN BETTER IF THE TWR CTLR HAD NOT BROUGHT MY ATTN TO THE XPONDER ISSUE AND THEN GIVEN ME A FREQ CHANGE BEFORE WE WERE GIVEN ENOUGH TIME TO BE OUT OF HARM'S WAY. IF THE CONCERN WAS THAT I MIGHT GET TOO CLOSE TO THE OTHER TFC; THE CTLR SHOULD HAVE CONFIRMED MY ALT AND POS VERBALLY; NOT THE FUNCTIONING OF MY XPONDER.

Data retrieved from NASA's ASRS site as of January 2009 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.