Narrative:

I was providing OJT to a radar trainee at hcf sector 7. Air carrier X strip was received showing the route hnl. Apack zuric A331 zibud&sedar&tou CASDY5 cyvr. Air carrier X checked on frequency and requested direct anele. My trainee responded cleared direct zuric. pilot replied zuric is not on our route. we asked the pilot what route he had. The pilotsouth copy of the flight plan read hnl apack R463 absol A332 hemlo sedar tou CASDY5 cyvr. We provided a full route clearance on the pilotsouth version of the route and entered the change in the computer. This potentially serious situation was only caught because the pilot requested a direct route shortcut. Normally these aircraft are cleared direct apack and radar service is terminated at that point. Apack was common in both versions of the flight plan. For the same reason, neither the pilot nor hnl clearance delivery would catch it, since the clearance is issued cleared to cyvr via apack transition as filed. the next real check on the route would be a position report to ZOA at anele versus zuric with the aircraft already in the oceanic non radar environment. The integrity of the system is based on pilot, dispatcher and ATC having the same flight plan information, especially critical in a non radar environment. We checked our local records, and determined that there was only 1 version of the flight plan received, with no changes or corrections. Air carrier X dispatcher was contacted, and the individual we talked to verified they filed only 1 flight plan. The air carrier X dispatcher also mentioned that he thought this had happened before, with the same flight. I donT know anything about their computerized dispatch system, but it sounds like it may have a glitch -- a serious glitch.

Related reports:

Google
 

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.