A flight crew described the confusion which resulted from a ACARS PDC with two routes and how they chose the incorrect routing. They question why during a reroute the invalid clearance is included in the final PDC paper work.
Synopsis
A flight crew described the confusion which resulted from a ACARS PDC with two routes and how they chose the incorrect routing. They question why during a reroute the invalid clearance is included in the final PDC paper work.
Narrative
Just before pushback; we received an ACARS text message that we had been rerouted over SUMMT4 and that Release 2 was ready. Release 2 route matched the message. The PDC showed two routes. One was an incomplete version of our original route using the DAWGS 4; and a complete version of our new route. The ACARS W/B came back with data for Release 2; reinforcing that the new data was correct. I have not encountered this PDC format for a route change. As far as I can tell there is nothing in any manual explaining how and why you would have two routes on a PDC or the proper format. My assumption was that the second route would be listed second; and a route with no clearance limit was not a valid route; so I discounted the DAWGS route. Maybe it is not a good idea to put a route on a PDC that has no validity or reason for being there. Why do I want or need to know where I am NOT going? If the FAA has a reason to put where I am not going on a clearance; why don't they write English words indicating what they really want instead of nonsense dashes; or asterisks. Compounding the problem is the extreme pressure from the Company to get the flight off on time. So there was no time for reflection with the last minute change. If a well rested 25;000 hour pilot with no history of enforcement actions cannot get through this minefield without a deviation; human factors may need another look.
Second reporter narrative
I was the First Officer on flight. When I showed up to the gate I received the release paper work. (Release 1) I showed us filed KATL DAWGS4; I programed the FMS with the appropriate route. About 20min prior to departure we received an ACARS message from dispatch informing us that he updated us to release 2 because of a new route due to the golf tournament at a nearby airport. I went up to the gate agent and retrieved release 2. I then reprogrammed the FMS with the new route; KATL SUMMT4.... I then sent for the PDC via ACARS. When we received the PDC from ATC it filed route as -DAWGS4....- (route shown exactly as written on PDC). Cleared KATL SUMMT4... (route shown exactly as written on PDC). Since the SUMMT4 was the departure that was on our release and discussed with dispatch I had no question or confusion on the clearance. No distraction or changes occurred during taxi. We were instructed to taxi to 8R. Our takeoff clearance was normal. Takeoff was uneventful and had a normal hand off to Departure. We checked in with Departure with standard phraseology and standard acknowledgment. About halfway to KLEGG ATC called us and inquired about our clearance; we responded with we were cleared SUMMT4 VXV transition. ATC came back and informed us that they are showing that we were cleared the DAWGS4 departure. They then proceeded to assign us a heading for radar vectors. Once on assigned heading ATC inquired more about our clearance; we thought we were cleared the SUMMT4 and ATC thought we were assigned the DAWGS4. Once we landed we looked in all the manuals to find guidance about PDC formats. We were unable to find any information on PDC formats. To help prevent this from happening again I would suggest making PDC standard; and not having the filed route in the PDC; just put the cleared route on the PDC. With having both filed and cleared route on the PDC makes it very confusing. Any time we talk to clearance delivery they never mention what route was filed they only give cleared routes. We have our dispatch release that shows our filed route if we need to reference any changes in the route assigned by ATC.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.