37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1699721 |
Time | |
Date | 201911 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DEN.Airport |
State Reference | CO |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Undershoot Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I believe the factors include a very busy flight deck coordinating and loading 2 different arrivals with descend via clearances; especially into den which has very specific transitions based on runways. This also includes changing the runway assignment close to the runway specific transition.I also believe the lido charts do not depict the mandatory altitudes clearly. A good example is to review the same jepp chart which breaks out the transitions and uses the word 'mandatory' on the chart depiction. It's an easy altitude to miss on the lidos especially during a high workload cockpit situations.another factor is ATC phraseology. When given an approach clearance with an altitude limit the 'cross xxxxx at 9;000 feet; cleared ILS 34R' is used. I understand bfree is a charted mandatory altitude; but that is not the norm; and is misleading.during the high workload environment of transitioning from a STAR to an ILS while being slowed by ATC my attention was also split to monitoring and providing guidance of aircraft and avionics configurations to a brand new first officer.an additional factor is SOP briefing guidance for approaches. It only speaks to brief initial approach altitude; GS intercept or FAF crossing altitude and minimums altitude. There is no guidance to brief any mandatory altitudes after the IAF which bfree was.the last factor is training. We do not train RNAV STAR to RNAV ILS transitions.while descending via the LDORA2 arrival in to den we received a new clearance to descend via the TELLR2 arrival. We loaded the new arrival and briefed the all the crossing restrictions and speeds on the new arrival from the runway assigned from TRACON. Somewhere around the thruu intersection we were told to change runway assignments from runway 35L to runway 34R. We quickly briefed the new runway; loaded new approach speeds; and loaded the new runway in to the FMS. At around narle we were told 'cleared for ILS runway 34R from tellr.' we completed the RNAV turn onto the inbound course; went to green needles and armed the approach. We then landed without incident. We were told on the ground that there was a potential pilot deviation. After speaking with an air traffic manager we were told that we did not descend to cross bfree at 10;000 feet; but that we were on profile for the rest of the STAR and ILS.
Original NASA ASRS Text
Title: CRJ-700 flight crew reported missing an altitude crossing restriction during approach to DEN airport.
Narrative: I believe the factors include a very busy flight deck coordinating and loading 2 different arrivals with descend via clearances; especially into DEN which has very specific transitions based on runways. This also includes changing the runway assignment close to the runway specific transition.I also believe the LIDO charts do not depict the mandatory altitudes clearly. A good example is to review the same JEPP chart which breaks out the transitions and uses the word 'MANDATORY' on the chart depiction. It's an easy altitude to miss on the LIDOs especially during a high workload cockpit situations.Another factor is ATC phraseology. When given an approach clearance with an altitude limit the 'cross XXXXX at 9;000 feet; cleared ILS 34R' is used. I understand BFREE is a charted mandatory altitude; but that is not the norm; and is misleading.During the high workload environment of transitioning from a STAR to an ILS while being slowed by ATC my attention was also split to monitoring and providing guidance of aircraft and avionics configurations to a brand new First Officer.An additional factor is SOP briefing guidance for approaches. It only speaks to brief initial approach altitude; GS intercept or FAF crossing altitude and minimums altitude. There is no guidance to brief any mandatory altitudes AFTER the IAF which BFREE was.The last factor is training. We do not train RNAV STAR to RNAV ILS transitions.While descending via the LDORA2 arrival in to DEN we received a new clearance to descend via the TELLR2 arrival. We loaded the new arrival and briefed the all the crossing restrictions and speeds on the new arrival from the runway assigned from TRACON. Somewhere around the THRUU Intersection we were told to change runway assignments from Runway 35L to Runway 34R. We quickly briefed the new runway; loaded new approach speeds; and loaded the new runway in to the FMS. At around NARLE we were told 'cleared for ILS Runway 34R from TELLR.' We completed the RNAV turn onto the inbound course; went to green needles and armed the approach. We then landed without incident. We were told on the ground that there was a potential pilot deviation. After speaking with an air traffic manager we were told that we did not descend to cross BFREE at 10;000 feet; but that we were on profile for the rest of the STAR and ILS.
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.