Widebody transport flight crew uses computer flight plan in FMS instead of revised clearance.

Attributes
ACN	126180
Time
Date	198910
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ptw
State Reference	PA
Altitude	msl bound lower : 19000 msl bound upper : 19000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : instrument
Experience	flight time last 90 days : 100 flight time total : 18350
ASRS Report	126180
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 20000 flight time type : 100
ASRS Report	126183
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance 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:

Computer flight plan as filed by company: phl direct ptw, ptw 320 degree right to J64 rav direct psb J60 lax. Phl clearance delivered clearance as: lax via rv ptw, ptw 320 degree right to J64, J64 to lax. FMS was loaded by first officer from computer flight plan. After takeoff and handoff to ZNY, center inquired if we were going to join J64. After some discussion we realized that the clearance was different from the computer flight plan. We had failed to detect this difference during out cockpit flight plan. We had failed to detect this difference during our cockpit preflight. Contributing to this failure was the similarity in the routings and the presence of a jump seat rider to whom I was showing the FMS to. Both the first officer and I went to great lengths to assure ourselves that the routing on the computer flight plan was properly loaded in the FMS. We obviously failed to pay enough attention to the ATC clearance as received from clearance delivery. We tend to get so involved in all the computers that we sometimes overlook the basics.

Original NASA ASRS Text

Title: WDB FLT CREW USES COMPUTER FLT PLAN IN FMS INSTEAD OF REVISED CLRNC.

Narrative: COMPUTER FLT PLAN AS FILED BY COMPANY: PHL DIRECT PTW, PTW 320 DEG R TO J64 RAV DIRECT PSB J60 LAX. PHL CLRNC DELIVERED CLRNC AS: LAX VIA RV PTW, PTW 320 DEG R TO J64, J64 TO LAX. FMS WAS LOADED BY FO FROM COMPUTER FLT PLAN. AFTER TKOF AND HDOF TO ZNY, CENTER INQUIRED IF WE WERE GOING TO JOIN J64. AFTER SOME DISCUSSION WE REALIZED THAT THE CLRNC WAS DIFFERENT FROM THE COMPUTER FLT PLAN. WE HAD FAILED TO DETECT THIS DIFFERENCE DURING OUT COCKPIT FLT PLAN. WE HAD FAILED TO DETECT THIS DIFFERENCE DURING OUR COCKPIT PREFLT. CONTRIBUTING TO THIS FAILURE WAS THE SIMILARITY IN THE ROUTINGS AND THE PRESENCE OF A JUMP SEAT RIDER TO WHOM I WAS SHOWING THE FMS TO. BOTH THE F/O AND I WENT TO GREAT LENGTHS TO ASSURE OURSELVES THAT THE ROUTING ON THE COMPUTER FLT PLAN WAS PROPERLY LOADED IN THE FMS. WE OBVIOUSLY FAILED TO PAY ENOUGH ATTN TO THE ATC CLRNC AS RECEIVED FROM CLRNC DELIVERY. WE TEND TO GET SO INVOLVED IN ALL THE COMPUTERS THAT WE SOMETIMES OVERLOOK THE BASICS.

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