A JetBlue Airways Airbus A320-232 operating as Flight 1230 from Cancun to Newark experienced a sudden pitch excursion over the Gulf of America on 30 October 2025, prompting a diversion to Tampa and triggering a multinational safety investigation.
The event, which resulted in minor injuries to 22 occupants, has since led to emergency airworthiness directives from both EASA and the FAA, as well as focused scrutiny on the aircraft’s elevator and aileron computer systems.
The NTSB’s preliminary report, released in late January 2026, outlines the known facts and the early investigative steps without drawing conclusions.
The Incident in Cruise Near Tampa…
According to the NTSB, the Airbus A320-232 registered N605JB was cruising at 35,000 feet in smooth air and clear weather when the aircraft experienced an unexpected pitch excursion at 17:48 UTC.
The aircraft momentarily pitched downward, resulting in an approximate altitude loss of around 100 feet.
The Aviation Herald’s account aligns with this description, noting that the pitch-down event lasted several seconds before the aircraft stabilised.
The flight crew elected to divert to Tampa International Airport, where the aircraft landed without further incident.
The remainder of the flight was uneventful, and no structural damage or fire was reported.
However, the abrupt manoeuvre caused minor injuries to four flight attendants and 18 passengers, bringing the total number of minor injuries to 22. The remaining 102 occupants were uninjured.
Flight Details and Conditions
Flight 1230 was a scheduled Part 121 passenger service from Cancun International Airport (MMUN) to Newark Liberty International Airport (KEWR).
The aircraft involved, an Airbus A320-232, was operating under JetBlue Airways’ flag carrier certificate.
Meteorological conditions at the time were visual meteorological conditions with clear skies, 11.5 miles visibility, and no significant turbulence reported.
Winds at altitude were recorded at 101 knots from 243 degrees, and the temperature was -12°C.
The aircraft was flying on an IFR flight plan and was approximately 300 kilometres southwest of Tampa when the event occurred.
Immediate Response and Diversion to Tampa
Following the pitch excursion, the crew assessed the situation and determined that a diversion was necessary.
Tampa International Airport was selected as the nearest suitable airport.
The aircraft landed safely, and injured passengers and crew received medical attention.
No ground injuries occurred, and the aircraft did not sustain major damage.
The NTSB noted that it did not travel to the scene, which is typical for incidents where the aircraft lands safely and damage is limited.
The investigation was formally opened the day after the event, on 31 October 2025.
Early Technical Findings
One of the most significant early developments came from Airbus’ preliminary technical assessment of the A320’s flight control system architecture.
Airbus identified a concern with the software design of the Elevator and Aileron Computers (ELACs), which form part of the aircraft’s primary flight control system.
These computers manage critical functions including pitch control, roll control, and autopilot interface.
Moreover, the ELAC units from the incident aircraft were removed and sent to Thales in Châtellerault, France, where they were examined in the presence of NTSB investigators.
Additional components were also removed from the aircraft and forwarded to their respective manufacturers for data recovery and functional testing.
While the NTSB preliminary report does not assign cause, it confirms that Airbus’ internal assessment identified ELAC software design as a potential contributing factor.
This finding prompted immediate action from regulators.
Regulatory Action and Operator Guidance
In response to Airbus’ assessment, the manufacturer issued Alert Operators Transmission (AOT) A27N022‑25 on 28 November 2025.
The AOT was released in three revisions within a 24‑hour period, reflecting the urgency of the issue.
The document provided operators with instructions for identifying affected aircraft and implementing corrective measures.
The European Union Aviation Safety Agency (EASA) subsequently issued Emergency Airworthiness Directive (EAD) 2025‑0268‑E on the same day, mandating compliance with the AOT.
The Federal Aviation Administration (FAA) followed with its own Emergency AD, 2025‑24‑51, also issued on 28 November 2025.
Both directives required operators of affected A320‑family aircraft to take immediate action before further flight.
Reporting notes that the event likely occurred during an ELAC switchover, a routine process in which control authority transitions between redundant flight control computers.
The NTSB has not confirmed this, but the detail is consistent with the focus of the technical investigation.
International Participation in the Investigation
The NTSB appointed several organisations as official parties to the investigation, including the FAA, JetBlue Airways, and the Air Line Pilots Association.
Under ICAO Annex 13 protocols, the Bureau d’Enquêtes et d’Analyses (BEA) was invited to participate as the Accredited Representative for France, given Airbus’ role as the aircraft manufacturer.
Airbus, Thales, and EASA were designated as technical advisors to the BEA.
Later in the process, Germany’s Bundesstelle für Flugunfalluntersuchung (BFU) was also notified, and an Accredited Representative was appointed with Northrop Grumman LITEF acting as a technical advisor.
This reflects the multinational nature of modern aircraft systems, where components and software originate from multiple countries and suppliers.
Recorder and Component Analysis
The flight data recorder (FDR) and cockpit voice recorder (CVR) were transported to the NTSB Vehicle Recorder Laboratory in Washington, D.C. for data extraction.
Also, the preliminary report confirms that data retrieval was successful, though it does not yet detail the findings.
The ELAC units, central to the early technical focus, were examined in France. Additional components from the aircraft were sent to their respective manufacturers for further analysis.
These steps are standard practice in incidents involving potential flight control anomalies, ensuring that investigators can reconstruct the event with precision.
Injuries and Aircraft Condition
The NTSB’s preliminary data confirms that the aircraft sustained only minor damage.
There was no fire, explosion, or structural compromise.
The injuries were limited to minor trauma, primarily among cabin crew and unrestrained passengers, consistent with a sudden pitch change in cruise.
The aircraft’s location at the time of the event was recorded as approximately 27.30702°N, -83.9257°W.
No ground injuries occurred, and the diversion to Tampa was executed without further complications.
Status of the Investigation of The Tampa Accident…
As of the preliminary report’s release, the investigation remains ongoing. The NTSB emphasises that all information is subject to change as additional data is analysed.
Furthermore, no probable cause has been identified, and no conclusions have been drawn.
The involvement of multiple international authorities, combined with the issuance of emergency directives, underscores the seriousness with which regulators and manufacturers are treating the event.
Overall, the final report, expected at a later date, will provide a comprehensive analysis of the sequence of events, contributing factors, and any required safety recommendations.
Continue to follow The Aviation Hub for more analysis and insight!
