37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1340550 |
Time | |
Date | 201603 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B787-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | Data Processing |
Person 1 | |
Function | First Officer Pilot Not Flying Relief Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Track / Heading All Types |
Narrative:
On the departure; climbing through approximately 3000 feet; both FMC's flashed momentarily with resulting failure of both flight directors; route and performance data. Route 2 (blue line was displayed) was activated. Crew was distracted with these events and subsequently ended up being slightly left of course. Departure control questioned our course. We let him know we had an aircraft navigation problem and asked for vectors. Departure provided an initial heading and subsequent direct routing. Aircraft was loaded with new FMC software.while I believe that the entire crew did a great job of handling the situation (fairly complex considering RNAV departure; international ops; etc); we certainly could have done a better job of transitioning back to a lower level of automation as well as delegating who's talking; flying; and working the issue.
Original NASA ASRS Text
Title: The B787 crew experienced an FMC malfunction which dumped the route and performance data while climbing out of 3;000 feet. They were able to activate Route 2 and proceed after getting vectors from ATC.
Narrative: On the departure; climbing through approximately 3000 feet; both FMC's flashed momentarily with resulting failure of both flight directors; route and performance data. Route 2 (blue line was displayed) was activated. Crew was distracted with these events and subsequently ended up being slightly left of course. Departure control questioned our course. We let him know we had an aircraft navigation problem and asked for vectors. Departure provided an initial heading and subsequent direct routing. Aircraft was loaded with new FMC software.While I believe that the entire crew did a great job of handling the situation (fairly complex considering RNAV departure; international ops; etc); we certainly could have done a better job of transitioning back to a lower level of automation as well as delegating who's talking; flying; and working the issue.
Data retrieved from NASA's ASRS site 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.