Narrative:

We were cleared to descend via the CHSLY2 from an altitude above the bluej FL270 and burrz 280 kts and FL270-FL240 restrictions. Prior to initiating the descent the PF and I had individually verified the arrival per SOP and discussed the message regarding the automation not honoring restrictions with this arrival in particular. For some reason on this particular day managed descent was commanding an unusually high rate of descent and at FL260 it became clear to me (pm) it was not going to honor the burrz at FL240 bottom window. I immediately communicated this to the PF who in turn immediately selected vertical speed zero on the FCU (flight control unit). Due in combination to both the high rate of descent and the 1G logic of the autopilot the aircraft leveled below the 24000 restriction. The PF immediately recaptured the path and continued the arrival.this is a known issue with the airbus on this arrival and it was discussed prior to initiating the descent. Both the PF and pm (myself) were monitoring the path and commented on the high rate of descent. When it became apparent pilot intervention was required the PF intervened immediately and even if uncomfortably high maneuvers with the autopilot off were used to level the aircraft it was not apparent the restriction would have been satisfied. A software fix would be a big help. I have seen numerous occasions were the automation seems satisfied only to attempt to bust a restriction and pilot intervention was required. Also less airspeed changes or changes in energy from ATC to the aircraft as this sets up a 'ripple' effect in regard to later restrictions. And; as always; constant crew vigilance in monitoring the vertical navigation and path.

Google
 

Original NASA ASRS Text

Title: A319 flight crew reported overshooting a crossing restriction on the CLT CHSLY2 Arrival. It appeared to be a problem with the Airbus FMS software not honoring the parameters of this STAR.

Narrative: We were cleared to descend via the CHSLY2 from an altitude above the BLUEJ FL270 and BURRZ 280 kts and FL270-FL240 restrictions. Prior to initiating the descent the PF and I had individually verified the arrival per SOP and discussed the message regarding the automation not honoring restrictions with this arrival in particular. For some reason on this particular day managed descent was commanding an unusually high rate of descent and at FL260 it became clear to me (PM) it was not going to honor the BURRZ at FL240 bottom window. I immediately communicated this to the PF who in turn immediately selected VERT SPEED ZERO on the FCU (Flight Control Unit). Due in combination to both the high rate of descent and the 1G logic of the autopilot the aircraft leveled below the 24000 restriction. The PF immediately recaptured the path and continued the arrival.This is a known issue with the Airbus on this arrival and it was discussed prior to initiating the descent. Both the PF and PM (myself) were monitoring the path and commented on the high rate of descent. When it became apparent pilot intervention was required the PF intervened immediately and even if uncomfortably high maneuvers with the autopilot off were used to level the aircraft it was not apparent the restriction would have been satisfied. A software fix would be a big help. I have seen numerous occasions were the automation seems satisfied only to attempt to bust a restriction and pilot intervention was required. Also less airspeed changes or changes in energy from ATC to the aircraft as this sets up a 'ripple' effect in regard to later restrictions. And; as always; constant crew vigilance in monitoring the vertical navigation and path.

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.