Morning traffic at London Heathrow on Thursday, Nov. 12 included a British Airways Airbus that hit the runway hard enough to bounce, struck its tail on the surface twice, and then climbed away without completing the landing. Flight BA431 from Amsterdam Schiphol came back around and touched down safely on its second approach, and the early reports listed no injuries among the passengers or crew.
Read next on Morning Overview: Two Kentucky residents died when a small plane crashed at Missouri’s Lake of the Ozarks, and the NTSB is investigating
Video from a live airport camera run by the Big Jet TV channel spread within hours, and it raised an obvious question about how much punishment an aircraft’s rear fuselage absorbs when it meets concrete at landing speed. British Airways has not published an answer, and neither have investigators. What exists so far is a short airline statement, an inquiry opened by the UK’s Air Accidents Investigation Branch, and a maintenance plan that tentatively had the jet flying again on Saturday, Nov. 14, depending on what engineers found under the skin.
BA431 on Runway 27L: a bounce, two tail contacts and one go-around
Migflug, an aviation-news site, put the event at around 10:35 local time on Thursday, Nov. 12, on Runway 27L in calm, clear weather. The Airbus bounced after its first touchdown, the tail met the runway twice, and the crew abandoned the landing and flew a go-around. The jet rejoined the circuit and landed about 14 minutes later. The aviation-safety.net wikibase lists the occurrence as a tailstrike incident involving Airbus A321-251NX G-TNEB, and a daily digest from the Aircraft Rescue and Fire Fighting Working Group recorded that the pilots went around and landed safely on the second attempt, with no injuries reported.
PYOK, another aviation site, published its own account the same day and described passengers leaving the aircraft normally after the second landing.
The flight number is the one detail that wanders between reports: that site gave BA432 in one place and BA431 in its body text, while the ASN and ARFFWG entries and a BBC London post all use BA431. The route is not in dispute, since every account has the aircraft arriving from Amsterdam.
British Airways said in a statement that the aircraft landed safely and that the airline is assisting the AAIB with its investigation, adding that it was legally unable to comment further at this stage. The statement names no spokesperson and offers no account of the bounce itself.
G-TNEB, an A321neo delivered in December 2023, and the inspection that followed
G-TNEB is a young airframe. Migflug reports it joined the British Airways fleet in December 2023, which makes it roughly two to three years old, and the A321-251NX designation in the ASN entry is Airbus’s code for the A321neo variant. Nothing in the public reporting points to a defect in the aircraft itself; the sources describe a landing that went wrong on a clear morning, and the reason it went wrong is the thing investigators have to establish.
British Airways took the jet out of service for inspection after the second landing. No damage assessment has been released. After a tail contact, engineers typically examine the aft fuselage skin and the structure beneath the contact area for abrasion, dents or cracks, and the scale of any repair decides whether an aircraft is back on the schedule in days or out for weeks.
Migflug offers one data point on that range. It notes that an Austrian Airlines A320neo suffered a tailstrike at Heathrow in September 2026 and then stayed out of service for about eight weeks. A return of G-TNEB on Nov. 14 would therefore signal light damage, while a longer absence would suggest structural work. The sources reviewed do not say which of the two happened.
The AAIB’s remit and the questions still open
The AAIB is, in its own description, an independent unit within the Department for Transport that investigates civil aircraft accidents and serious incidents in the UK. Its reports set out the circumstances and causes of an event without attributing blame, and its Chief Inspector of Air Accidents reports directly to the Secretary of State for Transport on air safety matters. A tail contact on landing that also required a go-around falls squarely inside that remit.
The central question belongs to the investigators. Migflug says the cause of the bounce is one for the AAIB to answer, and a bounce is what turned an ordinary touchdown into a tail contact. Candidates a safety investigator would normally weigh include the pilot’s handling of the flare, wind and gusts near the ground, and the approach profile, though none of those has been named by anyone with access to the flight data.
As of Sunday, Nov. 15, the public record on BA431 ends with the airline’s two-sentence statement and the Big Jet TV footage. The extent of the damage to G-TNEB, the cause of the bounce, and whether the aircraft returned to service on Saturday, Nov. 14 as planned all remain unanswered in the sources reviewed for this article.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- Shaq spent $1.3 million on three Rolls-Royce Phantoms to prove a point to a salesman
- The Justice Department asked courts to undo approvals for three offshore wind farms, one already making power
- Over 20 trillion gallons of rain fell on the Four Corners states and Nevada in two weeks
- 11 engines built to run well past 200,000 miles