FirstAlerts
Plane CrashesVersion 2

Two Killed in Beech B100 Crash Near Coral Springs, Florida

The accident record lists two aboard, two fatalities and the aircraft destroyed; the National Transportation Safety Board is investigating and the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 11:11 a.m. ET
people were killed when a crashed near Coral Springs, Florida, on November 10, 2025, at about 3:19 p.m. local time, according to the accident record. The available information comes from official records rather than from on-scene reporting, and the investigation is open. The accident record lists people on board and fatalities, and states that the aircraft was destroyed. The record classifies the flight as a Part 91 general aviation flight. The accident and registry records identify the aircraft as a registered . Geographic reference data places Coral Springs in Broward County, Florida, and lists the settlement's own terrain elevation — not that of the accident site — as 16 feet. The same reference data situates the city 8.0 miles northwest of Fort Lauderdale Executive Airport (KFXE), 10 miles west of Pompano Beach Airpark (KPMP) and 13 miles southwest of Boca Raton Airport (KBCT). The records available do not state where along that area the aircraft came down. The National Transportation Safety Board is listed in the accident record as the investigating body. The cause has not been determined.

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.

Terrain elevation
16 ft
Nearest aerodrome
8.0 miles NW of Fort Lauderdale Executive Airport (KFXE/FXE)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 15:11current

    Corrected the bearings between Coral Springs and the three nearby airports to match the geographic reference data, and clarified that the elevation figure and the airport distances refer to the settlement rather than the accident site.

  2. Version 15 Aug 2026, 19: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.