Plane CrashesVersion 2

NTSB Record Lists Key Lime Air Fairchild SA227-AC Accident Near Denver

An accident record filed with the National Transportation Safety Board lists substantial damage to a twin turboprop near Denver early on March 7, 2026; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:32 a.m. ET

This is a developing story. An accident record filed with the National Transportation Safety Board lists an accident involving a near Denver, Colorado, at about 4:40 a.m. local time on March 7, 2026. The record identifies the aircraft as , names the operator as , classifies the flight as a Part 135 commuter or on-demand operation, and states the aircraft sustained substantial damage. The NTSB is investigating. The cause has not been determined. The accident record does not list injury counts, which is usual for a preliminary filing, and no casualty figures are available in the material reviewed for this report. Aircraft registry records list as a twin-engine turboprop landplane, serial number AC-640, powered by AiResearch TPE331-series engines, built in 1986 and 40 years old, registered in the United States. The registry lists the registered owner as CBG LLC; the owner of record is not necessarily the operator of the flight, the pilot, or otherwise connected to it. FAA-sourced registrant records and aviation fleet directories describe CBG LLC as a limited liability company with an address in Englewood, Colorado, appearing as the registered owner of Metroliner-series aircraft including N885DC and N542FA; those directories state they hold no operator information for the company. That is background on the owner of record and says nothing about this accident. Geographic reference data places Denver at a settlement elevation of 5,279 ft, 13 miles WNW of Buckley Space Force Base, 14 miles W of Simons Airport and 14 miles SSE of Rocky Mountain Metropolitan Airport. A weather observation recorded at Rocky Mountain Metropolitan Airport, 13.7 miles away and 15 minutes from the reported time, showed wind from 220° at 3 knots, visibility 10 statute miles, clear skies and 23°F. The observation is an instrument reading at a nearby field and is not a stated factor in the accident. For context of record, the NTSB database, which begins in 2008, contains 6 other cases involving the , of which 1 involved a fatality. That count is a matter of public record and says 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: N425MA
Type: Fairchild SA227-AC — twin-engine turboprop landplane
Engines: AIRESEARCH TPE331 SERIES
Built: 1986-01-01 (40 years old)
Registered owner: Cbg LlcThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation: 5,279 ft
Nearest aerodrome: 13 miles WNW of Buckley Space Force Base (KBKF/BFK)

Sources

Revision history

Version 27 Aug 2026, 14:32current
Corrected the bearings between Denver and the nearby aerodromes to match the geographic reference data, and added the owner-background source URLs.
Version 15 Aug 2026, 16:34
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.