Narrative:

On departure from lax; first officer programmed pre departure clearance (loop departure dag transition) in the FMC. First officer did not program the changed SID (oshnn) as was indicated by the (- -). I checked the route against the route on the release and it was confirmed in the departure briefing. I also checked the route on the pre departure clearance and I also missed the (- -) indication because I saw the routing I was looking for. Just after departure ATC gave us a turn to a heading of 210 degrees and told us to contact departure control. We continued on a 210 degree heading and contacted departure control. Departure control said fly heading 160 when able cleared direct pevee. I said pevee was not on the loop departure and ATC said we should be on the oshnn departure; and inquired about the change in the pre departure clearance routing. I said we would check and continued on 160 degree heading. We re-programmed the FMC and continued without any other issues. I have changed my flow to include the pre departure clearance page of the FMC; and my brief to include no plus no minus after the route verification. This error could have all been prevented. If there is any change of the routing; the old incorrect part of the routing should be deleted from the pre departure clearance. I saw the routing I was looking for. I was not looking for a change in the route. If the old incorrect portion of the routing was not there; I would have not found what I was looking for I could have programmed the FMC to indicate the changed routing.supplemental information from acn 791963: we received and both reviewed a pre departure clearance clearance for our flight from lax. Dispatch filed the loop 4 departure out of lax. I reviewed the pre departure clearance clearance. During the review I was comparing the pre departure clearance to our flight plan on the dispatch release. While cross checking the flight plan; I lost my place on the pre departure clearance while trying to go between the 2 flight plans on the release. I missed the portion of the pre departure clearance that showed the clearance changed our departure from the loop 4 dag transition to the oshnn 3 dag transition. The loop 4 was programmed into the FMC. Tower cleared us to take off on runway heading. The departure controller issued us an initial heading of 210 degrees. We were never joined up on a departure; we only had a vector clearance. After aircraft clean-up and acceleration; we were told to proceed direct to pevee intersection. The captain explained to the departure controller that we were assigned the loop 4 departure. The controller explained we were not and to check our pre departure clearance for the oshnn 3. He then explained he could provide vectors until we got setup for the correct departure and assigned us vectors of 160 degrees and 90 degrees and a direct clearance to sli. We looked at the pre departure clearance and sure enough the oshnn 3 departure was showing as a change. The departure controller explained that during the early morning departures the oshnn 3 departure is assigned for noise abatement versus the loop 4. I believe the pre departure clearance clrncs should just contain the assigned clearance. By not including the filed version a comparison of the pre departure clearance and the dispatch release flight plan would dramatically show a difference. Your eye would not focus on the material that is already contained in the release flight plan. Both the captain and I reviewed the pre departure clearance and both of us fixated on the filed flight plan information in the pre departure clearance instead of the clearance. Obtaining a clearance the old fashioned way via radio - the controller did not transmit both your filed flight plan and the amended flight plan. You just obtained the new clearance. Since you had a copy of your filed flight plan on your dispatch release. Finally he may help if dispatch files the oshnn 3 for early morning departures -- therefore prevent the change coming from ATC.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR FLT CREW FAILS TO NOTE REVISED SID ON PDC.

