Air carrier deviates from clearance when wrong routing is entered into FMC.

Attributes
ACN	451890
Time
Date	199910
Day	Mon
Local Time Of Day	1201 To 1800
Place
State Reference	UT
Altitude	msl single value : 31000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zla.artcc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : level
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : flight engineer pilot : atp pilot : cfi pilot : commercial
Experience	flight time last 90 days : 100 flight time total : 13000 flight time type : 2400
ASRS Report	451890
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	non adherence : clearance non adherence : company policies other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance Chart Or Publication
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Just prior to pushback, agent gave the first officer our pre departure clearance. I was handed the latest WX and our takeoff performance data. Unknown to me, the first officer changed the routing in the FMS to comply with his understanding of the pre departure clearance. Unfortunately it caused us to deviate from our clearance. Flight planned route was phx.drkg.drk.J11.bce...dta...slc. The pre departure clearance said cleared as filed phx DRK6 drk J11 ***slc. I don't know why but the first officer thought that meant J11 all the way to the slc VOR. Departing bce the controller asked if we were going direct dta. There was no conflict and I don't believe the controller was too worried about it. However, this is an opportunity to point out how inconsistent the pre departure clearance's are. It seems each one is unique. You have to hunt for the departure procedure, some have the departure frequency, some don't. Some have the initial altitude, some don't. Some have the planned route (which I think should be left off the pre departure clearance), some don't. I'd like to see an identify block at the top and the text in the same format used for yrs over the radio from clearance delivery.

Original NASA ASRS Text

Title: ACR DEVIATES FROM CLRNC WHEN WRONG ROUTING IS ENTERED INTO FMC.

Narrative: JUST PRIOR TO PUSHBACK, AGENT GAVE THE FO OUR PDC. I WAS HANDED THE LATEST WX AND OUR TKOF PERFORMANCE DATA. UNKNOWN TO ME, THE FO CHANGED THE ROUTING IN THE FMS TO COMPLY WITH HIS UNDERSTANDING OF THE PDC. UNFORTUNATELY IT CAUSED US TO DEVIATE FROM OUR CLRNC. FLT PLANNED RTE WAS PHX.DRKG.DRK.J11.BCE...DTA...SLC. THE PDC SAID CLRED AS FILED PHX DRK6 DRK J11 ***SLC. I DON'T KNOW WHY BUT THE FO THOUGHT THAT MEANT J11 ALL THE WAY TO THE SLC VOR. DEPARTING BCE THE CTLR ASKED IF WE WERE GOING DIRECT DTA. THERE WAS NO CONFLICT AND I DON'T BELIEVE THE CTLR WAS TOO WORRIED ABOUT IT. HOWEVER, THIS IS AN OPPORTUNITY TO POINT OUT HOW INCONSISTENT THE PDC'S ARE. IT SEEMS EACH ONE IS UNIQUE. YOU HAVE TO HUNT FOR THE DEP PROC, SOME HAVE THE DEP FREQ, SOME DON'T. SOME HAVE THE INITIAL ALT, SOME DON'T. SOME HAVE THE PLANNED RTE (WHICH I THINK SHOULD BE LEFT OFF THE PDC), SOME DON'T. I'D LIKE TO SEE AN IDENT BLOCK AT THE TOP AND THE TEXT IN THE SAME FORMAT USED FOR YRS OVER THE RADIO FROM CLRNC DELIVERY.

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.