 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B747 flight crew experiences a dual FMC failure while attempting to enter a new arrival per ATC instructions during descent into rksi. Radar vectors are requested from ATC and received with normal FMC operation regained later in the descent.
| Attributes | |
| ACN | 1315329 |
| Time | |
| Date | 201512 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | RKSI.Airport |
| State Reference | FO |
| Aircraft 1 | |
| Make Model Name | B747 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 129 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Track / Heading All Types |
Narrative:
When inbound to rksi and just checking into icn approach control. We were filed for the karbu 1P arrival and ATIS was saying landing runway 33R and 34; and this arrival is for those runways as well. ATC on initial contact clears us for karbu 1N which is for runway 15 and 16 and he said information X current. So [the first officer] pulled up new ATIS while I was changing over to karbu 1 north arrival; all while being over karbu. Karbu 1P goes 267 degrees to notin then 231 degrees to si 857; which is what was in the FMC and we were filed for. So while I was pulling up karbu 1N which is karbu 267 degrees to egoba then 266 degrees to sel; we had a dual FMC failure; autopilot disconnected; auto throttle disconnected; all sorts of EICAS messages and FMC saying timed out standby. Once we had FMC coming back and could pass along to ATC that we had an FMC navigation problem we did. Then ATC preceded to put us on a vector and so never flew the arrival and he then said landing runway 33R. I believe we were off course due to what was planned and in the FMC and would have had us left of course; due to not being able to get the FMC to change the arrival due to the failure. After shutdown we wrote up the [FMC] and I spoke with maintenance.
Original NASA ASRS Text
Title: A B747 flight crew experiences a dual FMC failure while attempting to enter a new arrival per ATC instructions during descent into RKSI. Radar vectors are requested from ATC and received with normal FMC operation regained later in the descent.
Narrative: When inbound to RKSI and just checking into ICN approach control. We were filed for the KARBU 1P arrival and ATIS was saying landing Runway 33R and 34; and this arrival is for those runways as well. ATC on initial contact clears us for KARBU 1N which is for Runway 15 and 16 and he said information X current. So [the first officer] pulled up new ATIS while I was changing over to KARBU 1 N arrival; all while being over KARBU. KARBU 1P goes 267 degrees to NOTIN then 231 degrees to SI 857; which is what was in the FMC and we were filed for. So while I was pulling up KARBU 1N which is KARBU 267 degrees to EGOBA then 266 degrees to SEL; we had a dual FMC failure; autopilot disconnected; auto throttle disconnected; all sorts of EICAS messages and FMC saying timed out standby. Once we had FMC coming back and could pass along to ATC that we had an FMC navigation problem we did. Then ATC preceded to put us on a vector and so never flew the arrival and he then said landing Runway 33R. I believe we were off course due to what was planned and in the FMC and would have had us left of course; due to not being able to get the FMC to change the arrival due to the failure. After shutdown we wrote up the [FMC] and I spoke with maintenance.
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.