If you work with Global Distribution Systems (GDS) like Amadeus, Sabre, or Travelport Galileo, you have likely seen ARNK inside a PNR.
This guide explains clearly what ARNK means, why it is important, and how to add it in different GDS systems.
What Does ARNK Mean?
ARNK stands for Arrival Unknown.
It is a non-air segment added to a PNR when a passenger travels between two cities without a booked flight in the system.
In simple terms:
ARNK connects two air segments when the passenger moves between cities by another method (car, train, bus, or separate ticket).
When Do You Use ARNK?
You must add ARNK when:
- The arrival city is different from the next departure city
- The passenger has an open-jaw itinerary
- The passenger is traveling overland between two airports
- There is a break in the routing that is not ticketed
Example:
- DXB → CAI (Flight)
- Passenger travels from CAI to HBE by car
- HBE → JED (Flight)
Since there is no flight between CAI and HBE in the PNR, you must insert ARNK between them.
Why Is ARNK Important?
ARNK is important because:
- It keeps the itinerary logically connected
- It prevents pricing errors
- It avoids ticketing issues
- It ensures proper fare construction
- It maintains correct segment sequence
Without ARNK, the system may return pricing or validation errors.
How to Add ARNK in Different GDS
Below are the standard formats to add an ARNK segment:
In Amadeus
SIARNK
In Galileo
Y
In Sabre
0AA
After entering the command, the ARNK segment will appear between the two air segments in the PNR.
Does ARNK Affect Pricing?
ARNK itself does not create a fare.
However, it affects:
- Fare calculation logic
- Open-jaw pricing rules
- Routing validation
- Minimum connection checks
If missing, the system may fail to price the itinerary correctly.
Key Takeaways
- ARNK means Arrival Unknown
- It connects two cities without an air segment
- It is required for open-jaw and overland travel
- It must be added manually in most cases
- It prevents pricing and ticketing errors
