Pieter van Dam, a Dutch national, presented a Skyscanner PDF at KLM's check-in desk at Amsterdam Schiphol in February 2026 for an AMS-LIM flight. The document showed flight options and prices. It had no booking reference. KLM held him at the counter for 31 minutes while a supervisor consulted Timatic. He missed the gate. This case study examines the document gap that caused the delay, Peru's entry compliance framework, and the compliant document set that would have cleared the counter in under two minutes.

Regulatory basis: Peru's departure-proof requirement

Peru's Dirección General de Migraciones requires visa-exempt visitors to demonstrate the intent and means to depart within their permitted stay. For most nationalities, this is 90 days. The requirement is encoded in the IATA Timatic database, which carriers consult at check-in under IATA Resolution 830d.

Under Resolution 830d, a carrier that transports a passenger subsequently refused entry at the destination bears the cost of repatriation. This creates a direct financial liability that drives carriers to conduct departure-proof checks at origin airports. KLM, Iberia, Air France, British Airways, and LATAM all include the departure-proof query as a standard step for Peru-bound passengers.

The document that satisfies this check is a dummy ticket, also called an onward ticket. An onward ticket is a real PNR booked for visa or border-check purposes without paying for the full flight. The PNR must be live and verifiable in a Global Distribution System at the moment of presentation.

Document gap analysis: Van Dam at Amsterdam Schiphol

The following table examines the document Pieter van Dam presented and its compliance status against the compliant alternative:

Field Van Dam's Skyscanner PDF Compliant replacement
Document type Comparison-site output Dummy ticket or paid e-ticket
PNR present No Yes
Passenger name match Not applicable Required: exact passport match
GDS-verifiable No Yes, resolves on terminal query
Carrier confirmation None Issued by operating carrier via GDS
Departure date within 90-day stay Not determinable Yes
Document format PDF screenshot Booking confirmation with PNR code

The core gap was the absence of a PNR. The KLM agent's terminal query requires a booking reference to return a result. Without one, the system returns nothing and the supervisor escalation follows. Thirty-one minutes and a missed gate.

Carrier enforcement obligations by hub

Carriers operating Peru routes from European and North American hubs apply consistent departure-proof checks. The following table reflects the enforcement approach by carrier:

Carrier Hub Departure-proof check Escalation path
KLM Amsterdam (AMS) Yes, Timatic query at primary desk Supervisor review on failure
Iberia Madrid (MAD) Yes, Timatic query plus boarding check Gate hold on failure
Air France Paris (CDG) Yes, standard Timatic procedure Supervisor review on failure
British Airways London (LHR) Yes, standard Timatic procedure Gate hold on failure
LATAM Bogotá (BOG) Yes, standard check for LIM flights Supervisor review on failure
American Airlines Miami (MIA) Yes, standard check for LIM flights Supervisor review on failure
Avianca Bogotá (BOG) Yes, standard regional procedure Gate hold on failure

Where a passenger cannot produce a valid PNR, the standard escalation is a supervisor review followed, in clear cases, by denial of boarding. The carrier isn't acting arbitrarily; it's managing the repatriation liability encoded in Resolution 830d.

The compliant document set

Had Pieter van Dam carried a dummy ticket with a live PNR showing departure from Lima within 90 days, the counter exchange would have been approximately two minutes rather than thirty-one. The compliant document set for this scenario is:

Document Required content Status in Van Dam's case
Passport (Dutch, valid) Photo, validity dates, machine-readable zone Held
Dummy ticket (LIM outbound) Live PNR, exact name match, departure within 90-day stay Not held
Accommodation confirmation First-night address in Lima Not held (recommended, not mandatory)

A dummy ticket from Lima to, for example, Santiago de Chile (SCL) or Buenos Aires (EZE) would have satisfied the Timatic condition immediately. The PNR resolves on query, the agent closes the check, the passenger boards.

At Proof of Travel, booking a verified onward ticket for Peru takes approximately two minutes and produces a GDS-issued PNR with a passenger name field that must match the passport exactly.

Land border enforcement matrix

Peru's departure-proof requirement applies at land crossings as well as at air entry points, though enforcement is less standardised. The following matrix reflects the known enforcement pattern at Peru's principal land borders:

Crossing Connects to Enforcement for non-regional passports Document types accepted
Desaguadero Bolivia Frequent Dummy ticket PNR, printed confirmation
Tacna / Santa Rosa Chile Moderate Dummy ticket PNR, bus ticket (sometimes)
Aguas Verdes / Huaquillas Ecuador Moderate Dummy ticket PNR, confirmed reservation
Iñapari Brazil Infrequent Dummy ticket PNR recommended

The Desaguadero crossing presents the highest and most consistent enforcement probability of the four principal land borders. EU, UK, US, and Australian passport holders at Desaguadero without departure documentation have been held and, in some cases, turned back.

The UK Government's Peru entry requirements guidance notes that travellers may be asked to show sufficient funds and evidence of onward travel at the point of entry.

For a comparative analysis of how carriers across multiple hubs approach departure-proof verification, see the Proof of Travel case study on airline check-in onward ticket document compliance.

Compliance principles

Three principles govern document compliance for Peru entry:

First, the PNR must be present and active. A document without a live booking reference doesn't pass the Timatic query regardless of format or presentation.

Second, payment amount is not queried. Whether the ticket is a dummy reservation or a fully paid fare isn't visible in the Timatic check. What the system confirms is that a departure booking exists in the name of the passenger.

Third, timing governs PNR validity. A PNR that has expired cancels in the GDS and returns no result on query, equivalent to having no documentation. Booking the dummy ticket within the carrier's hold window, typically 24 to 72 hours before check-in, keeps the PNR live at the critical moment.

For detail on PNR hold windows by carrier, see the Proof of Travel analysis of onward ticket PNR validity compliance.

If you need a compliant departure document for Peru entry, book a verified onward ticket at Proof of Travel and the PNR is issued through a live GDS within two minutes.

Frequently asked questions

Does Peru's Migraciones check for a dummy ticket at Jorge Chávez Airport?

Yes, at secondary inspection, and occasionally at the primary desk when the entry pattern looks unusual. The more consistent enforcement point is the carrier check-in desk in the origin country, where the Timatic query is a standard procedural step.

What Timatic condition does Peru set for onward travel documentation?

Timatic records the condition as a requirement for proof of onward or return travel for visa-exempt nationals. The carrier agent's system confirms whether a departure booking exists in the passenger's name. The format of the document is secondary to the presence of a live PNR.

Can a dummy ticket be used for a Peruvian consulate visa application?

Yes. Nationalities that require a visa apply at their local Peruvian consulate. Most consulate file checklists include onward travel documentation. A dummy ticket with a live GDS-issued PNR satisfies this requirement in the same way it satisfies the carrier check-in query.

What if the PNR expires between booking and the check-in date?

An expired PNR returns no result on a Timatic terminal query, which is functionally equivalent to no documentation. The booking must be active at the moment the check is conducted. This is why timing the dummy ticket to the check-in window, within 24 to 48 hours, is an operational requirement rather than a preference.