 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Wide body first officer reported requesting a different departure from lax when their FMC showed a wrong turn programmed on the original HOLZ9 departure.
| Attributes | |
| ACN | 1324660 |
| Time | |
| Date | 201601 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | LAX.Tower |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
During preflight while briefing the HOLZ9 RNAV departure we saw a discrepancy between the flight plan points and the mcu (mode control unit) navigation display; which displayed a right 360 degree magenta turn just after takeoff. We reloaded the SID for both 25 left and right but the turn would reinsert itself after about a 15 second delay. Called maintenance and wrote an aml (aircraft maintenance log) discrepancy; we also informed the dispatcher and the duty officer of the problem. Maintenance reset the circuit breakers but the turn remained on the navigation display. After more consulting between lax maintenance they said they had seen this before and the turn would clear itself when we lined up on the runway. We assessed the operational risk and decided we would taxi out and see if the turn would remove itself from the display when we lined up for takeoff; if it did not clear itself we would cancel our clearance and taxi off the runway and then ask clearance for the laxx 7. The anomaly did not clear; we cancelled our takeoff clearance and taxied clear. No traffic separation issues occurred. Once stopped on taxiway alpha we executed our game plan refilling and receiving clearance for the LAXX7 SID. No anomaly appeared with that SID; flight continued with no further issues. Navigation error on mcu displayed that did not match the waypoints on mcdu.
Original NASA ASRS Text
Title: Wide body First Officer reported requesting a different departure from LAX when their FMC showed a wrong turn programmed on the original HOLZ9 departure.
Narrative: During preflight while briefing the HOLZ9 RNAV departure we saw a discrepancy between the flight plan points and the MCU (Mode Control Unit) NAV display; which displayed a right 360 degree magenta turn just after takeoff. We reloaded the SID for both 25 left and right but the turn would reinsert itself after about a 15 second delay. Called maintenance and wrote an AML (Aircraft Maintenance Log) discrepancy; we also informed the dispatcher and the duty officer of the problem. Maintenance reset the circuit breakers but the turn remained on the NAV display. After more consulting between LAX maintenance they said they had seen this before and the turn would clear itself when we lined up on the runway. We assessed the operational risk and decided we would taxi out and see if the turn would remove itself from the display when we lined up for takeoff; if it did not clear itself we would cancel our clearance and taxi off the runway and then ask clearance for the LAXX 7. The anomaly did not clear; we cancelled our takeoff clearance and taxied clear. No traffic separation issues occurred. Once stopped on taxiway Alpha we executed our game plan refilling and receiving clearance for the LAXX7 SID. No anomaly appeared with that SID; flight continued with no further issues. Navigation error on MCU displayed that did not match the waypoints on MCDU.
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.