B737-300 flight crew flies loop departure as filed vice oshnn as shown in the revised route portion ...

Attributes
ACN	777349
Time
Date	200803
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 2500
Environment
Flight Conditions	VMC
Light	Dawn
Aircraft 1
Controlling Facilities	tracon : sct.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : initial
Route In Use	departure sid : loop
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 262 flight time type : 9000
ASRS Report	777349
Person 2
Affiliation	government : faa
Function	controller : departure
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were flying from lax. We received our clearance via pre departure clearance. Our dispatch release had us flying the LOOP4 departure. We did our preflight checklist and I verified that we had the LOOP4 and route in our FMC. The taxi out and takeoff were normal. As we flew our departure ATC called us up and asked us what departure clearance we had been given. We told them our pre departure clearance had given us the LOOP4. They informed us that this early in the day we should be on the OSHNN3 departure. They gave us a vector to intercept the OSHNN3 which we did. I pulled up our ACARS received messages to look at our pre departure clearance. The pre departure clearance had an amended departure clearance for the OSHNN3 which somehow I did not catch as our proper departure. So we flew the wrong departure because we had not interpreted the amended pre departure clearance clearance correctly. There were no traffic conflicts that I could see and the departure controller did not seem too upset. The rest of the flight was uneventful. Check the route and the pre departure clearance clearance as part of your captain route verification. Have dispatch file the routes ATC really wants.

Original NASA ASRS Text

Title: B737-300 FLT CREW FLIES LOOP DEPARTURE AS FILED VICE OSHNN AS SHOWN IN THE REVISED ROUTE PORTION OF THEIR PDC CLRNC OUT OF LAX.

Narrative: WE WERE FLYING FROM LAX. WE RECEIVED OUR CLEARANCE VIA PDC. OUR DISPATCH RELEASE HAD US FLYING THE LOOP4 DEPARTURE. WE DID OUR PREFLIGHT CHECKLIST AND I VERIFIED THAT WE HAD THE LOOP4 AND ROUTE IN OUR FMC. THE TAXI OUT AND TAKEOFF WERE NORMAL. AS WE FLEW OUR DEPARTURE ATC CALLED US UP AND ASKED US WHAT DEPARTURE CLEARANCE WE HAD BEEN GIVEN. WE TOLD THEM OUR PDC HAD GIVEN US THE LOOP4. THEY INFORMED US THAT THIS EARLY IN THE DAY WE SHOULD BE ON THE OSHNN3 DEPARTURE. THEY GAVE US A VECTOR TO INTERCEPT THE OSHNN3 WHICH WE DID. I PULLED UP OUR ACARS RECEIVED MESSAGES TO LOOK AT OUR PDC. THE PDC HAD AN AMENDED DEPARTURE CLEARANCE FOR THE OSHNN3 WHICH SOMEHOW I DID NOT CATCH AS OUR PROPER DEPARTURE. SO WE FLEW THE WRONG DEPARTURE BECAUSE WE HAD NOT INTERPRETED THE AMENDED PDC CLEARANCE CORRECTLY. THERE WERE NO TRAFFIC CONFLICTS THAT I COULD SEE AND THE DEPARTURE CONTROLLER DID NOT SEEM TOO UPSET. THE REST OF THE FLIGHT WAS UNEVENTFUL. CHECK THE ROUTE AND THE PDC CLEARANCE AS PART OF YOUR CAPTAIN ROUTE VERIFICATION. HAVE DISPATCH FILE THE ROUTES ATC REALLY WANTS.

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

B737-300 flight crew flies loop departure as filed vice oshnn as shown in the revised route portion of their pre departure clearance clearance out of lax.