London's Gatwick Airport remain shut due to drone sightings

London's Gatwick Airport remain shut due to drone sightings

London's Gatwick Airport remain shut due to drone sightings

However, the airfield only reopened for a mere 44 minutes before being closed again after a further sighting of the drones.

Flights are reportedly being diverted to other airports in the United Kingdom and across Europe due to the emergency.

London's Gatwick Airport shut down late Wednesday, Dec. 19, 2018, while officials urgently investigated reports that two drones were flying above the airfield.

It is illegal to fly drones within 1 kilometer of an airfield and a police investigation was underway, Gatwick said.

"Our airlines are working to provide affected passengers with hotel accommodation or transport passengers landing at other airports to Gatwick by other means, and Gatwick staff are looking after passengers in our terminals", the airport said.

Ms Jaworska said it was "strange" that two drones had led to the closure of the airport.

Picture taken with permission from the Twitter feed of Luke Mccomiskie showing the scene inside a plane three hours after it landed at Manchester having been diverted from Gatwick Airport which had been closed because of the sighting of drones.

More news: Aaron Rodgers offers striking endorsement for Randall Cobb: 'He's what we need'

Here we look at the law surrounding drones.

Passengers faced severe disruption as some flights were unable to leave the tarmac while others were diverted to other airports.

Gatwick first closed Wednesday night at around 9 p.m. (2100 GMT) when drones were sighted.

"Our focus is now on working, with the airport community, to catch up on the flight schedule", the airport spokesman said.

Gatwick is a busy airport 27 miles (43 kilometers) south of central London.

After spending about two hours on the plane, she said the couple were put on a bus to Gatwick, from where they had been due to fly to Istanbul. "Which has made the delay better".

Related news



[an error occurred while processing the directive]