British Airways Flight BA295 declared a BA295 emergency over Ireland after an unexpected operational issue about an hour into its London Heathrow Airport to Chicago O'Hare International Airport service. The Boeing 777-200ER dropped from 37,000 feet to 9,000 feet within minutes before turning back to London Heathrow.
The flight had left Terminal 5 at 11:50 AM on a scheduled 8-hour and 40-minute trip. Passengers and crew on the 30 year-old Boeing 777-200ER, registered G-VIIA, faced a same-day return instead of the planned Chicago arrival.
British Airways and runway 27L
British Airways Flight BA295 remained airborne over central Ireland while the crew coordinated with air traffic control. Shortly after the steep descent began, the crew issued squawk 7700, the emergency code used to tell controllers the aircraft needs priority handling.
The aircraft later made a U-turn and headed back toward London Heathrow. It touched down on runway 27L at 16:05 UTC, and the airline cancelled the flight at 16:30 UTC.
Fuel burn before landing
British Airways said there was no fuel jettison and that 30T fuel was on board. The crew lowered the landing gear while holding to burn more fuel, a standard way to increase drag and reduce landing weight before touchdown.
By 15:26 UTC, the aircraft was returning to Heathrow after burning 30T of fuel. That sequence leaves one practical question for passengers waiting for the Chicago service: what specific operational issue forced the emergency declaration over Ireland?
What BA295 passengers faced
The diversion turned a long-haul transatlantic departure into a return to the same airport where it started. The airline first scheduled a new departure for 15:00 local time, then set another for 17:30 local time, leaving passengers to rebook around a same-day disruption rather than an overnight cancellation at the outset.
A controlled descent below 10,000 feet can often point to a cabin depressurization event, but British Airways did not identify that as the cause here. The flight data show the aircraft had an unexpected operational issue, an emergency descent, a fuel-burn holding pattern, and a return to Heathrow — enough to explain the disruption, not enough to explain the trigger.
