37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1170226 |
Time | |
Date | 201405 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | RJBB.TRACON |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B777-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
We requested the continuous descent operation (cdo) 1 arrival to runway 24R. ATC cleared cdo-1 arrival descend to 4;000 ft. Contacted arrival advised on cdo 1 arrival and she didn't change anything. Changed to next controller. Just inside evian; controller asked if we were going to tomo with 080 heading. Flew the 080 and was told to fly the tomo arrival. Could not get the arrival in quick enough then asked to fly 360 heading. Then direct to mayah. Cross mayah at 4;000 ft. After landing and debrief realized that the confusion was how the cdo-1 is written in one area of the plates and the becky arrival is written in the arrival plates. What we read and briefed was strictly what was written in the box notes for the cdo-1. Karin-becky-evian-mayah and the altitude requirements. After evian we were proceeding direct to mayah and the becky delta arrival was expected. ATC never mentioned fly the cdo-1 for the becky delta arrival. Both of us had developed the start of a cold while on the trip and both had terrible sleep periods. Having the procedures in two different places in the charts. A very poor explanation of these procedures. This is kind of a cut and paste method for a cdo [continuous descent operation] arrival and should be listed on one page and used in the FMC as a database arrival. I have flown this cdo before; but did not notice the page being written like this. This page was changed in march 1; 2013. Do not accept this arrival unless it is written and put in the FMC database like every other arrival.
Original NASA ASRS Text
Title: B777 Captain reports confusion attempting to fly the CDO 1 route to Runway 24R at RJBB. The altitude restrictions and the fixes listed for the CDO 1 are interpreted as the route instead of flying the CDO 1 route (SUC Y53 to BECKY) then the BECKY DELTA arrival. Fatigue and a developing cold were cited as factors.
Narrative: We requested the Continuous Descent Operation (CDO) 1 Arrival to Runway 24R. ATC cleared CDO-1 Arrival descend to 4;000 FT. Contacted Arrival advised on CDO 1 Arrival and she didn't change anything. Changed to next Controller. Just inside EVIAN; Controller asked if we were going to TOMO with 080 heading. Flew the 080 and was told to fly the TOMO arrival. Could not get the arrival in quick enough then asked to fly 360 heading. Then direct to MAYAH. Cross MAYAH at 4;000 FT. After landing and debrief realized that the confusion was how the CDO-1 is written in one area of the plates and the BECKY Arrival is written in the arrival plates. What we read and briefed was strictly what was written in the box notes for the CDO-1. KARIN-BECKY-EVIAN-MAYAH and the altitude requirements. After EVIAN we were proceeding direct to MAYAH and the BECKY DELTA Arrival was expected. ATC never mentioned fly the CDO-1 for the BECKY DELTA Arrival. Both of us had developed the start of a cold while on the trip and both had terrible sleep periods. Having the procedures in two different places in the charts. A very poor explanation of these procedures. This is kind of a cut and paste method for a CDO [Continuous Descent Operation] arrival and should be listed on one page and used in the FMC as a database arrival. I have flown this CDO before; but did not notice the page being written like this. This page was changed in MARCH 1; 2013. Do not accept this arrival unless it is written and put in the FMC database like every other arrival.
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.