The U.S. aircraft register, updated daily
Accidents · NTSB ERA23FA321 · Final report

Kolb FIRESTAR accident near Mcalpin, Florida, August 3, 2023

On August 3, 2023 at about 1:30 pm local time, a Kolb FIRESTAR, an amateur-built aircraft,, registered UNREG, was substantially damaged in an accident during takeoff near Mcalpin, Florida (Little River airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A collision with trees during takeoff for reasons that could not be determined based on available information.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 3, 2023 · about 1:30 pm local time
Place
Mcalpin, Florida · Little River · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Kolb FIRESTAR UNDESIGNAT, amateur-built · all FIRESTARs on the register
Registration
UNREG · no longer on the register · serial amateur built
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot of an unregistered airplane was taking off when the accident occurred. There were no witnesses to the accident; however, one witness watched as the pilot started his takeoff roll. As the airplane passed his hangar, he could no longer see the airplane but he heard a decrease in the engine noise that he attributed to the pilot aborting the takeoff, as if the power was reduced to idle. He went inside for a few minutes before deciding to drive down the runway and see if the pilot needed any help. He did not see the pilot or the airplane. Later in the evening, he walked down the runway again and located the airplane suspended about 50 ft high in the treetops. Postaccident examination of the airplane revealed that it was inverted and hanging from the trees by the left main landing gear. About 4 ft of the left outer wing and the rudder displayed damage consistent with their contact with tree limbs. The engine, cabin, and propeller were intact and unremarkable. An engine test run was attempted, and the engine started immediately when the key was turned to start. The engine ran smoothly and ran up to high rpm without any hesitation or other problems noted. Flight control continuity was established to all flight controls. Given the lack of witness information or other more-detailed descriptions of the takeoff, along with the lack mechanical issues found during the examination of the wreckage, it could not be determined why the airplane came to rest in the trees adjacent to the runway during the attempted takeoff.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision with terrain or object (not controlled flight into terrain) during takeoff defining event

The NTSB's findings

  • Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,160 hours in all
  • Medical certificate: BasicMed (with waivers/limitations)
  • Seat: sngl
  • Injury: fatal

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 725 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Hirth 3202 (piston); 0 hours total

The flight

  • Flight plan: none
  • Runway 18, 3,400 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: from 120° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 82°F (28°C), dew point 75°F (24°C)
  • Altimeter: 30.09 inHg
  • Observation at 9:35 am from CTY, 31 miles away

Weather report (METAR): KCTY 031335Z AUTO 12006KT 10SM CLR 28/24 A3009 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on July 5, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Memorandum for Record A�� Telephone Interview, Witness PDF, 1 page · our copy View Download
2 Investigative Photographs PDF, 4 pages · our copy View Download
3 Toxicological Report PDF, 1 page · our copy View Download
4 Wreckage Examination Summary PDF, 4 pages · our copy View Download
5 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download

The same docket at the NTSB.

Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.