A B737 FO ENTERED A ROUTE INTO THE FMC INCORRECTLY READ FROM THE PDC. AFTER TKOF; ATC QUERIED ABOUT THE ROUTE.

Date: 2008-04 · Aircraft: B737-300 · Phase: initial_climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

A B737 FO ENTERED A ROUTE INTO THE FMC INCORRECTLY READ FROM THE PDC. AFTER TKOF; ATC QUERIED ABOUT THE ROUTE.

Narrative

DURING NORMAL PREFLIGHT DUTIES; THE FO ENTERED A NON STD ROUTE INTO THE FMC. AFTER REVIEWING THE PDC; THE FO FOCUSED ON THE FILED ROUTE ON THE REPLY. THE FO MISSED THE CHANGE FROM THE FILED LOOP4 DEPARTURE TO THE OSHNN5 DEPARTURE. WHEN THE FO RETURNED TO THE ACARS PDC PAGE; THE -OSHNN5 DAG- WAS PRESENT ON THE PAGE. AFTER DEPARTING LAX ON RWY 24L; WE WERE GIVEN AN INITIAL VECTOR OF 180 DEGS. WE WERE THEN CLEARED TO A POINT ON THE OSHNN5 DEPARTURE PEVEE; WHICH WE ASKED FOR CLARIFICATION. WE INFORMED ATC THAT WE THOUGHT WE WERE ON THE LOOP4 AND THEY REPLIED THAT THE LOOP4 DEPARTURE WAS NOT UTILIZED DURING THAT PART OF THE DAY. THEY REQUESTED THAT WE UPDATE OUR FMC WITH THE OSHNN5 AND NOTIFY THEM WHEN WE WERE READY FOR CLEARANCE. THEY THEN CLEARED US TO OSHNN AND THE REST OF THE DEPARTURE. FIRST; THE FO NEEDS TO REVIEW EACH LINE OF THE PDC TO ENSURE THAT CHANGES ARE NOTED. IT IS EASY TO JUST FOCUS ON WHAT YOU ARE EXPECTING TO SEE. I REALIZE THAT I MADE AN ERROR AND WILL WORK TO NOT ALLOW THAT TO HAPPEN TO ME AGAIN. HOWEVER; A NOTE ON THE LOOP4 STATING WHEN IT IS OR IS NOT UTILIZED MAY ALSO HELP A CREW CATCH THIS BEFORE THEY ARE AIRBORNE ON THE DEPARTURE. ANOTHER TECHNIQUE WOULD BE TO PULL UP THE PDC PAGE AFTER LOOKING AT THE ROUTE PAGE 2 AS A CREW.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.