NTSB CAROL · Event
Event CHI00LA157
Aircraft involved
Probable cause & findings
altitude/clearance from the trees not being obtained/maintained by the pilot during the initial climb after takeoff. Factors to the accident were the inadequate preflight planning/preparation by the pilot, including takeoff performance data not being calculated, the correct procedures/directives for a short field takeoff with obstacles not being followed by the pilot, the trees, and the encountered stall.
Factual narrative
On June 10, 2000, at 1405 eastern daylight time, a Piper PA-28R-200, N2379T, owned and piloted by a private pilot, sustained substantial damage during an in-flight collision with trees and terrain following a loss of control while on initial climb from runway 18 (2,510 feet by 50 feet, dry/asphalt) at the Dalton Airport, Flushing, Michigan. Visual metrological conditions prevailed during the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 and was not on a flight plan. The pilot and the single passenger sustained serious injuries. The flight was originating at the time of the accident and had the intended destination of Luce County Airport, Newberry, Michigan. The pilot stated in a written statement, "We departed with 10-degrees flaps, prop [propeller] full forward, mixture rich and the throttle full forward. I rotated at 65 mph for lift-off. The airplane immediately lifted off but felt sluggish while climbing up. When we got to the end of the runway, we were at tree top level and it felt like our wheels were in the tops of the trees. The airplane was not climbing as it should and did not feel it had normal power nor was it performing as it normally does under the same flight conditions." The pilot reported, "I banked slightly to the left after reaching the end of the runway trying to go for clearer area, as I felt we were in trouble. I wanted to avoid setting the airplane down in a nearby subdivision. As I banked, I noticed the stall light blink one time and I could no longer hold altitude. The next thing I can recall is being rescued." The pilot stated that he had 50-gallons (300-lbs) of fuel on board the aircraft at the time of the accident. The pilot reported that the airplane was loaded with himself (200-lbs), one passenger (130-lbs), a load of fishing gear (exact weight unknown), and personal luggage (exact weight unknown). According to the POH, utilizing a calculated density altitude of 2,785-feet and 25-degrees of flaps used during the takeoff, the distance to clear a 50-foot obstacle was approximated at 2,250-feet. Utilizing the same density altitude but 0-degrees of flaps used for the takeoff, the distance to clear a 50-feet obstacle was approximated at 2,500-feet. The takeoff calculations were based on a takeoff from a paved, dry, level runway and at the aircraft's certified maximum gross weight of 2,600-lbs. According to the POH, the procedure used for a takeoff from a short field with obstacles was listed as: "Short Field, Obstacle Clearance: Lower flaps to 25-degrees (second notch), accelerate aircraft to 60-65 MPH and ease back on the wheel to rotate. After breaking ground, accelerate to best angle of climb speed, 85 MPH, select gear "up" and continue climb while accelerating to best rate of climb speed, 100 MPH, and slowly retract the flaps while climbing out." Post-accident investigation revealed that the landing gear was fully extended and the flaps were at 10-degrees (first notch). A weather observation station, located at the Bishop International Airport (FNT), 6 nautical miles from the accident site on 154-degree magnetic heading, reported the weather 12-minutes prior to the accident as: Observation Time: 1353 eastern daylight time Wind: 250-degrees at 11 knots with gusts of 21 knots Visibility: 10 statute miles Sky Condition: Sky Clear Temperature: 31-degrees centigrade Dew Point Temperature: 19-degrees centigrade Pressure: 29.95 inches of mercury No anomalies were found with the aircraft or its related control systems that could be associated with a preexisting condition. No anomalies were found with the aircraft engine or it related systems that could be associated with a preexisting condition. The pilot attempted to takeoff from a 2,510-foot long runway with trees at the end, at a weight near maximum gross-weight, with a 2,785-feet density altitude. The aircraft stalled at the end of the runway, at treetop level, subsequently impacting the trees and terrain. The pilot reported that he selected 10-degrees of flaps for the takeoff. The Pilot's Operating Handbook (POH) for the accident aircraft indicates that 25-degrees of flap is to be used for short-field takeoffs that have obstacles and that the landing gear to be retracted after lift-off. Post-accident investigation revealed that the landing gear was fully extended and the flaps were at 10-degrees (first notch). According to the POH, utilizing a calculated density altitude of 2,785-feet and 25-degrees of flaps used during the takeoff, the distance to clear a 50-foot obstacle was approximated at 2,250-feet. Utilizing the same density altitude but 0-degrees of flaps used for the takeoff, the distance to clear a 50-feet obstacle was approximated at 2,500-feet. The takeoff calculations were based on a takeoff from a paved, dry, level runway and at the aircraft's certified maximum gross weight of 2,600-lbs. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_CHI00LA157.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- 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…
- arXiv 2025 · arXiv preprint
Quadratic Programming Approach to Flight Envelope Protection Using Control Barrier Functions
Ensuring the safe operation of aerospace systems within their prescribed flight envelope is a fundamental requirement for modern flight control systems.
- 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.
Browse the full corpus — academia portal ↗