|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1801 To 2400|
|Locale Reference||atc facility : air|
|Altitude||msl bound lower : 35000|
msl bound upper : 35000
|Controlling Facilities||artcc : zid|
|Operator||general aviation : corporate|
|Make Model Name||Light Transport, Low Wing, 2 Turboprop Eng|
|Flight Phase||cruise other|
|Route In Use||enroute airway : j80|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : cfi|
pilot : atp
|Experience||flight time last 90 days : 50|
flight time total : 8500
flight time type : 2000
|Function||flight crew : first officer|
|Qualification||pilot : instrument|
pilot : commercial
|Anomaly||aircraft equipment problem : critical|
other anomaly other
|Independent Detector||other flight crewa|
|Resolutory Action||controller : issued new clearance|
flight crew : declared emergency
Cruising at FL350 we received a frequency change, changing from ZOB to ZID, as happens on occasion, it was the wrong frequency. At precisely on contact with the new, wrong frequency, we had an engine fail. The copilot working the radios went back to the last frequency set and unchanged in the standby position and the controller on this frequency. Didn't know who we were, where we were our altitude, etc. This event effectively put my copilot to work dealing with communications which left the aircraft to me. Following single engine procedures the aircraft was unable to maintain altitude. I was forced to squawk 7700. Communications re-established the aircraft was now at FL330 the controller cleared us to 11000' further to 4000', frequency change to cmh adp we requested equipment standing by. Frequency change to the tower, 'cleared to land.' after communication was regained all was like clock work. The controller was very helpful in pointing out closest airport, lower altitude and handoffs. Frequency switching problems are not uncommon, but this untimely communication problem coupled with an engine problem left me with immediate communication requirements and difficulty to find someone to talk to.
Original NASA ASRS Text
Title: CORP LTT ENGINE FAILURE UNABLE TO MAINTAIN ALT. EMERGENCY DECLARED.
Narrative: CRUISING AT FL350 WE RECEIVED A FREQ CHANGE, CHANGING FROM ZOB TO ZID, AS HAPPENS ON OCCASION, IT WAS THE WRONG FREQ. AT PRECISELY ON CONTACT WITH THE NEW, WRONG FREQ, WE HAD AN ENG FAIL. THE COPLT WORKING THE RADIOS WENT BACK TO THE LAST FREQ SET AND UNCHANGED IN THE STANDBY POS AND THE CTLR ON THIS FREQ. DIDN'T KNOW WHO WE WERE, WHERE WE WERE OUR ALT, ETC. THIS EVENT EFFECTIVELY PUT MY COPLT TO WORK DEALING WITH COMS WHICH LEFT THE ACFT TO ME. FOLLOWING SINGLE ENG PROCS THE ACFT WAS UNABLE TO MAINTAIN ALT. I WAS FORCED TO SQUAWK 7700. COMS RE-ESTABLISHED THE ACFT WAS NOW AT FL330 THE CTLR CLRED US TO 11000' FURTHER TO 4000', FREQ CHANGE TO CMH ADP WE REQUESTED EQUIP STANDING BY. FREQ CHANGE TO THE TWR, 'CLRED TO LAND.' AFTER COM WAS REGAINED ALL WAS LIKE CLOCK WORK. THE CTLR WAS VERY HELPFUL IN POINTING OUT CLOSEST ARPT, LOWER ALT AND HDOFS. FREQ SWITCHING PROBS ARE NOT UNCOMMON, BUT THIS UNTIMELY COM PROB COUPLED WITH AN ENG PROB LEFT ME WITH IMMEDIATE COM REQUIREMENTS AND DIFFICULTY TO FIND SOMEONE TO TALK TO.
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.