WPR10LA137
2010-02-17 · Imperial, California, United States · None · 1 aircraft · Status: Completed
Airport IPL
Aircraft involved
Probable cause & findings
The pilot's inadequate preflight inspection and his failure to ensure that the speed brakes were retracted, which resulted in a loss of control during takeoff.
Factual narrative
On February 17, 2010, at 1424 Pacific standard time, a Fouga CM 170 Magistar, N6222N, collided with terrain during takeoff from runway 32 at Imperial County Airport, Imperial, California. The airline transport pilot was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. The pilot was not injured. The airplane sustained substantial damage. Visual meteorological conditions prevailed and no flight plan was filed. The pilot reported that he had stopped at the airport to refuel and was departing from runway 32 when the accident occurred. After completing his pre-takeoff checklists, he departed down the runway. During the takeoff roll, the airplane's nose rose and the pilot pushed the stick forward. The pilot reported that the airplane was slower than normal and after reaching 100 knots, the airplane lifted from the runway. The pilot attempted to obtain 140 knots; however, the airplane "pitched up, rolled, and yawed to the right." He indicated that he shut the engines and electrical system down, and then exited the airplane. His initial assessment was that a gust of wind blew the airplane off of the runway. In a later statement, he indicated that he thought the airplane could have experienced drag from a clear coat of paint that was peeling, allowing sand to accumulate on the wings and result in drag. The local fire department responded to the accident site. Fire department personnel advised the pilot to shut down the engines and get out of the airplane. The pilot was having difficulty shutting down the engines and airport personnel responded to the airplane and shut the engines down. A witness, who was employed as a captain for Skywest Airlines, was standing at the terminal and observed the accident airplane. He saw the airplane taxiing and noted that the speed brakes were deployed on both sides. The airplane began the takeoff roll on runway 32 and was approximately 1,500 feet down the runway when it appeared the pilot “jerked the nose off of the runway.” The airplane did not accelerate and when it broke ground, it climbed 15 to 20 feet in the air and continued flying in ground effect. The right and left wings alternately dropped, and then the left wing stalled, the airplane rolled, and twisted to the right 110 degrees. Due to his location, the witness could not see the speed brakes during the takeoff. The witness indicated that the airplane appeared to rotate too early. At the time, the winds were reported as light and variable. The witness did not hear a change in engine noise until after the airplane impacted the ground. A Federal Aviation Administration inspector examined the airplane. The left main landing gear punctured through the right wing, the right main gear had separated, and there were multiple areas of damage to the fuselage belly. The right speed brake was deployed approximately halfway. The left speed brake was found stowed. No mechanical anomalies were identified. The speed brakes are electrically controlled and hydraulically operated. To set the position of the speed brakes, the pilot activates a switch in the cockpit, looks at the speed brakes, and releases the switch when the speed brakes are in the appropriate position based on the visual reference. During the landing approach, the speed brakes are normally deployed halfway. During the takeoff roll, the airplane accelerated slower than normal and approximately 1,500 feet down the runway, the nose abruptly rose and the airplane lifted off. The airplane continued in ground effect until, according to a witness, the right and left wings alternatively dropped, the left wing stalled, and the airplane rolled until it impacted the ground. The witness stated that prior to the airplane's takeoff, he saw the airplane taxiing to the runway and both speed brakes were deployed. He could not see the speed brakes during the takeoff, but felt that the pilot may have rotated the airplane from the runway too soon. Following the accident, FAA inspectors found the right speed brake deployed approximately halfway. The left speed brake was found stowed. No mechanical anomalies were identified. The speed brakes, which are located on the side of the fuselage aft of the wing, are electrically controlled and hydraulically operated. To set the position of the speed brakes, the pilot activates a switch in the cockpit, visually looks at the speed brakes, and releases the switch when the speed brakes are in the desired position. During the landing approach, the speed brakes are normally deployed halfway. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Action/decision-Action-Forgotten action/omission-Pilot - C
- C Personnel issues-Task performance-Planning/preparation-(general)-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2010_WPR10LA137.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, loss of control). All research papers
- Semantic Scholar 2016 · Article (Interacción) Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- Semantic Scholar 2024 · Article (International Conference on Networking and Services) Risk Assessment of Loss of Control In-Flight Trajectories for Urban Air Mobility Safety
In Urban Air Mobility (UAM), maintaining a minimum separation between aircraft is a safety requirement, which becomes challenging amidst congested air traffic and off-nominal conditions, such as Loss …