A TAP Air Portugal Airbus A321 bound for Lisbon scraped its tail against the runway while taking off from Rome’s Fiumicino Airport in late May 2026, forcing the pilots to abandon the climb, loop back over the Italian coastline, and land the jet safely. None of the passengers or crew on board were hurt, and the aircraft taxied to the gate under its own power.
The incident triggered standard safety reviews by Italian regulators but did not shut down runway operations at one of Europe’s busiest airports. Flights continued on schedule while the damaged A321 was pulled from service for inspection.
Key details that have not been publicly disclosed include the flight number, the number of passengers and crew on board, and the precise date of the event. Neither TAP Air Portugal nor Italian authorities have released a public statement with those specifics.
How the tail strike unfolded
A tail strike happens when the underside of an aircraft’s rear fuselage hits the runway surface, usually because the nose pitches up too steeply or too early during rotation. Pilots in the cockpit typically feel it as a sharp jolt or a scraping vibration through the airframe.
In this case, the TAP crew recognized the contact almost immediately. Rather than continue the climb toward Lisbon, they elected to circle back to Fiumicino, a decision consistent with airline procedures for suspected structural damage. The return flight and landing were uneventful, and passengers disembarked normally at the gate.
Italy’s National Agency for Civil Aviation, known as ENAC, is the primary safety regulator for Italian airports. A review of ENAC’s official communications page showed no operational restrictions or safety directives listed for Fiumicino in connection with the event, though the page is a general index and may not capture all regulatory actions. Italy’s Ministry of Infrastructure and Transport, which oversees broader transport policy, listed the incident on its institutional website, though no specific statement or detailed account has been published there.
The lack of posted airport-wide restrictions is worth noting but should not be read as a definitive all-clear. ENAC may have taken internal steps that do not appear on its public communications page, and the absence of a published directive does not rule out ongoing review.
What investigators still need to determine
The exact cause of the excessive pitch angle has not been publicly confirmed. Tail strikes can stem from several factors: a miscalculated rotation speed, an aft-heavy center of gravity caused by unusual cargo or passenger loading, a sudden wind gust at the moment of liftoff, or a combination of all three. Fiumicino sits along the Mediterranean coast, where shifting winds are common, and even a modest gust during the critical seconds of rotation can push the tail dangerously close to the pavement.
Neither TAP Air Portugal nor Italian authorities have released statements from the flight crew or data from the aircraft’s flight recorders. No public comments from passengers have surfaced either. Those details would clarify how quickly the pilots identified the strike and how the jet handled during the climb and return. Aviation investigations, even for incidents that end without injuries, follow a structured timeline. Preliminary findings from recorder analysis and crew interviews typically take weeks to months before they appear in formal reports.
The physical extent of the damage also remains undisclosed. The Airbus A321 is equipped with a tail skid, a sacrificial bumper on the underside of the rear fuselage designed to absorb light runway contact during steep rotations. If the damage stayed confined to the tail skid and superficial fuselage scraping, repairs are relatively straightforward. But if the forces during the strike exceeded design limits, inspectors must look deeper, particularly at the rear pressure bulkhead, internal frames, and floor beams. Hidden damage in those areas can have serious long-term safety consequences if left undetected, a lesson the industry absorbed from past incidents involving other aircraft types.
It is also unknown whether runway inspections produced any findings or caused any delays for other traffic. Airports typically examine the surface for debris or scoring after a tail strike, but no inspection results or delay reports have been published in connection with this event.
No timeline for the aircraft’s return to commercial service has been published. Airlines typically keep a jet grounded after a tail strike until engineers complete non-destructive testing and a full structural assessment, a process that can take days or weeks depending on what they find.
How common are tail strikes?
Tail strikes are among the most frequent types of ground-contact events in commercial aviation. Industry estimates place the rate at roughly one to two occurrences per 1,000 departures for narrow-body aircraft, though the figure varies by aircraft type, operator, and airport conditions. Airbus and Boeing have both published guidance urging operators to treat every occurrence seriously, even when the visible damage appears minor. The A321’s tail skid exists precisely because engineers know the geometry of the aircraft makes contact possible during aggressive rotations, especially at higher takeoff weights.
Most tail strikes end the way this one did: the crew detects the problem, returns or diverts, and the aircraft is inspected and repaired. Serious structural failures from a single tail strike are rare but not unheard of, which is why regulators and manufacturers insist on thorough post-event inspections before clearing a jet to fly again.
TAP Air Portugal operates a mixed fleet of Airbus narrow-body jets on its European and medium-haul routes. The airline, Portugal’s flag carrier, has not issued a public statement about the Rome incident.
Why the crew’s decision to turn back matters for safety
For anyone booked on TAP flights through Fiumicino, the practical takeaway is that no broader safety concerns have been flagged by Italian regulators for the airport itself. The incident was contained to a single aircraft that is now out of service for inspection.
The crew’s decision to turn back rather than press on to Lisbon reflects exactly the kind of conservative judgment that aviation safety systems are built to encourage. Pilots are trained to treat any suspected structural contact as a reason to land at the nearest suitable airport, and Fiumicino, already behind them, was the obvious choice.
Until ENAC or Italy’s accident investigation body publishes further findings, the specific cause of the tail strike will remain an open question. Any conclusions about pilot error, weather, or loading issues are speculative at this stage. What is confirmed is the outcome: a controlled return, a safe landing, and no one hurt.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
