A British Airways Airbus A321 abandoned its route to Faro and squawked the emergency code 7700 over north-western France after crew identified a cracked passenger window, forcing a return to Gatwick and an aircraft swap for passengers bound for the Algarve.
The british airways flight ba2660 emergency began shortly after departure from London Gatwick on Tuesday 13 October 2026, when a cracked passenger window forced the Airbus A321 to turn back, according to the BBC.
Flight BA2660, operated by an Airbus A321-231 registered G-EUXD, had departed Gatwick at approximately 9:00am BST bound for Faro, according to airlive. Roughly one hour into the flight, the crew issued a squawk 7700 emergency signal to air traffic control after identifying damage to a window panel near row 3R on the right side of the cabin, airlive reports. Cabin pressure was maintained throughout, airlive adds, but standard protocol called for an immediate turn and descent to a lower altitude. The aircraft diverted over north-western France before landing safely back at Gatwick, the BBC reports. A British Airways spokesperson said: “We have apologised to customers for the delay to their journey, and our teams are working hard to get their travel plans back on track,” as quoted by the BBC.
Why it matters to the people who run airports
A cracked window is a minor technical fault by aviation safety standards, but the cost sits entirely in recovery, not repair. Airlive reports that diversions of this kind trigger immediate aircraft replacement protocols to get passengers to their final destination, meaning Gatwick’s operations team had to find gate capacity for an unscheduled emergency landing and British Airways had to source a replacement aircraft to complete the Faro rotation. That is turnaround planning, stand allocation and crew rostering disrupted on no notice, the exact cost line that lands on an airport’s operations desk rather than the airline’s.
Gatwick Airport confirmed the aircraft landed safely, The Argus reports, which meant emergency ground crews were mobilised to meet the aircraft as a precaution, per airlive, even though the squawk 7700 code ultimately resolved without further incident. For heads of operations, that is the planning case worth keeping: a 7700 squawk commits airside and emergency response resources the moment it is transmitted, regardless of how the flight actually lands. The same logic sat behind Nuremberg’s full airport closure after a fake hijack code was transmitted by radio fault, where an emergency signal triggered a response disproportionate to the eventual cause.
The BBC notes this is the second British Airways technical diversion inside a week, after a Chicago-bound service spent five hours circling over Ireland before turning back to Heathrow, with passengers reporting oxygen masks deploying and tracking data showing a descent from 37,000ft to 9,000ft. Two unscheduled BA returns in quick succession is a pattern worth watching for engineering and MRO capacity, not just a coincidence. It sits alongside other recent A321 diversions this title has covered, including IndiGo’s power bank fire forcing an A321 diversion to Hyderabad and BA295’s 28,000ft drop forcing a return to Heathrow, both of which required the same rapid stand reallocation and passenger rebooking response now facing Gatwick’s team.
What to do now
British Airways engineering teams will inspect the damaged window assembly on G-EUXD to determine the cause of the fracture before returning the aircraft to service, airlive reports. For airports, the practical checklist is the same one every unscheduled technical return demands: confirm stand availability before the aircraft is on final approach, have ground handling ready to meet an emergency squawk even when cabin pressure holds, and have a rebooking and passenger welfare plan ready the moment an airline confirms a diversion rather than after. Commercial and passenger experience teams should also expect the knock-on costs: delayed connections, duty-of-care obligations and, as with the Chicago incident the week before, reputational scrutiny that outlasts the technical fix. Diversions of this kind are rarely about the fault itself; they are about how fast the ground side absorbs it, a resilience cost comparable to the economics seen when Emirates diverted EK31 to Frankfurt after a medical emergency and Frankfurt had to find stand capacity for an unscheduled A380.
What caused the BA2660 emergency?
A cracked passenger window identified roughly an hour into the flight, which prompted the crew to issue a squawk 7700 emergency code and return to Gatwick, according to airlive and the BBC.
Did BA2660 land safely?
Yes. Gatwick Airport confirmed the aircraft landed safely, The Argus reports, and cabin pressure was maintained throughout the diversion, according to airlive.
Is this related to other recent British Airways incidents?
The BBC reports it follows a separate BA flight to Chicago that turned back to Heathrow the previous week after an emergency alert and a rapid descent from 37,000ft to 9,000ft, though the two events are reported separately and no link between their causes has been stated.
The takeaway: the fault was minor, but the ground response it demanded, from stand reallocation to aircraft replacement, is the real cost line every airport operations team should be planning against.
