CHECK PASSENGER ASSOCIATION

This error occurs when the PNR contains more than one passenger, and the agent enters a command that requires a specific passenger association without specifying the passenger number.

Example scenario:
When manually creating an EMD using a command like:
IUSMNN1PENFSHJ
The system does not know which passenger (P1, P2, etc.) this EMD belongs to, so it returns the CHECK PASSENGER ASSOCIATION error.

---

Solution:

To resolve this, simply add the passenger association to the end of the command using /P followed by the passenger number.

Example:
Instead of:
IUSMNN1PENFSHJ

Use:
IUSMNN1PENFSHJ/P1

This explicitly tells the system to apply the EMD to Passenger 1 only, and the error will be resolved.

---

Also Read:

CHECK ITINERARY

CANCEL SEAT ITEM OR SPLIT PNR PRIOR TO NAME RE-ENTER

*ATTN – ISSUE SEPARATE TICKETS

Linkedin