Cancelled Etihad flight leaves more than 200 abandoned at airport

‘We had the comical/dangerous sight of people scaling fences and crossing scrub land, trying to make their way to the Crowne Plaza at the airport only to find that was the wrong hotel'

Simon Calder
Travel Correspondent
Monday 01 April 2019 16:29 BST
Comments
Rescue mission: eventually the stranded passengers flew out on a Boeing 787 jet
Rescue mission: eventually the stranded passengers flew out on a Boeing 787 jet (Etihad)

Furious passengers have lambasted Etihad after it cancelled an evening flight from Manchester to Abu Dhabi and “deserted” more than 200 passengers.

Flight EY22 was due to leave Manchester at 7.10pm on 27 March, arriving in the UAE capital at 6.15am the next day.

The inbound aircraft suffered a suspected lightning strike and required technical attention.

After hours of confusion the passengers were told at 10.30pm that the flight was cancelled.

David Reynolds, one of the passengers, told The Independent: “We were told we would be coached back to a Crowne Plaza hotel in Manchester. They couldn’t tell us to which Crowne Plaza, though.

“So in the intervening two-hour wait for coaches, with no assistance from either Etihad or its ground handling staff, we had the comical/dangerous sight of people, including women with very young babies, scaling fences and crossing scrub land, trying to make their way to the Crowne Plaza at the airport only to find that was the wrong hotel.”

Eventually they arrived at the right hotel at 2am, but were told they would need to leave on coaches back to the airport at 6am.

“There was no information on arrival, and we queued for check in for three-and-a-half hours,” said Mr Reynolds.

“We boarded by 11am and then sat on the tarmac for at least two hours,” said Mr Reynolds. “All this time no apology.”

Passengers took to social media to express their frustration.

Jay Sungsit tweeted: “Worst service ever. Everyone is on the plane now and the plane haven’t take off yet.”

Many of the passengers missed flight connections.

Chris Burz, who was flying to Sydney to join a cruise, tweeted: “EY22 still at Manchester. Totally incomprehensible. No info or help from Etihad staff. Onward flight missed. Dream cruise in jeopardy. Disappointed and deserted by Etihad. Never again.”

The replacement plane eventually took off almost 18 hours late.

A spokesperson for Etihad Airways told The Independent that the cause of the problem was a ”gradually extended delay due to a technical checks required following a suspected lightning strike on the inbound flight”.

The airline said: “Due to the lengthy delay, the decision was made to cancel the flight and provide customers with overnight accommodation in Manchester and to operate the flight the following morning.

“During the transfer to the hotel, a bus driver inadvertently drove to another property, and then drove customers to the correct hotel.”

Explaining the problems the following morning, the spokesperson said: “Flight EY22 on 28 March was subsequently delayed due to a baggage discrepancy and staff provided up-to-date information on the delay.

“Ground personnel worked diligently to resolve the issue and to minimise any inconvenience to guests.

“The safety of our guests and crew is Etihad Airways’ highest priority and Etihad Airways regrets any inconvenience experienced by our valued guests.”

Etihad said it would not pay compensation under European passengers’ rights rules, as the original cause of the delay was a lightning strike.

Last May a planeload of Tui Airways passengers at Manchester Airport ended up sleeping on the floor of the terminal.

The airline, which has a big presence at Manchester, said it could not find hotel rooms “due to a number of concerts and events happening in the Manchester area over the bank holiday weekend”.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in