Track deviation due to improperly programmed FMC.

Attributes
ACN	301980
Time
Date	199504
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : aus
State Reference	TX
Altitude	msl bound lower : 19000 msl bound upper : 19000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zhu
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude cruise other ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 10000 flight time type : 1000
ASRS Report	301980
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	atc equipment other atc equipment : unspecified other controllera
Resolutory Action	flight crew : became reoriented flight crew : returned to intended course or assigned course other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While departing austin for dallas and attempting to intercept the 019 degree radial of austin (using navigation mode through the FMS), it was discovered that the 009 degree radial had been inadvertently entered. A correction was immediately initiated when the controller gave a 30 degree heading change and a level at FL190 (we were climbing to FL210). I had spend the time immediately prior to pushback dealing with a situation that was brought up by a passenger. The copilot entered the FMS information (it was his leg). He had only 1 month on the aircraft, but I had been flying with him for 3 days. 5 mins prior to the pushback I finished with the passenger issue and got into the seat. We completed the checklists and pushed back. I had neglected to check the FMS inputs. This is a series of events that continues to point out the fact that in aviation you never take anything for granted. Supplemental information from acn 301234: inexperience on the part of the first officer, and the captain being in the terminal dealing with a passenger problem from a previous leg when the first officer loaded the flight plan in the FMS, and not catching the error on the preflight check caused this situation to develop.

Original NASA ASRS Text

Title: TRACK DEV DUE TO IMPROPERLY PROGRAMMED FMC.

Narrative: WHILE DEPARTING AUSTIN FOR DALLAS AND ATTEMPTING TO INTERCEPT THE 019 DEG RADIAL OF AUSTIN (USING NAV MODE THROUGH THE FMS), IT WAS DISCOVERED THAT THE 009 DEG RADIAL HAD BEEN INADVERTENTLY ENTERED. A CORRECTION WAS IMMEDIATELY INITIATED WHEN THE CTLR GAVE A 30 DEG HDG CHANGE AND A LEVEL AT FL190 (WE WERE CLBING TO FL210). I HAD SPEND THE TIME IMMEDIATELY PRIOR TO PUSHBACK DEALING WITH A SIT THAT WAS BROUGHT UP BY A PAX. THE COPLT ENTERED THE FMS INFO (IT WAS HIS LEG). HE HAD ONLY 1 MONTH ON THE ACFT, BUT I HAD BEEN FLYING WITH HIM FOR 3 DAYS. 5 MINS PRIOR TO THE PUSHBACK I FINISHED WITH THE PAX ISSUE AND GOT INTO THE SEAT. WE COMPLETED THE CHKLISTS AND PUSHED BACK. I HAD NEGLECTED TO CHK THE FMS INPUTS. THIS IS A SERIES OF EVENTS THAT CONTINUES TO POINT OUT THE FACT THAT IN AVIATION YOU NEVER TAKE ANYTHING FOR GRANTED. SUPPLEMENTAL INFO FROM ACN 301234: INEXPERIENCE ON THE PART OF THE FO, AND THE CAPT BEING IN THE TERMINAL DEALING WITH A PAX PROB FROM A PREVIOUS LEG WHEN THE FO LOADED THE FLT PLAN IN THE FMS, AND NOT CATCHING THE ERROR ON THE PREFLT CHK CAUSED THIS SIT TO DEVELOP.

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.