Proof of Travel
Yannick Drescher, a German software consultant based in Chiang Mai on consecutive Thai visa exemptions, presented a PDF booking summary from a third-party aggregator at the Sadao land crossing in January 2026. The document showed a Bangkok-to-Frankfurt route with a departure date 12 days out. The officer entered the 6-character reference into the airline's lookup tool. The record didn't exist. The PNR had expired two days earlier, and Drescher had no way to verify this before arriving at the border.
The Document Set Drescher Presented
Drescher carried three items at the counter: a PDF booking summary from a third-party aggregator, a screenshot of a Google Flights result for the same route, and his German passport.
What Thai immigration requires for visa-exemption entry is a confirmed onward ticket, also called a dummy ticket, with a verifiable PNR in a major GDS, a route departing Thailand within the permitted stay window, and a passenger name matching the passport.
| Document | Format | Contains live PNR | GDS-verifiable | Accepted at Sadao |
|---|---|---|---|---|
| Third-party PDF export | No (expired) | No | No | |
| Google Flights screenshot | Image | No | No | No |
| Dummy ticket (GDS PNR) | Digital or print | Yes | Yes | Yes |
| Confirmed airline e-ticket | PDF / Email | Yes | Yes | Yes |
The route on the PDF was fine. Bangkok to Frankfurt departs Thailand, which is what the officer needed. The problem was not direction or destination: it was the PNR layer, which had ceased to exist.
Why the PNR Expired: Ticketing Time Limits
Economy class PNRs booked without full payment are subject to a ticketing time limit. When the TTL passes without a ticket number being issued, the carrier's inventory system releases the seat and the PNR is removed from the GDS.
TTL ranges vary by carrier type and fare class:
| Carrier type | Typical TTL range |
|---|---|
| Low-cost carrier (AirAsia, Scoot, Ryanair) | 24 to 72 hours |
| Full-service carrier, economy saver | 72 hours to 7 days |
| Full-service carrier, flex economy | 7 to 30 days |
| Travel agency booking via GDS | Often 24 to 72 hours |
Drescher's aggregator issued a booking reference in its own system but did not generate a live PNR in Amadeus or Sabre. When the carrier's TTL passed, the record was removed from the GDS. The booking reference on the PDF remained valid on the aggregator's platform but pointed to nothing that an immigration officer's lookup could find.
This structural gap between a booking reference and a GDS PNR is the core distinction that differentiates a compliant dummy ticket from an aggregator export. IATA's guidance on PNR structure and GDS documentation is available at iata.org.
The Compliant Document Set
Had Drescher used a proper onward ticket service, his document set would have resolved the gap as follows:
| Field | Required standard | Drescher (actual) | Compliant dummy ticket |
|---|---|---|---|
| PNR format | 6-character GDS locator | Aggregator reference only | Amadeus or Sabre PNR |
| GDS status | HK (confirmed) | Expired / not found | HK |
| Route direction | Departing Thailand | Bangkok to Frankfurt | Bangkok to Singapore |
| Passenger name | Exact passport match | Drescher (correct) | Drescher |
| Departure date | Within permitted stay | Day 12 of 60 (correct) | Day 12 of 60 |
| Airline booking site lookup | Returns live record | No | Yes |
The only failure was the PNR layer. Every other field was correct. A dummy ticket booked 24 to 48 hours before the crossing would have resolved the issue entirely.
For a detailed analysis of how PNR validity windows interact with consulate and border timelines, see the onward ticket PNR validity compliance case study on Proof of Travel.
Implications for Recurring Nomad Border Crossings
Drescher's situation illustrates what compliance analysts would call a recycled proof failure: a document that was valid at the time of original booking but was not renewed or verified before use.
For a nomad on a 60-day Thai visa exemption doing one Sadao crossing every two months, the exposure window is significant:
| Event | Day |
|---|---|
| Dummy ticket booked | Day 1 |
| TTL expires (full-service economy) | Day 7 to 14 |
| PNR no longer live | Day 7 to 14 |
| Border crossing attempted | Day 60 |
| Gap of invalid proof | 46 to 53 days |
The resolution is straightforward: book the dummy ticket within 48 hours of the crossing, not at the start of the stay period. The PNR must be live at the time of the border check, not at the time of original booking.
Carrier Obligations at Land Borders vs. Airports
A point that surprises many nomads: carriers don't bear the same document-responsibility obligations at land crossings that they do at air boardings.
Under IATA Resolution 830d, carriers are financially liable for the cost of repatriating a passenger denied entry at an air destination. This creates a commercial incentive for airlines to check documents at check-in. Land crossings don't have that carrier layer.
At a land crossing, the obligation sits entirely on the traveller. There's no gate agent to catch a defective document before you reach immigration. That's why the Sadao check-post can and does turn back travellers who would have been stopped by airline check-in staff at Suvarnabhumi Airport.
For a full analysis of how carrier verification works at air check-in and how that differs from the border-officer check, see the airline check-in document compliance case study.
The practical implication: the onward-ticket compliance burden at land borders is higher, not lower, than at airports. Don't assume that because a crossing is small or informal, the document standard is lower.
If your document set needs a verified PNR before a crossing, book a compliant dummy ticket at Proof of Travel with a live GDS record that can withstand a lookup at any crossing point.
Frequently asked questions
What is the difference between a booking export and a valid onward ticket?
A booking export from a third-party aggregator contains a reference number from that platform's system. It may or may not correspond to a live PNR in a GDS. A valid dummy ticket, also an onward ticket, contains a 6-character PNR verifiable directly in the airline's own booking system.
How do I check whether my PNR is still live before travel?
Open the airline's official "manage my booking" page, enter the 6-character PNR and your last name. If the booking loads and shows a confirmed flight, the record is live. If the page returns an error or "no record found", the PNR has expired.
Do Thai immigration officers at land crossings verify PNRs?
Yes, at the major crossings between Thailand and Malaysia. Officers at Sadao and Padang Besar use the airline's public booking-lookup tool. The standard of verification is applied consistently.
How far in advance should a dummy ticket be booked for a land-border crossing?
Within 48 hours of the crossing. Most economy PNRs booked without payment expire within 7 to 14 days. Booking close to the crossing date ensures the PNR is live at the time of the check.
Does the destination on the dummy ticket need to match the traveller's actual next stop?
Not in most cases. The officer is verifying that the traveller has a confirmed departure from the country being entered. The specific destination is not typically checked in detail at land crossings.