

        📚 GDS Academy

        
            
                
                    Amadeus GDS Commands & Lessons | GDS Hub
                    35
                

            
                
                    Galileo GDS Commands & Lessons | GDS Hub
                    27
                

            
                
                    Sabre GDS Commands & Lessons | GDS Hub
                    20
                

                    

        
            🛠 Tools
            Airport Taxes Database
            Airports Database
            Farebase Generator
            Tax Checker
            Airline Special Services

CHECK PASSENGER ASSOCIATION

A practical guide for travel agents on fixing the CHECK PASSENGER ASSOCIATION error in Amadeus when creating EMDs or entering commands that require a specific passenger number.

The CHECK PASSENGER ASSOCIATION error is a common PNR error in Amadeus that appears whenever a PNR contains more than one passenger and the agent enters a command that requires a specific passenger association — without actually specifying which passenger it applies to. The system cannot decide on its own whether the entry belongs to Passenger 1, Passenger 2, or the whole party, so it blocks the command and returns the error. This article explains exactly when the error occurs, using a real EMD example, and shows you the simple fix that clears it instantly.

Why the “Check Passenger Association” Error Happens

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: Add the Passenger Association

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

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 immediately.

Matching the Passenger Number to the Right Traveller

Before adding the association, always confirm which passenger number belongs to which traveller in the PNR. The passenger numbers follow the order in the name field:

/P1 — the first passenger listed in the PNR.
/P2 — the second passenger listed in the PNR.
/P3 — the third passenger, and so on.

If the EMD applies to more than one passenger, add each passenger number separately rather than leaving the command without an association.

Quick Fix Checklist

Check how many passengers exist in the PNR.
Identify which passenger the EMD or service applies to.
Add /P plus the passenger number at the end of the command.
Verify the passenger number matches the correct traveller.
Re-enter the command and confirm the error is cleared.

Frequently Asked Questions

What causes the CHECK PASSENGER ASSOCIATION error?

It happens when a PNR has multiple passengers and you enter a command that requires a specific passenger number — such as an EMD creation — without specifying which passenger it belongs to.

How do I fix it?

Add the passenger association to the end of the command using /P followed by the passenger number, for example IUSMNN1PENFSHJ/P1.

Does this error appear only with EMDs?

No. It can appear with any command that requires a passenger association in a multi-passenger PNR, but EMD creation is the most common case.

Conclusion

The CHECK PASSENGER ASSOCIATION error is one of the easiest Amadeus errors to fix. It simply means the system needs to know which passenger your command applies to. By adding /P plus the passenger number — for example IUSMNN1PENFSHJ/P1 — the EMD is linked to the correct traveller and the error disappears. Always verify the passenger number against the PNR before re-entering the command, and repeat the association for each passenger when the service applies to more than one traveller.

🏷 Tags: amadeus Amadeus errors