Narrative:

Air carrier generated flight plan release was not received by gander control even though initial clearance out of jfk was 'as filed.' INS was preloaded and coordinates checked by both pilots. Just prior to reaching redby, gander informed us that they did not have our track across the atlantic on file and issued us a new one. The new clearance was: present position direct to oyster, 56N 50W, 58N 40W etc. While reloading the INS, oyster's latitude was entered correctly. However, the longitude was incorrectly entered for scrod -- approximately 1 degree north of oyster. This resulted in our position being 19 mi northwest of oyster. We notified gander of our transposing the wrong longitude and were told the track was protected 30 mi on either side.

Google
 

Original NASA ASRS Text

Title: GROSS NAV ERROR IN HDG TRACK DEV.

Narrative: ACR GENERATED FLT PLAN RELEASE WAS NOT RECEIVED BY GANDER CTL EVEN THOUGH INITIAL CLRNC OUT OF JFK WAS 'AS FILED.' INS WAS PRELOADED AND COORDINATES CHKED BY BOTH PLTS. JUST PRIOR TO REACHING REDBY, GANDER INFORMED US THAT THEY DID NOT HAVE OUR TRACK ACROSS THE ATLANTIC ON FILE AND ISSUED US A NEW ONE. THE NEW CLRNC WAS: PRESENT POS DIRECT TO OYSTER, 56N 50W, 58N 40W ETC. WHILE RELOADING THE INS, OYSTER'S LATITUDE WAS ENTERED CORRECTLY. HOWEVER, THE LONGITUDE WAS INCORRECTLY ENTERED FOR SCROD -- APPROX 1 DEG N OF OYSTER. THIS RESULTED IN OUR POS BEING 19 MI NW OF OYSTER. WE NOTIFIED GANDER OF OUR TRANSPOSING THE WRONG LONGITUDE AND WERE TOLD THE TRACK WAS PROTECTED 30 MI ON EITHER SIDE.

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.