 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot reported a navigation error when the aircraft was supposed to turn but did not.
| Attributes | |
| ACN | 1591733 |
| Time | |
| Date | 201811 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | DEN.Airport |
| State Reference | CO |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Type 2048 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
While on arrival for denver we received an arrival change and subsequent runway change due to the landing direction being changed from south to north. We set up on the anchr arrival and loaded the ILS 35R as the expected approach and runway. During this time we were told to maintain speeds that differed from the published speeds on the arrival and were then instructed to fly the rnavz to 35R which we loaded and briefed. In our haste to get the procedure loaded and verify waypoints et al we forgot to sequence the FMC to leave the arrival after doggg and fly the approach. Msims appeared to be the active waypoint with fronz being the next waypoint as both were indicated magenta on the FMC. What we failed to notice was that after doggg the aircraft was programmed to continue straight ahead for 'vectors' off the arrival. We noticed our error right at msims and immediately began to turn the rejoin the course. At the same time ATC noticed our error and gave us vectors for a visual approach to runway 35R. We landed safely without further incident.
Original NASA ASRS Text
Title: Pilot reported a navigation error when the aircraft was supposed to turn but did not.
Narrative: While on arrival for Denver we received an arrival change and subsequent runway change due to the landing direction being changed from south to north. We set up on the ANCHR Arrival and loaded the ILS 35R as the expected approach and runway. During this time we were told to maintain speeds that differed from the published speeds on the arrival and were then instructed to fly the RNAVZ to 35R which we loaded and briefed. In our haste to get the procedure loaded and verify waypoints et al we forgot to sequence the FMC to leave the arrival after DOGGG and fly the approach. MSIMS appeared to be the active waypoint with FRONZ being the next waypoint as both were indicated magenta on the FMC. What we failed to notice was that after DOGGG the aircraft was programmed to continue straight ahead for 'vectors' off the arrival. We noticed our error right at MSIMS and immediately began to turn the rejoin the course. At the same time ATC noticed our error and gave us vectors for a visual approach to Runway 35R. We landed safely without further incident.
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.