FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA016 · Kitfox IV

14 Oct 2021 · North Canaan, CT, United States

Kitfox IV · Accident: landing area overshoot during an emergency descent

Report a problem

Event

NTSB case
ERA22LA016
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
Completed
API-reported fatalities
0 · 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 IV

Aircraft type
Kitfox IV
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
N9259M
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 25 years (built 1996)
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
Emergency descent
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
Landing area overshoot
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that shortly after takeoff during climbout, the engine began to sputter. He checked the magnetos, fuel switches, ignition, and fuel pressure. He did not notice any abnormalities; however, full engine power did not return. He subsequently performed a 180° turn back to the runway, but the airplane was too high and fast to land. The airplane overflew the runway toward a wooded area, and as the pilot attempted to increase power, the engine again sputtered. The pilot maintained a safe airspeed and flew into the tops of the trees. The airplane momentarily was suspended in the trees but then fell vertically and impacted muddy and swampy terrain in a nose-low attitude. Examination of the airplane did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that he utilized full carburetor choke to start the engine and partial carburetor choke to warm-up the engine. He could not recall stowing the lever prior to takeoff (as was required for this type of choke) nor did he recall checking the lever during the troubleshooting in-flight. The pilot reported the partial loss of power would worsen only when he attempted to add full power and that the engine would run normally at idle power. Weather conditions in the area at the time of the accident flight were conducive to serious carburetor icing at glide power; however, the description of the partial loss of engine power and the phase of flight at which it occurred were not indicative of carburetor icing. Given the circumstances described by the pilot, it is likely that the carburetor choke remained partially applied during the takeoff and climbout, which flooded the engine at high power settings. Although the spring-loaded choke lever was photographed in the stowed position shortly after the accident, it is possible that the choke switch was moved to that position during the impact sequence or during the pilot’s evacuation after the accident. The pilot reported that he turned back toward the departure runway while he was troubleshooting the engine issue, but the airplane was too high and fast to land and overflew the runway. Had the pilot managed the altitude, airspeed, and course toward the runway better, the collision with trees likely could have been avoided and a safe landing likely could have been made at the airport.

Probable cause

The pilot's mismanagement of the airplane's altitude, airspeed, and course during a forced landing following a partial loss of engine power, which resulted in collision with trees and terrain. Contributing was the pilot’s inadvertent omission of stowing the carburetor choke before takeoff and in-flight after experiencing a partial loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA016
Event ID
20211015104104
Case number
ERA22LA016
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, cause areas. 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: db162303c5ab61ef31b24a45506814e228f0688a68451db924dee341af3c77c6; retrieved 2026-09-16T14:40:04.989Z.