 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B747 first officer states that the STAR names in the FMC do not match the names on the arrival charts for zbaa; causing late selection of the assigned arrival procedure.
| Attributes | |
| ACN | 1248602 |
| Time | |
| Date | 201503 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZBAA.Airport |
| State Reference | FO |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B747 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Experience | Flight Crew Last 90 Days 300 Flight Crew Total 15000 Flight Crew Type 4000 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Stars in the 747 navigation (navigation) database do not match the charted stars by name. They are not even close. Zbaa (beijing) has a history of assigning the arrival procedure very late in the arrival sequence. When the procedure designation in the FMC does not remotely match the name on any chart; and one only has a couple of minutes to load the procedure; there is no time to start at the top and search manually for one that follows the same points. We almost flew past a clearance limit due to not knowing which arrival to program in. Chinese controllers are not adept with manual control of aircraft in airspace where they expect it to be automated. We were minutes from a potentially very dangerous situation. At the very least; we were minutes away from a chinese violation. This is a regular occurrence flying into zbaa and unsatisfactory. In addition; every database update changes enough of the stars that familiarity cannot be counted on. A good example of this is; one first officer (first officer) on this leg had the 'paired' FMC database STAR electronically written on the page in his efb. That STAR no longer existed in the FMC for the runway we were assigned. It was pure luck that we found the correct one in the FMC before flying past the first fix associated with the clearance.
Original NASA ASRS Text
Title: A B747 First Officer states that the STAR names in the FMC do not match the names on the arrival charts for ZBAA; causing late selection of the assigned arrival procedure.
Narrative: STARS in the 747 Navigation (NAV) database do not match the charted STARs by name. They are not even close. ZBAA (Beijing) has a history of assigning the arrival procedure very late in the arrival sequence. When the procedure designation in the FMC does not remotely match the name on ANY chart; and one only has a couple of minutes to load the procedure; there is no time to start at the top and search manually for one that follows the same points. We almost flew past a clearance limit due to not knowing which arrival to program in. Chinese controllers are not adept with manual control of aircraft in airspace where they expect it to be automated. We were minutes from a potentially very dangerous situation. At the very least; we were minutes away from a Chinese violation. This is a regular occurrence flying into ZBAA and unsatisfactory. In addition; every database update changes enough of the STARS that familiarity cannot be counted on. A good example of this is; one First Officer (FO) on this leg had the 'paired' FMC database STAR electronically written on the page in his EFB. That STAR no longer existed in the FMC for the runway we were assigned. It was pure luck that we found the correct one in the FMC before flying past the first fix associated with the clearance.
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.