Airbus captain states that his aircraft does not comply with the fnchr 1 RNAV arrival to mem using f...

Attributes
ACN	1042776
Time
Date	201210
Local Time Of Day	0001-0600
Place
Locale Reference	MEM.Airport
State Reference	TN
Aircraft 1
Make Model Name	Airbus Industrie Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR FNCHR1
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Flying
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 Published Material / Policy

Narrative:

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 first officer 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.

Original NASA ASRS Text

Title: 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.

Narrative: 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.

Data retrieved from NASA's ASRS site as of July 2013 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.

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.