Schaefer Kitfox 4 near Glendale, AZ — 2010-12-23
- Date
- 2010-12-23
- Location
- Glendale, AZ, USA
- Airport
- GEU
- Aircraft
- Schaefer Kitfox 4
- Registration
- N95FT
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Takeoff roll
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.
Contributing factors
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.
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.
Analysis
- Primary failure mode
- Human factors
- First missed decision gate
- Pilot should have used full throttle for takeoff as per operating procedures.
NTSB coding
Evidence available
- 11 docket documents
Docket documents11
- Air Traffic Controller Statementsatc
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Stall Warning System Informationform
- Pilot's Written Statementinterview
- METARsother
- Pilot and Airplane Recordsother
- Record of Communication - FAA and Pilotother
- Record of Conversation - FAA Inspectorother
- Record of Conversation Airport Operation's Managerother
- Site and Airplane Documentationother
- Airport Operations Accident Reportreport
Related mishaps
- CASSUTT IIIM
2026-07-05 · Odessa, TX
- PIPER PA-22-108
2026-06-05 · Westminster, MD
- TORRES RUBEN AVENTURA II
2025-11-15 · Culebrita Beach, PR
- CESSNA 152
2025-10-23 · St. Augustine, FL
- SCOTT VINCIN JUST ACFT HIGHLANDER
2025-07-13 · Mancos, CO
- Kyle Koncak Aventura II
2025-07-03 · DeLand, FL