 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Multiple and intermittent primary flight display and autopilot problems occurred on a B737 during cruise. Crew elected to continue to destination.
| Attributes | |
| ACN | 868083 |
| Time | |
| Date | 201001 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZLC.ARTCC |
| State Reference | UT |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigational Equipment and Processing |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical |
Narrative:
Our flight was about 200 miles northeast of las vegas and we were climbing from FL380 to FL400 after burning enough fuel to climb higher. This was routine. A few minutes after reaching FL400; the power levers retarded to idle; the over speed clacker was heard and the primary flight display on the captain's side was showing completely inaccurate airspeed; altitude and vertical speed information. The 'a' autopilot disengaged as well. The first officer's primary flight display was unaffected so I transferred control of the aircraft to him by making his flight director the master. We ran numerous QRH checklists but the problem still persisted. Since the first officer's side was not affected; I elected to continue on to our destination. I then started a descent to FL360 to give us more buffet margin in case the false airspeed indications continued. As soon as we left FL400; all problems with my pfd stopped and everything was normal for the rest of the flight. I elected to let the first officer land the aircraft just in case my pfd malfunctioned again. I also chose to continue based of the lower terrain since this flight was at night. Maintenance met us and performed numerous tests. The cause was not immediately identified but the FMC showed 48 events of a malfunctioning adiru-1.
Original NASA ASRS Text
Title: Multiple and intermittent primary flight display and autopilot problems occurred on a B737 during cruise. Crew elected to continue to destination.
Narrative: Our flight was about 200 miles northeast of Las Vegas and we were climbing from FL380 to FL400 after burning enough fuel to climb higher. This was routine. A few minutes after reaching FL400; the power levers retarded to idle; the over speed clacker was heard and the Primary Flight Display on the Captain's side was showing completely inaccurate airspeed; altitude and vertical speed information. The 'A' autopilot disengaged as well. The First Officer's Primary Flight Display was unaffected so I transferred control of the aircraft to him by making his flight director the master. We ran numerous QRH checklists but the problem still persisted. Since the First Officer's side was not affected; I elected to continue on to our destination. I then started a descent to FL360 to give us more buffet margin in case the false airspeed indications continued. As soon as we left FL400; all problems with my PFD stopped and everything was normal for the rest of the flight. I elected to let the First Officer land the aircraft just in case my PFD malfunctioned again. I also chose to continue based of the lower terrain since this flight was at night. Maintenance met us and performed numerous tests. The cause was not immediately identified but the FMC showed 48 events of a malfunctioning ADIRU-1.
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.