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

Kolb Company FIRESTAR accident near Frankfort, New York, July 31, 1995

On July 31, 1995 at about 10:00 pm local time, a Kolb Company FIRESTAR, an amateur-built aircraft,, registered UNREG, was destroyed in an accident near Frankfort, New York. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Inflight collision with the ground for undetermined reasons.

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

What the record shows

Date
July 31, 1995 · about 10:00 pm local time
Place
Frankfort, New York · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Kolb Company FIRESTAR, amateur-built
Registration
UNREG · no longer on the register
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

On July 31, 1995, at 1800 eastern daylight time, a Kolb Firestar experimental, homebuilt airplane was destroyed when it collided with the ground during takeoff climb near Frankfort, New York. The non-certificated pilot received serious injuries. Visual meteorological conditions prevailed for the local, personal flight. According to a Federal Aviation Administration (FAA) Inspector, the airplane was in the initial climb after takeoff when the pilot executed a right turn. During the turn, the airplane descended and impacted the ground. Postaccident examination by the FAA Inspector revealed no discrepancies with the airplane. No additional information is available.

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

Pilot

  • Medical certificate: Unknown
  • Seat: unk

The aircraft

  • Last inspection: inspection type not recorded
  • Landing gear: fixed
  • Engine: (type not recorded); 0 hours total
  • Not recorded

The flight

  • Flight plan: not recorded
  • Runway 0

Weather at the time

  • Light: not reported
  • Sky: not recorded; not recorded
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the 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.