Amateur-built KITFOX accident near Parma, Idaho, August 8, 2025
On August 8, 2025 at about 5:20 pm local time, a 2006 amateur-built KITFOX, registered N300KF, was substantially damaged in an accident during landing near Parma, Idaho (Parma airport). 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
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 8, 2025 · about 5:20 pm local time
- Place
- Parma, Idaho · Parma · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built KITFOX IV, built 2006
- Registration
- N300KF · no longer on the register · serial C9904-0300
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On August 8, 2025, about 1120 mountain daylight time, an experimental amateur-built Kitfox airplane, N300KF, was substantially damaged when it was involved in an accident near Parma, Idaho. The pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that after an uneventful 2 hour flight, he was on the base leg of the traffic pattern with the engine operating at 3,000 rpm when it abruptly lost all power. He then advanced the throttle, but the engine did not respond. The pilot noted that the engine did not sputter or exhibit any unusual sounds before the engine lost power. With insufficient altitude to reach the runway, he selected a nearby pasture and performed a forced landing. During the landing roll, the airplane nosed over and came to rest inverted, resulting in substantial damage to the vertical stabilizer and rudder. The pilot additionally stated that he did not have sufficient time to restart the engine before the airplane touched down. The airplane was recovered to a secure location for further examination.
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
- Powerplant sys/comp malf/fail during landing defining event
The aircraft
- Landing gear: fixed
The flight
- Flight plan: none
- Runway 12/3, 2,700 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 260° at 11 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 43°F (6°C)
- Altimeter: 30.17 inHg
- Observation at 11:56 am from KEUL, 15 miles away
Weather report (METAR): KEUL 081756Z AUTO 26011KT 10SM CLR 22/06 A3017 RMK AO2 SLP201 6//// T02220061 10222 20122 58000 PNO $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
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.