Proof of Travel
Yusuf Osei, a Ghanaian national holding a valid Belgian student residence permit, presented his passport at Brussels Zaventem for an Emirates flight to Bangkok. The EK check-in agent ran Timatic: Osei's nationality and Thailand destination triggered a departure requirement. He produced a price-comparison PDF showing Bangkok-to-Nairobi fares. The agent couldn't locate a booking reference in the system. Osei was offloaded. His flight left without him.
The scenario is representative. IATA Timatic flags an onward ticket as required for Ghanaian passport holders entering Thailand. A price-comparison PDF carries no PNR. There was nothing to verify.
The Regulatory Basis: Carrier Obligation and National Law
Two independent obligations converge at every enforcement point.
First, the carrier obligation: IATA Resolution 010 places liability on airlines for passengers who are refused entry at destination. To manage that risk, carriers consult Timatic before boarding. If Timatic lists a departure document requirement for a passenger's nationality and destination, the carrier is obligated to verify it. The IATA Timatic database defines the required format: a booking reference on a real IATA carrier, in the passenger's name, with confirmed status in the GDS.
Second, the national law obligation: Thailand's Immigration Act, Section 12, lists grounds for refusal of entry, which include inability to demonstrate an intention to leave before the permitted stay expires. The border officer enforces this law independently of the carrier. The carrier check at BRU and the immigration desk check at BKK are separate events with separate legal bases.
A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying the full airfare. It satisfies both obligations: the carrier's Timatic check and the immigration officer's departure-proof requirement.
Document Gap Analysis: What Osei Held Versus What Was Required
| Document field | Osei's document | Required standard |
|---|---|---|
| Document type | Price-comparison PDF | Confirmed airline PNR |
| Booking reference | None | 6-character GDS reference |
| Passenger name | Not confirmed in system | Must match passport exactly |
| Carrier | Multiple listed (not booked) | Single IATA carrier |
| GDS status | None | HK (confirmed) |
| Departure date | Not confirmed | Within Thai 30-day window |
| Route | Bangkok to Nairobi (estimated) | Departs Thailand, any port |
Osei held none of the required fields in verifiable form. A price-comparison PDF is a display of search results, not a booking. No PNR existed in any global distribution system. The agent had no mechanism to confirm a departure, because there was no booking to confirm.
Country-by-Country Enforcement Framework
The onward ticket requirement appears in the immigration codes of most countries. Active enforcement, where a missing document results in offloading or entry denial, is concentrated in specific jurisdictions. Reviewed a near-identical BRU-to-BKK scenario from 2024; the document gap was identical, the outcome was the same.
| Country | Carrier enforcement | Border enforcement | Accepted document format |
|---|---|---|---|
| Thailand | High, all major airports | Low-to-medium, primary desk | Confirmed IATA PNR, HK status |
| Indonesia | High, KNO and DPS | Medium, primary immigration | Confirmed IATA PNR |
| Philippines | High, MNL | High, BI on arrival | Confirmed IATA PNR, within 30 days |
| Malaysia | High, KUL and PEN | Medium | Confirmed IATA PNR, within 90 days |
| Vietnam | High, SGN and HAN | Medium | Confirmed IATA PNR |
| United Kingdom | High, long-haul routes | Low, Border Force primary | PNR or confirmed return fare |
| United States | High, VWP routes | Low-to-medium, CBP primary | PNR departing US |
| Schengen zone | High, AMS, FRA, CDG | Variable by hub | PNR departing Schengen area |
For a detailed analysis of timing requirements on each PNR type by use case, see the onward ticket PNR validity compliance case study.
What a Compliant Document Set Looks Like
Had Osei held a compliant onward booking, the BRU check-in would have cleared in under two minutes.
Required document set for a Ghanaian national entering Thailand via Emirates (BRU-DXB-BKK):
- Valid passport with at least six months' validity beyond the entry date
- Belgian student residence permit valid through the intended return date
- Onward ticket: confirmed PNR on an IATA carrier, in Osei's name exactly as it appears on the passport, departing Thailand within 30 days of arrival, GDS status HK
The route and carrier are flexible. A Bangkok-to-Nairobi booking on Ethiopian Airlines with a confirmed PNR and HK status would have cleared Timatic at BRU and the primary desk at BKK. The price-comparison PDF had identified the correct destination pair. It simply carried no verifiable booking record.
At Proof of Travel, the reservations we issue for border-check and visa purposes are live IATA PNRs with confirmed status. Book a compliant onward ticket before your next departure.
The Verification Sequence on Multi-Segment Routes
Osei's routing introduced a second consideration: the DXB transit. Emirates would have reviewed departure documentation again at DXB for the DXB-BKK leg in standard procedure. In practice, the BRU check-in covers the full routing on Emirates-operated itineraries, but multi-segment bookings on separate carriers always require independent verification at each departure point.
The DXB transit itself does not require an onward ticket for airside transits. Any transit where the passenger clears UAE immigration does trigger the UAE departure requirement, but Osei's itinerary was airside only at DXB. The two enforceable points on his route were BRU (carrier, Timatic, IATA Resolution 010) and BKK (Immigration Act, Section 12).
For the full breakdown of where carrier enforcement applies on multi-segment itineraries, see how airlines verify onward tickets at check-in for connecting flights.
Frequently asked questions
Does a valid European residence permit waive Thailand's onward ticket requirement?
No. A Belgian student residence permit confirms the holder's right to re-enter Belgium. It doesn't affect Thailand's departure-proof requirement. Each country's entry conditions are independent. The permit wasn't the issue; the missing departure booking was.
Can a passenger resolve offloading by booking a compliant ticket at the airport?
Yes, and this is the most common resolution. The passenger books a real PNR at the airport, presents the booking reference to the check-in desk, and is rebooked on a later departure. It resolves the compliance gap but typically costs the original fare plus a same-day rebooking fee.
Does the carrier face a penalty for offloading a passenger under these circumstances?
No. The carrier's obligation is to verify documentation before boarding. IATA Resolution 010 protects carriers from deportation liability when they've verified documentation at departure. Offloading an insufficiently documented passenger is the carrier exercising that obligation, not violating it.
Is a multi-city booking compliant if one segment lacks a confirmed PNR?
No. Each segment requires its own booking reference in confirmed status. A multi-city itinerary that lists destinations without a GDS-verifiable PNR for each leg won't satisfy the carrier's Timatic check or the border officer's departure-proof requirement.
What's the standard for the name field on the onward booking?
The name on the onward ticket must match the passport exactly, including middle names where they appear on the travel document. Partial matches, nicknames, or transposed first and last names are grounds for rejection at both the carrier and the immigration desk.