FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26FA022 · Kitfox II

17 Oct 2025 · Spruce Pine, NC, United States

Kitfox II · Accident during takeoff

Report a problem

Event

NTSB case
CEN26FA022
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Kitfox II

Aircraft type
Kitfox II
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N8610X
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On October 17, 2025, about 1154 eastern daylight time, a Kitfox II airplane, N8610X was destroyed when it was involved in an accident near Spruce Pine, North Carolina. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Witness 1 reported that the pilot completed one takeoff and landing on grass runway 17 at the Avery County Airport-Morrison. Later, two witnesses saw the airplane taxiing on the grass east of the asphalt runway near the windsock. Witness 1 reported that he briefly observed what appeared to be the accident airplane executing a takeoff roll from the east side of the airport, parallel to runway 17 (Figure 1).

Figure 1 – Overview of Accident Site The accident site was located about 60 ft below airport field elevation on the side of a brush-covered embankment southeast of the approach end of runway 35. Examination of the accident site revealed that the airplane impacted the terrain in a nose-low attitude on a northwesterly heading (See Figure 2). The airframe fabric was consumed by the post impact fire, and the underlying tubular structure exhibited aft crushing consistent with impact damage. Both wings remained partially attached to the fuselage, with both flaperons found separated near their respective wings. Flight control continuity was established from the cockpit to the center fuselage near the wing roots for flaperon controls. The empennage, to include the horizontal and vertical stabilizer, elevator, and rudder, remained attached to the airframe. The rudder and elevator controls were continuous from the cockpit to their respective control surfaces. The engine was found partially attached to the airframe, with the propeller separated from the engine at the gearbox. The main wreckage was partially embedded in the ground. All three composite propeller blades were found to be thermally damaged and relatively straight. Blade A was separated near the propeller hub, blade B was partially cracked near the propeller hub, and blade C was unremarkable. Initial examination of the engine revealed damage to the engine assembly consistent with impact and the post impact fire. The crankshaft could not be rotated due to damage consistent with the impact sequence. The cylinder head and cylinders were removed, and no anomalies were observed to the engine that would have precluded normal operation. Figure 2 – View of Main Wreckage

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN26FA022
Event ID
20251017201880
Case number
CEN26FA022
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 2b938a4517301d3f6dbf93881669d78b373834883b6d0501404944923c6f85d9; retrieved 2026-09-15T09:10:14.580Z.