India e-Visa Onward Ticket Compliance: A Case Study from FRA-DEL

Petra Novak, a Slovak national holding a 30-day e-Tourist visa for India, presented at the Lufthansa check-in counter at Frankfurt Airport (FRA) for flight LH 761 to Delhi Indira Gandhi International (DEL). Her document set included a valid passport, the Indian e-Visa printout, a hotel booking confirmation from Booking.com, and a screenshot of a return fare from Skyscanner. Lufthansa's check-in agent queried the Timatic record for a Slovak passport with an Indian e-Tourist visa. The system returned a "may require" flag for onward or return travel evidence. The agent requested a verifiable departure booking. Neither the hotel confirmation nor the Skyscanner screenshot contained a PNR. Boarding was denied.

A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. Novak's case illustrates the most common India check-in failure pattern: the traveller arrives with evidence of accommodation intent but no verifiable departure booking.

The Regulatory Framework

India's Bureau of Immigration does not publish a standalone onward-ticket mandate as a single identifiable statute. The operative authority derives from two sources. First, the Foreigners Act 1946 grants immigration officers broad discretion to require any evidence they consider necessary when assessing whether a foreign national should be admitted or what conditions should govern their stay. Second, IATA Timatic records India as a destination where carriers "may require" proof of onward or return travel.

Lufthansa's obligation is both contractual and regulatory. Under the IATA Conditions of Carriage and standard carrier liability rules, an airline that transports a passenger who is subsequently refused entry at the destination bears the cost of deportation and return transport. This gives carriers a direct financial incentive to enforce Timatic requirements at departure, not to leave compliance screening to destination immigration.

Document Set Analysis: What Novak Presented

Two of four documents were compliant with India's general entry conditions. Two were presented to address the departure-intent requirement but contained no verifiable reference. The gap is structural, not incidental.

A hotel booking demonstrates accommodation intent, not departure intent. A Skyscanner screenshot shows that a fare was researched, not that a booking was made. Neither constitutes onward travel evidence under Timatic's India standard. This distinction is consistent across all four major GDS platforms: Amadeus, Sabre, Travelport, and Farelogix all return null on queries for non-existent or expired PNRs.

What a Compliant Onward Ticket Must Contain

For India entry at the boarding stage, a compliant onward ticket must satisfy three criteria:

1. A live PNR registered in a GDS accessible to the carrier's check-in system at the time of the query.
2. A passenger name that matches the travel document presented.
3. A departure routing from an Indian airport to any international destination, dated within the permitted stay period stated on the visa.

The destination does not need to be the passenger's country of residence or domicile. Routings from DEL or BOM to Bangkok (BKK), Colombo (CMB), Dubai (DXB), or Doha (DOH) all satisfy the requirement. The route must originate from India.

For the technical detail on GDS status codes that carriers use to assess PNR health at check-in, see the airline check-in onward ticket document compliance analysis.

Novak's Resolution: The Corrected Document Set

Novak obtained an onward ticket from Proof of Travel before the gate closed, providing a PNR for a DEL-DXB routing dated day 26 of her 30-day permitted stay. The corrected document set:

The Booking.com and Skyscanner documents were set aside. Three compliant documents satisfied the check-in requirement and Novak boarded on schedule.

Timing and PNR Validity Considerations

Novak's case also highlights a validity-window risk that applies even to travellers who do book onward tickets in advance. A PNR issued at the e-Visa application stage, typically 30 to 90 days before travel, may expire before the departure date.

PNR validity windows range from approximately 14 days to 72 days depending on the carrier, the inventory class used, and the ticketing time limit applied by the GDS. For India travel, the relevant validity window is from the moment of the check-in query, not from the moment the dummy ticket was issued. A PNR that was live at visa application but has since lapsed will return no result when the carrier queries it at the departure gate. For a detailed case study on PNR validity windows and their compliance implications, see onward ticket PNR validity: a document compliance case study.

PNR validity scenarios for India-bound travel

Structural Implications for India-Bound Document Sets

Novak's case is structurally representative of a recurring compliance failure at European departure points for India-bound flights. India's e-Visa portal does not prompt applicants to book onward travel before applying. The onward-ticket requirement surfaces at the carrier's check-in counter, not at the application stage, which means a traveller can hold a valid e-Visa and still be non-compliant under the carrier's boarding criteria.

Don't assume the e-Visa satisfies the carrier's compliance check. The e-Visa addresses the right to enter India. The onward ticket addresses departure evidence. They're two separate requirements and both must be present in the document set.

A hotel confirmation is not a substitute for an onward ticket. A search-results screenshot is not a substitute. The document that satisfies the requirement is a live, name-matched PNR showing departure from India within the permitted stay window.

If your onward plans aren't confirmed at booking time, book a verified onward ticket through Proof of Travel before you travel, not at the departure counter.

Frequently asked questions

Does holding an Indian e-Visa mean the carrier won't ask for onward travel evidence?

No. The e-Visa establishes the right to enter India. The carrier's check-in query is a separate assessment under Timatic, which operates independently of the visa type held.

Can a traveller re-present after a boarding denial if they obtain an onward ticket at the airport?

Yes, provided the gate is still open and the document is obtained before the departure cutoff. Novak's case demonstrates this outcome. The window is narrow; departure-day corrections carry significant operational risk and are not a planning strategy.

Is the Timatic "may require" standard different from a hard requirement?

In compliance terms, a "may require" entry means the carrier has discretion to enforce. Most carriers operating European or Gulf routes into India treat the India onward-travel flag as a standard boarding requirement to avoid deportation liability. Discretion, in practice, tends toward enforcement.

What is the minimum notice period for booking an onward ticket before India travel?

PNR propagation across GDS systems takes 12 to 48 hours after issue. Booking an onward ticket less than 24 hours before departure carries the risk that the record hasn't replicated to the carrier's check-in system at the time of query.

Does the departure airport on the onward ticket need to match the Indian arrival airport?

No. Arriving at DEL and presenting a departure from BOM is acceptable. The onward ticket requirement is departure from India, not departure from the specific port of entry.