Narrative:

I lost transmit capability on both radios. I was on flight following with ZOA (128.7). ZOA made 4 attempts to alert me of the close proximity traffic. On all 4 occasions I pressed the yoke push-to-transmit button and answered that I had the traffic in sight, it was a single engine, retractable gear, piper, and there was no conflict problem. After the 4TH call from ZOA and my attempts to respond, I realized that I had lost transmit capability on both radios. However, I could still receive and hear ZOA clearly on both radios. I made the following decisions: 1) did a 180 degree turn and headed back nwbound towards salinas airport (sns) for an emergency landing. I had plenty of fuel aboard and the engine and all other system were working properly. I descended from 5500 ft MSL to 4500 ft MSL. 2) squawked code 7600 so ZOA would know I had lost communications with them. Smart moves. ZOA immediately called recognizing the 7600 code. ZOA correctly determined that I could hear them and requested that I respond yes or no via the identify feature on the transponder. By using the transponder identify for yes and doing nothing for no, ZOA determined that I was at 4500 ft MSL and had turned around and was heading back towards salinas airport for landing. ZOA then had me return to my assigned squawk code of XXXX. Using the identify feature on the transponder to respond to ZOA, ZOA took excellent care of me by asking yes/no questions and: alerted monterey approach of my situation, requested monterey approach to arrange for my landing at salinas, kept me informed of my progress and ATC actions on my behalf, and advised me that salinas airport had been alerted and was anticipating my arrival and landing. At the appropriate time, ZOA advised me to monitor monterey approach (133.0). When monterey approach called me, I responded with a transponder identify. Monterey approach advised me when to monitor salinas tower (119.4). When I arrived at salinas airport, the tower immediately called to let me know I was cleared for landing on runway 26. I landed without incident. After landing at salinas, I telephoned my home base airport, san carlos, ca (sql), and advised them of my problem. The controller at san carlos tower agreed to accept my arrival using a battery operated hand held transceiver. Coordinating with the salinas tower, I subsequently departed the salinas airport and flew to san carlos airport, using a hand held receiver for communications with san carlos tower. I landed at san carlos airport without further incident. At FAA wings air safety seminars I have heard instructors talk about how ATC bends over backwards to assist pilots in trouble. This was the first incident in 828 hours of flying where I had what I considered to be an in-flight emergency requiring ATC help. Wow. The system really does work. My thanks and praises for the way ATC took care of me. All of the controllers really did a fantastic job to ensure my landing safely at salinas. The trouble turned out to be an electronic failure in the 17 yr old intercom. The yoke push button-to-transmit feature which is incorporated in intercom and supports the headset mikes had failed. It is not repairable. I now have to install a new intercom in the airplane.

Google
 

Original NASA ASRS Text

Title: ATC PROVIDES EXCELLENT SVC TO ACFT WITH A XMITTER FAILURE.

