Small transport requested to call approach after landing regarding communication problem.

Attributes
ACN	152024
Time
Date	199007
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ccr
State Reference	CA
Altitude	msl bound lower : 4000 msl bound upper : 4000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : suu
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	descent : approach descent other landing other
Route In Use	enroute airway : suu
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 10400 flight time type : 800
ASRS Report	152024
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

On landing at concord, ca, I was asked to call travis approach. When I let them know I was flying small transport, and asked what the problem was, I was asked if I had a communications problem. I answered, 'not that I know of,' and then, 'was something wrong?' all that the controller said was in asking if I had a communications problem. As far as I know I had not had a problem, but the next day when climbing out of ccr and talking to ZOA, they would call me back to confirm that I had received their instructions. I found that my push to talk button on the pilots yoke was starting to malfunction and now is being fixed. Callback conversation with reporter revealed the following: reporter states he was using a boom microphone and apparently the switch on yoke was cutting out. Travis apparently not receiving xmissions but never really stated such. When reporter phoned he spoke with a different controller than he did airborne and situation seemed confused. They simply asked him if he was having communication problems. When ZOA called after he had responded, he became aware of possible problem and switched to hand-held microphone. Filed report just in case.

Original NASA ASRS Text

Title: SMT REQUESTED TO CALL APCH AFTER LNDG REGARDING COM PROBLEM.

Narrative: ON LNDG AT CONCORD, CA, I WAS ASKED TO CALL TRAVIS APCH. WHEN I LET THEM KNOW I WAS FLYING SMT, AND ASKED WHAT THE PROB WAS, I WAS ASKED IF I HAD A COMS PROB. I ANSWERED, 'NOT THAT I KNOW OF,' AND THEN, 'WAS SOMETHING WRONG?' ALL THAT THE CTLR SAID WAS IN ASKING IF I HAD A COMS PROB. AS FAR AS I KNOW I HAD NOT HAD A PROB, BUT THE NEXT DAY WHEN CLBING OUT OF CCR AND TALKING TO ZOA, THEY WOULD CALL ME BACK TO CONFIRM THAT I HAD RECEIVED THEIR INSTRUCTIONS. I FOUND THAT MY PUSH TO TALK BUTTON ON THE PLTS YOKE WAS STARTING TO MALFUNCTION AND NOW IS BEING FIXED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR STATES HE WAS USING A BOOM MIC AND APPARENTLY THE SWITCH ON YOKE WAS CUTTING OUT. TRAVIS APPARENTLY NOT RECEIVING XMISSIONS BUT NEVER REALLY STATED SUCH. WHEN RPTR PHONED HE SPOKE WITH A DIFFERENT CTLR THAN HE DID AIRBORNE AND SITUATION SEEMED CONFUSED. THEY SIMPLY ASKED HIM IF HE WAS HAVING COM PROBLEMS. WHEN ZOA CALLED AFTER HE HAD RESPONDED, HE BECAME AWARE OF POSSIBLE PROB AND SWITCHED TO HAND-HELD MIC. FILED RPT JUST IN CASE.

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.