CONFUSION AND TRACK DEVS RESULT FROM B737-700 FLT CREW FAILING TO RECOGNIZE THE REVISED SEGMENT PORTION OF THEIR PDC WHICH CHANGED FROM THE LOOP SID TO THE OSHNN RNAV SID.

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

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

Synopsis

CONFUSION AND TRACK DEVS RESULT FROM B737-700 FLT CREW FAILING TO RECOGNIZE THE REVISED SEGMENT PORTION OF THEIR PDC WHICH CHANGED FROM THE LOOP SID TO THE OSHNN RNAV SID.

Narrative

I MISREAD THE PDC OR DID NOT NOTICE THE REVISION WITHIN THE SLASHES TO OUR RTE. ORIGINALLY CLRED PER RELEASE VIA THE LOOP4 AND PDC AMENDMENT WAS THE OSHNN DEP. UPON TKOF; FLEW THE LOOP AND WE WERE GIVEN A HDG BY ATC; AND THEN CLRED TO SLI WHICH HE REFERRED TO AS 'SEAL BEACH.' HOWEVER; HE SAID IT IN SUCH A WAY THAT IT SOUNDED LIKE SEBBY (HE SAID 'SEE-BEE' WITH NO 'CH' SOUND). WE READ BACK DIRECT SEBBY (SEE-BEE) AND HE DID NOT CORRECT US. NO ONE USED THE PHONETIC SPELLING AT THIS TIME. WE WERE TOLD THAT WE WERE SUPPOSED TO BE ON A DIFFERENT DEP THAN THE LOOP. I THINK HE SAID THE OSHNN BUT AFTER HE CLRED US DIRECT SEBBY; WE ASSUMED THE SEBBY DEP. THINGS WERE GETTING VERY BUSY NOW WITH TRYING TO PROGRAM THE FMC AND FINDING THE RIGHT DEP. WE STARTED LNAV TOWARD SEBBY AND STARTED LOOKING FOR OUR CHART AND THEN ATC TOLD US TO TURN BACK TO A HDG OF 150 DEGS AND ASKED US WHERE WE WERE GOING AND ALSO INFORMED US THAT WE SHOULD BE DIRECT SEAL BEACH (SLI) AND SHOULD BE ON THE OSHNN AND NOT THE SEBBY DEP. EARLY AFTER TKOF; WHEN HE DISCOVERED WE WERE DOING THE LOOP; ATC COMMENTED THAT THIS MISTAKE HAS BEEN OCCURRING FREQUENTLY AND THAT THE LOOP IS NEVER USED AFTER XA00. THIS WAS UNNECESSARY COM BY HIM AND ONLY ADDED TO THE DISTR AND WORKLOAD. FINALLY NOW WE WERE GOING SEAL BEACH AND ON THE OSHNN DEP. THEY HANDED US OFF TO ANOTHER CTLR BUT WE ASKED THEM TO VERIFY WHAT RTE THEY NOW WANTED US ON AS WE WANTED TO MAKE SURE WE WERE DOING THE RIGHT THING. INCREDIBLY; HE COULD NOT TELL US AS OUR STRIP HAD ALREADY BEEN SENT SOMEWHERE ELSE. WE PROCEEDED TO CONTACT THE NEXT CTLR AND HE CLRED US DIRECT DAG ON COURSE WITHOUT FURTHER INCIDENT. AT NO TIME DID WE APPEAR TO GET NEAR ANY OTHER ACFT OR LOSE REQUIRED SEPARATION (THANKFULLY). CHANGE THE FLT PLAN TO REFLECT THE ACTUAL ONE WE SHOULD GET FOR THAT TIME. PROVIDE A TRAINING PRODUCT INSTEAD OF WX PACKET TEXTUAL DESCRIPTION THAT SHOWS EXACTLY WHAT AN AMENDED PDC LOOKS LIKE. CHANGE THE NAME OF THE FIXES THAT SOUND SIMILAR. EMPHASIZE BOTH CREW LOOKING FOR PLUS (+) OR MINUS (-) IN THE PDC. GET RID OF THE OLD RTE IN THE PDC FORMAT AND ONLY HAVE THE ACTUAL NOW CLRED RTE (I HAVE THE OLD RTE ON MY RELEASE). IN ABSENCE OF THE AFOREMENTIONED; HAVE BOTH CREW REVIEW THE PDC AND MAKE A STATEMENT TO THE EFFECT 'NO PLUSES OR MINUSES.' SUPPLEMENTAL INFO FROM ACN 780956: FO GAVE COMPLETE CLRNC BRIEFING. WHILE THERE HAS BEEN A LOT OF TRAINING ABOUT THE PDC PROCESS FROM THE TRAINING DEPT; I WILL NO LONGER ASSUME THAT THE FO UNDERSTANDS HOW IT WORKS. OUR PROC HAS HISTORICALLY BEEN FOR THE FO TO GET THE CLRNC; AND THEN GIVE BRIEFING. CAPT GENERALLY DID NOT LISTEN TO ATC GIVE CLRNC. I HAVE BEEN CONTENT TO LISTEN TO FO GIVE BRIEFING; CHK AGAINST FLT PLAN; AND VERIFY FMC PROGRAMMING. I WILL NOW LOOK AT THE ACTUAL PDC WHILE FO GIVES BRIEFING. THIS WOULD HAVE CAUGHT THE ERROR.

More incidents for this aircraft family →

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