 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported the cpdlc reroute did not load the new SID into the FMS flight plan and missed a delayed turn on the departure.
| Attributes | |
| ACN | 1579271 |
| Time | |
| Date | 201809 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SJC.Airport |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Next Generation Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | SID SJC2 |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 269 |
| Person 2 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
We received a different clearance than our filed route from ATC. Our revised route was SJC2 moony sjc bmrng af (as filed). Our filed route was loupe 4 bmrng. We accepted the new route from cpdlc and auto loaded it into the FMC. We verified the route fixes together during the briefings. After departure; ATC queried us about making an early right turn on the departure after takeoff. At that point; we noticed on the SJC2 text that instructs to fly a 306 degree heading off of [runway] 30R to 1.8 DME on the sjc VOR before making the right turn. We looked at the route page and found the SJC2 SID was not there. We realized we had verified the fixes on the legs page on the ground but had not reviewed the route page. When we auto loaded the route change from cpdlc; it put in the fixes but did not load the SID so the 1.8 DME delay turn was not in the FMC. We continued the fight uneventfully. We should have verified and briefed the new routing on both the route page and the legs page. If we had done that; we could have trapped our error that the SJC2 SID did not get auto loaded from cpdlc.
Original NASA ASRS Text
Title: B737 flight crew reported the CPDLC reroute did not load the new SID into the FMS flight plan and missed a delayed turn on the departure.
Narrative: We received a different clearance than our filed route from ATC. Our revised route was SJC2 MOONY SJC BMRNG AF (as filed). Our filed route was LOUPE 4 BMRNG. We accepted the new route from CPDLC and auto loaded it into the FMC. We verified the route fixes together during the briefings. After departure; ATC queried us about making an early right turn on the departure after takeoff. At that point; we noticed on the SJC2 text that instructs to fly a 306 degree heading off of [Runway] 30R to 1.8 DME on the SJC VOR before making the right turn. We looked at the Route page and found the SJC2 SID was not there. We realized we had verified the fixes on the LEGS page on the ground but had not reviewed the Route page. When we auto loaded the route change from CPDLC; it put in the fixes but did not load the SID so the 1.8 DME delay turn was not in the FMC. We continued the fight uneventfully. We should have verified and briefed the new routing on both the Route page and the LEGS page. If we had done that; we could have trapped our error that the SJC2 SID did not get auto loaded from CPDLC.
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.