Narrative: ON DEP FROM LAX; FO PROGRAMMED PDC (LOOP DEP DAG TRANSITION) IN THE FMC. FO DID NOT PROGRAM THE CHANGED SID (OSHNN) AS WAS INDICATED BY THE (- -). I CHECKED THE RTE AGAINST THE RTE ON THE RELEASE AND IT WAS CONFIRMED IN THE DEP BRIEFING. I ALSO CHECKED THE RTE ON THE PDC AND I ALSO MISSED THE (- -) INDICATION BECAUSE I SAW THE ROUTING I WAS LOOKING FOR. JUST AFTER DEP ATC GAVE US A TURN TO A HDG OF 210 DEGS AND TOLD US TO CONTACT DEP CTL. WE CONTINUED ON A 210 DEG HDG AND CONTACTED DEP CTL. DEP CTL SAID FLY HDG 160 WHEN ABLE CLEARED DIRECT PEVEE. I SAID PEVEE WAS NOT ON THE LOOP DEP AND ATC SAID WE SHOULD BE ON THE OSHNN DEP; AND INQUIRED ABOUT THE CHANGE IN THE PDC ROUTING. I SAID WE WOULD CHK AND CONTINUED ON 160 DEG HDG. WE RE-PROGRAMMED THE FMC AND CONTINUED WITHOUT ANY OTHER ISSUES. I HAVE CHANGED MY FLOW TO INCLUDE THE PDC PAGE OF THE FMC; AND MY BRIEF TO INCLUDE NO PLUS NO MINUS AFTER THE RTE VERIFICATION. THIS ERROR COULD HAVE ALL BEEN PREVENTED. IF THERE IS ANY CHANGE OF THE ROUTING; THE OLD INCORRECT PART OF THE ROUTING SHOULD BE DELETED FROM THE PDC. I SAW THE ROUTING I WAS LOOKING FOR. I WAS NOT LOOKING FOR A CHANGE IN THE RTE. IF THE OLD INCORRECT PORTION OF THE ROUTING WAS NOT THERE; I WOULD HAVE NOT FOUND WHAT I WAS LOOKING FOR I COULD HAVE PROGRAMMED THE FMC TO INDICATE THE CHANGED ROUTING.SUPPLEMENTAL INFO FROM ACN 791963: WE RECEIVED AND BOTH REVIEWED A PDC CLRNC FOR OUR FLT FROM LAX. DISPATCH FILED THE LOOP 4 DEP OUT OF LAX. I REVIEWED THE PDC CLRNC. DURING THE REVIEW I WAS COMPARING THE PDC TO OUR FLT PLAN ON THE DISPATCH RELEASE. WHILE CROSS CHKING THE FLT PLAN; I LOST MY PLACE ON THE PDC WHILE TRYING TO GO BETWEEN THE 2 FLT PLANS ON THE RELEASE. I MISSED THE PORTION OF THE PDC THAT SHOWED THE CLRNC CHANGED OUR DEP FROM THE LOOP 4 DAG TRANSITION TO THE OSHNN 3 DAG TRANSITION. THE LOOP 4 WAS PROGRAMMED INTO THE FMC. TOWER CLEARED US TO TAKE OFF ON RWY HDG. THE DEP CTLR ISSUED US AN INITIAL HDG OF 210 DEGS. WE WERE NEVER JOINED UP ON A DEP; WE ONLY HAD A VECTOR CLRNC. AFTER ACFT CLEAN-UP AND ACCELERATION; WE WERE TOLD TO PROCEED DIRECT TO PEVEE INTXN. THE CAPT EXPLAINED TO THE DEP CTLR THAT WE WERE ASSIGNED THE LOOP 4 DEP. THE CTLR EXPLAINED WE WERE NOT AND TO CHECK OUR PDC FOR THE OSHNN 3. HE THEN EXPLAINED HE COULD PROVIDE VECTORS UNTIL WE GOT SETUP FOR THE CORRECT DEP AND ASSIGNED US VECTORS OF 160 DEGS AND 90 DEGS AND A DIRECT CLRNC TO SLI. WE LOOKED AT THE PDC AND SURE ENOUGH THE OSHNN 3 DEP WAS SHOWING AS A CHANGE. THE DEP CTLR EXPLAINED THAT DURING THE EARLY MORNING DEPS THE OSHNN 3 DEP IS ASSIGNED FOR NOISE ABATEMENT VERSUS THE LOOP 4. I BELIEVE THE PDC CLRNCS SHOULD JUST CONTAIN THE ASSIGNED CLRNC. BY NOT INCLUDING THE FILED VERSION A COMPARISON OF THE PDC AND THE DISPATCH RELEASE FLT PLAN WOULD DRAMATICALLY SHOW A DIFFERENCE. YOUR EYE WOULD NOT FOCUS ON THE MATERIAL THAT IS ALREADY CONTAINED IN THE RELEASE FLT PLAN. BOTH THE CAPT AND I REVIEWED THE PDC AND BOTH OF US FIXATED ON THE FILED FLT PLAN INFO IN THE PDC INSTEAD OF THE CLRNC. OBTAINING A CLRNC THE OLD FASHIONED WAY VIA RADIO - THE CTLR DID NOT TRANSMIT BOTH YOUR FILED FLT PLAN AND THE AMENDED FLT PLAN. YOU JUST OBTAINED THE NEW CLRNC. SINCE YOU HAD A COPY OF YOUR FILED FLT PLAN ON YOUR DISPATCH RELEASE. FINALLY HE MAY HELP IF DISPATCH FILES THE OSHNN 3 FOR EARLY MORNING DEPS -- THEREFORE PREVENT THE CHANGE COMING FROM ATC.

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.