NTSB Record Lists Delta A320 Accident Near Chase City, Virginia
An official accident record places the August 28, 2025 event at about 4:00 p.m. local time, with three people on board and one serious and two minor injuries; the cause has not been determined.
By AI ReporterUpdated Aug 7, 2026, 9:14 a.m. ET
Details in this matter remain limited. An official National Transportation Safety Board accident record lists an accident on August 28, 2025 at about 4:00 p.m. local time near Chase City, Virginia, involving an registered and operated by . The record lists people on board and injuries of one serious and two minor, and classifies the flight as a Part 121 scheduled air carrier operation.
The cause has not been determined. The accident record names the National Transportation Safety Board as the investigating body and lists the investigation as open. No preliminary findings appear in the available record.
Aircraft registry records list as an , a twin-engine jet landplane with CFM International CFM56-series engines, serial number 1641, first flown in 2001 and 24 years old at the time of the accident, registered in the United States. The registry lists the registered owner as ; the owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight. Company filings and Delta's own published material describe Delta Air Lines, Inc. as a Delaware-incorporated major U.S. air carrier with principal executive offices at Hartsfield-Jackson Atlanta International Airport, publicly traded as NYSE: DAL. Delta's S.V.P. of Corporate Safety, Security and Compliance and FAA-designated Director of Safety is Brad Sheehan; the investigation has made no finding connecting him to this accident.
Weather observations recorded at Chase City Municipal Airport (KCXE), 2.5 miles from the settlement and five minutes from the reported time, showed wind from 230 degrees at knots, visibility 10 statute miles, broken cloud at 6,500 feet and a temperature of 78 degrees Fahrenheit. These are instrument readings only, and are not stated to have any bearing on what happened.
As a matter of record, the NTSB database, which begins in 2008, contains one other case involving an , of which none involved a fatality. NTSB records also list other cases involving the same operator: DCA25LA276, N422DZ, an Airbus A330 at Creston, Wyoming on July 30, 2025; DCA25WA292, N3766, a Boeing 737-832 at Ciudad de México on July 21, 2025; DCA25LA269, N229JQ, an Embraer ERJ 170-200 LR at Jacksonville, Georgia on July 21, 2025; OPS25LA052, N604CZ, an Embraer ERJ 170-200 LR at Minot, North Dakota on July 19, 2025; and DCA25LA272, N330PQ, a Bombardier CL-600-2D24 at Germantown, Kentucky on July 17, 2025. Those records say nothing about the cause of this accident. The investigation remains open.
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
N373NW
Type
Airbus Industrie A320-212 — twin-engine jet landplane
Engines
CFM INTL. CFM56 SERIES
Built
2001-01-01 (24 years old)
Registered owner
Delta Air Lines IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
545 ft
Nearest aerodrome
2.5 miles ENE of Chase City Municipal Airport (KCXE)
Sources
No sources recorded.
Revision history
Version 27 Aug 2026, 13:14current
Reframed from developing-event language to a published record account and closed on the open status of the NTSB investigation; no new facts.
Version 15 Aug 2026, 21:25
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.