![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 850828 |
| Time | |
| Date | 200908 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Private |
| Experience | Flight Crew Last 90 Days 89 Flight Crew Total 850 Flight Crew Type 654 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
I had an alternator failure; the second one in 6 flight hours; and was diverting. I was above the cloud deck at 12;000; with cloud cover being approx 50%. ATC told me to descend to 11;000. As I recalled at the time I believed the descent was to 10;000 ft so set the autopilot to 10k. Apparently I confirmed 11;000 according to ATC; but then I programmed the wrong altitude of 10;000. ATC called when I was at 10;300 and indicated 11;000 was the assigned altitude; which I climbed back up to. At the time I was in VMC and there was no other aircraft nearby. A compounding distraction was there was a cloud deck ahead that I expected would contain ice as I had picked up some flash ice just prior to the alternator failure. Just after the discussion about my incorrect altitude I requested lower and the controller gave me 5;000. To prevent this from happening again; I've started to set the altitude preselect first and then verbally confirm from that reading; rather than confirm and then later set the altitude. I do this procedure when changing frequencies; set; then confirm and that works well; other than in very busy airspace where an immediate response is appropriate.
Original NASA ASRS Text
Title: An SR22 pilot experienced an altitude deviation when he was distracted by weather and an alternator failure.
Narrative: I had an alternator failure; the second one in 6 flight hours; and was diverting. I was above the cloud deck at 12;000; with cloud cover being approx 50%. ATC told me to descend to 11;000. As I recalled at the time I believed the descent was to 10;000 FT so set the autopilot to 10k. Apparently I confirmed 11;000 according to ATC; but then I programmed the wrong altitude of 10;000. ATC called when I was at 10;300 and indicated 11;000 was the assigned altitude; which I climbed back up to. At the time I was in VMC and there was no other aircraft nearby. A compounding distraction was there was a cloud deck ahead that I expected would contain ice as I had picked up some flash ice just prior to the alternator failure. Just after the discussion about my incorrect altitude I requested lower and the controller gave me 5;000. To prevent this from happening again; I've started to set the altitude preselect first and then verbally confirm from that reading; rather than confirm and then later set the altitude. I do this procedure when changing frequencies; set; then confirm and that works well; other than in very busy airspace where an immediate response is appropriate.
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.