37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1063636 |
Time | |
Date | 201301 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Component | |
Aircraft Component | MCP |
Person 1 | |
Function | First Officer Pilot Flying |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
I was the pilot flying. We started initial descent on the RNAV arrival. Around FL300; the autopilot disconnected with the associated warning and also an altitude warning. I began hand-flying the aircraft. The other problems included failed autothrottles; a frozen MCP with 50;000 feet in the altitude window and heading and airspeed were also frozen on inaccurate values. The captain was coming back from an interphone call to try to rid the flight deck of his dinner tray. At this time; I was still responsible for the radios while he was 'off' and I requested a pilot's discretion descent to 10;000 feet. The captain was very interested in canceling the altitude warning alert; which seemingly could not be canceled by any means; that we had available to us. The captain began to troubleshoot. I hand flew the aircraft with no autopilot; autothrottles; flight directors; or advanced navigation. I did have primary flight and engine instruments with correct information. The captain was under the impression that the FMC's were frozen and the ultimate cause of our problem. I was able to see our original magenta course on my map display and attempted to stay on flight planned course by flying the magenta line referencing the cross track error on progress page 2 on the first officer's CDU. The captain declared an emergency. ATC provided altitudes and headings for [the airport]. ATC also verified headings; altitudes; and distances with us; and we were able to make confirmations (i.e. They showed us heading 210 and we concurred). At this point; we were below FL240 and ATC was trying to understand the nature of our emergency. We were positioned on an extended left downwind. On the downwind; the aircraft seemingly started to correct itself; including the altitude warning ceasing because the MCP came 'unfrozen.' the flight conditions had been and continued to be day VFR; so we accepted a visual to the runway. I flew a non-coupled (no flight director; autopilot; or autothrottle) visual backed up with a raw data ILS. ATC notified us that the emergency equipment was standing by. I landed the aircraft with no further abnormalities.
Original NASA ASRS Text
Title: B737 crew experienced an MCP failure during initial descent; resulting in loss of autopilot; flight directors; auto thrust; and a frozen MCP. An emergency is declared and vectors provided by ATC to a safe landing.
Narrative: I was the Pilot Flying. We started initial descent on the RNAV Arrival. Around FL300; the autopilot disconnected with the associated warning and also an altitude warning. I began hand-flying the aircraft. The other problems included failed autothrottles; a frozen MCP with 50;000 feet in the altitude window and heading and airspeed were also frozen on inaccurate values. The Captain was coming back from an interphone call to try to rid the Flight Deck of his dinner tray. At this time; I was still responsible for the radios while he was 'off' and I requested a pilot's discretion descent to 10;000 feet. The Captain was very interested in canceling the altitude warning alert; which seemingly could not be canceled by any means; that we had available to us. The Captain began to troubleshoot. I hand flew the aircraft with no autopilot; autothrottles; flight directors; or advanced navigation. I did have primary flight and engine instruments with correct information. The Captain was under the impression that the FMC's were frozen and the ultimate cause of our problem. I was able to see our original magenta course on my map display and attempted to stay on flight planned course by flying the magenta line referencing the cross track error on Progress Page 2 on the First Officer's CDU. The Captain declared an emergency. ATC provided altitudes and headings for [the airport]. ATC also verified headings; altitudes; and distances with us; and we were able to make confirmations (i.e. they showed us heading 210 and we concurred). At this point; we were below FL240 and ATC was trying to understand the nature of our emergency. We were positioned on an extended left downwind. On the downwind; the aircraft seemingly started to correct itself; including the altitude warning ceasing because the MCP came 'unfrozen.' The flight conditions had been and continued to be day VFR; so we accepted a visual to the runway. I flew a non-coupled (no flight director; autopilot; or autothrottle) visual backed up with a raw data ILS. ATC notified us that the emergency equipment was standing by. I landed the aircraft with no further abnormalities.
Data retrieved from NASA's ASRS site as of July 2013 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.