ZLA controller and the A320 flight crew involved reported problems associated with the airbus comput...

Attributes
ACN	1436405
Time
Date	201704
Local Time Of Day	1801-2400
Place
Locale Reference	ZLA.ARTCC
State Reference	CA
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR ANJLL 1
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 8.5
Person 2
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Security

Narrative:

The exact same thing happened with this aircraft; only on a different arrival. Aircraft was landing lax. Level at FL240. Tonight; the altitude restriction busted was glesn; which is charted 240b300. Aircraft was level at FL240; was issued the descend via instructions; and immediately started to descend for the 2nd altitude constraint. While I have not yet spoken to the PIC of this flight; the situation is exactly the same as referenced above; and as I found out last night; is a known issue with airbus aircraft. Descend via/climb via arrivals have been around for ages. We had the civet profile arrival 15-20 years ago. This is nothing new; which is why I am completely and utterly shocked that this issue has not been brought up before; and has not been resolved. While the two events I have witnessed (in less than 24 hours; mind you) have not caused specific safety issues; in relation to smashing into other aircraft or airspace; the possibility of this happening is very real. This is a major safety concern; as far as I'm concerned; and needs to be resolved before something bad happens.1) disallow these airbus aircraft from flying in the NAS.2) since I know #1 isn't going to happen; have them fix their airplane so this doesn't occur over and over again. This is not acceptable.

Original NASA ASRS Text

Title: ZLA Controller and the A320 flight crew involved reported problems associated with the Airbus computer that does not comply with descend via clearances correctly.

Narrative: The exact same thing happened with this aircraft; only on a different arrival. Aircraft was landing LAX. Level at FL240. Tonight; the altitude restriction busted was GLESN; which is charted 240B300. Aircraft was level at FL240; was issued the descend via instructions; and immediately started to descend for the 2nd altitude constraint. While I have not yet spoken to the PIC of this flight; the situation is exactly the same as referenced above; and as I found out last night; is a known issue with Airbus aircraft. Descend via/Climb via arrivals have been around for ages. We had the CIVET profile arrival 15-20 years ago. This is nothing new; which is why I am completely and utterly shocked that this issue has not been brought up before; and has not been resolved. While the two events I have witnessed (in less than 24 hours; mind you) have not caused specific safety issues; in relation to smashing into other aircraft or airspace; the possibility of this happening is very real. This is a major safety concern; as far as I'm concerned; and needs to be resolved before something bad happens.1) Disallow these Airbus aircraft from flying in the NAS.2) Since I know #1 isn't going to happen; have them fix their airplane so this doesn't occur over and over again. This is not acceptable.

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.

ZLA controller and the A320 flight crew involved reported problems associated with the airbus computer that does not comply with descend via clearances correctly.