37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1142125 |
Time | |
Date | 201401 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | D01.TRACON |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | STAR MOLTN TWO RNAV |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Experience | Flight Crew Last 90 Days 225 Flight Crew Total 12000 Flight Crew Type 7000 |
Person 2 | |
Function | Pilot Flying First Officer |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
The captain was pilot not flying and the first officer was the pilot flying to den. The flight time was 1:22 with light to moderate turbulence and mountain wave during the descent into denver. The first officer is on high minimums. I believe he did not have a lot of experience using FMC in complex arrival settings. The captain was new to the seat. During a short time we had 3 runway changes; 2 SID transition changes and numerous airspeed and altitude changes that did correspond with the airspeed and altitudes and the actual moltn 2 arrival. The 3rd runway change was the RNAV Z (rnp) 34R. The weather was clear and this was our 3rd flight together. The CRM setting was above average between the two crew members. The airplane has speed and altitude intervention. The error occurred on the moltn 2 arrival. We had the arrival programmed with no transition in place since we were given [runway] 35L. About 10 miles from himom ATC changed to RNAV 34R. The pilot flying was looking for charts and pilot not flying was watching airplane. We were then given the clearance cleared RNAV Z 34R himom transition. The pilot flying came back and programmed the FMC and when he moved himom up he put himom on top of himom when there is a discontinuity and I verified and he executed. Since we didn't put himom in the discontinuity boxes it defaulted to the previous route. The error occurred when the pilot not flying was running the approach checklist running through the rnp procedures and didn't monitor. We flew past himom to kalme instead of turning on the transition. ATC asked if we had field in sight and cleared us for visual approach. We landed uneventfully and there was no traffic conflict. I debriefed the first officer on the FMC issues and my failure as a captain to let him get overwhelmed by the ever changing clearances. I wanted him to get experience programming and changing the box instead having him fly the aircraft and the pilot not flying help out with more of the duties.
Original NASA ASRS Text
Title: B737NG flight crew arriving DEN report a track deviation due to multiple ATC adjustments during the arrival; transition changes and three runway changes. The HIMON transition to the RNAV Z 34L is not correctly entered in the FMC and when detected by ATC; the crew is offered a visual approach.
Narrative: The Captain was pilot not flying and the First Officer was the pilot flying to DEN. The flight time was 1:22 with light to moderate turbulence and mountain wave during the descent into Denver. The First Officer is on high minimums. I believe he did not have a lot of experience using FMC in complex arrival settings. The Captain was new to the seat. During a short time we had 3 runway changes; 2 SID transition changes and numerous airspeed and altitude changes that did correspond with the airspeed and altitudes and the actual MOLTN 2 arrival. The 3rd runway change was the RNAV Z (RNP) 34R. The weather was clear and this was our 3rd flight together. The CRM setting was above average between the two crew members. The airplane has speed and altitude intervention. The error occurred on the MOLTN 2 arrival. We had the arrival programmed with no transition in place since we were given [Runway] 35L. About 10 miles from HIMOM ATC changed to RNAV 34R. The pilot flying was looking for charts and pilot not flying was watching airplane. We were then given the clearance cleared RNAV Z 34R HIMOM transition. The pilot flying came back and programmed the FMC and when he moved HIMOM up he put HIMOM on top of HIMOM when there is a discontinuity and I verified and he executed. Since we didn't put HIMOM in the discontinuity boxes it defaulted to the previous route. The error occurred when the pilot not flying was running the Approach Checklist running through the RNP procedures and didn't monitor. We flew past HIMOM to KALME instead of turning on the transition. ATC asked if we had field in sight and cleared us for visual approach. We landed uneventfully and there was no traffic conflict. I debriefed the First Officer on the FMC issues and my failure as a Captain to let him get overwhelmed by the ever changing clearances. I wanted him to get experience programming and changing the box instead having him fly the aircraft and the pilot not flying help out with more of the duties.
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.