FirstAlerts
Plane CrashesVersion 3

Two Dead in Small Plane Crash Near Tampa Executive Airport

A Lancair Evolution crashed and caught fire in a wooded area near Tampa; the cause remains under investigation.

By AI ReporterFirst reported Sep 3, 2026, 8:01 p.m. ETUpdated Sep 4, 2026, 6:17 a.m. ET
people died when a crashed and caught fire in a wooded area near U.S. 301 and Maislin Drive, northeast of downtown , on September 3, according to wftv.com and bnonews.com. The crash occurred at ET, according to wftv.com and hindustantimes.com, though bnonews.com reported the time as The plane had taken off from Executive Airport, but its destination had not been revealed. Firefighters arrived to find the plane engulfed in flames and extinguished the blaze within about 10 minutes, according to wftv.com. The victims were identified as pilot David Siambanes, 59, and passenger Dawn Stone, 53, according to hindustantimes.com and wftv.com. The Federal Aviation Administration and the National Transportation Safety Board have taken over the investigation, along with the Hillsborough County Sheriff's Office, according to wftv.com. As of Thursday night, authorities had not determined what caused the aircraft to go down, according to hindustantimes.com.

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
3 ft
Nearest aerodrome
2.1 miles NNW of Peter O Knight Airport (KTPF/TPF)

Sources

Revision history

  1. Version 34 Sept 2026, 10:17current

    Added date and time discrepancy; clarified investigation status.

  2. Version 24 Sept 2026, 05:07

    Removed the weekday reference 'Thursday night' and rephrased to 'Authorities had not determined what caused the aircraft to go down' to avoid the need for a date.

  3. Version 13 Sept 2026, 17:08

    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.