37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1128652 |
Time | |
Date | 201311 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZTL.ARTCC |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR IVANE |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Clearance |
Narrative:
We were flying the ivane RNAV STAR routing. We had checked to be certain that the arrival was set up and briefed the way it was charted. At some point we were cleared to cross mayos at FL220. The fact that it was a hard altitude as opposed to the window of FL260 to FL220 didn't dawn on me until we were too high to make the crossing restriction. We advised ATC we not be able to make the restriction. The first officer was the flying pilot and I was the monitoring pilot.I think this was a case of thinking you heard what you expected to hear and not what was really said. We expected to cross mayos as per the opd [optimized profile descent] and the lower; hard altitude was not what was loaded.if we are going to be expected to fly these types of arrivals; then let us fly them as published. If ATC keeps modifying these things mistakes of this kind will probably continue. We've been given a lot of guidance on these arrivals. But what I was not prepared for (but will be in the future) was for a significant modification that involved not being cleared to descend via; but instead simple step down altitudes that completely negate what was set up in the FMS. We don't need these complicated arrivals in 2013 if our clearances only mimic the arrivals of 20 years ago. Clear us and let us do it and get out of our way or give us less complicated arrivals. If ATC can't or won't do it; then I fail to see the value of opd's.
Original NASA ASRS Text
Title: When cleared to cross MAYOS at FL220 (vice the charted 'between FL260 & FL220') on the IVANE RNAV STAR to CLT; the Pilot Not Flying of an A321 failed to program the change in the FMS and; as a result; was unable to comply with the more restrictive clearance. The reporter took umbrage with the frequency with which ATC modifies OPD (Optimized Profile Descent) STARs rather than clearing flights to descend 'via' them.
Narrative: We were flying the IVANE RNAV STAR routing. We had checked to be certain that the arrival was set up and briefed the way it was charted. At some point we were cleared to cross MAYOS at FL220. The fact that it was a hard altitude as opposed to the window of FL260 to FL220 didn't dawn on me until we were too high to make the crossing restriction. We advised ATC we not be able to make the restriction. The First Officer was the Flying Pilot and I was the Monitoring Pilot.I think this was a case of thinking you heard what you expected to hear and not what was really said. We expected to cross MAYOS as per the OPD [Optimized Profile Descent] and the lower; hard altitude was not what was loaded.If we are going to be expected to fly these types of arrivals; then let us fly them as published. If ATC keeps modifying these things mistakes of this kind will probably continue. We've been given a lot of guidance on these arrivals. But what I was not prepared for (but will be in the future) was for a significant modification that involved not being cleared to descend via; but instead simple step down altitudes that completely negate what was set up in the FMS. We don't need these complicated arrivals in 2013 if our clearances only mimic the arrivals of 20 years ago. Clear us and let us do it and get out of our way or give us less complicated arrivals. If ATC can't or won't do it; then I fail to see the value of OPD's.
Data retrieved from NASA's ASRS site as of July 2013 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.