Improper FMC entry results in a track deviation.

Attributes
ACN	534978
Time
Date	200201
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : pxr.vortac
State Reference	AZ
Altitude	msl single value : 5000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 7500 flight time type : 4500
ASRS Report	534978
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	non adherence : published procedure non adherence : clearance non adherence : company policies other spatial deviation
Independent Detector	other controllerb
Resolutory Action	controller : issued advisory controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Flight plan was filed via sjn 1 departure to abq. Actual clearance was dryheat 2 J74 irw as filed. We entered J74 in the FMS from sjn to dryheat, but failed to change actual departure. Departure control saw us fly the wrong departure and got us back on course. Captain entered flight plan in accordance with SOP's. I pointed out change of clearance from pre departure clearance. Captain entered routing change but did not change departure. I failed to note error while checking route in mcdu. Prior to taxi, ground control changed runway to runway 8 vice runway 7L,. I changed runway but did not notice wrong departure as we started to taxi. Requested new weight data for takeoff. Prior to takeoff, I read verbal description from correct (dryheat 2) departure and noted first 2 points on mcdu flight plan scroll as 078 degrees (runway heading) and 080 degrees (initial climb). These looked and were correct and I concentrated on visual clearing until departure control asked where we were going. No other traffic affected. In addition, during engine start, both generators faulted and had to be reset. Distrs should not have caused me to miss departure change.

Original NASA ASRS Text

Title: IMPROPER FMC ENTRY RESULTS IN A TRACK DEV.

Narrative: FLT PLAN WAS FILED VIA SJN 1 DEP TO ABQ. ACTUAL CLRNC WAS DRYHEAT 2 J74 IRW AS FILED. WE ENTERED J74 IN THE FMS FROM SJN TO DRYHEAT, BUT FAILED TO CHANGE ACTUAL DEP. DEP CTL SAW US FLY THE WRONG DEP AND GOT US BACK ON COURSE. CAPT ENTERED FLT PLAN IN ACCORDANCE WITH SOP'S. I POINTED OUT CHANGE OF CLRNC FROM PDC. CAPT ENTERED ROUTING CHANGE BUT DID NOT CHANGE DEP. I FAILED TO NOTE ERROR WHILE CHKING RTE IN MCDU. PRIOR TO TAXI, GND CTL CHANGED RWY TO RWY 8 VICE RWY 7L,. I CHANGED RWY BUT DID NOT NOTICE WRONG DEP AS WE STARTED TO TAXI. REQUESTED NEW WT DATA FOR TKOF. PRIOR TO TKOF, I READ VERBAL DESCRIPTION FROM CORRECT (DRYHEAT 2) DEP AND NOTED FIRST 2 POINTS ON MCDU FLT PLAN SCROLL AS 078 DEGS (RWY HDG) AND 080 DEGS (INITIAL CLB). THESE LOOKED AND WERE CORRECT AND I CONCENTRATED ON VISUAL CLRING UNTIL DEP CTL ASKED WHERE WE WERE GOING. NO OTHER TFC AFFECTED. IN ADDITION, DURING ENG START, BOTH GENERATORS FAULTED AND HAD TO BE RESET. DISTRS SHOULD NOT HAVE CAUSED ME TO MISS DEP CHANGE.

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