37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1233662 |
Time | |
Date | 201501 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZSPD.TRACON |
State Reference | FO |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B747-400 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR SAS 12I |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 80 Flight Crew Total 5600 Flight Crew Type 400 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
About an hour from zspd the relief crew asked for expected arrival procedure in to zspd. The relief crew asked two different controllers. Both controllers told them to ask the next controller. About 50 min from zspd capt. And first officer (first officer) resumed operation of the aircraft. We also inquired about approach in use and were passed on to the next controller. At this point the controller cleared us direct to the second fix on the arrival and handed us over to a new controller. We inquired what to expect after (second fix) and were give the following clearance - cleared for the SAS12i arrival. This starts at sasan. The SAS12i was entered in to the FMC; it appeared normal on the legs page and the nd and was executed. LNAV was engaged. About 30 sec later I said why is the aircraft turning. The aircraft had turned 30 degrees to the left of desired heading. My immediate action was to select 'heading select' and turn the aircraft about 60 degrees in the opposite direction in order to get back on course. It came to our realization the IAF sasan never cycled thereby creating a classic problem of having the active waypoint behind us. The clearance to fly the approach was given either right before the IAF sasan or on top of it. The IAF sasan was literally at the back of the aircraft diamond on the navigation display. I estimate the error to be less than one mile left off course given the speed of about kias 280. ATC asked why we were turning and we tried to convey this to ATC; I am however pretty sure the information was not understood. Contributing factors: 1. Chinese ATC not giving an approach clearance in a timely manner when requested.2. Operating crew did not catch that the aircraft was close enough that it might not cycle properly; as there is a small delay in the FMC. 3. The FMC contains 19 pages of arrivals in to zspd each has several variations and multiple transitions. It is time consuming to figure out exactly which one is the correct approach. Even when selecting the runway in use in this case runway 16 there is still 7 FMC pages with variations and transitions. These are not readily identifiable when compared to jeppesen approach plates. Several must be entered in to the FMC in order to be compared to a jeppesen plate for verification. 4. Fatigue: this was at the end of an 18 hour duty day with a rolling 2 hour delay.
Original NASA ASRS Text
Title: B747-400 flight crew reports being cleared direct to the second fix on an SAS 12I arrival to ZSPD before being cleared for the arrival. When the arrival clearance is issued the crew does not clean up the legs page in the FMC to reflect direct to the second waypoint and a minor track deviation occurs.
Narrative: About an hour from ZSPD the relief crew asked for expected arrival procedure in to ZSPD. The relief crew asked two different controllers. Both controllers told them to ask the next controller. About 50 min from ZSPD Capt. and First Officer (FO) resumed operation of the aircraft. We also inquired about approach in use and were passed on to the next controller. At this point the controller cleared us direct to the second fix on the arrival and handed us over to a new controller. We inquired what to expect after (second Fix) and were give the following clearance - Cleared for the SAS12i arrival. This starts at SASAN. The SAS12i was entered in to the FMC; It appeared normal on the legs page and the ND and was executed. LNAV was engaged. About 30 sec later I said why is the Aircraft turning. The Aircraft had turned 30 degrees to the left of desired heading. My immediate action was to select 'Heading Select' and turn the aircraft about 60 degrees in the opposite direction in order to get back on Course. It came to our realization the IAF SASAN never cycled thereby creating a classic problem of having the active waypoint behind us. The clearance to fly the approach was given either right before the IAF SASAN or on top of it. The IAF SASAN was literally at the back of the Aircraft Diamond on the Navigation Display. I estimate the error to be less than one mile left off course given the speed of about Kias 280. ATC asked why we were turning and we tried to convey this to ATC; I am however pretty sure the information was not understood. Contributing factors: 1. Chinese ATC not giving an approach clearance in a timely manner when requested.2. Operating crew did not catch that the aircraft was close enough that it might not Cycle properly; as there is a small delay in the FMC. 3. The FMC contains 19 pages of arrivals in to ZSPD each has several variations and multiple transitions. It is time consuming to figure out exactly which one is the correct approach. Even when selecting the Runway in use in this case RWY 16 there is still 7 FMC pages with variations and transitions. These are not readily identifiable when compared to Jeppesen approach plates. Several must be entered in to the FMC in order to be compared to a Jeppesen plate for verification. 4. Fatigue: This was at the end of an 18 hour duty day with a rolling 2 hour delay.
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.