Proof of Travel
Marco Ferreira, a Portuguese national, arrived at Manila's Ninoy Aquino International Airport Terminal 1 in April 2026 on QR 932 from Doha. At the primary immigration counter, the officer asked for proof of onward travel. Ferreira presented a PDF exported from a comparison website. The document displayed a route, dates, and a reference string labelled "booking reference." The officer typed the reference into the terminal. No record returned. Ferreira was referred to secondary inspection, where he spent 2 hours and 20 minutes before the duty supervisor authorised entry conditional on his purchasing a verifiable outbound flight before leaving the terminal.
The document Ferreira presented was not a GDS record. It was a comparison-site export. The distinction is the one that matters.
Document Gap Analysis: What Ferreira Presented vs. What Was Required
The Philippines' Bureau of Immigration requires proof of onward travel for nationalities entering on visa-exempt status. The requirement is not satisfied by a comparison-site itinerary, a screenshot, or a search-result export. It requires a Passenger Name Record, or PNR, that is queryable in one of the major Global Distribution Systems: Amadeus, Sabre, or Travelport (Galileo).
| Document field | Ferreira's comparison-site PDF | Compliant alternative |
|---|---|---|
| PNR present | No (internal site reference only) | Yes (six-character GDS code) |
| GDS queryable | No | Yes |
| Passenger name field | Shown on PDF, not in GDS record | In GDS record, matches passport |
| Booking status code | Not applicable | HK (confirmed) |
| Carrier GDS record | Not present | Confirmed, airline-matched |
| Departure date within stay | Date present on PDF, unverifiable | Date within 30-day VE window |
| Document source | Third-party comparison site | IATA-member carrier or authorised agent |
A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the full fare. The PNR exists in Amadeus or Sabre, returns HK status when queried, and carries the passenger's name exactly as it appears in the travel document. It is structurally identical to a paid booking from the perspective of a GDS terminal query.
The Regulatory Framework for Onward Ticket Verification at Immigration
The Philippines' Bureau of Immigration enforces onward travel requirements under Section 29(a) of Commonwealth Act 613, which permits refusal of entry to any alien who cannot demonstrate intent to depart. In practice, the bureau operationalises this as a proof-of-departure check at the primary desk.
Airlines operating into the Philippines are required under IATA Resolution 830d to verify onward travel before boarding. The carrier check at Doha, which Qatar Airways runs as standard procedure on Manila-bound passengers, should have flagged Ferreira's document at departure. It did not, either because the officer assessed the PDF as sufficient or because the check was not run on that specific passenger.
The immigration check at NAIA is independent of the carrier check. Passing one does not mean passing the other. In Ferreira's case, the boarding check and the immigration check produced different outcomes on the same document.
How Officers Query PNRs at Primary Desk
Officers at NAIA T1 use a terminal with direct GDS access. The query sequence is standard: the officer reads the PNR from the passenger's document, enters it in the terminal, and receives a response containing booking status, passenger name, carrier, route, and departure date.
The critical status codes are HK (hard block confirmed), UN (unable to confirm, supplier rejected), and XX (cancelled). An expired PNR, whether paid or dummy, returns XX. Comparison-site references return no result, since they are not GDS identifiers.
Officers do not see: fare paid, booking class, ticket price, or refundability conditions. The compliance requirement is met by a valid PNR at HK status with a departure date within the permitted stay window. Nothing more is required. Nothing else is relevant.
See how airlines verify onward tickets at check-in for a parallel analysis of the carrier-side verification process, which applies upstream of the immigration check.
Carrier Enforcement Patterns on Philippines-Bound Routes
The carrier check is the first intervention point. Several major carriers serving Manila have established specific procedures.
| Carrier | Hub | Onward verification method | Enforcement consistency |
|---|---|---|---|
| Qatar Airways | DOH | Timatic query at check-in, PNR required | High |
| Emirates | DXB | Timatic query, printout accepted if PNR present | High |
| Lufthansa | FRA, MUC | Agent check, PNR required for VE nationalities | High |
| British Airways | LHR | Timatic check, PNR required | High |
| Singapore Airlines | SIN | Timatic query, PNR required | High |
| Cebu Pacific | Regional | Check-in agent discretion varies | Medium |
| AirAsia | KUL, MNL | Agent discretion varies | Medium |
Ferreira's carrier, Qatar Airways, runs a consistent Timatic check. The failure to intercept his document at DOH is an anomaly, not standard practice. Travellers should not assume that passing the carrier check means the immigration desk will apply the same assessment.
The PNR Validity Problem
An additional compliance risk that Ferreira did not face, but that commonly affects travellers with valid-looking documents, is PNR expiry. A dummy ticket booked well in advance of a travel date may lapse before the travel date arrives if the booking's ticketing time limit expires.
PNR hold windows vary by carrier and GDS configuration. The mechanisms are analysed in detail in the onward ticket PNR validity compliance guide. For the purpose of border compliance, what matters is that the PNR status at the moment of immigration check is HK. An expired PNR returns XX and fails the same way Ferreira's document failed.
Compliant Document Set
A compliant proof-of-onward-travel document for a Philippines VE entry has the following characteristics:
| Field | Requirement |
|---|---|
| Document type | Real PNR from IATA-member carrier |
| GDS presence | Record queryable in Amadeus, Sabre, or Travelport |
| Passenger name | Matches passport exactly, including middle names |
| Status code | HK (confirmed) at time of immigration check |
| Departure date | Falls within the 30-day visa-exemption window |
| Route | Departs from the Philippines to any destination |
| Ticketing | Not assessed; irrelevant to immigration query |
Proof of Travel generates onward ticket PNRs on live carrier records, verifiable in Amadeus and available for real-time query at any GDS-connected immigration terminal. Order a compliant onward ticket here before your next Philippines entry.
Three Compliance Principles
This case study supports three principles that apply across all GDS-verified border checks, not only the Philippines:
First, a PNR is required, not a document. No printout, PDF, or screenshot substitutes for a GDS-queryable booking record. The officer isn't verifying the paper. They're verifying the record the paper refers to.
Second, the fare paid is not assessed. Compliance turns on status code, name match, route, and departure date. A dummy ticket satisfies all four criteria. Payment is not part of the query.
Third, timing is the second failure point. The PNR must be active at the moment of check, and the departure date must fall within the stay window being granted. Both conditions require attention before travel, not at the desk.
Frequently asked questions
Can the immigration officer see that a ticket is a dummy ticket?
No. The terminal query returns name, status, route, and departure date. There's no "dummy" flag in the GDS schema. A real PNR at HK status is a real PNR at HK status, regardless of how the booking was made.
What if the comparison-site document has a real PNR printed on it?
Some comparison sites do display actual airline PNRs alongside their own internal references. If the six-character GDS code is present and the booking is active, the officer's query will return a valid result. The problem in Ferreira's case was that the reference shown was a site-internal reference, not a GDS PNR. Always verify which reference type is shown before travel.
Does the duty supervisor at immigration have authority to admit passengers despite a failed onward check?
Yes. Secondary inspection officers and duty supervisors have discretion to grant entry on other grounds: demonstrated funds, credible purpose statement, same-day purchase of a verifiable ticket. However, this is discretionary and should not be relied upon as a contingency.
Is the onward ticket requirement enforced differently for different passport nationalities at NAIA?
The Philippines applies the onward ticket requirement selectively based on nationality risk profile. Nationalities with strong visa-exemption agreements face lighter scrutiny than those on heightened review lists. The requirement is formally applicable to all visa-exempt arrivals, but officer discretion determines how consistently it's applied at the primary desk.
How is "within the permitted stay" calculated when multiple stay windows apply?
Use the standard visa-exemption window for your nationality, which for most passport holders at NAIA is 30 days. If you hold a pre-issued visa with a fixed entry window, the departure date should fall within that window. When uncertain, set the onward departure conservatively inside the shorter of the applicable windows.