B737-700 FLT CREW FAILS TO RECOGNIZE REVISED RTE SEGMENT OF PDC. PROGRAMS AND FLIES FILED RTE UNTIL ALERTED BY DEP CTLR.
Synopsis
B737-700 FLT CREW FAILS TO RECOGNIZE REVISED RTE SEGMENT OF PDC. PROGRAMS AND FLIES FILED RTE UNTIL ALERTED BY DEP CTLR.
Narrative
I'VE READ ALL THE BULLETINS; ETC; BUT THEY DIDN'T PREVENT ME FROM A HUMAN ERROR THAT OTHERS HAVE RECENTLY MADE. I ALREADY KNEW MY MISTAKE; WHAT LED TO IT; AND HOW TO PREVENT IT; THE VERY MOMENT IT HAPPENED WHILE DEPARTING LAX. I HAD MISSED ON PDC THAT WE WERE ISSUED OSHNN 3 DEP; AND RATHER; HAD ENTERED OUR FILED DEP OF LOOP 4 INTO THE FMC. IT WAS AN EARLY ORIGINATOR FROM LAX. WE WERE CLRED FOR TAKEOFF FROM RWY 24L AND ISSUED A HEADING OF 210 DEGS AFTER DEP. AFTER TAKEOFF AND CHKING IN WITH SOCAL DEP; WE WERE EVENTUALLY ISSUED DIRECT PEVEE. I; THE FO AND PM; STATED THAT IT WASN'T ON OUR DEP. SOCAL RETURNS WITH; WHERE DID WE RECEIVE OUR CLRNC? (AT THIS POINT I ALREADY KNEW WHAT HAD HAPPENED.) I SAID PDC. HE SAID; 'PDC SHOULD HAVE SHOWN THE OSHNN DEP (WHICH IT DID; BUT WE MISSED ON PREFLIGHT) BECAUSE LOOP DEP IS ESSENTIALLY NOT USED DURING LATE NIGHT AND EARLY MORNING HOURS.' WE ENTERED THE OSHNN DEP INTO THE FMC WHILE RECEIVING A COUPLE OF VECTORS FROM ATC; AND SOON AFTER WE WERE ESTABLISHED DIRECT TO SEAL BEACH TO RESUME THE OSHNN DEP WITH NO FURTHER EVENTS. IT HAS ALREADY BEEN EMPHASIZED HOW TO READ THE PDC ON ACARS AND THAT THE CREW SHOULD REVIEW THE CLRNC TOGETHER INCLUDING INITIAL LEGS OF THE SID. WE HAD BOTH REVIEWED THE PDC INDIVIDUALLY AND BRIEFED THE LOOP 4 DEP FROM LAX; INCLUDING FIXES AND REQUIRED ALTITUDES. HOWEVER; WE STILL HAD BOTH MISSED THE PREFERRED DEP ROUTING OF OSHNN 3 FROM LAX INCLUDED ON PDC. I TAKE BLAME IN NOT PAYING CLOSER ATTENTION AND MISSING WHAT PDC HAD ISSUED TO US; HOWEVER; I DO BELIEVE THIS WILL REMAIN A COMMON ERROR DUE TO THE WAY PDC IS ISSUED. WHEN CALLING ATC FOR A CLRNC VIA RADIO; AND IF CLRED AS FILED; THE CTLR STATES 'CLRED AS FILED.' IN CONTRAST; PDC SEEMS TO PRESENT A JUMBLED MESS OF INFORMATION. IF 'CLRED AS FILED' WAS TYPED; THEN THE PLT COULD SIMPLY REFER TO THEIR RELEASE. IF NOT CLRED AS FILED; THEN THE RTE SHOULD BE SHOWN ON PDC AND THAT WOULD BE A CUE TO THE PLT THAT SOMETHING IS DIFFERENT COMPARED TO WHAT IS ON THE RELEASE. INSTEAD; THE FILED RTE IS SHOWN ON THE PDC; SOMETIMES COMPLETELY; SOMETIMES 'TRUNCATED;' SOMETIMES WITH A PDR; ETC. BUT I FIND IT VERY EASY TO MAKE A MISTAKE TO SEE THE FILED DEP INCLUDED ON THE PDC ALONG WITH A PDR THAT CALLS FOR A DIFFERENT DEP. MY EYES SAW THE LOOP DEP ON PDC AND THE RELEASE WHILE MISSING OSHNN WHICH WAS ALSO INCLUDED IN THE PDR. IN ADDITION FOR THIS PARTICULAR CASE; IF THE OSHNN 3 DEP IS THE PDR FOR EARLY MORNING HOURS OUT OF LAX; SHOULD IT BE FILED THAT WAY FROM THE BEGINNING?SUPPLEMENTAL INFO FROM ACN 779278: I NEVER ACTUALLY PULLED UP THE PDC PAGE ON THE ACARS AND VERIFIED ANY CHANGES. WE ARE BOTH FAMILIAR WITH PDCS AND THEIR DIFFERENT FORMATS. NO EXCUSES; I NEED TO MAKE CHECKING THE PDC PAGE PART OF MY HABIT PATTERN LIKE I DO THE RTE PAGE. LIKE I MENTIONED EARLIER; I HAVE TO PHYSICALLY PULL THE PDC PAGE UP MYSELF AND MAKE IT A HABIT. NOT THAT TIME (FEELING RUSHED) WAS AN ISSUE HERE; BUT IT DOES TAKE QUITE A LOT OF BUTTON PUSHING ON THE ACARS TO GET TO THE PDC.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.