Lucas Hartmann, a German national and Berlin-based consultant, arrived at Frankfurt Airport Terminal 1 in February 2026 with a Lufthansa flight to Manila, a hotel booking for Makati, and no onward travel document. The Lufthansa check-in agent flagged the gap before boarding. Under IATA Resolution 735, the carrier bears the cost of returning a passenger refused entry. The agent asked for an onward or return ticket.

Hartmann did not have one. He held only a one-way booking from Frankfurt to Manila and a hotel confirmation for three weeks. Neither document constituted proof of departure from the Philippines under Section 29 of Commonwealth Act 613.

The Philippines' onward ticket requirement derives from Section 29(a)(7) of Commonwealth Act 613, the Philippine Immigration Act of 1940. It authorises immigration officers to exclude from entry any alien who cannot demonstrate the intention and means to depart. The Bureau of Immigration at NAIA and at every other Philippine international port operationalises this through a practical check: a confirmed PNR showing a departure within the permitted initial stay.

For German nationals under the bilateral visa exemption, the initial stay is 30 days. The departure document must show a booking dated within that 30-day window to be fully compliant with the officer's expectation.

A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the full flight fare. The term "dummy" refers to the booking's purpose, not its authenticity. The PNR record is live in the Global Distribution System and fully verifiable by any carrier or immigration authority with GDS access.

The Document Gap: What Hartmann Presented vs. What Was Required

In twelve years reviewing immigration compliance files, this is the most common confusion I encounter: travellers who conflate accommodation evidence with departure evidence. They're not the same document under Section 29, and no officer at NAIA treats them as equivalent.

The table below sets out the documents Hartmann held against the Bureau of Immigration's standard expectation for a visa-exempt arrival:

Document Presented by Hartmann Required under CA 613, Section 29
Valid passport (German) Yes Yes
Inbound flight confirmation Yes (LH 738, FRA-MNL) Required by carrier, not by BI
Onward or return flight with PNR No Yes, departure within permitted stay
Hotel accommodation booking Yes (Makati, three weeks) Not required; does not substitute for departure evidence
Itinerary letter from travel agent No Not recognised as proof of departure
Visa exemption applicable Yes (30-day tourist) N/A: exemption covers visa only

The hotel confirmation was not a substitute for the onward ticket. It evidenced intent to stay, not intent to depart. Without a departure booking, Hartmann's documentation set was non-compliant at carrier check-in.

The Carrier's Position: IATA Resolution 735

Lufthansa's obligation to check arose from IATA Resolution 735, which assigns to the transporting carrier the cost and responsibility of returning a passenger refused entry at the destination. An agent who allows a passenger to board without the required documentation, and that passenger is subsequently refused entry at NAIA, faces a repatriation liability.

The agent at Frankfurt Terminal 1 was acting within standard carrier compliance protocol. This wasn't a discretionary ask. It was the standard documentation check applied on this route.

Hartmann had approximately 40 minutes before boarding closed. He booked a dummy onward ticket through Proof of Travel, received a confirmed PNR within two minutes, and returned to the check-in desk. The Lufthansa agent verified the code in the GDS, confirmed the departure date fell within the 30-day stay window, and completed check-in.

The Compliant Document Set

Following the booking, Hartmann's documentation was fully compliant:

Document Status post-booking Notes
Valid passport (German) Compliant Confirms visa exemption for 30 days
Inbound flight (LH 738) Compliant Real-time PNR, name confirmed
Onward flight PNR Compliant Live GDS record, departure within 30-day stay
Hotel booking Supplementary Not required under CA 613 but supports declared purpose

At NAIA immigration, the Bureau of Immigration officer at primary inspection reviewed the passport and asked Hartmann where he was going after the Philippines. He produced the onward booking reference. The officer confirmed the departure date fell within the permitted stay and stamped admission for 30 days. No secondary inspection was required.

Document Compliance Guidance for Philippine Entry

The Hartmann scenario is a common one, particularly for travellers accustomed to destinations where departure evidence isn't checked at origin. Several structural points arise from it.

First, the onward ticket requirement is a carrier obligation before it's an immigration one. The check-in agent enforces it first because the carrier bears the liability. Even if an immigration officer were somehow to overlook the check on arrival (which Section 29 doesn't permit), the traveller would first need to pass the carrier's gate check.

Second, hotel bookings don't substitute. This misconception is widespread and arises from conflating accommodation evidence with departure evidence. The two are legally distinct under Section 29.

Third, a dummy onward ticket with a live GDS record is identical in evidentiary value to a fully-paid flight booking at the point of check. The officer or agent looks up the PNR. If it resolves to an active booking with the correct name and a plausible departure date, the requirement is met.

For the document verification mechanics across carrier types and the GDS status codes relevant to onward ticket validity, the airline check-in onward ticket compliance analysis covers this in detail. For the PNR validity windows relevant to visa applications ahead of travel, see the onward ticket PNR validity compliance case study.

The UK Government's Philippines travel advice and IATA's Timatic documentation database both confirm the departure evidence requirement for visa-exempt arrivals at Philippine ports.

If you're flying to Manila and haven't arranged departure evidence yet, book a verified onward ticket through Proof of Travel before check-in.

Frequently asked questions

Is the onward ticket check done at the airline or at immigration?

Both. The carrier enforces it at origin check-in under IATA Resolution 735 liability rules. The Bureau of Immigration enforces it at primary inspection under Commonwealth Act 613, Section 29. A valid document satisfies both.

Does a valid PNR have to be on a major carrier?

No. Any carrier operating scheduled international services from a Philippine airport is acceptable. The PNR must be verifiable in a GDS system. PNRs from Cebu Pacific, AirAsia, and Scoot resolve correctly in standard GDS queries.

What is the minimum validity period for the PNR at Philippine immigration?

The officer's concern is whether the PNR is active at the moment of inspection. A live record on the day of arrival satisfies the requirement. PNRs typically expire 48 to 72 hours after booking unless extended. Book accordingly.

Can a return ticket to the country of origin serve as an onward ticket?

Yes. A return ticket to Germany, for instance, satisfies Section 29 equally. The departure evidence requirement doesn't specify a third country. It requires proof of departure from the Philippines within the permitted stay.

What documentation applies on re-entry after a visa run?

At each re-entry, the traveller is on a new permitted stay, and a current onward ticket is required for each entry. The Bureau of Immigration maintains no standing record of a traveller's previous onward booking. Maintain a current booking at each entry point.