The dispatcher and the captain involved describe the events leading up to a track deviation. The rou...

Narrative:

Flight was planned and released by the previous midnight shift dispatcher. The flight plan was filed using our normal routing; but because of the early departure time; it should have been filed on a noise abatement route. There was a 2nd release sent with the correct route for fuel burn purposes; but that flight strip was not filed with ATC. The pre departure clearance on ACARS shows where ATC made the change from the original route to SLNT8 lin peons inslo dta. But nothing beyond that; which should mean 'as filed'. Upon reaching dta; slc contacted the flight regarding confusion as to whether the flight was proceeding to ekr or rlg. They were instructed to contact ZLC upon landing. I did receive a phone call from ZLC center asking if rbl was part of the flight strip. I replied that it was the original filing; but that a new release was issued with the special routing; but it was not filed that way. The change in filing came from ZOA center on his pre departure clearance. I was not involved in the preflight planning of either flight release. I was queried by the flight crew via ACARS; asking if rbl was part of their flight strip. I replied the same as I told ATC; it was part of the original filing.

Original NASA ASRS Text

Title: The Dispatcher and the Captain involved describe the events leading up to a track deviation. The route had been revised on the dispatch release but never refiled with ATC.

Narrative: Flight was planned and released by the previous midnight shift dispatcher. The flight plan was filed using our normal routing; but because of the early departure time; it should have been filed on a noise abatement route. There was a 2nd release sent with the correct route for fuel burn purposes; but that flight strip was not filed with ATC. The PDC on ACARS shows where ATC made the change from the original route to SLNT8 LIN PEONS INSLO DTA. But nothing beyond that; which should mean 'as filed'. Upon reaching DTA; SLC contacted the flight regarding confusion as to whether the flight was proceeding to EKR or RLG. They were instructed to contact ZLC upon landing. I did receive a phone call from ZLC CTR asking if RBL was part of the flight strip. I replied that it was the original filing; but that a new release was issued with the special routing; but it was not filed that way. The change in filing came from ZOA CTR on his PDC. I was not involved in the preflight planning of either flight release. I was queried by the flight crew via ACARS; asking if RBL was part of their flight strip. I replied the same as I told ATC; it was part of the original filing.

Data retrieved from NASA's ASRS site 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.

Attributes
ACN	1191022
Time
Date	201407
Local Time Of Day	0001-0600
Place
Locale Reference	ZLC.ARTCC
State Reference	UT
Aircraft 1
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Dispatcher
Qualification	Dispatch Dispatcher
Person 2
Function	Captain
Experience	Flight Crew Last 90 Days 181 Flight Crew Type 12500
Events
Anomaly	Deviation - Procedural Clearance Deviation - Track / Heading All Types

The dispatcher and the captain involved describe the events leading up to a track deviation. The route had been revised on the dispatch release but never refiled with ATC.