Narrative:

Our filed route was iad-ldn-J134-stl-J24-mkc-J80-fqf-J116- ekr-mtu-slc. Our pre departure clearance read 'capital 4 departure ldn-J134-hnn then as filed.' wnw of hnn VOR ZID asked if we were proceeding on J134. We told them 'negative -- direct stl.' upon examining the pre departure clearance, we concluded that the pre departure clearance clearance could easily be interpreted either way, ie, after hnn VOR direct stl or J134 6 stl, and since our filed routing was different from the pre departure clearance, we assumed ATC wanted hnn direct stl. The hnn-J134-stl didn't even arise as a question until queried by ATC. We were also aware of the hnn-J134-stl dogleg. Our decision was based on the ATC issued pre departure clearance.

Google
 

Original NASA ASRS Text

Title: AN ACR B757 FLC GOT OFF RTE WHEN THEY MISINTERPRETED THEIR PDC AS BEING DIFFERENT FROM THEIR FILED RTE.

Narrative: OUR FILED RTE WAS IAD-LDN-J134-STL-J24-MKC-J80-FQF-J116- EKR-MTU-SLC. OUR PDC READ 'CAPITAL 4 DEP LDN-J134-HNN THEN AS FILED.' WNW OF HNN VOR ZID ASKED IF WE WERE PROCEEDING ON J134. WE TOLD THEM 'NEGATIVE -- DIRECT STL.' UPON EXAMINING THE PDC, WE CONCLUDED THAT THE PDC CLRNC COULD EASILY BE INTERPRETED EITHER WAY, IE, AFTER HNN VOR DIRECT STL OR J134 6 STL, AND SINCE OUR FILED ROUTING WAS DIFFERENT FROM THE PDC, WE ASSUMED ATC WANTED HNN DIRECT STL. THE HNN-J134-STL DIDN'T EVEN ARISE AS A QUESTION UNTIL QUERIED BY ATC. WE WERE ALSO AWARE OF THE HNN-J134-STL DOGLEG. OUR DECISION WAS BASED ON THE ATC ISSUED PDC.

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.