Proof of Travel
Consider a hypothetical applicant, labelled here as Applicant T, flying from Madrid to Santiago (SCL) with a one-way booking and no return leg. The file turns on a single document: a dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. This case study examines what that document must contain and who reads it.
The scenario and the record
Applicant T is a composite constructed for illustration. It doesn't describe a real person or a real incident.
The facts of the file are simple. Applicant T holds a passport, a one-way fare into Chile, and an itinerary that ends overland at one of Chile's neighbours, which are Peru, Bolivia and Argentina. No flight leaves Chile in the file, and that absence is the compliance gap.
Entry conditions for Chile depend on nationality and are subject to change. This study therefore states no specific rule. The applicable position should be taken from the "Entry requirements" section of the UK government travel advice for Chile and from the traveller's own government.
Checkpoint one: the departure airline
The first reader of the record is not a Chilean officer. It is the carrier's agent at the departure airport.
Carriers consult IATA's Timatic database, described on the IATA Timatic page, to establish what a passenger needs for the destination. Where the database indicates a requirement for onward travel, the agent will request evidence before boarding. A carrier is generally expected to carry back a passenger refused entry, so the check is cautious by design.
For Applicant T, the missing outbound leg would be flagged here, not in Santiago. The remedy is a document that satisfies this checkpoint and remains accurate when scrutinised at the next.
Checkpoint two: border control in Santiago
On arrival, the record is read again, this time by an officer with discretion over admission. The officer may ask about purpose, duration and plans. The answers should match the documents.
The table below sets the two checkpoints side by side for a one-way arrival with an overland exit.
| Item | Departure airline | Chilean border control |
|---|---|---|
| Who decides | Carrier agent, guided by Timatic | Border officer, with discretion |
| Typical request | Booking showing departure from Chile | Questions on plans, sometimes the same booking |
| Weak point | Booking that cannot be retrieved | Answers that contradict the paperwork |
| Consequence of failure | Refused boarding | Refused admission or further questioning |
The pattern is consistent. A document that looks correct but fails retrieval fails at the first checkpoint. A document that retrieves but contradicts the stated plan fails at the second.
Findings: what the record should contain
For Applicant T, the compliant record has five elements:
- The applicant's name, identical to the passport.
- A confirmed status that an airline's own booking page can display.
- A departure from Chile on a date after the planned arrival.
- A route consistent with the stated itinerary.
- A retained copy, in print and in digital form.
Verification is the control that matters most. The applicant should open the airline's booking-management page, enter the surname and booking reference, and confirm that the record appears as expected. Our existing document compliance case study on proof of onward travel sets out the verification steps in more detail.
Holds can lapse. The applicant should confirm with the provider how long the booking remains active and align the booking date with the travel date.
Documentary risks in the record
Three failure modes recur in files of this kind, and each can be tested before departure.
Retrieval failure. The booking exists in the provider's records but cannot be found in the airline's own system. The test is the airline's booking-management page. If the record doesn't display there, the file isn't ready.
Identity mismatch. A single transposed letter in the surname is enough to defeat the match with the passport. The test is a character-by-character comparison, repeated after any amendment.
Lapse of the hold. Some reservations remain active only for a limited period, and the provider is the authority on how long. The test is a written confirmation of the active period, and a booking date set close to travel so that the record is live at both checkpoints.
None of these risks depends on the destination. They arise from the nature of a reservation held for document purposes, which is why the verification routine is worth performing for every trip, whatever Chile or any other country requires.
Retention and review
A compliant file is also one that can be reviewed afterwards. The applicant should retain the confirmation, the airline booking page capture and the date of the last check. If circumstances change, for example the route is altered or the dates move, the record should be updated and the earlier version kept for reference.
This discipline has a practical benefit. If an agent or officer queries the document, the applicant can show a coherent trail instead of a single printout of uncertain provenance.
Variations for overland exits
Where the real plan is a land crossing, the airline still needs a readable document, and the officer still expects a coherent account. Our case study on leaving by land with an onward ticket examines how the two interact.
The document shouldn't replace candour. If asked about plans, the applicant should state them accurately. This study offers general guidance only and is not legal or immigration advice.
Applicants who need the document can order a dummy ticket from Proof of Travel and file the verified confirmation with the rest of the record.