 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A319 first officer reported falling into the old airbus FMS altitude constraints deleted above cruise altitude trap during descent on the CHSLY1. The flight had originally been cruising at FL220 which automatically deleted the burrz FL240 restriction. The flight was then cleared to FL240 for traffic and the burrz restriction was forgotten about.
| Attributes | |
| ACN | 1364551 |
| Time | |
| Date | 201606 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZDC.ARTCC |
| State Reference | VA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
We were filed at FL220 as a final and were at cruising altitude. I had already accomplished my arrival review and noted the altitudes above our cruising altitude had been deleted on the CHSLY1 arrival; specifically burrz between fl 240 and fl 270; but didn't think much of it at the time. ATC then asked us if we could climb to FL240 for traffic; which we did. ATC eventually cleared us to descend via the CHSLY1 arrival; landing north; and the captain dialed in the bottom altitude of 6;000 feet; but was waiting to descend. Between wrlld and bluej; we began to encounter turbulence and the captain began a managed descent. I told him to wait because I thought there were some altitudes that were deleted; and at first saw skles at or above FL220; so the descent continued. Then I saw the burrz restriction and told the captain to stop the descent. At almost the same time; ATC asked about our altitude; which was FL235; and I replied we were climbing back to FL240. ATC said there was no conflicting traffic and asked if it was an FMS issue; which it was. After the flight; the captain called center and said this was almost a daily occurrence. We definitely fell into the airbus FMS altitude constraints deleted above cruise altitude trap. We might have been ok if the center had left us at FL220; but the extra climb put us right into the danger zone. The other factor for me was performing the arrival verification before being recleared to FL240. When I had seen it earlier I thought the burrz restriction wouldn't be a factor since we were not scheduled to climb that high. When we began the early descent I remembered a restriction being deleted but not the details. I spoke up about it immediately; but lost 500 feet before we figured it out. We should have maintained altitude until verifying the restrictions on the chart.
Original NASA ASRS Text
Title: A319 First Officer reported falling into the old Airbus FMS altitude constraints deleted above cruise altitude trap during descent on the CHSLY1. The flight had originally been cruising at FL220 which automatically deleted the BURRZ FL240 restriction. The flight was then cleared to FL240 for traffic and the BURRZ restriction was forgotten about.
Narrative: We were filed at FL220 as a final and were at cruising altitude. I had already accomplished my arrival review and noted the altitudes above our cruising altitude had been deleted on the CHSLY1 arrival; specifically BURRZ between FL 240 and FL 270; but didn't think much of it at the time. ATC then asked us if we could climb to FL240 for traffic; which we did. ATC eventually cleared us to descend via the CHSLY1 arrival; landing north; and the captain dialed in the bottom altitude of 6;000 feet; but was waiting to descend. Between WRLLD and BLUEJ; we began to encounter turbulence and the captain began a managed descent. I told him to wait because I thought there were some altitudes that were deleted; and at first saw SKLES at or above FL220; so the descent continued. Then I saw the BURRZ restriction and told the captain to stop the descent. At almost the same time; ATC asked about our altitude; which was FL235; and I replied we were climbing back to FL240. ATC said there was no conflicting traffic and asked if it was an FMS issue; which it was. After the flight; the captain called center and said this was almost a daily occurrence. We definitely fell into the Airbus FMS altitude constraints deleted above cruise altitude trap. We might have been ok if the center had left us at FL220; but the extra climb put us right into the danger zone. The other factor for me was performing the arrival verification before being recleared to FL240. When I had seen it earlier I thought the BURRZ restriction wouldn't be a factor since we were not scheduled to climb that high. When we began the early descent I remembered a restriction being deleted but not the details. I spoke up about it immediately; but lost 500 feet before we figured it out. We should have maintained altitude until verifying the restrictions on the chart.
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.