September 5, 2026

BA’s booking system created the name error that blocked a baby from flying

British Airways Airbus A320 landing at Heathrow, London on a clear day.

One letter, 35 hours, no way out

Fleur Lonsdale was travelling solo with her one-year-old son Oakley on a 35-hour journey when British Airways refused to let the infant board at Auckland Airport. The cause was not her mistake. It was BA’s booking system, which printed only the first letter of Oakley’s first name and four letters of his surname on the ticket.

Lonsdale had spotted the error back in February 2026 when she booked, contacted BA’s online chat, and was told it was a known system fault that would not affect boarding. It did. At the gate, the flight’s actual operator told her she needed a name correction form from British Airways. BA’s phone support could not produce one, and at one point an agent left the call to go home mid-process. She broke down in tears before a supervisor finally escalated the matter and rebooked her for the next day.

BA later put it in writing, acknowledging her frustration that the problem stemmed “from a system-related issue rather than any error on your part”. When RNZ asked directly whether the error was known and whether there were plans to fix it, BA did not answer. It paid for accommodation and food and issued a goodwill voucher. It said nothing about repairing the system that caused the whole thing.

The pattern is the story

One stranded passenger is a bad travel day. A documented pattern is a systems failure. In February 2025, Hertfordshire designer Claire Hannington was wrongly refused boarding at Gatwick for a BA flight after staff applied incorrect passport rules, then spent 12 weeks chasing compensation only for BA to deny liability and, she said, falsely claim she had missed check-in.

More recently, in August 2026, South African travel agents raised formal complaints about BA’s disruption handling. Jacques Louw of XL Sandown Travel said he found it “concerning that my clients sometimes receive information about changes to their bookings before I do,” leaving agents unable to help and forced to buy replacement tickets on other carriers then chase BA for refunds.

The pattern is not unique to BA. In September 2024, an Auckland father could not send his three-month-old daughter overseas after a travel agent put their own name on the infant’s ticket, a practice the agency called “common”. In March 2025, the Disputes Tribunal ordered an airline to pay a couple $700 after boarding pass confusion, with the referee finding it “fell upon the airline to display accurate and clear information to passengers”.

Rights that might as well not exist

New Zealand’s consumer protection framework leaves passengers badly exposed. Consumer NZ research shows 90% of New Zealanders are unaware of their air travel rights, and 75% rely solely on airlines for disruption information. Campaigns manager Jess Walker put it plainly in July 2026: “if people don’t know their rights, those rights might as well not exist.”

Consumer NZ has been blunt about the incentive at play, noting “it’s in an airline’s interest to control how and what information is shared, because it costs an airline to comply with the law and pay compensation.” A petition of over 10,500 signatures has gone to parliament seeking EU-style rules forcing airlines to inform passengers of their rights at the point of disruption. TAANZ, meanwhile, welcomed the development of an Aviation Consumer Charter in July 2026, noting support levels “can vary depending on circumstances”.

What this means for anyone with a travel programme

The scale of exposure is not trivial. NZ Customs recorded 674,679 international departures in January 2025 alone, and BA, Qatar and Iberia together serve roughly 548 New Zealand routes based on summer 2024 data. For corporate travel buyers, the Lonsdale case is a procurement question, not a human interest story. When the cheapest booking channel offers no real escalation path, the cost of failure lands on your traveller and, by extension, on you.

The broader lesson reaches every business running automated customer-facing systems. Automation is efficient right up until the escalation path disappears and a frontline staffer at the point of failure has neither the authority nor the tools to fix it. BA’s own chat agent gave false reassurance, its own system generated the error, and its own staff could not resolve it at the gate. Admitting fault in an email afterwards is not the same as building the infrastructure to catch and correct errors in real time. Until BA fixes the system it admits is broken, the next passenger is just a matter of time.

Sources

Community

Join the discussion

Add useful context, ask a good question, or challenge an idea — keep it specific and respectful.

Create a commenter account

Enter the name you want shown publicly and your email. We will email you a password-set link; you cannot comment until you use it.

Your email is used for sign-in and account security. It is not published with comments.

Subscribe for weekly news

Subscribe For Weekly News

* indicates required