Stuck microphone creates points of interest for pilot and controller alike.

Attributes
ACN	231929
Time
Date	199301
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lgb
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : lgb
Operator	general aviation : instructional
Make Model Name	Small Aircraft, High Wing, 1 Eng, Retractable Gear
Flight Phase	climbout : takeoff cruise other landing other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial
Experience	flight time last 90 days : 50 flight time total : 1450 flight time type : 40
ASRS Report	231929
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	aircraft equipment problem : less severe non adherence : published procedure non adherence : far other anomaly other other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing my aircraft to the active runway at lgb, all taxi and runup procedures were fine until I noticed I could not hear the tower controller on my speaker and was wearing a headset. I could have had a dead radio or speaker when, in fact, I had a stuck microphone on the control wheel. I eventually got the microphone switch disengaged and elected to depart not thinking about whether or not the problem would arise again. After departing lgb, I headed up towards the bur arsa and tried calling them (approach) for advisories and eventually got a stuck microphone again. At that time, I knew I was in trouble and without tying up the frequencys, elected to turn off my radios. I made a 180 degree turn and returned back to lgb, and called both the tower and bur approach controllers to inform them of my situation and that I was on the ground. I also squawked the radio failure code 7600 on my transponder to inform controllers of my situation. No other incidents took place this flight. I have received instruction by the rental agency that I fly with on emergency procedures. I have also been counseled on not using profanity when having radio problems. Lgb tower stated I had a stuck microphone for over 4 mins. Aircraft was an small aircraft based at FBO in lgb.

Original NASA ASRS Text

Title: STUCK MIKE CREATES POINTS OF INTEREST FOR PLT AND CTLR ALIKE.

Narrative: WHILE TAXIING MY ACFT TO THE ACTIVE RWY AT LGB, ALL TAXI AND RUNUP PROCS WERE FINE UNTIL I NOTICED I COULD NOT HEAR THE TWR CTLR ON MY SPEAKER AND WAS WEARING A HEADSET. I COULD HAVE HAD A DEAD RADIO OR SPEAKER WHEN, IN FACT, I HAD A STUCK MIKE ON THE CTL WHEEL. I EVENTUALLY GOT THE MIKE SWITCH DISENGAGED AND ELECTED TO DEPART NOT THINKING ABOUT WHETHER OR NOT THE PROB WOULD ARISE AGAIN. AFTER DEPARTING LGB, I HEADED UP TOWARDS THE BUR ARSA AND TRIED CALLING THEM (APCH) FOR ADVISORIES AND EVENTUALLY GOT A STUCK MIKE AGAIN. AT THAT TIME, I KNEW I WAS IN TROUBLE AND WITHOUT TYING UP THE FREQS, ELECTED TO TURN OFF MY RADIOS. I MADE A 180 DEG TURN AND RETURNED BACK TO LGB, AND CALLED BOTH THE TWR AND BUR APCH CTLRS TO INFORM THEM OF MY SIT AND THAT I WAS ON THE GND. I ALSO SQUAWKED THE RADIO FAILURE CODE 7600 ON MY XPONDER TO INFORM CTLRS OF MY SIT. NO OTHER INCIDENTS TOOK PLACE THIS FLT. I HAVE RECEIVED INSTRUCTION BY THE RENTAL AGENCY THAT I FLY WITH ON EMER PROCS. I HAVE ALSO BEEN COUNSELED ON NOT USING PROFANITY WHEN HAVING RADIO PROBS. LGB TWR STATED I HAD A STUCK MIKE FOR OVER 4 MINS. ACFT WAS AN SMA BASED AT FBO IN LGB.

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.