The $1,863 mistake: Why a missing last name cost one passenger his ticket
in this case
- Saurabh Kumar’s passport lists his full name in the given-name field and leaves the surname blank, common in parts of the world, but a problem for airline systems that demand a last name. Booking on Expedia, he split it into a first and last name to get past the form.
- He had done the same thing before and flown without trouble. This time, at Toronto Pearson, Porter Airlines would not issue a boarding pass over the mismatch between his ticket and his passport, and told him only Qatar Airways, the ticketing carrier, could authorize a correction.
- With his flight closing and the airlines pointing at each other, he bought a costly last-minute replacement ticket to reach his family. His case sits at the intersection of rigid security rules, aging airline technology, and a booking form that forced him to enter data his passport does not contain, raising the question of who is responsible when the interface itself sets the trap.
Saurabh Kumar had a passport, a plane ticket, and a plan to visit Delhi. He was good to go-or so he thought.
Kumar had booked his flight months in advance through Expedia, securing a complex itinerary that would take him from Toronto to Montreal, then on to Doha, and finally to India.
But Kumar had a problem he didn't quite understand until he was standing at the check-in counter at Toronto Pearson Airport: Technically, he has one name.
His passport lists his given name as “Saurabh Kumar.” It leaves the last name field blank. This is not uncommon in some parts of the world, but it is a digital headache for the rigid, binary brains of Western airline reservation systems.
When he tried to book the flight on Expedia, the website demanded a last name. It wouldn’t let him proceed without one.
So Kumar improvised. He did what any reasonable person trying to navigate a stubborn web form would do: He split his name in two.
“I entered ‘Saurabh’ as my first name and ‘Kumar’ as my last name while booking, since Expedia's system requires a last name,” he explains.
It seemed like a harmless administrative workaround, a logical fix to a digital problem. He had even done it before with American Airlines and flown without a hitch. He clicked “buy” and received his confirmation.
Not so fast
He didn’t know it yet, but that simple improvisation had just doomed his trip. When he arrived at the airport ready to board his Porter Airlines flight to Montreal for the first leg of his journey, the computer stopped him.
This case raises a few difficult questions about the intersection of rigid security protocols, archaic airline technology, and common sense in modern travel. We’ll answer these questions:
- Why are airline reservation systems so unforgiving when it comes to name formats, even when the person standing at the counter is clearly the person on the passport?
- What is the correct way to book a ticket if you have a mononym or a passport with no surname, and why is “guessing” the most dangerous thing you can do?
- Who is responsible when an online travel agency's interface forces a user to enter data that technically renders their ticket invalid?
A check-in nightmare
Kumar arrived at the airport with his bags packed, expecting a routine check-in. He had paid $1,497 for his roundtrip ticket. The itinerary was a bit of a patchwork quilt, involving Porter Airlines for the domestic leg and Qatar Airways for the long haul.
But the trouble had started even before he got to the airport. When he attempted to check in online, the system blocked him. Porter gave him an error message that online check-in was only available for U.S. and Canadian passport holders. It was a red flag, but one that could usually be resolved by a human agent at the desk verifying his visa and documents.
When he handed his passport to the Porter Airlines staff, the mood shifted from routine to rigid. The agent looked at the passport. He looked at the ticket.
The ticket read: Kumar, Saurabh.
The passport read:
Given Name: Saurabh Kumar
Surname: Blank
To a human being using common sense, this is obviously the same person. To a security protocol designed to screen millions of passengers against international watchlists, it was a mismatch.
Porter's staff refused to issue a boarding pass. They told him the “correction could be made only with Qatar Airways' approval,” according to Kumar.
Ah, the Catch-22 of modern aviation. When you book a ticket that spans multiple airlines-known in the industry as an “interline” booking-the first carrier (Porter) is often hamstrung by the rules of the ticketing carrier (Qatar). Porter’s agents couldn’t just change the name in the system because the ticket wasn’t theirs to change.
“I was refused check-in due to a minor name mismatch caused by the booking system requiring a last name,” Kumar says. “My passport does not have one.”
He was stuck. He frantically tried to contact Expedia and Qatar Airways from the airport terminal, but the clock was ticking. The flight was closing.
He was denied boarding.
To get to India, he had to make a desperate choice. He pulled out his credit card and bought a replacement ticket on the spot. An agent filled in the correct fields. The price for the last-minute, one-way fare was $1,863- significantly more than the cost of his original roundtrip.
Is there a ‘close enough’ rule when you’re flying?
Here’s the cold, hard truth about air travel: “Close enough” counts in bocce, but not in aviation security.
In a post-9/11 world, passenger data is shared with immigration and border agencies worldwide. This is the Secure Flight program in the U.S., and similar APIS (Advance Passenger Information System) protocols exist globally. The name on your ticket must match the name on your government-issued ID character for character.
This creates a massive headache for the millions of people globally who do not follow the Western “First Name, Last Name” naming convention. Passports from India, Indonesia, and many other nations often list a single name or place the entire name in the “Given Name” field.
But airline websites are built on databases that demand two fields. They are binary systems in a nonbinary world.
If you don’t have a last name, there are specific, rigid protocols for how to book a ticket.
No guessing, no improvising.
So what is it? The standard convention for most airlines is to use “LNU” (Last Name Unknown) in the surname field. Alternatively, some airlines require you to repeat your first name in the last name field (e.g., Saurabh Kumar Saurabh Kumar) or use “FNU” (First Name Unknown) if the name is in the surname field.
“If a traveler is unsure of how to enter their name or finds a mistake after booking, they should contact our customer support team immediately,” an Expedia spokesperson later explained regarding the incident.
But Kumar didn’t know the secret code. He just wanted to fill in the boxes on the screen so he could visit his family in India.
The investigation
Kumar contacted my advocacy team months after the incident, still stinging from the financial hit. He felt that he had been led into a trap. He argued that Porter Airlines bore the responsibility for denying him boarding over what was, effectively, a technicality.
“The refusal was due to an administrative mismatch and interline approval process-not my fault,” he insisted. He pointed out that his passport and identity were valid and he was ready to travel.
He felt the system had failed him, and he wanted a refund.
“I entered ‘Saurabh’ as my first name and ‘Kumar’ as my last name while booking, since Expedia's system requires a last name,” he reiterated to my team. “I followed the same process last time when I booked through Expedia with American Airlines, and everything went smoothly without any issues.”
That’s the most dangerous part of this story: It worked once. Because American Airlines had apparently let it slide (or their system auto-corrected it), Kumar assumed he had found the correct way to navigate the Expedia form. He hadn’t. He had just gotten lucky. And when he tried to fly to Delhi, his luck ran out.
I contacted Expedia to see if they could secure a goodwill exception. It was a long shot. The ticket was nonrefundable, the flight had long since departed, and the error-technically-was the passenger’s.
Expedia's response was sympathetic but firm on the rules.
“When booking flights on Expedia, travelers are reminded that their name must match their government ID,” a representative told us.
Still, Expedia agreed to reach out to Qatar Airways, the airline that actually owned the reservation, to see if it would retroactively fix the mess or offer a refund.
The complexity of interline tickets
This case highlights a specific peril of booking flights that involve multiple carriers. Kumar's itinerary was a nightmare for resolving disputes. He bought the ticket on Expedia. It was ticketed by Qatar Airways, but the first flight was operated by Porter Airlines.
When you have a problem with a ticket like this, the finger-pointing begins immediately. Porter says, “Not our ticket, talk to Qatar.” Qatar says, “You're at the Porter counter, talk to them.” Expedia says, “We just sell the tickets, talk to the airline.”
The reality is that name corrections on interline tickets are notoriously difficult. If it were just a Qatar Airways flight, the airline might have been able to fix the ticket and let him fly. But because the reservation data had to pass from Qatar's system to Porter's system, the names had to match exactly to validate the flight coupons.
When they didn’t match, the electronic handshake between the airlines failed. Porter couldn’t change his ticket to let him board. And because the flight was imminent, there was no time to reissue the ticket.
The verdict
This is where the story takes an unfortunate turn. You might expect the airline to look at the passport, see that it was clearly the same person-Saurabh Kumar standing in front of them-and issue a refund for the unused ticket.
But you’d be wrong.
Expedia came back to us with the final word from the airline.
“Unfortunately, Qatar Airways' policy does not allow name corrections for itineraries with flights operated by multiple airlines,” the Expedia spokesperson told me.
Because the itinerary involved Porter Airlines, a simple name fix wasn’t possible. The policy is rigid. If you fly on a plane operated by a partner, the name on the PNR (Passenger Name Record) must be perfect.
“Since Saurabh's itinerary included Qatar Airways and Porter Airlines flights, a name correction was not possible,” Expedia explained.
And what about a refund now?
“We reached out to Qatar Airways on Saurabh's behalf to see if a refund or compensation could be offered,” Expedia said. “However, they are not able to, and we adhere to all our partners' policies.”
There is a small silver lining, though it's faint. Expedia agreed to process an $840 refund for taxes and fees.
As for the rest of his money, it’s gone.
The takeaway is brutal but simple: If your name doesn’t fit the little boxes on the screen, don’t guess, and don’t improvise. Call a professional. If you force a square peg into a round hole on an airline website, you might end up paying for the privilege of staying home.
If you have a mononym or a complicated passport name, use a travel advisor who knows how to enter the specific codes (LNU/FNU) required by the airlines. Or contact the airline and have an agent book the flight. A computer booking engine doesn’t have the capacity for nuance, and an airport check-in counter is the wrong place to try and debug a reservation error.
Your voice matters
A booking form that demands a last name can trap travelers whose passports do not have one. Kumar’s case raises real questions about who should bear the risk.
- If a booking site forces you to enter data your passport does not contain, like a surname you do not have, should the site be responsible when that entry invalidates your ticket?
- Should airlines and booking platforms be required to properly support mononyms and passports with no surname, rather than making travelers guess at a workaround?
- Have you ever run into a form or system that could not handle your name, address, or documents correctly? How did you get around it?
Booking a flight with a mononym or no surname: what to know
Travelers whose passports list a single name face a hidden trap in airline booking systems. Here is what to know before you book.
Why do airline systems reject a name that clearly matches the passport?
Because the match is done by computer, not by a person. Passenger data is checked against international watchlists through programs like Secure Flight and Advance Passenger Information System protocols, and those systems expect the ticket name to match the ID character for character. A human agent may see the same person, but the automated handshake between systems does not allow for judgment.
What is the correct way to book if I have no surname?
Do not guess. Airlines use set conventions for missing names, such as “LNU” for last name unknown, “FNU” for first name unknown, or repeating your name across both fields. The right one depends on the airline, so the safest path is to have an airline agent or a knowledgeable travel advisor enter it for you.
Why is improvising a name split so risky?
Because it can technically invalidate your ticket while appearing to work. Splitting a single name into a first and last name may pass the booking form and even clear one flight, but the next airline’s system may reject the mismatch and deny boarding. Getting away with it once does not mean it is correct.
What makes multi-airline (interline) tickets especially tricky?
When one booking spans several carriers, the ticketing airline owns the reservation and the operating airline often cannot change it. The name has to pass cleanly from one airline’s system to another, so a mismatch can freeze everyone: the operating carrier cannot fix a ticket that is not theirs, and time runs out before the ticketing carrier can reissue it.
Who is responsible if the booking form forced the bad entry?
This is the hard question at the center of such cases. The traveler entered the data, but only because the form demanded a surname the passport does not contain. Booking platforms generally remind travelers that the name must match their ID and advise contacting support with any uncertainty, which places much of the practical burden on the traveler to get it right before flying.
Can a name error be fixed at the airport?
Usually not in time. A check-in counter is the wrong place to debug a reservation, especially on an interline ticket, because the agent in front of you may not have the authority to change it and the flight is often minutes from closing. Corrections should be handled well before the day of travel.
How can I protect myself before I travel?
If your name does not fit the standard fields, book through the airline directly or use a travel advisor who knows the correct codes. Verify the reservation name against your passport as soon as you book, and resolve any discrepancy with customer support long before your departure. For more help with travel disputes, see Elliott Advocacy’s travel resources.
Copyright 2026 Elliott Report
This story was originally published July 14, 2026 at 6:00 AM.