 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported missing a crossing restriction after multiple changes to the OAKES2 RNAV arrival to oak by ATC.
| Attributes | |
| ACN | 1373906 |
| Time | |
| Date | 201607 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | OAK.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | Mixed |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR OAKES2 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | MCP |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 225 |
| Person 2 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 166 Flight Crew Type 7500 |
| Events | |
| Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
Joshua approach had cleared us direct to toool; well before arriving at oakes. Oakland center subsequently cleared us to oakes. As I recall; they then cleared us to descend via the oakes 2 arrival. Before reaching oakes; oakland center cleared us 'direct toool; descend and maintain 17;000; at toool resume the oakes 2 arrival.' captain interpreted this to mean cleared the oakes 2 lateral routing only and reentered 17;000 ft into the MCP altitude window. I asked oakland center to clarify whether we were cleared to descend via the oakes 2 arrival upon reaching toool; and oakland center confirmed that this is what they expected us to do. Captain entered 4500 ft into the MCP altitude window; and I asked whether we should set the FMS altitude at toool to a hard 17;000 ft (instead of the 11;000-17;000 ft altitude defaulted for the RNAV arrival). Ca suggested that the path would have us cross toool at 17;000 ft anyway; and that struck me as plausible so I agreed that we would watch and see what it does. After passing FL180; I ran the approach checklist and there was a radio frequency change. As we were passing toool; I realized we'd crossed toool at approximately 13;000 ft instead of 17;000 ft.
Original NASA ASRS Text
Title: B737 flight crew reported missing a crossing restriction after multiple changes to the OAKES2 RNAV arrival to OAK by ATC.
Narrative: Joshua Approach had cleared us direct to TOOOL; well before arriving at OAKES. Oakland Center subsequently cleared us to OAKES. As I recall; they then cleared us to descend via the OAKES 2 Arrival. Before reaching OAKES; Oakland Center cleared us 'Direct TOOOL; descend and maintain 17;000; at TOOOL resume the OAKES 2 Arrival.' Captain interpreted this to mean cleared the OAKES 2 lateral routing only and reentered 17;000 ft into the MCP altitude window. I asked Oakland Center to clarify whether we were cleared to descend via the OAKES 2 Arrival upon reaching TOOOL; and Oakland Center confirmed that this is what they expected us to do. Captain entered 4500 ft into the MCP altitude window; and I asked whether we should set the FMS altitude at TOOOL to a hard 17;000 ft (instead of the 11;000-17;000 ft altitude defaulted for the RNAV arrival). CA suggested that the PATH would have us cross TOOOL at 17;000 ft anyway; and that struck me as plausible so I agreed that we would watch and see what it does. After passing FL180; I ran the Approach Checklist and there was a radio frequency change. As we were passing TOOOL; I realized we'd crossed TOOOL at approximately 13;000 ft instead of 17;000 ft.
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.