Narrative: I LOST XMIT CAPABILITY ON BOTH RADIOS. I WAS ON FLT FOLLOWING WITH ZOA (128.7). ZOA MADE 4 ATTEMPTS TO ALERT ME OF THE CLOSE PROX TFC. ON ALL 4 OCCASIONS I PRESSED THE YOKE PUSH-TO-XMIT BUTTON AND ANSWERED THAT I HAD THE TFC IN SIGHT, IT WAS A SINGLE ENG, RETRACTABLE GEAR, PIPER, AND THERE WAS NO CONFLICT PROB. AFTER THE 4TH CALL FROM ZOA AND MY ATTEMPTS TO RESPOND, I REALIZED THAT I HAD LOST XMIT CAPABILITY ON BOTH RADIOS. HOWEVER, I COULD STILL RECEIVE AND HEAR ZOA CLRLY ON BOTH RADIOS. I MADE THE FOLLOWING DECISIONS: 1) DID A 180 DEG TURN AND HEADED BACK NWBOUND TOWARDS SALINAS ARPT (SNS) FOR AN EMER LNDG. I HAD PLENTY OF FUEL ABOARD AND THE ENG AND ALL OTHER SYS WERE WORKING PROPERLY. I DSNDED FROM 5500 FT MSL TO 4500 FT MSL. 2) SQUAWKED CODE 7600 SO ZOA WOULD KNOW I HAD LOST COMS WITH THEM. SMART MOVES. ZOA IMMEDIATELY CALLED RECOGNIZING THE 7600 CODE. ZOA CORRECTLY DETERMINED THAT I COULD HEAR THEM AND REQUESTED THAT I RESPOND YES OR NO VIA THE IDENT FEATURE ON THE XPONDER. BY USING THE XPONDER IDENT FOR YES AND DOING NOTHING FOR NO, ZOA DETERMINED THAT I WAS AT 4500 FT MSL AND HAD TURNED AROUND AND WAS HEADING BACK TOWARDS SALINAS ARPT FOR LNDG. ZOA THEN HAD ME RETURN TO MY ASSIGNED SQUAWK CODE OF XXXX. USING THE IDENT FEATURE ON THE XPONDER TO RESPOND TO ZOA, ZOA TOOK EXCELLENT CARE OF ME BY ASKING YES/NO QUESTIONS AND: ALERTED MONTEREY APCH OF MY SIT, REQUESTED MONTEREY APCH TO ARRANGE FOR MY LNDG AT SALINAS, KEPT ME INFORMED OF MY PROGRESS AND ATC ACTIONS ON MY BEHALF, AND ADVISED ME THAT SALINAS ARPT HAD BEEN ALERTED AND WAS ANTICIPATING MY ARR AND LNDG. AT THE APPROPRIATE TIME, ZOA ADVISED ME TO MONITOR MONTEREY APCH (133.0). WHEN MONTEREY APCH CALLED ME, I RESPONDED WITH A XPONDER IDENT. MONTEREY APCH ADVISED ME WHEN TO MONITOR SALINAS TWR (119.4). WHEN I ARRIVED AT SALINAS ARPT, THE TWR IMMEDIATELY CALLED TO LET ME KNOW I WAS CLRED FOR LNDG ON RWY 26. I LANDED WITHOUT INCIDENT. AFTER LNDG AT SALINAS, I TELEPHONED MY HOME BASE ARPT, SAN CARLOS, CA (SQL), AND ADVISED THEM OF MY PROB. THE CTLR AT SAN CARLOS TWR AGREED TO ACCEPT MY ARR USING A BATTERY OPERATED HAND HELD TRANSCEIVER. COORDINATING WITH THE SALINAS TWR, I SUBSEQUENTLY DEPARTED THE SALINAS ARPT AND FLEW TO SAN CARLOS ARPT, USING A HAND HELD RECEIVER FOR COMS WITH SAN CARLOS TWR. I LANDED AT SAN CARLOS ARPT WITHOUT FURTHER INCIDENT. AT FAA WINGS AIR SAFETY SEMINARS I HAVE HEARD INSTRUCTORS TALK ABOUT HOW ATC BENDS OVER BACKWARDS TO ASSIST PLTS IN TROUBLE. THIS WAS THE FIRST INCIDENT IN 828 HRS OF FLYING WHERE I HAD WHAT I CONSIDERED TO BE AN INFLT EMER REQUIRING ATC HELP. WOW. THE SYS REALLY DOES WORK. MY THANKS AND PRAISES FOR THE WAY ATC TOOK CARE OF ME. ALL OF THE CTLRS REALLY DID A FANTASTIC JOB TO ENSURE MY LNDG SAFELY AT SALINAS. THE TROUBLE TURNED OUT TO BE AN ELECTRONIC FAILURE IN THE 17 YR OLD INTERCOM. THE YOKE PUSH BUTTON-TO-XMIT FEATURE WHICH IS INCORPORATED IN INTERCOM AND SUPPORTS THE HEADSET MIKES HAD FAILED. IT IS NOT REPAIRABLE. I NOW HAVE TO INSTALL A NEW INTERCOM IN THE AIRPLANE.

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.