 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 first officer reported they deviated from cleared track because they failed to see a change to their route in the pre departure clearance.
| Attributes | |
| ACN | 1322382 |
| Time | |
| Date | 201601 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZDV.ARTCC |
| State Reference | CO |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 133 Flight Crew Type 535 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
While enroute to [destination] inside denver ARTCC airspace; the enroute controller queried us about our clearance and indicated that we were deviating from what he thought our clearance was. We were at FL370 and in LNAV/VNAV modes with a route of dta ekr KD63W jalap. The controller thought we were dta ekr frogs sny lnk jalap. He cleared us direct to jalap without further comment.the dispatched route had a non-standard route and the pre departure clearance had an amendment to that route. The pre departure clearance amendment changed the SID and first transition point. Though we both reviewed the pre departure clearance and the route page 2; somehow we failed to ensure the correct route was inserted. We accomplished the FMC briefing prior to the before start originating checklist.we were in the process of an aircraft swap on the last day of a four-day and though the airplane arrived on time; the gate was occupied and we did not board the plane to begin our preflight until 20 minutes prior to scheduled push.I have seen at least three different pre departure clearance formats in our mcdus. I am not a fan of a pre departure clearance amendment that is not displayed as a full-route clearance. The partial clearance is confusing. Somehow two pilots incorrectly verified the pre departure clearance and entered route. I still don't know how; but I suspect the amended clearance displayed on the pre departure clearance in our -800 today contributed to the error.
Original NASA ASRS Text
Title: B737-800 First Officer reported they deviated from cleared track because they failed to see a change to their route in the PDC.
Narrative: While enroute to [destination] inside Denver ARTCC airspace; the enroute Controller queried us about our clearance and indicated that we were deviating from what he thought our clearance was. We were at FL370 and in LNAV/VNAV modes with a route of DTA EKR KD63W JALAP. The Controller thought we were DTA EKR FROGS SNY LNK JALAP. He cleared us direct to JALAP without further comment.The dispatched route had a non-standard route and the PDC had an amendment to that route. The PDC amendment changed the SID and first transition point. Though we both reviewed the PDC and the Route page 2; somehow we failed to ensure the correct route was inserted. We accomplished the FMC briefing prior to the Before Start Originating Checklist.We were in the process of an aircraft swap on the last day of a four-day and though the airplane arrived on time; the gate was occupied and we did not board the plane to begin our preflight until 20 minutes prior to scheduled push.I have seen at least three different PDC formats in our MCDUs. I am not a fan of a PDC amendment that is not displayed as a full-route clearance. The partial clearance is confusing. Somehow two pilots incorrectly verified the PDC and entered route. I still don't know how; but I suspect the amended clearance displayed on the PDC in our -800 today contributed to the error.
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.