HCF CTLR EXPRESSED CONCERN REGARDING FILED RTE DIFFERENCES.

Date: 2004-04 · Aircraft: B737-700 · Phase: climb

Anomalies: other-atc-flc-rte-descrepancy

Synopsis

HCF CTLR EXPRESSED CONCERN REGARDING FILED RTE DIFFERENCES.

Narrative

I WAS PROVIDING OJT TO A RADAR TRAINEE AT HCF SECTOR 7. ACR X STRIP WAS RECEIVED SHOWING THE RTE HNL. APACK ZURIC A331 ZIBUD&SEDAR&TOU CASDY5 CYVR. ACR X CHKED ON FREQ AND REQUESTED DIRECT ANELE. MY TRAINEE RESPONDED CLRED DIRECT ZURIC. PLT REPLIED ZURIC IS NOT ON OUR RTE. WE ASKED THE PLT WHAT RTE HE HAD. THE PLTS COPY OF THE FLT PLAN READ HNL APACK R463 ABSOL A332 HEMLO SEDAR TOU CASDY5 CYVR. WE PROVIDED A FULL RTE CLRNC ON THE PLTS VERSION OF THE RTE AND ENTERED THE CHANGE IN THE COMPUTER. THIS POTENTIALLY SERIOUS SIT WAS ONLY CAUGHT BECAUSE THE PLT REQUESTED A DIRECT RTE SHORTCUT. NORMALLY THESE ACFT ARE CLRED DIRECT APACK AND RADAR SVC IS TERMINATED AT THAT POINT. APACK WAS COMMON IN BOTH VERSIONS OF THE FLT PLAN. FOR THE SAME REASON; NEITHER THE PLT NOR HNL CLRNC DELIVERY WOULD CATCH IT; SINCE THE CLRNC IS ISSUED CLRED TO CYVR VIA APACK TRANSITION AS FILED. THE NEXT REAL CHK ON THE RTE WOULD BE A POS RPT TO ZOA AT ANELE VERSUS ZURIC WITH THE ACFT ALREADY IN THE OCEANIC NON RADAR ENVIRONMENT. THE INTEGRITY OF THE SYS IS BASED ON PLT; DISPATCHER AND ATC HAVING THE SAME FLT PLAN INFO; ESPECIALLY CRITICAL IN A NON RADAR ENVIRONMENT. WE CHKED OUR LCL RECORDS; AND DETERMINED THAT THERE WAS ONLY 1 VERSION OF THE FLT PLAN RECEIVED; WITH NO CHANGES OR CORRECTIONS. ACR X DISPATCHER WAS CONTACTED; AND THE INDIVIDUAL WE TALKED TO VERIFIED THEY FILED ONLY 1 FLT PLAN. THE ACR X DISPATCHER ALSO MENTIONED THAT HE THOUGHT THIS HAD HAPPENED BEFORE; WITH THE SAME FLT. I DONT KNOW ANYTHING ABOUT THEIR COMPUTERIZED DISPATCH SYS; BUT IT SOUNDS LIKE IT MAY HAVE A GLITCH -- A SERIOUS GLITCH.

More incidents for this aircraft family →

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