Instructor with instrument student in a C172 making an instrument approach has a stuck microphone. This creates a problem of less than standard separation for the approach controller.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	403700
Time
Date	199805
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : dhp airport : opf
State Reference	FL
Altitude	msl bound lower : 2000 msl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mia
Operator	general aviation : instructional
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	enroute : on vectors
Flight Plan	None
Person 1
Affiliation	Other
Function	instruction : instructor
Qualification	pilot : instrument pilot : cfi pilot : commercial
Experience	flight time last 90 days : 150 flight time total : 1030 flight time type : 800
ASRS Report	403700
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	aircraft equipment problem : critical conflict : airborne less severe non adherence : required legal separation
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	Pilot Deviation

Narrative:

I was flying back from tmb to opf after practicing NDB approach with my instrument student at tmb. We were vectored back to opf by mia approach so we could practice an ILS approach to a full stop at opf. After receiving a vector, I didn't realize that my microphone was stuck. After about 10 mins, I realized that my microphone had been stuck, and I was so advised by the controller. After landing, I received a phone call from mia approach and I was advised that they had a system failure because of me, and that their minimum separation was violated between 2 aircraft since they couldn't call them. I was also advised that I will be contacted by the FAA in the next few days. I have reported to the school owner and mechanic about the faulty push-to-talk button and it will be fixed before the next flight. I realize that this situation could have caused an accident or incident, and that I should pay more attention, and if the frequency is quiet for too long, check that my microphone is not stuck, and also look for the transmitter light or indicator to verify that we are not transmitting.

Original NASA ASRS Text

Title: INSTRUCTOR WITH INST STUDENT IN A C172 MAKING AN INST APCH HAS A STUCK MIKE. THIS CREATES A PROB OF LTSS FOR THE APCH CTLR.

Narrative: I WAS FLYING BACK FROM TMB TO OPF AFTER PRACTICING NDB APCH WITH MY INST STUDENT AT TMB. WE WERE VECTORED BACK TO OPF BY MIA APCH SO WE COULD PRACTICE AN ILS APCH TO A FULL STOP AT OPF. AFTER RECEIVING A VECTOR, I DIDN'T REALIZE THAT MY MIKE WAS STUCK. AFTER ABOUT 10 MINS, I REALIZED THAT MY MIKE HAD BEEN STUCK, AND I WAS SO ADVISED BY THE CTLR. AFTER LNDG, I RECEIVED A PHONE CALL FROM MIA APCH AND I WAS ADVISED THAT THEY HAD A SYS FAILURE BECAUSE OF ME, AND THAT THEIR MINIMUM SEPARATION WAS VIOLATED BTWN 2 ACFT SINCE THEY COULDN'T CALL THEM. I WAS ALSO ADVISED THAT I WILL BE CONTACTED BY THE FAA IN THE NEXT FEW DAYS. I HAVE RPTED TO THE SCHOOL OWNER AND MECH ABOUT THE FAULTY PUSH-TO-TALK BUTTON AND IT WILL BE FIXED BEFORE THE NEXT FLT. I REALIZE THAT THIS SIT COULD HAVE CAUSED AN ACCIDENT OR INCIDENT, AND THAT I SHOULD PAY MORE ATTN, AND IF THE FREQ IS QUIET FOR TOO LONG, CHK THAT MY MIKE IS NOT STUCK, AND ALSO LOOK FOR THE XMITTER LIGHT OR INDICATOR TO VERIFY THAT WE ARE NOT XMITTING.

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.