B737 FLT CREW MISUNDERSTANDS REVISED SEGMENT ON PDC AND HAS TRACK DEV.

Date: 2008-05 · Aircraft: B737-300 · Phase: climb

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

Synopsis

B737 FLT CREW MISUNDERSTANDS REVISED SEGMENT ON PDC AND HAS TRACK DEV.

Narrative

WHEN RECEIVING THE PDC CLRNC VIA ACARS; I MISREAD/MISINTERPRETED THE CHANGE CLRNC VS WHAT WAS FILED. WE SUBSEQUENTLY FLEW THE FILED RTE VS THE REROUTE ATC ISSUED. FILED RTE WAS CWK 3.TNV EIC ELD; CHANGED RTE WAS CWK 3.TNV LFK ELD. ONE SOLUTION WOULD BE TO ONLY DISPLAY THE ACTUAL ATC CLRNC VS SHOWING BOTH THE FILED AND THE CHANGE OR USE PLAIN ENGLISH STATING 'CHANGE RTE TO READ.'SUPPLEMENTAL INFO FROM ACN 786186: IN DEP BRIEFING AFTER BEFORE START ORIGINATING CHKLIST I FAILED TO NOTICE THE AMENDED CLRNC ABOVE THE FILED CLRNC IN THE PDC; EVEN THOUGH IT WAS ON THE LINE RIGHT ABOVE THE FILED CLRNC. IT READ LIKE THIS: -CWK 3 TNV LFK ELD- AUS CWK 3 TNV EIC. FO HAD LOADED THE COMPANY RTE WHICH MATCHED THE FILED CLRNC. I SAW WHAT I WAS LOOKING FOR IN THE SECOND LINE AND DISREGARDED THE AMENDED LINE ABOVE. MY MISTAKE FOR NOT THOROUGHLY DOUBLE CHKING THE PDC VS FMC ROUTING AS PER OUR PROCS. AFTER TAKEOFF WE FLEW TO TNV THEN EIC UNTIL QUERIED BY HOUSTON CENTER. THEY THEN CLEARED US DIRECT TO ELD. MEMPHIS CENTER PASSED A PHONE # AND I TALKED TO THEM AFTER LNDG. THEY SAID THERE WAS NO TFC CONFLICT BUT WANTED TO MAKE SURE WE KNEW WHERE THE PROBLEM CAME FROM. I TOLD HIM IT WAS MY MISTAKE FOR NOT RECOGNIZING THE CORRECT DEP INSTRUCTIONS ON OUR PDC. FOLLOW OUR PROCS EVERY TIME. THE ONLY OTHER INPUT I HAVE FOR REDUCING THE INCIDENCE OF THIS MISTAKE IS TO ONLY PRINT ONE ROUTING ON THE PDC. AS LONG AS TWO ROUTINGS ARE PRINTED ON THE PDC; THE FILED AND THE AMENDED ROUTING; SOMEONE (THIS TIME IT WAS ME) WILL FLY THE WRONG ONE. NOT AN EXCUSE; JUST AN OBSERVATION.

More incidents for this aircraft family →

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