37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1228557 |
Time | |
Date | 201412 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DEN.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR ANCHR3 |
Flight Plan | IFR |
Component | |
Aircraft Component | Autoflight System |
Person 1 | |
Function | First Officer Pilot Flying |
Experience | Flight Crew Last 90 Days 169 |
Person 2 | |
Function | Pilot Not Flying Captain |
Experience | Flight Crew Last 90 Days 176 Flight Crew Type 11000 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Miss Distance | Vertical 300 |
Narrative:
Descending via ANCHR3 arrival into den expecting runway 35R. Several approach clearance changes inbound (runway changed from 16 to 35) changed to anchr arrival. We reprogrammed the FMC and set up for the ANCHR3 followed by visual approach to 35R backed up by the ILS. Approaching doggg; we were cleared for the RNAV rnpz approach to 35R. We quickly pulled up the new approach on our efb and I intended to enter the 35R rnp Z approach into the FMC but inadvertently selected the 34R rnp Z approach without realizing it. I quickly briefed the points while selecting .3RNP; but we were VMC with the field in sight; being instructed to slow to 170 knots getting traffic point outs and configuring with gear and flaps to slow down. The first two points are the same for both approaches (doggg and msims) before the 34R approach continues west across the 35L approach corridor to a final on 34R. We didn't catch the error and continued to configure. As we approached the centerline for 35R; it didn't appear that the plane was turning so I disengaged the autopilot and took over visually to not overshoot continuing to a normal landing. In retrospect; I believe the end game visual approach closely tracked both vertical and lateral course of the rnp approach. However; there was traffic on final to 35L and if we had not noticed the error and intervened; we could have easily caused a conflict
Original NASA ASRS Text
Title: An air carrier crew entered the FMS ANCHR3 arrival and to expect Runway 35R RNAV RNPZ but mistakenly entered Runway 34R. After a TA alert; they flew the remainder of the 35R approach visually and landed uneventfully.
Narrative: Descending via ANCHR3 Arrival into DEN expecting Runway 35R. Several approach clearance changes inbound (runway changed from 16 to 35) changed to ANCHR Arrival. We reprogrammed the FMC and set up for the ANCHR3 followed by visual approach to 35R backed up by the ILS. Approaching DOGGG; we were cleared for the RNAV RNPZ approach to 35R. We quickly pulled up the new approach on our EFB and I intended to enter the 35R RNP Z approach into the FMC but inadvertently selected the 34R RNP Z approach without realizing it. I quickly briefed the points while selecting .3RNP; but we were VMC with the field in sight; being instructed to slow to 170 knots getting traffic point outs and configuring with gear and flaps to slow down. The first two points are the same for both approaches (DOGGG and MSIMS) before the 34R approach continues W across the 35L approach corridor to a final on 34R. We didn't catch the error and continued to configure. As we approached the centerline for 35R; it didn't appear that the plane was turning so I disengaged the autopilot and took over visually to not overshoot continuing to a normal landing. In retrospect; I believe the end game visual approach closely tracked both vertical and lateral course of the RNP approach. However; there was traffic on final to 35L and if we had not noticed the error and intervened; we could have easily caused a conflict
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.