Falcon 2000 flight crew reports inadvertently selecting runway 02R in the FMC when attempting to swi...

Narrative:

We were given the RNAV CHSNE2 arrival chsne transition. The flight was uneventful and when checking in with center we were given the south transition. The pilot not flying put the 20C runway in the FMS from ATIS and the arrival fixes and altitude crossings were crosschecked. 20L/right and C all had the same transition on the approach. We started our descent via the CHSNE2 arrival and crosschecked the altitudes again. Upon switching to approach we were given runway 20R and changed the FMS to reflect the right runway from the 20C. The new runway was not cross checked by both pilots and ended up being programmed as 2R; the north runway. This changed the RNAV arrival points from olnah to gdstf we took up a heading via FMS LNAV to 086 to bgstr; instead of picking up an FMS LNAV heading of 066 to olnah. Before we got to bgstr the controller told us it looked like we had taken the north transition and not the south transition. He instructed us to turn to a heading 040 and maintain 5000 feet minimum. We descended from 6300 to 5000 feet and turned to the heading given. There was never a TCAS alert; nor did we hear any other aircraft given instruction due to our deviation. The remainder of the flight was uneventful. The runway change came extremely late in the arrival and almost over the initial transition fix that determined the heading to take for the different runway selections. Upon landing we discussed the error and confirmed the other pilot did not verify the new runway selection. We also tried the programming of the different runway and found that indeed changing the runway changed the arrival points; to what was observed. We have reviewed our sops and will confirm each FMS change against the arrival chart; no matter how close or what phase of flight we are in. This will alert us to a possible deviation much sooner; and has been our standard SOP in the past.

Original NASA ASRS Text

Title: Falcon 2000 flight crew reports inadvertently selecting Runway 02R in the FMC when attempting to switch from Runway 20C to Runway 20R at ATC's direction; late in the arrival. This results in a change to the arrival transition resulting in a track deviation which is corrected by ATC.

Narrative: We were given the RNAV CHSNE2 arrival CHSNE transition. The flight was uneventful and when checking in with center we were given the south transition. The pilot not flying put the 20C runway in the FMS from ATIS and the arrival fixes and altitude crossings were crosschecked. 20L/R and C all had the same transition on the approach. We started our descent via the CHSNE2 arrival and crosschecked the altitudes again. Upon switching to approach we were given Runway 20R and changed the FMS to reflect the right runway from the 20C. The new runway was not cross checked by both pilots and ended up being programmed as 2R; the north runway. This changed the RNAV arrival points from OLNAH to GDSTF we took up a heading via FMS LNAV to 086 to BGSTR; instead of picking up an FMS LNAV heading of 066 to OLNAH. Before we got to BGSTR the controller told us it looked like we had taken the north transition and not the south transition. He instructed us to turn to a HDG 040 and maintain 5000 Feet minimum. We descended from 6300 to 5000 feet and turned to the HDG given. There was never a TCAS alert; nor did we hear any other aircraft given instruction due to our deviation. The remainder of the flight was uneventful. The runway change came extremely late in the arrival and almost over the initial transition fix that determined the heading to take for the different runway selections. Upon landing we discussed the error and confirmed the other pilot did not verify the new runway selection. We also tried the programming of the different runway and found that indeed changing the runway changed the arrival points; to what was observed. We have reviewed our SOPs and will confirm each FMS change against the arrival chart; no matter how close or what phase of flight we are in. This will alert us to a possible deviation much sooner; and has been our standard SOP in the past.

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	1274907
Time
Date	201506
Local Time Of Day	1201-1800
Place
Locale Reference	BNA.Airport
State Reference	TN
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Falcon 2000
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	STAR CHSNE2 Arrival
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Commercial
Experience	Flight Crew Last 90 Days 90 Flight Crew Total 16500 Flight Crew Type 450
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 250 Flight Crew Total 8200 Flight Crew Type 450
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Falcon 2000 flight crew reports inadvertently selecting runway 02R in the FMC when attempting to switch from runway 20C to runway 20R at ATC's direction; late in the arrival. This results in a change to the arrival transition resulting in a track deviation which is corrected by ATC.