FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD96LA049 · Kitfox IV-1200

14 Mar 1996 · Saluda, VA, United States

Kitfox IV-1200 · Accident: partial loss of engine power (mechanical failure) during initial climb

From Hummel Field (W75) to an unrecorded destination

Report a problem

Event

NTSB case
IAD96LA049
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-1200

Aircraft type
Kitfox IV-1200
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
N32495
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hummel Field (W75)To 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
Initial climb
First occurrenceThe 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
Partial loss of engine power (mechanical failure)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
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

  • Ignition system, spark plug › Failure
  • Pilot in command › Evasive maneuver, intentional

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that there was a partial loss of engine power shortly after the airplane lifted off. The airplane would not climb, so he elected to land on the remaining runway. In his attempt to avoid lights at the end of the runway, the pilot stalled the airplane approximately ten feet above the surface. The airplane impacted the runway in a steep nose down attitude, then '...rolled over onto it's back.' Postaccident investigation revealed that the #1 spark plug failed an electrical function test. The pilot stated that the spark plug operated normally under low load conditions, but '...[stopped] under full load.'

Probable cause

a partial loss of engine power due to spark plug failure, and the pilot's evasive maneuver to avoid lights at the end of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD96LA049
Event ID
20001208X05412
Case number
IAD96LA049
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 5dab40ebafb507ee1dd7090e0e734e3d22852bcaf5a24fb1e65bf5e1ea46e0c7; retrieved 2026-09-21T21:56:59.484Z.