An air carrier medium large transport failed to follow its filed airways routing.

Attributes
ACN	255842
Time
Date	199311
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : acy airport : phl
State Reference	NJ
Altitude	msl bound lower : 17000 msl bound upper : 17000
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude ground : preflight
Route In Use	departure other departure sid : sid enroute : on vectors enroute airway : zny
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 10000 flight time type : 250
ASRS Report	255842
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
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:

During FMC preflight we did not notice that our dispatcher had filed us on the #2 stored flight plan (this is always noted in the remarks section). We received our pre departure clearance clearance 'as filed' and departed with the primary route (#1) in the FMC (phl isp 1/#1934). The 2 rtes start out the same, but shortly after we made an incorrect intercept, ATC assigned us vectors to isp (we were the second air carrier X flight to attempt the wrong route that day). Callback conversation with reporter revealed the following information: the reporting captain admits that he goofed -- he did not jerk the flight plan from his first officer's hands and read it to find that they were going on route 2 this evening. 99 plus percent of the time, this air carrier's flts are routed over route 1. On this particular day, several were sent on route 2 and every one made the same mistake when the 2 rtes diverged, partly because the dispatcher didn't emphasize the change in routing. The reporting captain deplores the fact that he can be taken out of the loop while the first officer is punching buttons and getting vital information that often is not properly shared.

Original NASA ASRS Text

Title: AN ACR MLG FAILED TO FOLLOW ITS FILED AIRWAYS ROUTING.

Narrative: DURING FMC PREFLT WE DID NOT NOTICE THAT OUR DISPATCHER HAD FILED US ON THE #2 STORED FLT PLAN (THIS IS ALWAYS NOTED IN THE REMARKS SECTION). WE RECEIVED OUR PDC CLRNC 'AS FILED' AND DEPARTED WITH THE PRIMARY RTE (#1) IN THE FMC (PHL ISP 1/#1934). THE 2 RTES START OUT THE SAME, BUT SHORTLY AFTER WE MADE AN INCORRECT INTERCEPT, ATC ASSIGNED US VECTORS TO ISP (WE WERE THE SECOND ACR X FLT TO ATTEMPT THE WRONG RTE THAT DAY). CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTING CAPT ADMITS THAT HE GOOFED -- HE DID NOT JERK THE FLT PLAN FROM HIS FO'S HANDS AND READ IT TO FIND THAT THEY WERE GOING ON RTE 2 THIS EVENING. 99 PLUS PERCENT OF THE TIME, THIS ACR'S FLTS ARE ROUTED OVER RTE 1. ON THIS PARTICULAR DAY, SEVERAL WERE SENT ON RTE 2 AND EVERY ONE MADE THE SAME MISTAKE WHEN THE 2 RTES DIVERGED, PARTLY BECAUSE THE DISPATCHER DIDN'T EMPHASIZE THE CHANGE IN ROUTING. THE RPTING CAPT DEPLORES THE FACT THAT HE CAN BE TAKEN OUT OF THE LOOP WHILE THE FO IS PUNCHING BUTTONS AND GETTING VITAL INFO THAT OFTEN IS NOT PROPERLY SHARED.

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.