FirstAlerts
Plane CrashesVersion 3

NTSB Investigating JetBlue A320 Accident Recorded Over the Atlantic Ocean

The accident record lists three people aboard, one seriously injured, on March 19, 2026; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 11:26 a.m. ET
The National Transportation Safety Board is investigating an accident involving an operated by on March 19, 2026, at about 9:28 a.m. local time. The matter is still developing, and the details below come from the accident record as it currently stands. According to that record, people were aboard, and injuries were recorded as one serious and two minor. The record classifies the flight as a Part 121 scheduled air carrier operation and gives the location as the Atlantic Ocean, in the United States. Geographic reference data for that place name places it in Cameron County, Texas, about 13 miles east-southeast of Port Isabel Cameron County Airport, at a settlement elevation of 7 feet; that locates a place name and nothing finer. The cause has not been determined, and the NTSB investigation is open. Aircraft registry records list the registration as , an twin-engine jet landplane with IAE V2500-series engines, serial number 2368, first flown in 2005 and 21 years old at the time. The registry lists the registered owner as ; a registered owner of record is not necessarily the operator, the pilot, or otherwise connected to a given flight. Public corporate filings and reporting describe JetBlue Airways Corporation as a publicly traded U.S. low-cost airline (Nasdaq: JBLU), incorporated in Delaware in August 1998 and headquartered in Long Island City, New York, with its main hub at John F. Kennedy International Airport. The company's investor relations announcement names Joanna Geraghty as chief executive officer effective February 12, 2024; the investigation has made no finding connecting company officers to this accident. Weather observed at Port Isabel Cameron County Airport, 13.1 miles away and 25 minutes from the reported time, recorded wind from 130 degrees at 8 knots, visibility 10 statute miles, clear skies and 72°F. Those are instrument readings at a nearby field, not a statement by anyone about what happened. As a matter of record, the NTSB database lists one prior case for this airframe: ENG26LA004 on October 30, 2025, over the Gulf of America. Other cases involving the same operator on record include DCA26LA115 (N2188J, Airbus A321-271NX) at San Francisco, California, on February 9, 2026; DCA25WA262 (N793JB, ) at Nassau on July 13, 2025; and DCA24LA092 at Boston, Massachusetts, on February 8, 2024, involving N956JT (Airbus A321-231) and N2157J (Airbus A321). The database, which begins in 2008, contains 11 other cases involving the , of which none involved a fatality. None of that history says anything about the cause of this accident.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Registration
N605JB
Type
Airbus A320-232 — twin-engine jet landplane
Engines
IAE V2500SERIES
Built
2005-01-01 (21 years old)
Registered owner
Jetblue Airways CorpThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
7 ft
Nearest aerodrome
13 miles ESE of Port Isabel Cameron County Airport (KPIL)

Sources

Revision history

  1. Version 37 Aug 2026, 15:26current

    Added headline and dek, restated the developing status in the lead, and added JetBlue's 1998 incorporation month; body facts otherwise unchanged.

  2. Version 25 Aug 2026, 20:38

    Clarified that the geographic reference locates only a place name, tightened attribution of weather and corporate-background material; no new facts available.

  3. Version 15 Aug 2026, 16:26

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.