Stuck microphone obscures real cause of loss of radio contact, radio communication problem.

Attributes
ACN	284837
Time
Date	199410
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bed
State Reference	MA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bed
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise other cruise other
Route In Use	enroute : direct
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 35 flight time total : 450
ASRS Report	284837
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

Shortly after takeoff I noticed that I was not hearing anything on my radios. I tried the second communication and switched all possible switches on the automatic panel. I also tried to receive ATIS from 2 different airports. We did some sightseeing while I tried to sort things out. After about an hour we returned to the field. I remained clear of all restr space, class B and C space, etc. Approximately 8 mi out of hanscom I called them on my hand held transceiver and landed without incident. After landing I was asked to call the tower and was told that I had a stuck microphone and was interfering with their communications for 45 mins after takeoff. While trying ATIS I also interfaced with that frequency. Better training on radio communications could have prevented this. If your radios aren't working -- turn them off. This won't help you but it will prevent you from interfering with others. Look for a common denominator -- it is very unusual for 2 radios to fail while navs continue to function.

Original NASA ASRS Text

Title: STUCK MIKE OBSCURES REAL CAUSE OF LOSS OF RADIO CONTACT, RADIO COM PROB.

Narrative: SHORTLY AFTER TKOF I NOTICED THAT I WAS NOT HEARING ANYTHING ON MY RADIOS. I TRIED THE SECOND COM AND SWITCHED ALL POSSIBLE SWITCHES ON THE AUTO PANEL. I ALSO TRIED TO RECEIVE ATIS FROM 2 DIFFERENT ARPTS. WE DID SOME SIGHTSEEING WHILE I TRIED TO SORT THINGS OUT. AFTER ABOUT AN HR WE RETURNED TO THE FIELD. I REMAINED CLR OF ALL RESTR SPACE, CLASS B AND C SPACE, ETC. APPROX 8 MI OUT OF HANSCOM I CALLED THEM ON MY HAND HELD TRANSCEIVER AND LANDED WITHOUT INCIDENT. AFTER LNDG I WAS ASKED TO CALL THE TWR AND WAS TOLD THAT I HAD A STUCK MIKE AND WAS INTERFERING WITH THEIR COMS FOR 45 MINS AFTER TKOF. WHILE TRYING ATIS I ALSO INTERFACED WITH THAT FREQ. BETTER TRAINING ON RADIO COMS COULD HAVE PREVENTED THIS. IF YOUR RADIOS AREN'T WORKING -- TURN THEM OFF. THIS WON'T HELP YOU BUT IT WILL PREVENT YOU FROM INTERFERING WITH OTHERS. LOOK FOR A COMMON DENOMINATOR -- IT IS VERY UNUSUAL FOR 2 RADIOS TO FAIL WHILE NAVS CONTINUE TO FUNCTION.

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.