Airbus Industrie Undifferentiated or Other Model
Flight Crew Air Transport Pilot (ATP)
Human-Machine Interface
Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Aircraft; Human Factors
At the FNCHR fix on the FNCHR 1 RNAV arrival to MEM. The airbus FMS system does not display the altitude window (10;000 to 16;000) at FNCHR as any kind of constraint. We attempted to fly the arrival in full automation (profile) but early in the arrival we had to resort to level change and manual speed control. I was distracted by doing everything manually and was relying on the displayed constraints on the ND. The F/O noticed (late) about a half mile past FNCHR we were about 200 feet high. So I estimate we were about 300 high (16;300) at FNCHR. Always enter something manually at every fix if it does not display it as part of the loaded nav data base. Then if you do not reference the plate (which I should for every upcoming fix anyway) and rely on the Nav Display as I did; you won't miss a restriction. Do not ever trust the Airbus to fly any of these arrivals as published in profile. I have not talked to one pilot that has had any luck doing this.
Airbus Captain states that his aircraft does not comply with the FNCHR 1 RNAV arrival to MEM using full automation and the altitude window at FNCHR is not displayed on the ND.