Andreas Keller, a German national holding a passport that qualifies for visa-free entry into Brazil under the bilateral arrangement currently in force, arrived at Frankfurt Airport (FRA) in March 2026 with a complete hotel booking portfolio, a valid travel insurance certificate, and a PDF exported from a price comparison website showing a flight from GRU to Lisbon priced at EUR 480. The Lufthansa check-in agent at terminal B entered the PDF's listed flight reference into the Timatic query system. The reference returned no result. The agent declined to issue a boarding pass until Mr Keller could provide a verifiable onward booking. 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 the document gap and the compliant set that replaced it.

The Regulatory Basis

Brazil's entry requirements derive from Lei 13.445/2017 (the Migration Law), which mandates that tourists entering Brazil demonstrate sufficient financial resources and a means of departure. The operationalisation of that mandate falls to two enforcement points: the airline carrier at the originating airport, acting under IATA Resolution 830d carrier liability provisions, and the Polícia Federal officer at the Brazilian port of entry.

Under IATA Resolution 830d, carriers face financial liability for passengers they board who subsequently fail to meet destination-country entry requirements. That liability gives carriers a direct commercial incentive to verify departure documentation rigorously. For Brazil routes, the IATA Timatic database specifies that passengers must hold a return or onward ticket. A reference that returns no GDS record doesn't satisfy that specification.

The IATA Travel Centre provides the public-facing Timatic interface; the check-in agent version runs the same underlying query.

Document Gap Analysis: The Keller Submission

Mr Keller's departure documentation at FRA comprised the following:

Document Format GDS verifiable Compliant
Price comparison PDF (GRU-LIS) Exported webpage No (no PNR) No
Hotel bookings (4 properties) Booking.com confirmations N/A Not applicable
Travel insurance certificate PDF, issuer-signed N/A Not applicable
Return Lufthansa ticket (FRA-GRU) Ticketed PNR Yes Yes (inbound only)

The critical deficiency: the PDF presented as the onward ticket contained a price and itinerary summary from a flight search aggregator, but no confirmed booking reference (PNR). When the Lufthansa agent entered the reference string visible on the PDF into the GDS terminal, the system returned a null result. The flight existed on the schedule; Mr Keller had not booked it.

The inbound Lufthansa ticket (FRA to GRU) was correctly ticketed and verifiable, but it served as proof of arrival, not proof of departure from Brazil. That distinction is commonly misunderstood: carriers and immigration officers require evidence that the traveller has arranged to leave the destination country, not simply that they've booked their way in.

The Compliant Document Set

Mr Keller used a mobile browser at the Lufthansa check-in desk to book a dummy ticket through a verified service. The booking generated a confirmed PNR on a LATAM Airlines route from GRU to Santiago de Chile (SCL), departing 72 days after his scheduled Brazil arrival. The PNR was issued within four minutes of booking.

Document Format GDS verifiable Compliant
Dummy ticket: LATAM GRU-SCL (PNR: confirmed) Booking confirmation PDF Yes Yes
Name match: Keller, Andreas Per passport Yes Yes
Departure date: within 90-day visa-free window Day 72 of permitted stay Yes Yes
Route: scheduled LATAM service Real airline, real schedule Yes Yes

The agent typed the new PNR into the terminal. The GDS returned the flight record with Mr Keller's name attached. The boarding pass was issued. Total delay: approximately 18 minutes.

For a full analysis of PNR validity windows and how long records persist in GDS after booking, see our PNR validity compliance case study.

Carrier Enforcement Patterns on Brazil Routes

The Keller case at FRA is representative of how major carriers on South America routes handle Timatic compliance. The enforcement rate varies by carrier, route, and traveller profile, but the check is not selective.

Carrier Hub Timatic check at check-in Notes
Lufthansa FRA Yes Standard Timatic terminal query
Air France CDG Yes Standard Timatic terminal query
KLM AMS Yes Standard Timatic terminal query
British Airways LHR Yes Standard Timatic terminal query
LATAM SCL, GRU Yes Queries own system plus Timatic
Delta JFK, ATL Yes Standard Timatic terminal query
American MIA, JFK Yes Standard Timatic terminal query
TAP Air Portugal LIS Yes Standard Timatic terminal query

Carriers face a financial penalty under IATA Resolution 830d for each passenger offloaded at the destination. That penalty is typically higher than the cost of the return flight the carrier would have to arrange. The incentive to verify at origin is therefore significant.

Polícia Federal Verification at the Port of Entry

Had Mr Keller boarded with his original non-verifiable PDF and reached GRU, the secondary exposure point would have been the Polícia Federal desk in the arrivals hall. Federal Police officers have access to GDS query tools and routinely verify onward booking references for passengers who appear to be long-term visitors or who present atypical documentation.

The verification process at the desk mirrors the carrier check: the officer enters the booking reference and the name into a terminal, the GDS returns the flight record, and the match is confirmed or rejected. A PDF without a PNR can't survive that check.

Denial of entry by the Polícia Federal triggers a deportation order. It's commercially and logistically disruptive for all parties. The airline that carried the passenger becomes responsible for the return flight under IATA Resolution 830d. In practice, the carrier absorbs that cost and subsequently strengthens its Timatic enforcement at origin.

Book a compliant onward ticket at Proof of Travel before you arrive at the check-in counter. The cost of a verified dummy ticket is a fraction of the commercial and logistical disruption that a documentation failure produces.

For documentation of a comparable carrier enforcement scenario, see our airline check-in onward ticket compliance case study.

Compliance Checklist: Brazil Onward Ticket Requirements

Requirement Compliant form Non-compliant form
Booking reference (PNR) Six-character alphanumeric confirmed by GDS Screenshot, price PDF, wishlist export
Name match Full legal name as on passport Nickname, surname transposition, middle name only
Departure date Within visa-free window (90 days max) or visa validity Date exceeding permitted stay
Route Real scheduled airline service Fictitious flight, cargo route
Carrier Operating carrier with GDS presence Unscheduled charter without GDS record

Frequently asked questions

What does IATA Resolution 830d require of carriers on Brazil routes?

Resolution 830d holds carriers liable for the cost of returning passengers who fail to meet destination-country entry requirements. For Brazil routes, that means carriers must verify that passengers hold a means of departure before issuing a boarding pass. Non-compliance exposes the carrier to repatriation costs and IATA administrative penalties.

Can the Polícia Federal deny entry despite a carrier having issued a boarding pass?

Yes. The carrier check and the immigration check are independent. That's not a technicality. A carrier that issues a boarding pass to a passenger with non-compliant documentation has already incurred liability exposure. The Polícia Federal officer's decision is sovereign and final at the port of entry.

Is a dummy ticket legally different from a paid ticket at Brazilian immigration?

For immigration purposes, the operative distinction is whether the booking reference returns a live result in GDS at the time of the check. A properly issued dummy ticket -- a confirmed PNR on a real scheduled service -- satisfies that requirement. The fare settlement status isn't part of the verification the Polícia Federal or the carrier conducts.

How long does a dummy ticket PNR remain active in GDS?

PNR persistence varies by carrier and fare class. Most airline reservations don't lapse immediately -- they remain in GDS for at least 24 to 72 hours beyond the scheduled departure time. For Brazil applications where the entry check and the departure date may be separated by 60 to 80 days, the relevant window is the active period before the dummy ticket's departure date, not after.

Does the destination airport within Brazil affect the verification requirements?

No. GRU, GIG, BSB, REC, SSA, and other international Brazilian airports all enforce the same national entry requirements under Lei 13.445/2017. Enforcement intensity may vary by terminal staffing, but the legal requirement is uniform.