|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : flo|
|Altitude||msl bound lower : 2200|
msl bound upper : 2200
|Controlling Facilities||tracon : flo|
tower : flo
artcc : zlc
|Operator||general aviation : instructional|
|Make Model Name||Small Aircraft, High Wing, 1 Eng, Fixed Gear|
|Flight Phase||climbout : intermediate altitude|
|Route In Use||enroute : on vectors|
|Function||instruction : instructor|
|Qualification||pilot : cfi|
pilot : commercial
pilot : instrument
|Experience||flight time last 90 days : 250|
flight time total : 850
flight time type : 350
|Function||instruction : trainee|
|Qualification||pilot : student|
|Anomaly||aircraft equipment problem : critical|
other anomaly other
|Independent Detector||other flight crewa|
|Resolutory Action||flight crew : overcame equipment problem|
flight crew : declared emergency
After touch and go runway 9 circle to land following VOR approach at flo, we were turning to 180 degrees and climbing to 2200'. We experienced intense squealing sound on radio frequency 135.25, flo approach, and checked second radio. Same problem, but flo approach did radio check with other aircraft and they did not experience the same problem. We proceeded on further vectors to shoot the ILS runway 9 approach flo. Last vector we received was 360 degrees, maintain 2200'. We were beginning to intercept the inbound course 089 degree. I questioned flo approach about flying through the localizer, but no response on 135.25. We tried 125.10, flo tower, and started to get vectors again for the ILS and the last vector we received was 140 degrees. At that point we didn't receive any further radio xmissions. We proceeded to execute lost communications procedures during IFR flight and started to tune and identify the flo VOR and mao NDB for navigation, but could not identify either. We tried several communication and navigation frequencys, but negative results. We continued on a heading of 140 degrees at 2200', transponder code 7700, 1 min and 7600, 15 mins, radio 121.5. With no navaids, we had to descend to an altitude that would allow us some visibility. Knowing that we had visibility on takeoff under 800' we continued to descend in slow small increments of 100-200' looking for ground contact and referring to VFR charts for obstruction clearance along our approximately route. We checked electrical supply several times according to checklist. We lost fuel gauge indications also. At 1200' we began to make contact and circled to 600' and then proceeded to highway via VFR pilotage. Callback conversation with reporter revealed the following: this aircraft has caused problems before and reporter doesn't think they really have the problem solved yet as it is intermittent. Not certain if problem in radios or in electrical supply as they did not loose all electrical. Confirmed student had just a student pilot license. Aircraft has been in maintenance several times for this problem. No FAA involvement. Verified flight was on IFR flight plan. VFR checked by mistake on form.
Original NASA ASRS Text
Title: GA SMA LOSS OF RADIO COM WHILE IMC. EMERGENCY DECLARED.
Narrative: AFTER TOUCH AND GO RWY 9 CIRCLE TO LAND FOLLOWING VOR APCH AT FLO, WE WERE TURNING TO 180 DEGS AND CLBING TO 2200'. WE EXPERIENCED INTENSE SQUEALING SOUND ON RADIO FREQ 135.25, FLO APCH, AND CHKED SECOND RADIO. SAME PROB, BUT FLO APCH DID RADIO CHK WITH OTHER ACFT AND THEY DID NOT EXPERIENCE THE SAME PROB. WE PROCEEDED ON FURTHER VECTORS TO SHOOT THE ILS RWY 9 APCH FLO. LAST VECTOR WE RECEIVED WAS 360 DEGS, MAINTAIN 2200'. WE WERE BEGINNING TO INTERCEPT THE INBND COURSE 089 DEG. I QUESTIONED FLO APCH ABOUT FLYING THROUGH THE LOC, BUT NO RESPONSE ON 135.25. WE TRIED 125.10, FLO TWR, AND STARTED TO GET VECTORS AGAIN FOR THE ILS AND THE LAST VECTOR WE RECEIVED WAS 140 DEGS. AT THAT POINT WE DIDN'T RECEIVE ANY FURTHER RADIO XMISSIONS. WE PROCEEDED TO EXECUTE LOST COMS PROCS DURING IFR FLT AND STARTED TO TUNE AND IDENT THE FLO VOR AND MAO NDB FOR NAV, BUT COULD NOT IDENT EITHER. WE TRIED SEVERAL COM AND NAV FREQS, BUT NEGATIVE RESULTS. WE CONTINUED ON A HDG OF 140 DEGS AT 2200', XPONDER CODE 7700, 1 MIN AND 7600, 15 MINS, RADIO 121.5. WITH NO NAVAIDS, WE HAD TO DSND TO AN ALT THAT WOULD ALLOW US SOME VISIBILITY. KNOWING THAT WE HAD VISIBILITY ON TKOF UNDER 800' WE CONTINUED TO DSND IN SLOW SMALL INCREMENTS OF 100-200' LOOKING FOR GND CONTACT AND REFERRING TO VFR CHARTS FOR OBSTRUCTION CLRNC ALONG OUR APPROX ROUTE. WE CHKED ELECTRICAL SUPPLY SEVERAL TIMES ACCORDING TO CHKLIST. WE LOST FUEL GAUGE INDICATIONS ALSO. AT 1200' WE BEGAN TO MAKE CONTACT AND CIRCLED TO 600' AND THEN PROCEEDED TO HWY VIA VFR PILOTAGE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: THIS ACFT HAS CAUSED PROBS BEFORE AND RPTR DOESN'T THINK THEY REALLY HAVE THE PROB SOLVED YET AS IT IS INTERMITTENT. NOT CERTAIN IF PROB IN RADIOS OR IN ELECTRICAL SUPPLY AS THEY DID NOT LOOSE ALL ELECTRICAL. CONFIRMED STUDENT HAD JUST A STUDENT PLT LICENSE. ACFT HAS BEEN IN MAINT SEVERAL TIMES FOR THIS PROB. NO FAA INVOLVEMENT. VERIFIED FLT WAS ON IFR FLT PLAN. VFR CHKED BY MISTAKE ON FORM.
Data retrieved from NASA's ASRS site as of August 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.