Narrative:

We were cleared to descend via the eagul 6 arrival landing runway 8. The arrival had been validated by both pilots. I had briefed a threat regarding difficulties the airbus has on this arrival landing on runway 8 crossing bohtx; geeno and queny. As we approached the homrr fix the autopilot began a level off to cross homrr at 17;000 feet; with the FMA indicating a level off for a hard altitude restriction. The autopilot then started to corrected back to the path as we manually intervened to make sure we successfully meet at or below altitude restriction and stayed on the vertical path. The FMA and pfd; however; continued to show a level off for a hard restriction until we crossed homrr at which point they reacquired the path. I was able to confirm in the mcdu before crossing that the homrr altitude crossing was indeed set correctly for at or below 17;000 [feet] and not at 17;000 feet. We continued to manually intervene to meet the bohx and geeno crossing retractions as this had thrown the descent profile off. An aml entry was made for the FMS anomaly. The eagul 6 arrival continues to be a problematic one for the airbus between homrr and queny; especially when flying an A321 with a tail wind. In this case; we were flying an A319 without a tailwind. I have consistently seen the FMS place itself at the top of the bohtx fix to then have difficulty making the next altitude window and speed at geeno; followed by an attempt to dip under queny to slow and make the hiney restriction. Typically; these issues will present themselves a mile or so outside these fixes leaving next to no time to intervene; while all the time the fsm shows on the vertical path meeting the restrictions. If you don't know what's coming (and even sometimes when you do) you can be caught unawares. In lieu of an adjustment to this segment of the arrival; a special briefing item on the jeppesen company charts regarding this segment of the arrival may help increase unfamiliar crew awareness.

Google
 

Original NASA ASRS Text

Title: A319 Captain reported it appears Airbus aircraft have difficulty complying with altitude restrictions on the EAGUL6 arrival into PHX.

Narrative: We were cleared to descend via the EAGUL 6 arrival landing Runway 8. The arrival had been validated by both pilots. I had briefed a threat regarding difficulties the Airbus has on this arrival landing on Runway 8 crossing BOHTX; GEENO and QUENY. As we approached the HOMRR fix the autopilot began a level off to cross HOMRR at 17;000 feet; with the FMA indicating a level off for a hard altitude restriction. The autopilot then started to corrected back to the path as we manually intervened to make sure we successfully meet at or below altitude restriction and stayed on the vertical path. The FMA and PFD; however; continued to show a level off for a hard restriction until we crossed HOMRR at which point they reacquired the path. I was able to confirm in the MCDU before crossing that the HOMRR altitude crossing was indeed set correctly for at or below 17;000 [feet] and not at 17;000 feet. We continued to manually intervene to meet the BOHX and GEENO crossing retractions as this had thrown the descent profile off. An AML entry was made for the FMS anomaly. The EAGUL 6 arrival continues to be a problematic one for the Airbus between HOMRR and QUENY; especially when flying an A321 with a tail wind. In this case; we were flying an A319 without a tailwind. I have consistently seen the FMS place itself at the top of the BOHTX fix to then have difficulty making the next altitude window and speed at GEENO; followed by an attempt to dip under QUENY to slow and make the HINEY restriction. Typically; these issues will present themselves a mile or so outside these fixes leaving next to no time to intervene; while all the time the FSM shows on the vertical path meeting the restrictions. If you don't know what's coming (and even sometimes when you do) you can be caught unawares. In lieu of an adjustment to this segment of the arrival; a special briefing item on the Jeppesen company charts regarding this segment of the arrival may help increase unfamiliar crew awareness.

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.