NTSB Investigating JetBlue Airbus A321 Accident Near Somerset, Colorado

The accident record lists one person on board and one serious injury; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 11:00 a.m. ET

The National Transportation Safety Board is investigating an accident involving a JetBlue Airways near Somerset, Colorado, on July 6, 2026, at about 11:30 p.m. local time. The event is developing and the accident record remains open. The accident record lists one person on board and one serious injury. It classifies the flight as a Part 121 scheduled air carrier operation and names the operator as . The cause has not been determined; the investigation is open. Aircraft registry records list the aircraft as an , registration , serial number 6326, a twin-engine jet landplane powered by IAE V2533-A5 engines, built in 2014 and 12 years old, registered in the United States. The registry lists the registered owner as ; the owner of record is not necessarily the operator of the flight, the pilot, or otherwise connected to it. Publicly available corporate sources describe as a US scheduled passenger air carrier headquartered at 27-01 Queens Plaza North in Long Island City, New York, with a travel-services subsidiary, Paisly, and describe Joanna Geraghty as chief executive officer and Warren Christie as chief operating officer; the investigation has made no finding connecting either post-holder to this accident. Geographic reference data places Somerset in Gunnison County, Colorado, at a settlement terrain elevation of 6,024 feet — not the elevation of the accident site — about 11 miles northeast of North Fork Valley Airport, 12 miles northeast of Boeing Field (US-5087) and 17 miles southwest of Marble Airstrip. Weather observations recorded at Montrose Regional Airport (KMTJ), 36.7 miles away and 23 minutes from the reported time, show wind from 160 degrees at 9 knots, visibility 10 statute miles, clear skies and 69°F. These are instrument readings and are not stated as having any bearing on the event. As a matter of record, the NTSB database lists five other cases involving JetBlue Airways: April 4, 2026 (DCA26WA177, N794JB, Airbus A320-232, Punta Cana, Dominican Republic); March 19, 2026 (DCA26LA165, N605JB, Airbus A320-232, Atlantic Ocean); February 9, 2026 (DCA26LA115, N2188J, Airbus A321-271NX, San Francisco, California); October 30, 2025 (ENG26LA004, N605JB, Airbus A320-232, Gulf of America); and July 13, 2025 (DCA25WA262, N793JB, Airbus A320-232, Nassau). The database, which begins in 2008, records 7 other cases involving the , of which none involved a fatality. Neither the operator history nor the type count 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: N943JT
Type: Airbus A321-231 — twin-engine jet landplane
Engines: IAE V2533-A5
Built: 2014-01-01 (12 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: 6,024 ft
Nearest aerodrome: 11 miles NE of North Fork Valley Airport (K7V2/WPO)

Sources

Revision history

Version 27 Aug 2026, 15:00current
Corrected the directions to the nearby aerodromes (Somerset is northeast of North Fork Valley Airport and Boeing Field, southwest of Marble Airstrip) and clarified that the 6,024 ft elevation is that of the settlement, not the accident site.
Version 15 Aug 2026, 15:23
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.