Misprogramming of arrival transition to dfw results in track deviation for carj.

Attributes
ACN	725658
Time
Date	200702
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : pxv.vortac
State Reference	IN
Altitude	msl single value : 36000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	Regional Jet 700 ER&LR
Operating Under FAR Part	Part 121
Navigation In Use	other Other
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : atp
Experience	flight time last 90 days : 150 flight time total : 7800 flight time type : 300
ASRS Report	725658
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory flight crew : returned to intended or assigned course
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft Chart Or Publication
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While en route we received a WX update for dfw. We changed our landing runway in our FMS to reflect the current operations at dfw. While updating our landing runway; we inadvertently entered the fsm VOR transition to the BONHAM5 arrival to dfw; as opposed to our original clearance which was the lit VOR transition to the BONHAM5 arrival to dfw. Approximately 10 miles past pxv VOR; ATC advised that we were north of course and issued a heading to fly to get back on our flight plan route. Once we resolved the confusion with ATC over which transition we were to fly; we revised our routing in our FMS; intercepted the course and proceeded on our flight plan route with no further incident. After review of this incident; I realized that we often fly the fsm VOR transition to this arrival to dfw; so the mistake was easily overlooked. To prevent this in the future; I think it would be a good practice to reconfirm the entire flight plan route any time a change is made in the FMS; as to the current practice of verifying just the perceived changes.

Original NASA ASRS Text

Title: MISPROGRAMMING OF ARR TRANSITION TO DFW RESULTS IN TRACK DEV FOR CARJ.

Narrative: WHILE ENRTE WE RECEIVED A WX UPDATE FOR DFW. WE CHANGED OUR LNDG RWY IN OUR FMS TO REFLECT THE CURRENT OPERATIONS AT DFW. WHILE UPDATING OUR LNDG RWY; WE INADVERTENTLY ENTERED THE FSM VOR TRANSITION TO THE BONHAM5 ARR TO DFW; AS OPPOSED TO OUR ORIGINAL CLRNC WHICH WAS THE LIT VOR TRANSITION TO THE BONHAM5 ARR TO DFW. APPROX 10 MILES PAST PXV VOR; ATC ADVISED THAT WE WERE NORTH OF COURSE AND ISSUED A HDG TO FLY TO GET BACK ON OUR FLT PLAN RTE. ONCE WE RESOLVED THE CONFUSION WITH ATC OVER WHICH TRANSITION WE WERE TO FLY; WE REVISED OUR ROUTING IN OUR FMS; INTERCEPTED THE COURSE AND PROCEEDED ON OUR FLT PLAN RTE WITH NO FURTHER INCIDENT. AFTER REVIEW OF THIS INCIDENT; I REALIZED THAT WE OFTEN FLY THE FSM VOR TRANSITION TO THIS ARR TO DFW; SO THE MISTAKE WAS EASILY OVERLOOKED. TO PREVENT THIS IN THE FUTURE; I THINK IT WOULD BE A GOOD PRACTICE TO RECONFIRM THE ENTIRE FLT PLAN RTE ANY TIME A CHANGE IS MADE IN THE FMS; AS TO THE CURRENT PRACTICE OF VERIFYING JUST THE PERCEIVED CHANGES.

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