FirstAlerts
Plane CrashesVersion 2

NTSB Investigating SkyWest Embraer ERJ 170-200 Accident Near Palm Coast, Florida

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

By AI ReporterUpdated Aug 7, 2026, 10:28 a.m. ET
The National Transportation Safety Board has an open investigation into an accident involving a SkyWest Airlines Embraer ERJ 170-200 near Palm Coast, Florida, according to the official accident record. The matter is still developing and the record remains limited in its details. The accident record gives the date as July 16, 2026 at about 2:02 p.m. local time, with the nearest city listed as Palm Coast, Florida. It lists one person on board and one serious injury, and classifies the flight as a Part 121 scheduled air carrier operation. The record identifies the operator as and the registration as , and gives the aircraft type as an . The cause has not been determined; the NTSB investigation is open. Aircraft registry records list as an Embraer S A ERJ 170-200 LR — a variant designation differing from the one in the accident record — a twin-engine jet landplane with GE CF34-8E5 engines, serial number 17000729, registered in the United States. The registry lists the operator of record and the registered owner as ; a registered owner of record is not necessarily the operator, the pilot, or otherwise connected to a given flight. As a matter of record only, the NTSB database lists three other cases involving the same operator: a Bombardier CL-600-2C11, N707EV, at Hibbing, Minnesota on November 23, 2025; an Embraer ERJ 170-200 LL, N110SY, at Peaster, Texas on August 29, 2025; and a Bombardier CL-600-2D24, N833SK, at Freeland, Michigan on July 16, 2025. The database, which begins in 2008, also lists nine other cases involving the Embraer ERJ 170-200 LR type, none of them fatal. Neither the operator history nor the type count says anything about the cause of this accident. Publicly available company and regulatory sources describe SkyWest Airlines, Inc. as a regional airline headquartered in St. George, Utah, held by the holding company SkyWest, Inc., and subject to FAA oversight through the SkyWest Certificate Management Office. Research did not establish any aviation organisation of that name based at or near Palm Coast or Flagler County. That background says nothing about 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
N271SY
Type
Embraer S A ERJ 170-200 LR — twin-engine jet landplane
Engines
GE CF34-8E5
Operator of record
Skywest Airlines
Registered owner
Skywest Airlines IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
39 ft
Nearest aerodrome
6.1 miles N of Flagler Executive Airport (KXFL)

Sources

Revision history

  1. Version 27 Aug 2026, 14:28current

    Noted that the accident record's type designation (ERJ 170-200 LL) differs from the registry's (LR), dropped the settlement-geography paragraph, and expanded the owner-background attribution.

  2. Version 15 Aug 2026, 15:18

    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.