Narrative:

Initial cruise altitude FL180 with washington center. We later climbed to FL240 due to turbulence. We were given the clearance descend via the IVANE5. We set the bottom altitude of 6;000 feet and armed the descent mode 10 miles prior to top of descent. Aircraft started down and crossed mayos intersection at 280 knots and FL220; mayos has a constraint of 280 knots and cross between FL260 & FL240. Because of the initial cruise altitude of FL180; the higher altitude constraints were deleted by the FMS. After receiving a climb clearance to FL240; we manually re-entered the higher constraints. For mayos we entered 280KTS and a hard altitude of FL240 (our current cruise altitude). All constraints were then re-checked by both pilots and were properly displayed on the navigational display. Approximately 10 miles prior to top of descent I armed the descent mode. At some point the FMS deleted the mayos altitude constraint and descended to FL220 which is the next constraint for kiyen intersection. This resulted in a low crossing over mayos. For many years prior to the ivan arrival; mayos had a FL220 crossing altitude. I believe this helped contribute to our missing the FMS deleting the FL240 constraint over mayos. While flying any RNAV arrival in the airbus; I would suggest to continually cross check the RNAV chart to what you see on the navigational display throughout the descent. This would enable the pilots to catch any FMS constraint deletions that may occur unexpectedly after the initial verification (by both pilots) as required by SOP's.

Related reports:

Google
 

Original NASA ASRS Text

Title: A320 flight crew reported they overshot a charted restriction on an RNAV arrival into CLT when the FMS dropped an altitude constraint and the crew did not catch it.

Narrative: Initial cruise altitude FL180 with Washington Center. We later climbed to FL240 due to turbulence. We were given the clearance descend via the IVANE5. We set the bottom altitude of 6;000 feet and armed the descent mode 10 miles prior to top of descent. Aircraft started down and crossed MAYOS intersection at 280 knots and FL220; MAYOS has a constraint of 280 knots and cross between FL260 & FL240. Because of the initial cruise altitude of FL180; the higher altitude constraints were deleted by the FMS. After receiving a climb clearance to FL240; we manually re-entered the higher constraints. For MAYOS we entered 280KTS and a hard altitude of FL240 (our current cruise altitude). All constraints were then re-checked by both pilots and were properly displayed on the navigational display. Approximately 10 miles prior to top of descent I armed the descent mode. At some point the FMS deleted the MAYOS altitude constraint and descended to FL220 which is the next constraint for KIYEN intersection. This resulted in a low crossing over MAYOS. For many years prior to the IVAN arrival; MAYOS had a FL220 crossing altitude. I believe this helped contribute to our missing the FMS deleting the FL240 constraint over MAYOS. While flying any RNAV arrival in the Airbus; I would suggest to continually cross check the RNAV chart to what you see on the navigational display throughout the descent. This would enable the pilots to catch any FMS constraint deletions that may occur unexpectedly after the initial verification (by both pilots) as required by SOP's.

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.