My Dummy Ticket
Why does my onward ticket suddenly show as "not found"?
You booked it two weeks ago. You've got the PDF, the PNR code, everything. Then you type that same code into the airline's "Manage My Booking" box the night before your flight and get a blunt "reservation not found." A dummy ticket, also called an onward ticket, is a real flight reservation, a genuine PNR issued through an airline's or travel agent's booking system, held for a visa application or border check without the flight actually being flown. The booking is real. The lookup tool that's supposed to confirm it is a separate, much fussier piece of software, and that's where most of these scares come from.
This isn't rare. It's one of the more common panic messages Priya at My Dummy Ticket hears about, right up there with denied boarding and expired PNRs.
Is a GDS booking different from what shows up on the airline's own website?
Often, yes, at least for a while. Most travel agencies and onward-ticket services book through a Global Distribution System (GDS) like Amadeus, Sabre, or Travelport, and the record created there is technically a PNR sitting in the GDS, cross-referenced into the airline's own reservation system. IATA's PNRGOV programme exists specifically because governments and airlines need a consistent way to exchange passenger record data, which tells you the industry itself treats "the booking" and "what shows up in any one lookup tool" as two separate things.
A few concrete reasons the airline's own site might not find it:
- Sync delay. A GDS booking can take anywhere from a few minutes to a few hours to fully propagate into the airline's direct-facing website, especially on a codeshare or interline itinerary.
- Name formatting mismatch. "Jean-Pierre" entered as one field versus two, a missing middle name, or a transposed surname and given name can make an otherwise valid PNR invisible to a strict lookup form.
- Reservation-only vs ticketed status. Some onward bookings are held as a reservation without a ticket number attached yet. Many airline self-service tools will only display bookings that already carry an issued ticket number, not a bare reservation.
- Third-party consolidator codes. If the ticket was issued through a consolidator or an agency using its own booking class, the airline's public-facing tool sometimes needs the agency's locator rather than the six-character PNR you were given.
- Scheduled maintenance or a temporary outage. Airline websites go down for maintenance windows too, same as any other system.
None of these mean the flight reservation doesn't exist. They mean one specific lookup channel hasn't caught up with it yet.
What should I actually do if the airline's site won't confirm my ticket?
Work down this list before you panic.
- Re-check the exact spelling. Compare the name on your passport, letter by letter, against what's in the booking. A single swapped letter is enough to break a lookup.
- Try the airline's app instead of the browser site, or the other way around. They don't always query the same backend cache.
- Call the airline directly and give them the PNR over the phone. A human agent with terminal access can usually see a booking the website can't.
- Ask whoever issued the ticket to confirm ticketing status. If it's still "on hold" with no ticket number, that's the fix, not a website bug.
- Keep the original confirmation email or PDF as your primary proof. For a visa application or a border officer, the document you were issued is usually what matters, not whether a specific self-service page loads it on a given evening.
If you're using My Dummy Ticket's booking service and a reservation genuinely won't confirm after 24 to 48 hours, flag it to support rather than assuming the trip is unbooked.
Manage-my-booking site vs check-in desk vs immigration desk: do they see the same thing?
Not always, and that's the part that trips people up.
| Checkpoint | What it actually checks | Typical failure mode |
|---|---|---|
| Airline's "Manage My Booking" page | Ticketed bookings synced to that airline's own web backend | Shows "not found" for fresh or reservation-only PNRs |
| Check-in counter or kiosk | Direct GDS or departure-control system query, usually real-time | Rarely fails on a valid PNR, but can flag one-way tickets for onward-proof review |
| Immigration or border officer | The physical or digital document you present, sometimes a quick verbal check with the airline | Almost never queries the GDS directly, relies on what you hand over |
Border officers and check-in agents are generally working from different systems than the consumer-facing website. That's exactly why a "not found" result on a phone browser doesn't mean immigration or the gate agent will see the same error.
How do I stop this from happening on my next booking?
Book with enough lead time that a sync delay isn't a same-day emergency. Double-check name spelling against your passport before you submit any booking request. And if you're relying on the ticket for a specific visa application, confirm with the issuer that it comes back as a fully ticketed PNR, not a held reservation, since that status is what most consulates and self-service tools actually check.
If you've already gone through a self-check and the PNR itself looks fine, the guide on how to check your onward ticket PNR yourself walks through the same lookup tools this article is talking about, step by step. And if the confirmation trouble escalates all the way to a gate agent refusing boarding, the piece on denied boarding for a missing onward ticket covers what to do in that specific moment.
Singapore Airlines' own manage booking page is a useful example of how narrow these tools can be: it's built around a ticketed confirmation number and a surname match, not a general PNR search, which is exactly the kind of mismatch that produces a false "not found."
Frequently asked questions
My PNR shows up on the airline app but not the website. Which one is right?
Both can be right at different times. Apps and websites sometimes pull from different cached layers, so treat a mismatch as a sync issue, not proof the booking failed.
Will an immigration officer try to look my ticket up online themselves?
Usually not. Most border checks rely on the document you present rather than a live database query, though officers can and do call an airline to confirm in ambiguous cases.
Should I panic if the booking still won't show 12 hours before my flight?
Not yet. Call the airline or your ticket issuer directly rather than repeatedly refreshing the same web form. A phone agent can usually see more than the public site does.
Does this happen more with one-way or onward bookings specifically?
It can, particularly with reservation-only PNRs that haven't been ticketed, since some self-service tools only display bookings with an issued ticket number attached.
Sort out a verified onward ticket through My Dummy Ticket's booking service so you've got a document ready before any lookup tool gets involved.