FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11LA080 · Schaefer Kitfox 4

23 Dec 2010 · Glendale, AZ, United States

Schaefer Kitfox 4 · Accident: loss of control in flight during initial climb

From Glendale Municipal Airport (GEU) to Glendale Municipal Airport (GEU)

Report a problem

Event

NTSB case
WPR11LA080
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
Unknown
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

Schaefer Kitfox 4

Aircraft type
Schaefer KITFOX 4
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
N95FT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Glendale Municipal Airport (GEU), Glendale, AZTo Glendale Municipal Airport (GEU), Glendale, AZ
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
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
Loss of control in flight
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

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The owner/pilot of the experimental amateur-built kit airplane was cleared by the air traffic controller to take off and remain in the traffic pattern for practice. Witnesses reported that the airplane climbed to about 200 feet above the runway before it banked sharply to the right and descended rapidly to ground impact. The impact location was offset about 300 feet from the runway centerline and was about 2,400 feet down the 7,150 foot long runway. The airplane motion, trajectory, and impact angle were consistent with an aerodynamic stall. The wind was calm, the density altitude was about 1,340 feet, and the airplane was about 380 pounds below its maximum gross weight of 1,350 pounds.

Several days after the accident, the pilot stated that he intentionally attempted to take off using partial engine power. The kit manufacturer's published guidance for the airplane contained conflicting information regarding the amount of power to be used for takeoff. The checklist section specified full power for takeoff. In contrast, the "Flight Tips" section instructed "new" pilots to "restrict take-off power to about 75% of full power" but did not provide any elaborating information. The guidance specified climb speeds between 45 and 65 mph and a clean power-off stall speed of 38 mph. The airplane was not equipped with either a stall warning or angle-of-attack indication system, and it was not required to be so equipped. Had the pilot recognized and correctly reacted to the impending stall, either by adding power, pushing the airplane nose down, or both, it is likely that the accident would not have occurred. The investigation was unable to determine the accuracy of the airspeed indication system or the actual stall speeds or stall characteristics of the airplane.

Probable cause

The pilot's failure to recognize the onset of and to prevent an aerodynamic stall at low altitude. Contributing to the accident were the manufacturer’s conflicting guidance about the power setting for takeoff and the pilot’s decision to conduct a partial-power takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11LA080
Event ID
20101223X72720
Case number
WPR11LA080
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. 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: 6251034cd12203dd07a81c3ab9d2315802dbd777b771bea285ae85a94769f029; retrieved 2026-09-15T15:38:33.630Z.