Corp jet misprograms flight computer flies 150 mi off course.

Attributes
ACN	204847
Time
Date	199203
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : nwu
State Reference	FO
Altitude	msl bound lower : 35000 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny
Operator	general aviation : corporate
Make Model Name	Medium Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	cruise other
Route In Use	enroute : other oceanic enroute : atlantic
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 7500
ASRS Report	204847
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : clearance non adherence : far other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : became reoriented
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We departed the bermuda control area in route to flann intersection. We had given estimates to flann based upon our navigation equipment (dual IRS, omega, DME) and the flight plan. All fixes had been loaded into our navigation computer by myself, but had not been crosschecked by the other pilot. We crossed the first fix on time and course, the aircraft automatically selected the next fix (flann) and proceeded to track to it. Our flight plan came from commercial WX service in standard format. About 35 min into the next leg of the flight plan the other pilot commented tag aircraft needed to proceed quite a ways northeast on this flight plan. At that moment I looked closely at our course and noted it seemed considerably different than the chart. I had not consulted the chart previously, only the time and fuel on the flight plan. Looking closer at the chart now, and our actual latitude-long I discovered we were 130 NM east of flann intersection. At this time we called commercial radio on HF and told them of the error. ATC contacted us, checked for traffic, then issued us a new routing and direct flann then as filed (bermuda-slc). Going back now and checking the flight computer I found that I entered the longitude of flann the same as the previous fix. The previous fix latitude/long are just above the following on the flight plans. Had we crosschecked each other we would have found this error. We were just coming off a 2 week europe trip, and had spent a long day in the aircraft the previous day. I can only attribute this error to complacency in the cockpit, partially due to an extremely active flight schedule. We had been to europe 3 times in 2 1/2 months plus other domestic flying. There are only 2 of us in the flight department, and we become comfortable with each other. In retrospect any ocean crossing should be treated the same. We cannot tolerate complacency in the cockpit. Supplemental information from duplicate acn 205168. We neglected to load each computer individually, which would have assisted us in catching the error.

Original NASA ASRS Text

Title: CORP JET MISPROGRAMS FLT COMPUTER FLIES 150 MI OFF COURSE.

Narrative: WE DEPARTED THE BERMUDA CTL AREA IN RTE TO FLANN INTXN. WE HAD GIVEN ESTIMATES TO FLANN BASED UPON OUR NAV EQUIP (DUAL IRS, OMEGA, DME) AND THE FLT PLAN. ALL FIXES HAD BEEN LOADED INTO OUR NAV COMPUTER BY MYSELF, BUT HAD NOT BEEN XCHKED BY THE OTHER PLT. WE CROSSED THE FIRST FIX ON TIME AND COURSE, THE ACFT AUTOMATICALLY SELECTED THE NEXT FIX (FLANN) AND PROCEEDED TO TRACK TO IT. OUR FLT PLAN CAME FROM COMMERCIAL WX SVC IN STANDARD FORMAT. ABOUT 35 MIN INTO THE NEXT LEG OF THE FLT PLAN THE OTHER PLT COMMENTED TAG ACFT NEEDED TO PROCEED QUITE A WAYS NE ON THIS FLT PLAN. AT THAT MOMENT I LOOKED CLOSELY AT OUR COURSE AND NOTED IT SEEMED CONSIDERABLY DIFFERENT THAN THE CHART. I HAD NOT CONSULTED THE CHART PREVIOUSLY, ONLY THE TIME AND FUEL ON THE FLT PLAN. LOOKING CLOSER AT THE CHART NOW, AND OUR ACTUAL LAT-LONG I DISCOVERED WE WERE 130 NM E OF FLANN INTXN. AT THIS TIME WE CALLED COMMERCIAL RADIO ON HF AND TOLD THEM OF THE ERROR. ATC CONTACTED US, CHKED FOR TFC, THEN ISSUED US A NEW ROUTING AND DIRECT FLANN THEN AS FILED (BERMUDA-SLC). GOING BACK NOW AND CHKING THE FLT COMPUTER I FOUND THAT I ENTERED THE LONGITUDE OF FLANN THE SAME AS THE PREVIOUS FIX. THE PREVIOUS FIX LAT/LONG ARE JUST ABOVE THE FOLLOWING ON THE FLT PLANS. HAD WE XCHKED EACH OTHER WE WOULD HAVE FOUND THIS ERROR. WE WERE JUST COMING OFF A 2 WK EUROPE TRIP, AND HAD SPENT A LONG DAY IN THE ACFT THE PREVIOUS DAY. I CAN ONLY ATTRIBUTE THIS ERROR TO COMPLACENCY IN THE COCKPIT, PARTIALLY DUE TO AN EXTREMELY ACTIVE FLT SCHEDULE. WE HAD BEEN TO EUROPE 3 TIMES IN 2 1/2 MONTHS PLUS OTHER DOMESTIC FLYING. THERE ARE ONLY 2 OF US IN THE FLT DEPT, AND WE BECOME COMFORTABLE WITH EACH OTHER. IN RETROSPECT ANY OCEAN XING SHOULD BE TREATED THE SAME. WE CANNOT TOLERATE COMPLACENCY IN THE COCKPIT. SUPPLEMENTAL INFO FROM DUPLICATE ACN 205168. WE NEGLECTED TO LOAD EACH COMPUTER INDIVIDUALLY, WHICH WOULD HAVE ASSISTED US IN CATCHING THE ERROR.

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.