Squawk 7700 over the Atlantic

Flight AC853, a 777-300ER registered C-FITL, departed Heathrow at 08:34 BST. The aircraft climbed to its initial cruising altitude of FL340 and was tracking west over the Atlantic when the crew transmitted a squawk 7700 emergency code at 09:30 BST, according to AirLive.

What squawk 7700 actually means

A transponder replies to radar with a four-digit code, and three of those codes are reserved worldwide. 7500 indicates unlawful interference, 7600 a radio communications failure, and 7700 a general emergency. Setting 7700 flags the aircraft on every controller’s display in range and buys the crew immediate priority — direct routing, protected airspace and emergency services on arrival.

The key point for reading a story like this one is that 7700 carries no information about severity or cause. It covers a technical malfunction, a medical event in the cabin, a pressurisation problem or a precautionary call by a crew who would rather have the airspace cleared than negotiate for it. A 7700 that ends in an uneventful landing with no injuries is a normal outcome, not a near-miss.

Why turn back rather than press on

Turning around mid-ocean rather than continuing to a North American alternate is standard practice for an unresolved fault. Once past the point where a return is straightforward, a North Atlantic crossing commits an aircraft to hours over water with a limited set of diversion fields — Keflavík, Shannon, Gander — none of which offers what a major hub does.

Heathrow, roughly an hour behind them, offered full emergency response for the Air Canada crew, the operator’s own engineering support and hotel and rebooking capacity for a full widebody load. Crews weigh landing weight in that decision too: an aircraft that has just tankered fuel for a transatlantic sector is well above its maximum landing weight, so a return usually means either holding to burn fuel down or accepting an overweight landing and the inspection that follows. Neither is an emergency in itself; both take time, which is part of why the aircraft was airborne for around 90 minutes on a flight that never left the region.

The Air Canada Heathrow return

The Air Canada Heathrow return ended on runway 27L at approximately 10:02 BST. Emergency vehicles met it at the gate. None of the occupants were injured.

Travel And Tour World reported that the cause of the emergency had not been disclosed by Air Canada at the time of publication. Yorkshire Live noted the aircraft was met at the gate by ground emergency response — standard procedure for any arrival squawking 7700, regardless of cause.

Who would investigate an Air Canada Heathrow diversion

Not every Air Canada Heathrow emergency becomes a formal investigation. The UK Air Accidents Investigation Branch has jurisdiction over occurrences in UK airspace, and Transport Canada has an interest as the regulator of the operator and the state of registry, but a reportable occurrence has to clear a threshold — serious injury, significant damage, or a safety issue with wider implications. A precautionary return that lands normally with no injuries frequently does not, and is handled through the operator’s own safety management system and routine occurrence reporting instead.

That is the most likely reason no findings have been published, and why none may be. Absence of an investigation report here is not evidence that something is being withheld.

The route and the type

The 777-300ER is the workhorse widebody for Air Canada’s transatlantic operations, and Heathrow–Toronto is one of the carrier’s highest-frequency routes on that side of the Atlantic, typically flown multiple times a day. That density matters operationally on Air Canada Heathrow services: a carrier with several daily rotations on a route can absorb one aircraft going technical far more easily than one flying it three times a week, which is why the disruption from an event like this is usually measured in hours rather than days.

AircrewNews will update this story if Air Canada or the UK Air Accidents Investigation Branch publish further information.

The post Air Canada Heathrow emergency: 777 returns after squawking 7700 first appeared on AircrewNews.com.

Engine failure as the SWISS A330 rejects takeoff

When the SWISS A330 rejects takeoff, flight LX147 was bound for Zurich with 228 passengers, four infants and 13 crew. The aircraft, registered HB-JHK, accelerated to about 104 knots before the crew rejected the takeoff. The airline confirmed the timeline in a newsroom statement.

Smoke was visible on the left side, where the No. 1 engine had failed. Ground crews then reported a fire near the right main landing gear after the aircraft came to a stop on the runway.

Why 104 knots matters

Rejected takeoffs are categorised by speed, because the consequences scale with kinetic energy — and where a SWISS A330 rejects takeoff at 104 knots, that energy is considerable. Below roughly 80 knots an abort is a low-risk decision and crews will reject for relatively minor indications. Above that, the calculus tightens as the aircraft approaches V1 — the decision speed past which the takeoff must be continued, because there is no longer enough runway remaining to stop.

At about 104 knots on a widebody near its maximum takeoff weight for a long sector to Zurich, this was a high-speed reject. That means maximum braking, ground spoilers and thrust reverse, dumping the aircraft’s energy into the brakes as heat over a few seconds. Carbon brake stacks on a heavy A330 can reach several hundred degrees in a high-speed abort, and heat soaks into the wheel and tyre assembly for some minutes afterwards, which is precisely when a gear-area fire becomes a live risk. Wheels are fitted with fusible plugs designed to deflate a tyre in a controlled way rather than let it burst under that heat load.

Two events on opposite sides of the aircraft

The detail investigators will focus on is geometry. The engine that failed was the No. 1 — the left engine. The fire was reported near the right main landing gear. Those are opposite sides of the aircraft, which makes a simple mechanical chain between the two harder to draw.

Two broad possibilities present themselves, and the published information does not distinguish between them. Brake energy from the reject alone can produce a gear-area fire with no connection to the engine event beyond having caused the abort. Alternatively, a common factor or a sequence not yet public could link them. Establishing which is exactly the sort of question a formal investigation exists to answer, and it would be wrong to assume either from the outside.

Evacuation and aftermath

The crew commanded an emergency evacuation via the slides. SWISS confirmed six minor injuries; no serious injuries were reported. Emergency services secured the area before the aircraft was removed from the runway for technical inspection.

A rejected takeoff also stops the aircraft on the runway rather than clearing it, which at a hub of Delhi’s size has immediate knock-on effects. A disabled widebody has to be inspected, its brakes allowed to cool and its tyres checked before it can be towed, and until then the runway is out of service — pushing arrivals into holding and departures into ground delay across the evening bank.

Minor injuries in a slide evacuation are common rather than exceptional. An A330 slide deploys at a steep angle from a door sill several metres above the ground, and an evacuation of more than 240 people down them at speed reliably produces sprains, abrasions and the occasional fracture. Six minor injuries across that number of occupants is, in evacuation terms, an orderly outcome.

What investigators watch after a SWISS A330 rejects takeoff

Simple Flying and The Aviation Herald reported the incident on the carrier’s evening Zurich rotation. Both noted that the No. 1 engine failure and the gear-area fire — on opposite sides of the aircraft — would be central questions for investigators.

Jurisdiction follows ICAO Annex 13: India is the state of occurrence and the DGCA leads, while Switzerland as the state of the operator and of registry is entitled to appoint an accredited representative, as are the states of design and manufacture for the airframe and engines.

SWISS said the A330 has been removed from service pending the DGCA investigation. The carrier has not commented on a likely return-to-service date or on the relationship between the engine failure and the fire. AircrewNews will update this story as official findings are released.

The post SWISS A330 rejects takeoff at Delhi; passengers evacuated first appeared on AircrewNews.com.