 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported being cleared for the BDEGA1 RNAV arrival to sfo runway 28R. Nct changes the runway during the descent to runway 28L. The ILS frequency is changed but the FMC is not updated resulting in the runway 28R transition being flown and not the runway 28L. Nct takes note and issued vectors.
| Attributes | |
| ACN | 1281473 |
| Time | |
| Date | 201507 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SFO.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | STAR BDEGA 1 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 136 Flight Crew Total 14000 Flight Crew Type 8000 |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 80 Flight Crew Total 10900 Flight Crew Type 4937 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On descent into san francisco we were descending via the bdega one rnav arrival planning on a visual 28r approach. Upon checking in with final approach descending through 17000 feet for 11000 feet; we were told again to descend via the bdega one arrival for a visual to 28L. The clearance was accepted and 28L was briefed. The fmc however was not loaded with the new approach and I as the monitoring pilot failed to verify this. Due to a failure to carefully review the arrival neither of us realized the arrival split at corkk for the separate runways. This caused us to turn towards finsh on the arrival for the 28R transition instead of toward brixx for the 28L transition. The approach controller notified us that we turned toward finsh instead of brixx flying the wrong transition. We were given a turn to a heading of 140 and further descent to 7000 feet. We acknowledged the mistake and preceded to properly program the FMC with the appropriate routing and approach. The rest of the arrival and approach was uneventful. I was simply complacent in the runway change and did not use due diligence to verify the effect of the runway change on the arrival routing. I should have become aware when the controller recleared us to descend via the arrival after administering the runway change.
Original NASA ASRS Text
Title: B737 flight crew reported being cleared for the BDEGA1 RNAV Arrival to SFO Runway 28R. NCT changes the runway during the descent to Runway 28L. The ILS frequency is changed but the FMC is not updated resulting in the Runway 28R transition being flown and not the Runway 28L. NCT takes note and issued vectors.
Narrative: On descent into San Francisco we were descending via the bdega one rnav arrival planning on a visual 28r approach. Upon checking in with final approach descending through 17000 feet for 11000 feet; we were told again to descend via the bdega one arrival for a visual to 28L. The clearance was accepted and 28L was briefed. The fmc however was not loaded with the new approach and I as the monitoring pilot failed to verify this. Due to a failure to carefully review the arrival neither of us realized the arrival split at corkk for the separate runways. This caused us to turn towards FINSH on the arrival for the 28R transition instead of toward BRIXX for the 28L transition. The approach controller notified us that we turned toward FINSH instead of BRIXX flying the wrong transition. We were given a turn to a heading of 140 and further descent to 7000 feet. We acknowledged the mistake and preceded to properly program the FMC with the appropriate routing and approach. The rest of the arrival and approach was uneventful. I was simply complacent in the runway change and did not use due diligence to verify the effect of the runway change on the arrival routing. I should have become aware when the controller recleared us to descend via the arrival after administering the runway change.
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.