A recurring point of confusion among flight crews has surfaced in a pilot forum discussion regarding how to correctly interpret route amendments on a Pre-Departure Clearance (PDC). The specific question involves how dashes are used within a PDC route string to denote a change—specifically, whether the dashes bracket a segment to be deleted, whether only the first fix in the bracketed segment should be dropped, or whether the entire enclosed segment should be excised and replaced by a direct routing between the two surrounding fixes. As the original poster notes, even experienced captains disagree on the correct interpretation, and there is no single, universally cited FAA source that unambiguously resolves the ambiguity for line pilots.
This matters operationally because PDC and CPDLC route amendments are parsed by both humans and flight management systems, and a misread dash convention can result in a wrong route being loaded into the FMS, an aircraft flying a fix it was never cleared to fly, or a controller having to intervene to correct a deviation. The formatting convention pilots are describing—ROUTE followed by a fix, then a string with dashes bracketing fixes to be removed—is consistent with how many ARINC 623-based PDC/CPDLC systems and dispatch release amendments format "delete" instructions: the dashes denote the fixes that are being removed from the previously filed or cleared route, with the route then closing directly between the fix before and the fix after the bracketed segment. In the example given (KABC DEF WAYPT UVW KXYZ), the correct read is almost certainly to delete DEF and UVW while retaining WAYPT, yielding KABC WAYPT KXYZ—exactly the interpretation the original poster proposes. However, formatting conventions can vary by ARINC vendor, ACARS provider, and even by facility, which is precisely why crews encounter inconsistent guidance from captain to captain.
The deeper issue this thread highlights is a gap between FAA regulatory guidance and the practical, vendor-specific formatting standards that airlines and ACARS/PDC providers actually use. The FAA's Aeronautical Information Manual and Order 7110.65 address clearance delivery phraseology in voice communications but do not comprehensively document PDC text-formatting conventions, since PDC/CPDLC message formatting is largely governed by ARINC/ATN data-link standards and individual air carrier training materials rather than direct FAA regulation. This leaves airlines responsible for training their own pilots on how their specific PDC/ACARS system renders amendments, and it means new-hire and transition pilots often rely on tribal knowledge, training department bulletins, or informal crew-to-crew explanations rather than a single authoritative FAA reference—precisely the vacuum the original poster is running into.
For working pilots, the practical takeaway is to treat any ambiguous PDC or CPDLC route amendment exactly as they would treat any unclear ATC clearance: verify via voice with ATC or company dispatch before loading and executing the change in the FMS, rather than guessing between competing interpretations in the cockpit. As data-link clearance delivery becomes more prevalent across commercial, cargo, and increasingly business aviation operations (with more Part 135 and Part 91K operators adopting CPDLC-capable avionics), this kind of formatting ambiguity is likely to recur, particularly as pilots transition between airlines or aircraft types with different ACARS/PDC vendors. It reinforces the value of airline-specific standardization: training departments should treat PDC/CPDLC route-amendment syntax as a formal SOP item with unambiguous, company-specific guidance and recurrent training reinforcement, since crew-level disagreement on how to parse a route amendment is a latent threat to route conformance and a potential contributor to track deviations or ATC pilot deviation reports.