 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reports misreading a revised pre departure clearance; which results in a track deviation noted by ATC.
| Attributes | |
| ACN | 1121289 |
| Time | |
| Date | 201310 |
| Place | |
| Locale Reference | ZDV.ARTCC |
| State Reference | CO |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Person 1 | |
| Function | Captain Pilot Flying |
| Experience | Flight Crew Last 90 Days 200 Flight Crew Total 17272 Flight Crew Type 11000 |
| Person 2 | |
| Function | Pilot Not Flying First Officer |
| Experience | Flight Crew Last 90 Days 220 Flight Crew Total 19500 Flight Crew Type 720 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
After programming the FMC; we failed to properly identify ATC routing change upon receiving pre departure clearance. Original cleared routing: -den BAYLR2 hbu dvc-; ATC routing change; -BAYLR2 tehru dvc-. With ATC routing change listed directly above the original cleared routing on the pre departure clearance; we inadvertently verified the cleared routing as the routing change. On departure at top of climb at bobba intersection we proceeded to fly the hbu transition. Shortly after turning den ATC cleared us direct to tehru flight planned route. ATC then questioned us about the clearance we received. At that time we believed the hbu transition to be correct. ATC then gave us a frequency change. We then reviewed the pre departure clearance and all that led up to the deviation and conclusion that we mis-identified the routing change. Several controllers later; we were advised to call den ATC about possible route deviation. I called immediately after completing the flight. The ATC supervisor indicated to me that this same deviation has been happening on a regular basis and that my explanation is the same as on most occurrences. The ATC routing change and the original cleared routing being so close together allows for the potential to make this mistake repeatedly. We realize the error and will be more diligent to not repeat this error.
Original NASA ASRS Text
Title: B737 flight crew reports misreading a revised PDC; which results in a track deviation noted by ATC.
Narrative: After programming the FMC; we failed to properly identify ATC routing change upon receiving PDC. Original cleared routing: -DEN BAYLR2 HBU DVC-; ATC routing change; -BAYLR2 TEHRU DVC-. With ATC routing change listed directly above the original cleared routing on the PDC; we inadvertently verified the cleared routing as the routing change. On departure at top of climb at BOBBA Intersection we proceeded to fly the HBU transition. Shortly after turning DEN ATC cleared us direct to TEHRU flight planned route. ATC then questioned us about the clearance we received. At that time we believed The HBU transition to be correct. ATC then gave us a frequency change. We then reviewed the PDC and all that led up to the deviation and conclusion that we mis-identified the routing change. Several controllers later; we were advised to call DEN ATC about possible route deviation. I called immediately after completing the flight. The ATC supervisor indicated to me that this same deviation has been happening on a regular basis and that my explanation is the same as on most occurrences. The ATC routing change and the original cleared routing being so close together allows for the potential to make this mistake repeatedly. We realize the error and will be more diligent to not repeat this error.
Data retrieved from NASA's ASRS site as of July 2013 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.