37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 879142 |
Time | |
Date | 201003 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Engine |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 1980 Flight Crew Type 535 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
On ILS descending out of 4;000 ft MSL on an assigned heading. Engine began to run rough and started 'missing.' pre-landing checklist completed with no improvement. Received clearance for descent to 3;600 ft until established on approach course. Engine roughness increased in power reduction for descent. Rechecked fuel valve on both; fuel shutoff in 'on' position; mixture rich; and magneto's isolated with no appreciable change. Pilot initially requested 180 degree turn back to a nearby airport. Approximately one second later; due to increase in roughness; pilot advised change of plan and pilot communicated to ATC that we would accept the ILS approach. After ATC query; pilot advised rough running engine. Pilot requested information on nearest airports in case we couldn't make runway. (Due to distance from my destination; pilot hoped to circle down over any airfield if total loss of power occurred.) ATC advised of two other airports but none closer than the destination. Pilot advised would continue ILS approach. Change of throttle position with descent seemed to change roughness; sometimes better; sometimes worse. ATC advised change to advisory frequency. Pilot requested to stay with ATC. ATC advised that pilot would need to declare an emergency if he wanted to stay on center. Due to pilot's concern that if engine failure became imminent and aircraft did not reach runway; rescue services could arrive faster if he was able to provide a detailed location after descending from cloud bases to center. Pilot declared emergency. At that time; it was not known by pilot if unicom was monitored at the destination. Pilot declared emergency but declined emergency services on the ground with ATC. ATC suggested that pilot monitor center and contact CTAF to monitor other inbound traffic. Ceiling was reported at 400 overcast on AWOS. Pilot raised unicom on the CTAF frequency; advised of location and asked if emergency services were located on the field. Unicom advised no and asked if we would like them to be called. Pilot advised 'not at this time.' unicom requested nature of problem and pilot asked unicom to 'standby' as he was approaching minimums. Aircraft was landed successfully with partial power. Center was advised that we would like to cancel IFR and that we were safely on the ground. No further assistance was needed.
Original NASA ASRS Text
Title: A C172 pilot declared an emergency after his engine began running rough. He was able to make his destination while descending with partial power.
Narrative: On ILS descending out of 4;000 FT MSL on an assigned heading. Engine began to run rough and started 'missing.' Pre-landing checklist completed with no improvement. Received clearance for descent to 3;600 FT until established on approach course. Engine roughness increased in power reduction for descent. Rechecked fuel valve on both; fuel shutoff in 'ON' position; mixture RICH; and Magneto's isolated with no appreciable change. Pilot initially requested 180 degree turn back to a nearby airport. Approximately one second later; due to increase in roughness; pilot advised change of plan and pilot communicated to ATC that we would accept the ILS approach. After ATC query; pilot advised rough running engine. Pilot requested information on nearest airports in case we couldn't make runway. (Due to distance from my destination; Pilot hoped to circle down over any airfield if total loss of power occurred.) ATC advised of two other airports but none closer than the destination. Pilot advised would continue ILS approach. Change of throttle position with descent seemed to change roughness; sometimes better; sometimes worse. ATC advised change to advisory frequency. Pilot requested to stay with ATC. ATC advised that pilot would need to declare an emergency if he wanted to stay on Center. Due to pilot's concern that if engine failure became imminent and aircraft did not reach runway; rescue services could arrive faster if he was able to provide a detailed location after descending from cloud bases to Center. Pilot declared emergency. At that time; it was not known by pilot if UNICOM was monitored at the destination. Pilot declared emergency but declined emergency services on the ground with ATC. ATC suggested that pilot monitor Center and contact CTAF to monitor other inbound traffic. Ceiling was reported at 400 overcast on AWOS. Pilot raised UNICOM on the CTAF frequency; advised of location and asked if emergency services were located on the field. UNICOM advised no and asked if we would like them to be called. Pilot advised 'not at this time.' UNICOM requested nature of problem and pilot asked UNICOM to 'standby' as he was approaching minimums. Aircraft was landed successfully with partial power. Center was advised that we would like to cancel IFR and that we were safely on the ground. No further assistance was needed.
Data retrieved from NASA's ASRS site as of April 2012 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.