Narrative:

The problem arose when tokyo company dispatch provided the crew with a primary flight plan but filed a secondary flight plan with japan ATC. The results were that the flight crew had a computer ICAO flight plan describing a north track as printed on the company release message and a computer flight plan for the same track, and only 1 paragraph defining a secondary flight plan, and no mention of a south track. An assistant dispatcher mistakenly by computer filed with tokyo ATC a more south track. (Company msp and tyo dispatch acknowledge this mistake and are taking steps to avoid a future occurrence). When crew received ATC clearance from nrt clearance delivery, they had what to them was a changed departure profile defined out to 33N 160E and then confirmed 'flight plan route' after that point. The problem is, 'flight plan route' meant 2 different things to the 2 parties involved. After reporting 33N 160E, tyo radio 3 times questioned our airrep which stated ETA for next position and 1 subsequent position. Finally, tyo radio and hnl radio defined the filed route and turned to navigation to a more south point. (Primary flight plan :34N 1703E; secondary flight plan, 23N 170E). Aircraft position at kse was approximately 3335 north or approximately halfway between north and south track: 120 NM separate the 2 tracks. Total excursion was approximately 65 NM of a 120 NM sep. Oak oceanic later stated they knew of no traffic conflict as a result of excursion from filed track.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR WDB TRACK HEADING DEVIATION AFTER DEP FROM NRT. COMPANY DISPATCH HAD FILED THE WRONG FLT PLAN.

Narrative: THE PROB AROSE WHEN TOKYO COMPANY DISPATCH PROVIDED THE CREW WITH A PRIMARY FLT PLAN BUT FILED A SECONDARY FLT PLAN WITH JAPAN ATC. THE RESULTS WERE THAT THE FLT CREW HAD A COMPUTER ICAO FLT PLAN DESCRIBING A N TRACK AS PRINTED ON THE COMPANY RELEASE MESSAGE AND A COMPUTER FLT PLAN FOR THE SAME TRACK, AND ONLY 1 PARAGRAPH DEFINING A SECONDARY FLT PLAN, AND NO MENTION OF A S TRACK. AN ASSISTANT DISPATCHER MISTAKENLY BY COMPUTER FILED WITH TOKYO ATC A MORE S TRACK. (COMPANY MSP AND TYO DISPATCH ACKNOWLEDGE THIS MISTAKE AND ARE TAKING STEPS TO AVOID A FUTURE OCCURRENCE). WHEN CREW RECEIVED ATC CLRNC FROM NRT CLRNC DELIVERY, THEY HAD WHAT TO THEM WAS A CHANGED DEP PROFILE DEFINED OUT TO 33N 160E AND THEN CONFIRMED 'FLT PLAN RTE' AFTER THAT POINT. THE PROB IS, 'FLT PLAN RTE' MEANT 2 DIFFERENT THINGS TO THE 2 PARTIES INVOLVED. AFTER RPTING 33N 160E, TYO RADIO 3 TIMES QUESTIONED OUR AIRREP WHICH STATED ETA FOR NEXT POS AND 1 SUBSEQUENT POS. FINALLY, TYO RADIO AND HNL RADIO DEFINED THE FILED RTE AND TURNED TO NAV TO A MORE S POINT. (PRIMARY FLT PLAN :34N 1703E; SECONDARY FLT PLAN, 23N 170E). ACFT POS AT KSE WAS APPROX 3335 N OR APPROX HALFWAY BTWN N AND S TRACK: 120 NM SEPARATE THE 2 TRACKS. TOTAL EXCURSION WAS APPROX 65 NM OF A 120 NM SEP. OAK OCEANIC LATER STATED THEY KNEW OF NO TFC CONFLICT AS A RESULT OF EXCURSION FROM FILED TRACK.

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.