Narrative:

We were cleared direct druzz; cross at 15;000 ft; 250 KIAS. Then after an ATC handoff; potomac stated; 'cleared to descend via the eldee 3 arrival.' prior to this point; 'all' fixes had been checked/verified for proper entry using the arrival chart; FMGC; and I also used the pfd in the plan mode with the fcp 'const' button to further check proper entry. Once the aircraft engaged into the altitude hold position at 15;000 ft; pilot flying requested and I set 12;000 ft for the next restriction at pugee. Making the crossing; the pilot flying pulled for open descent to meet the pugee altitude. Moments later; ATC then stated; 'air carrier X; check your altitude.' we did; and all appeared fine (meeting pugee altitude and altimeters properly set). I then immediately rechecked the arrival and realized we missed the 'revue at 15;000 ft restriction.' we remained focused and completed the arrival to an uneventful visual approach to runway 1. Sky was clear; minimum traffic. During descent; we did notice the arrival altitudes had dropped out of the FMGC. The pilot flying re-entered our current altitude of FL290 to re-engaged the cruise phase and subsequent restrictions. I then noticed all the magenta altitude restrictions reappear on the pfd. Pilot flying then descended to 15;000 ft. However; I did not notice that the revue parameter did not reload into the vertical path. I made the error of trusting the FMGC to reload 'all' the proper restraints when I saw the magenta altitudes reappear as having just checked them against the STAR chart. On this recheck; I evidently scanned right over the revue altitude and went to the next restriction (pugee) and then the rest. All appeared correct. Revue should have loaded for the restriction like every other fix on the arrival; but it did not. We should not have re-entered the cruise phase and just used the chart and backed it up with one another. Fly the aircraft first. Automation second. Arrival helps via automation should be used as assistance. When we were in the actual arrival phase that is not the time to get bogged down with the FMGC. We had all the tools needed to safely and accurately complete the arrival -- a chart! It can and did actually cause a distraction and subsequent error because we allowed it to be used as a primary reference. In the future; should this happen again; I will focus all attention to the chart; period. It is the fastest; easiest; and 'the' source document. An immediate TCAS scan above; at; and below did not reveal any proximity traffic. I am so thankful it turned out s it did and the flight landed without further incident. Paper backup is now my first and last master reference.

Google
 

Original NASA ASRS Text

Title: A319 flight crew reports missing crossing restriction at REVUE on the ELDEE4 arrival to DCA. Restriction dropped from FMGC for unknown reasons.

Narrative: We were cleared direct DRUZZ; cross at 15;000 FT; 250 KIAS. Then after an ATC handoff; Potomac stated; 'cleared to descend via the ELDEE 3 arrival.' Prior to this point; 'all' fixes had been checked/verified for proper entry using the arrival chart; FMGC; and I also used the PFD in the Plan Mode with the FCP 'CONST' button to further check proper entry. Once the aircraft engaged into the altitude hold position at 15;000 FT; Pilot Flying requested and I set 12;000 FT for the next restriction at PUGEE. Making the crossing; the Pilot Flying pulled for open descent to meet the PUGEE altitude. Moments later; ATC then stated; 'Air Carrier X; check your altitude.' We did; and all appeared fine (meeting PUGEE altitude and altimeters properly set). I then immediately rechecked the arrival and realized we missed the 'REVUE at 15;000 FT restriction.' We remained focused and completed the arrival to an uneventful visual approach to Runway 1. Sky was clear; minimum traffic. During descent; we did notice the arrival altitudes had dropped out of the FMGC. The Pilot Flying re-entered our current altitude of FL290 to re-engaged the cruise phase and subsequent restrictions. I then noticed all the magenta altitude restrictions reappear on the PFD. Pilot Flying then descended to 15;000 FT. However; I did not notice that the REVUE parameter did not reload into the vertical path. I made the error of trusting the FMGC to reload 'all' the proper restraints when I saw the magenta altitudes reappear as having just checked them against the STAR chart. On this recheck; I evidently scanned right over the REVUE altitude and went to the next restriction (PUGEE) and then the rest. All appeared correct. REVUE should have loaded for the restriction like every other fix on the arrival; but it did not. We should not have re-entered the cruise phase and just used the chart and backed it up with one another. Fly the aircraft first. Automation second. Arrival helps via automation should be used as assistance. When we were in the actual arrival phase that is not the time to get bogged down with the FMGC. We had all the tools needed to safely and accurately complete the arrival -- a chart! It can and did actually cause a distraction and subsequent error because we allowed it to be used as a primary reference. In the future; should this happen again; I will focus all attention to the chart; period. It is the fastest; easiest; and 'the' source document. An immediate TCAS scan above; at; and below did not reveal any proximity traffic. I am so thankful it turned out s it did and the flight landed without further incident. Paper backup is now my first and last master reference.

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