Consider the file of an illustrative applicant, a software contractor from Lagos applying for a Schengen visa in Amsterdam. He booked a dummy ticket, also called an onward ticket, a real PNR held in Amadeus for a Paris-to-Lagos return leg, six weeks before his consulate appointment. By the time he printed it for the interview, the PNR had vanished. The airline hadn't singled him out. His ticketing deadline had simply passed.

That gap, between what a held booking promises and what actually survives to the appointment or the gate, is the question worth answering properly: will the airline cancel a held reservation, and on what schedule does it happen?

What "held" means inside the reservation record

A booking made through a real GDS channel is a live PNR: a named passenger, a flight number, a status code, sitting inside a system such as Amadeus, Sabre, or Travelport. It looks identical to a paid reservation right up until someone tickets it. What keeps it alive isn't goodwill, it's time. Airlines assign every unticketed PNR a ticketing deadline, and once that deadline passes, the reservation is normally purged automatically so the seat returns to inventory. IATA's PNRGOV framework, which sets out how carriers exchange booking data with government systems, treats these records as structured and time-bound rather than static, which is exactly why they don't just sit there.

For a booking held purely to satisfy a visa officer or a border check, that distinction matters. The record is real. Its lifespan isn't.

The clock that actually does the cancelling

Airlines don't run enforcement sweeps looking for onward tickets bought for paperwork rather than travel. They don't need to. Revenue management does the work for them: a seat held indefinitely without payment is a seat that can't be sold to anyone else, so most carriers' inventory systems are built to reclaim unticketed holds on a fixed timetable rather than on request.

That's a useful distinction to hold onto. The cancellation isn't a judgment about intent. It's a housekeeping function that runs whether the passenger behind the PNR is flying next Tuesday or was never planning to fly at all.

Three routine triggers, not targeted enforcement

The ticketing deadline lapses

This is the most common cause. Every unticketed PNR carries a deadline set by the operating carrier, sometimes visible in the booking confirmation, sometimes not. Once it passes, most systems auto-cancel the segment without notice.

The schedule changes underneath you

Airlines revise timetables constantly. A schedule change can force a PNR into re-validation, and a hold that isn't actively managed can drop out of the system during that process instead of being reissued automatically.

A fare rule or deposit condition gets flagged

Some fare classes require a deposit or a minimum-payment check before a set date. If that condition isn't met, the segment can cancel even though the passenger's name, flight, and dates never changed.

None of this requires anyone at the airline to have decided a booking "looked like" a dummy or onward ticket. The same triggers fire for a paying traveller who forgets to complete a deposit.

Full-service and budget carriers don't manage holds the same way

Full-service carriers on Amadeus or Sabre tend to run longer, more predictable ticketing windows, since a large share of their bookings involve agents and corporate travel accounts that need lead time. Low-cost carriers, several of which sell largely through their own direct-booking engines rather than a traditional GDS, often expect payment at the point of booking in the first place, which leaves far less room for an unticketed hold to exist at all. The practical result is the same either way: the earlier a booking is made relative to the date it needs to survive until, the more the ticketing deadline becomes the deciding factor rather than the passenger's own plans.

How the booking states compare on the file

Booking state What the GDS shows What a border officer sees on request Typical risk of disappearing before travel
Held, unticketed, for visa purposes Live PNR, no ticket number issued A real reservation, name and flight visible High, tied directly to the ticketing deadline
Ticketed and paid in full Live PNR plus ticket number Confirmed, not subject to the deadline mechanism Low
Refundable fare held with deposit Live PNR, partial payment on file Reservation with a payment trail Moderate, depends on deposit terms
"Reservation" from an unofficial generator No real GDS record at all Nothing that verifies on the airline's own system Certain, it was never a bookable PNR in the first place

The pattern worth noticing: the deadline risk applies to any unticketed hold, not only to ones booked specifically as onward tickets for immigration purposes. A dummy ticket issued through a real GDS channel carries the same clock as any traveller's unpaid hold. It just has less reason to be extended, since nobody intends to come back and pay for the flight.

Checking your own deadline instead of guessing

Most travellers never look. The booking confirmation email rarely spells out a ticketing deadline in plain language, and the date sitting on the PDF is the departure date, not the date the hold itself expires. Two checks are worth doing before assuming a held PNR will simply wait: pull up the reservation on the airline's own manage-booking page using the record locator, not a screenshot or an old confirmation email, and if the site shows a "ticket by" or "time limit" field, treat that date, not the flight date, as the one that actually governs the booking.

A booking that still shows active today can still disappear next week if the deadline falls in between. That's the part a printed itinerary can't tell you. If a consulate visit or a boarding gate is still two or three weeks out, book the hold closer to the date its deadline is likely to fall, rather than simply as early as possible. How long an onward ticket's PNR stays valid depends on the fare class and the carrier, so it's worth checking that window before relying on a single booking to outlast a long wait. And if the mechanics of the hold itself are unclear, it helps to read how GDS holds and PNRs actually work before assuming a booking will simply wait for you.

For a Schengen file specifically, supporting travel documents are generally expected to reflect a traveller's current, workable itinerary, not one filed and forgotten months in advance.

None of this means a held onward ticket is unreliable by design. It means it behaves like what it is: a live airline record with its own expiry logic, not a static document that outlasts the system that created it.

Book a verifiable onward ticket through Proof of Travel timed to actually survive until your appointment or your flight, not just to exist on paper today.