An air carrier pilot reports expecting a dca runway 1 approach but being assigned runway 19. Aircraf...

Attributes
ACN	769772
Time
Date	200801
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dca.airport
State Reference	DC
Altitude	msl single value : 15000
Aircraft 1
Controlling Facilities	artcc : zdc.artcc
Operator	common carrier : air carrier
Make Model Name	Boeing Company Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : eldee
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
ASRS Report	769772
Person 2
Affiliation	government : faa
Function	controller : radar
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : company policies non adherence : clearance non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : unable
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were cleared to cross revue at 15000 ft on the ELDEE2 to dca. We selected the altitudes correctly and the captain selected prof. The aircraft began the descent as expected but as we neared that fix we noticed that the aircraft was high. We reached the 15000 ft clearance altitude within about 2 mi after revue. ATC did ask us if we were on the ELDEE2. I responded that we were but we would probably not make revue at 15000 ft due to an issue with the FMS. Nothing more was said about it from ATC. Near the time that we discovered that the aircraft would be high; we had picked up the latest ATIS that indicated that we would be landing runway 19 rather than runway 1. At this time I initiated a runway change in the FMS. The FMS also doubled up much of the arrival after I did this. I suspect that this is why the aircraft had trouble with the profile. I also suspect; but can't confirm that the reason the arrival was doubled up was probably because I may have selected a point too far along the arrival to do the lateral revision. The ELDEE2 splits at eldee and I suspect that I did the revision off of sabbi inadvertently.

Original NASA ASRS Text

Title: AN ACR PILOT REPORTS EXPECTING A DCA RWY 1 APCH BUT BEING ASSIGNED RWY 19. ACFT WAS HIGH AT THE ELDEE 2 REVUE'S INTXN MISSING THE CONSTRAINT BY 2 MILES.

Narrative: WE WERE CLRED TO CROSS REVUE AT 15000 FT ON THE ELDEE2 TO DCA. WE SELECTED THE ALTS CORRECTLY AND THE CAPT SELECTED PROF. THE ACFT BEGAN THE DSCNT AS EXPECTED BUT AS WE NEARED THAT FIX WE NOTICED THAT THE ACFT WAS HIGH. WE REACHED THE 15000 FT CLRNC ALT WITHIN ABOUT 2 MI AFTER REVUE. ATC DID ASK US IF WE WERE ON THE ELDEE2. I RESPONDED THAT WE WERE BUT WE WOULD PROBABLY NOT MAKE REVUE AT 15000 FT DUE TO AN ISSUE WITH THE FMS. NOTHING MORE WAS SAID ABOUT IT FROM ATC. NEAR THE TIME THAT WE DISCOVERED THAT THE ACFT WOULD BE HIGH; WE HAD PICKED UP THE LATEST ATIS THAT INDICATED THAT WE WOULD BE LNDG RWY 19 RATHER THAN RWY 1. AT THIS TIME I INITIATED A RWY CHANGE IN THE FMS. THE FMS ALSO DOUBLED UP MUCH OF THE ARR AFTER I DID THIS. I SUSPECT THAT THIS IS WHY THE ACFT HAD TROUBLE WITH THE PROFILE. I ALSO SUSPECT; BUT CAN'T CONFIRM THAT THE REASON THE ARR WAS DOUBLED UP WAS PROBABLY BECAUSE I MAY HAVE SELECTED A POINT TOO FAR ALONG THE ARR TO DO THE LATERAL REVISION. THE ELDEE2 SPLITS AT ELDEE AND I SUSPECT THAT I DID THE REVISION OFF OF SABBI INADVERTENTLY.

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.

An air carrier pilot reports expecting a dca runway 1 approach but being assigned runway 19. Aircraft was high at the eldee 2 revue's intersection missing the constraint by 2 miles.