37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1293808 |
Time | |
Date | 201509 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZDV.ARTCC |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Beginning the kippr three arrival into den; ATC assigned FL280. Prior to reaching sushe; ATC assigned descend via the kippr three arrival. Pilot flying (PF) started descent from FL280 prior to passing sushe; which had the restriction of FL300 or above. Pilot monitoring (pm) advised ATC of the descent to which ATC responded 'roger'. Passing through FL200; ATC inquired as to why the descent was started prior to sushe. The pm explained that given our altitude being lower than the restriction at sushe; we had interpreted we could begin descending. ATC responded that we were supposed to maintain FL280 until after sushe. ATC then handed us off to the next controller; and we continued on the arrival; meeting all altitude and speed restrictions. The flight concluded with no more issues/deviations.there was a misinterpretation of what was expected at sushe. Given that the aircraft was assigned FL280; lower than the crossing restriction at sushe; the PF interpreted that there was no addition restrictions and began decent to meet the subsequent altitude/speed restrictions. It wasn't until later that ATC explained we needed to maintain FL280 until sushe; regardless of the published altitude.the flight crew should spend more time briefing the arrival; which may have allowed us to recognize the unique situation. From there; an inquiry can be made to ATC as to what is expected at sushe or other applicable fixes. Another mitigation strategy would be to hold off on descending until passing the first fix with a crossing restriction when given 'descend via' when the aircraft is at a lower altitude; unless confirmed by ATC. In addition; if ATC clears 'cross sushe at FL280; then descend via...' in a similar nonstandard situation; it would have been clear as to what the expectation was for the arrival.
Original NASA ASRS Text
Title: A flight was cleared to descend and maintain FL280 on the DEN KIPPR 3 STAR; 2;000 feet below the charted SUSHE FL300 constraint. The confused crew continued the descent to cross ANCHR near FL240. ATC queried the crew about the continued descend below FL280 prior to SUSHE.
Narrative: Beginning the KIPPR THREE arrival into DEN; ATC assigned FL280. Prior to reaching SUSHE; ATC assigned descend via the KIPPR THREE arrival. Pilot Flying (PF) started descent from FL280 prior to passing SUSHE; which had the restriction of FL300 or above. Pilot Monitoring (PM) advised ATC of the descent to which ATC responded 'Roger'. Passing through FL200; ATC inquired as to why the descent was started prior to SUSHE. The PM explained that given our altitude being lower than the restriction at SUSHE; we had interpreted we could begin descending. ATC responded that we were supposed to maintain FL280 until after SUSHE. ATC then handed us off to the next controller; and we continued on the arrival; meeting all altitude and speed restrictions. The flight concluded with no more issues/deviations.There was a misinterpretation of what was expected at SUSHE. Given that the aircraft was assigned FL280; lower than the crossing restriction at SUSHE; the PF interpreted that there was no addition restrictions and began decent to meet the subsequent altitude/speed restrictions. It wasn't until later that ATC explained we needed to maintain FL280 until SUSHE; regardless of the published altitude.The flight crew should spend more time briefing the arrival; which may have allowed us to recognize the unique situation. From there; an inquiry can be made to ATC as to what is expected at SUSHE or other applicable fixes. Another mitigation strategy would be to hold off on descending until passing the first fix with a crossing restriction when given 'descend via' when the aircraft is at a lower altitude; unless confirmed by ATC. In addition; if ATC clears 'Cross SUSHE at FL280; then descend via...' in a similar nonstandard situation; it would have been clear as to what the expectation was for the arrival.
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.