Narrative:

We were descending on the cliper one RNAV arrival into dca. The approach for ILS 1 had already been briefed and loaded in the FMS by my first officer (PF); landing data for runway 1 was loaded and everything was normal. I was unable to reach dca operations in prior attempts so I tried once again over baltimore and was off frequency for approx one minute. When I finished with my in-range call I noticed we were approaching waypoint eyess on the arrival and the map was showing a turn to the right when it should be left. I grabbed my chart to verify and at the same time the aircraft started a turn to the right. There was frequency congestion and after 30 seconds ATC advised that we were on the arrival for runway 19 (which we already knew). ATC then issued right hand vectors to rejoin the arrival at brunc. Somehow runway 19 was accidentally loaded in the FMS. The runway was changed to ILS 1 in the FMS; we rejoined the arrival and the flight finished with no further issues. I believe I was off freq the first time the approach was loaded and because I had to go off a second time it took my attention away from the oversight of making sure the correct approach/arrival sequence was loaded. It was briefed; discussed; and in our heads we both knew what we wanted to do but had I gone back to check that the correct runway was loaded after being off frequency this wouldn't have happened. I think its important for the pilot monitoring to carefully watch the other pilot load the correct approach especially when there is a directional RNAV arrival involved.

Related reports:

Google
 

Original NASA ASRS Text

Title: With DCA landing north the First Officer incorrectly selects Runway 19 in the FMC and the CLIPR 1 RNAV; resulting in a track deviation at EYESS. The Captain was distracted by communications with the company on COMM 2.

Narrative: We were descending on the CLIPER ONE RNAV ARRIVAL into DCA. The approach for ILS 1 had already been briefed and loaded in the FMS by my First Officer (PF); landing data for runway 1 was loaded and everything was normal. I was unable to reach DCA operations in prior attempts so I tried once again over Baltimore and was off frequency for approx one minute. When I finished with my In-range call I noticed we were approaching waypoint EYESS on the arrival and the map was showing a turn to the right when it should be left. I grabbed my chart to verify and at the same time the aircraft started a turn to the right. There was frequency congestion and after 30 seconds ATC advised that we were on the arrival for Runway 19 (which we already knew). ATC then issued right hand vectors to rejoin the arrival at BRUNC. Somehow Runway 19 was accidentally loaded in the FMS. The runway was changed to ILS 1 in the FMS; we rejoined the arrival and the flight finished with no further issues. I believe I was off freq the first time the approach was loaded and because I had to go off a second time it took my attention away from the oversight of making sure the correct approach/arrival sequence was loaded. It was briefed; discussed; and in our heads we both knew what we wanted to do but had I gone back to check that the correct runway was loaded after being off frequency this wouldn't have happened. I think its important for the pilot monitoring to carefully watch the other pilot load the correct approach especially when there is a directional RNAV arrival involved.

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