Distracted during the taxi checklist; an air carrier flight crew failed to set the proper takeoff ru...

Narrative:

We were taxiing out for takeoff on runway 1C. This is an unusual setup for iad. They normally use the east runway; 1R; for takeoff but it was closed this day. As we were taxing out for takeoff; we started the taxi checklist. ATC interrupted that by telling us to switch to tower and they actually gave us the wrong one and then called us back to give us the right frequency. After that we completed the taxi checklist. We were the only ones out there but neither of us felt rushed. After takeoff; we turned to a heading of 340 per tower instructions and after contacting potomac dep.; they told us to proceed direct to zehrn but we didn't show that in the FMS - we showed hefln. After giving us direct to jeres; they told us that hefln was used for runway 30 departures. I double checked the fuel page and sure enough we had runway 30 selected. While there was no deviation; it could have been serious if this was a true RNAV departure - they use headings off all runways at iad.whenever a checklist is interrupted; especially more than once as this one was by the two different ATC calls because of the wrong tower frequency given to us; it is imperative that the checklist is restarted from the beginning; not picked up from where we left off - because you may pick up at the wrong point as we did. Also; we must verify the runway in the FMS with the heading and the runway number as we line up on that runway.

Original NASA ASRS Text

Title: Distracted during the Taxi checklist; an air carrier flight crew failed to set the proper takeoff runway in the FMC. The error was caught when ATC issued clearance to a fix that was not in the FMC.

Narrative: We were taxiing out for takeoff on Runway 1C. This is an unusual setup for IAD. They normally use the east runway; 1R; for takeoff but it was closed this day. As we were taxing out for takeoff; we started the taxi checklist. ATC interrupted that by telling us to switch to Tower and they actually gave us the wrong one and then called us back to give us the right frequency. After that we completed the taxi checklist. We were the only ones out there but neither of us felt rushed. After takeoff; we turned to a heading of 340 per Tower instructions and after contacting Potomac Dep.; they told us to proceed direct to ZEHRN but we didn't show that in the FMS - we showed HEFLN. After giving us direct to JERES; they told us that HEFLN was used for Runway 30 departures. I double checked the fuel page and sure enough we had Runway 30 selected. While there was no deviation; it could have been serious if this was a true RNAV departure - they use headings off all runways at IAD.Whenever a checklist is interrupted; especially more than once as this one was by the two different ATC calls because of the wrong Tower frequency given to us; it is imperative that the checklist is restarted from the beginning; not picked up from where we left off - because you may pick up at the wrong point as we did. Also; we must verify the runway in the FMS with the heading and the runway number as we line up on that runway.

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.

Attributes
ACN	1261027
Time
Date	201505
Local Time Of Day	1201-1800
Place
Locale Reference	IAD.Airport
State Reference	DC
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turboprop Eng
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Flying
Events
Anomaly	Deviation - Procedural Published Material / Policy

Distracted during the taxi checklist; an air carrier flight crew failed to set the proper takeoff runway in the FMC. The error was caught when ATC issued clearance to a fix that was not in the FMC.