British Airways A320 Disabled on Gatwick Runway Triggers Fuel Emergencies and Diversions

A British Airways Airbus A320 encountered a nose wheel steering failure after landing at London Gatwick Airport, leaving the aircraft stranded on the airport’s only operational runway and triggering a cascade of operational disruptions. The flight, BA-2673, had just returned from Palma Mallorca when the pilots reported issues with the nose wheel to Air Traffic Control (ATC). After circling in a holding pattern over South East England attempting to troubleshoot, the aircraft was cleared to land on runway 8L. Upon touchdown, the nose wheel steering failure became evident, disabling the plane on the runway and blocking all traffic.

London Gatwick operates with only one active runway at a time due to international safety rules, despite having two parallel runways (8L/26L and 8R/26R). Normally, the southern runway (8R/26R) handles departures and arrivals while the northern runway (8L/26L) functions as a taxiway. On this occasion, the southern runway was closed for maintenance, leaving runway 8L as the sole operational surface at the airport. With the British Airways A320 immobilized there, no other planes could land or take off on that runway until the incident was resolved.

The stranded aircraft’s position forced ATC to instruct numerous inbound flights to enter holding patterns. Nine of those flights soon declared fuel emergencies, signaling they had limited extra fuel reserves and requesting priority landing clearance. A fuel emergency code does not indicate imminent danger but alerts controllers that the aircraft cannot safely continue prolonged circling without landing promptly.

The disruption escalated as it became unclear how long the British Airways plane would remain on runway 8L. This forced ATC to redirect 14 flights originally scheduled to land at Gatwick to alternative airports across England. Five flights diverted to London Luton, four to London Stansted, three to Birmingham, one to Bristol, and another was permitted to land at London Heathrow despite the airport’s nighttime curfew.

The affected British Airways Airbus A320, registration G-GATS, was subsequently removed from service, leading to the cancellation of a planned round trip to Alicante, Spain, the following day. This incident highlights vulnerabilities in Gatwick’s runway operational capacity, especially when one runway is offline, given that it ranks as the world’s second busiest single-runway airport after Mumbai.

The event comes shortly after a High Court ruling upheld a government decision permitting Gatwick to bring its northern runway into routine use. To comply with international standards, the centerline of the northern runway will need to be shifted 12 meters north to ensure sufficient separation from the southern runway. Despite seeming straightforward, Gatwick does not anticipate this change will be implemented before 2030, meaning single-runway operations will persist for some years.

Given Gatwick’s critical position within the UK’s air travel infrastructure, incidents like this underscore significant operational challenges. Runway unavailability at such a busy airport causes broad disruptions, with fuel emergencies an acute consequence for aircraft holding in congested airspace. The delayed activation of Gatwick’s second runway will continue to pose risks of similar occurrences during maintenance or emergencies on the primary runway.