Hundreds stranded on second day of disruption at Bristol Airport
Summarized and contextualized by DistantNews.
At a glance
- Hundreds of travelers faced disruption for a second day at Bristol Airport due to an unspecified technical defect.
- Passengers reported poor communication and a lack of information from airline staff and airport tannoy announcements.
- Some flights were diverted, forcing passengers onto lengthy bus journeys to alternative airports.
Bristol Airport experienced a second day of significant disruption, leaving hundreds of passengers stranded and frustrated. The ongoing issues stem from an unspecified technical defect, the nature of which has not been officially released, leading to widespread flight cancellations and delays.
The communication, advice and support for passengers has been really poor.
Travelers described a chaotic experience, citing a severe lack of communication and support from airline representatives and airport authorities. Paul Smith, who was set to fly to Glasgow for his son's 20th birthday, had to cancel his trip. He told the BBC that announcements on the tannoy system were absent for over an hour, leaving EasyJet representatives in the departure lounge as the sole source of information.
What we've heard is that there's a hole in the runway.
For others, the disruption meant significant diversions. Dave Blackwell, returning from Rhodes, Greece, found his flight diverted to Newcastle. He described the situation as "a shambles," detailing a three-hour wait at Rhodes Airport with no information before being told his flight would land in Newcastle, followed by a five to six-hour bus journey. Passengers are advised to contact their airlines for the latest information and support.
We were in Rhodes Airport for three hours with no information. Now we have all been told our flight is going to Newcastle and then a five or six hour bus ride - why Newcastle? How appalling.
Originally published by BBC News. Summarized and contextualized by our editorial team with added local perspective. Read our editorial standards.