Narrative:

I was the dispatcher for flight sfo to nrt on the sat of jan/92. Flts which transit paza airspace were to comply with paza NOTAM A0009192 which specifies rtes which may be selected. I chose the G469 transition to R580 for this flight and filed the ICAO flight plan. Our computer identifies rtes by alpha-numeric code and automatically addresses and files ATC flight plans while creating a computer flight plan, release, and flight following record. Dispatchers may also attach secondary computer flight plans to the document which is generated for the flcs. The error occurred at this point in the planning process. After selecting the primary route and filing the ICAO flight plan, I selected the wrong activation code while attempting to attach a secondary flight plan via A342 transition to R580. The code which I selected revised the release and primary flight plan using the intended route code for the secondary flight plan. I did not notice the mistake because I did not check the computer flight plan against the ICAO flight plan. I plan to change my procedure to xchk these documents. One more factor sealed the fate of flight. I briefed the captain and specifically discussed the fact that he was file on G469. He might have noticed the error by noting the discrepancy between our conversation and his computer flight plan. Perhaps he was too trusting.

Related reports:

Google
 

Original NASA ASRS Text

Title: DISPATCHER RPTS OF POOR DISPATCH PROC RESULTING IN FLC FLT PLAN DIFFERING FROM THE ONE FILED WITH ATC.

Narrative: I WAS THE DISPATCHER FOR FLT SFO TO NRT ON THE SAT OF JAN/92. FLTS WHICH TRANSIT PAZA AIRSPACE WERE TO COMPLY WITH PAZA NOTAM A0009192 WHICH SPECIFIES RTES WHICH MAY BE SELECTED. I CHOSE THE G469 TRANSITION TO R580 FOR THIS FLT AND FILED THE ICAO FLT PLAN. OUR COMPUTER IDENTIFIES RTES BY ALPHA-NUMERIC CODE AND AUTOMATICALLY ADDRESSES AND FILES ATC FLT PLANS WHILE CREATING A COMPUTER FLT PLAN, RELEASE, AND FLT FOLLOWING RECORD. DISPATCHERS MAY ALSO ATTACH SECONDARY COMPUTER FLT PLANS TO THE DOCUMENT WHICH IS GENERATED FOR THE FLCS. THE ERROR OCCURRED AT THIS POINT IN THE PLANNING PROCESS. AFTER SELECTING THE PRIMARY RTE AND FILING THE ICAO FLT PLAN, I SELECTED THE WRONG ACTIVATION CODE WHILE ATTEMPTING TO ATTACH A SECONDARY FLT PLAN VIA A342 TRANSITION TO R580. THE CODE WHICH I SELECTED REVISED THE RELEASE AND PRIMARY FLT PLAN USING THE INTENDED RTE CODE FOR THE SECONDARY FLT PLAN. I DID NOT NOTICE THE MISTAKE BECAUSE I DID NOT CHK THE COMPUTER FLT PLAN AGAINST THE ICAO FLT PLAN. I PLAN TO CHANGE MY PROC TO XCHK THESE DOCUMENTS. ONE MORE FACTOR SEALED THE FATE OF FLT. I BRIEFED THE CAPT AND SPECIFICALLY DISCUSSED THE FACT THAT HE WAS FILE ON G469. HE MIGHT HAVE NOTICED THE ERROR BY NOTING THE DISCREPANCY BTWN OUR CONVERSATION AND HIS COMPUTER FLT PLAN. PERHAPS HE WAS TOO TRUSTING.

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.