Proof of Travel
Bianca Rossi, a Brazilian passport holder, was held at a Wizz Air check-in desk in Budapest in early 2026, booked one-way to London Luton with a Skyscanner comparison PDF standing in for proof of onward travel. The airline refused to accept it. A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight, and the distinction is exactly what her documentation lacked.
The scenario
Rossi's booking was straightforward on paper: a confirmed Wizz Air PNR from Budapest to London Luton, visa-exempt entry as a Brazilian tourist under UK rules, no return flight. What she carried instead of proof of onward travel was a saved PDF of a comparison-site search, generated the night before at a hostel, showing return fares from London to São Paulo. It was not a booking. It had no PNR, no airline record locator, and nothing a gate agent could query.
The Wizz Air agent's objection was not personal or discretionary. It reflected the airline's own exposure under UK carrier liability rules, where a carrier that boards a passenger later refused entry can be fined and required to return that passenger at its own cost. Rossi was held at the desk for roughly twenty minutes while ground staff attempted, unsuccessfully, to locate a bookable record behind the document she presented.
Document gap analysis
| Field | What immigration and the carrier require | What the PDF showed |
|---|---|---|
| PNR or booking reference | A live, queryable reservation | None |
| Passenger name match | Exact match to travel document | Not present, generic search |
| Departure date | A specific, future date | A range of illustrative dates |
| Carrier and flight number | Identifiable operating airline | None, aggregator listing only |
| Fare status | Confirmed or held, not merely quoted | Quoted price only, no hold |
None of the five fields that a gate agent or border officer can actually verify were present. This is not a minor formatting issue; it is the difference between a document and a query result.
Why budget carriers enforce this more visibly than legacy airlines
The underlying liability framework is the same across the industry and traces back to the logic behind IATA Resolution 830d, documented as part of IATA's carrier compliance framework: an airline is financially responsible for passengers it boards who are then found inadmissible. Legacy carriers, with wider staffing and longer turnaround windows, tend to absorb ambiguous cases quietly. Budget carriers operating on tighter margins per seat, including Wizz Air, Ryanair, and easyJet, push the same liability check down to gate and check-in staff who have less time and less discretion to resolve an unclear document on the spot. The result is a check that looks stricter, though the underlying rule has not changed.
The corrected document set
| Field | Corrected document |
|---|---|
| PNR or booking reference | A confirmed Wizz Air return sector or a separately issued onward ticket, referenceable by name |
| Passenger name match | Rossi's full name as it appears on her passport |
| Departure date | A specific date within her permitted stay |
| Carrier and flight number | A named operating carrier, queryable in the global distribution system |
| Fare status | A booked reservation, paid or unpaid, not a quote |
Rossi resolved the hold by booking a genuine onward PNR from her phone at the desk, referenced against Wizz Air's own published document requirements, a dummy ticket for a return sector she had no intention of flying, which restored every field in the table above. Boarding proceeded roughly ten minutes later.
Generalising beyond this case
The same enforcement pattern recurs across budget carriers on one-way, visa-exempt routes into the UK and Schengen area, and it mirrors the document standards discussed in our dummy ticket versus real ticket compliance case study. The specific check performed at a Wizz Air or Ryanair desk is narrower than a full immigration review, covering PNR existence and currency rather than visa eligibility itself, a distinction unpacked further in airline check-in onward ticket verification.
This case also illustrates why compliance teams reviewing dummy or onward ticket documentation for clients should treat "confirmed" and "quoted" as distinct states, not interchangeable descriptions of the same booking. A quoted fare, however specific it looks with dates and a price attached, is not a reservation until a PNR is generated against it. Rossi's PDF quoted a fare range; it never crossed into reservation status, which is precisely why it failed every field in the gap analysis above rather than failing on a single technicality.
What this means for onward-ticket compliance more broadly
Organisations that advise employees or clients on travel documentation, including HR teams processing relocation cases and consultants preparing visa file checklists, should treat the budget-carrier check-in desk as an earlier and stricter enforcement point than the destination's border control. Advising a traveller to sort out proof of onward travel "at immigration if it comes up" ignores that boarding may be refused well before that stage, at a check-in counter with no appeal process and a flight closing in minutes.
Three compliance principles
A confirmed PNR is required; a search result or fare quote is not sufficient. Payment status is not the variable under review, a genuinely unpaid dummy ticket satisfies the same check as a paid one. Currency matters: the booking must reflect a plausible, future departure date, not an expired or illustrative one.
Frequently asked questions
Is a comparison-site PDF ever accepted as proof of onward travel?
No. It lacks a queryable PNR and cannot be verified against any reservation system, regardless of how detailed it looks.
Does this liability rule apply equally to budget and legacy carriers?
Yes, the underlying framework is identical. Budget carriers simply enforce it with less discretion at the point of check-in.
Would a paid return ticket have avoided this entirely?
Yes. A confirmed return booking satisfies the same requirement as a dummy ticket, since payment status is not the field under review.
Could this happen again on a connecting itinerary?
Only where the passenger clears immigration at the connection point. Airside transit without an immigration check does not trigger this review.
Rossi's case is not unusual. It's common. If your documentation would not survive the same five-field review, book a real onward ticket in two minutes.