CHI02LA047
2001-12-09 · Lawrence, Kansas, United States · None · 1 aircraft · Status: Completed
Airport LWC
N202DN has since been reassigned. It is now registered to a different aircraft (FLYING LEGEND ITALIA SRLS TUCANO REPLICA, built 2018), which was not involved in this event.
Aircraft involved
Probable cause & findings
The copilot's failure to maintain aircraft control during the landing. Factors relating to this accident were the copilot's improper in-flight decision not to execute a go-around, the copilot not performing a go-around, the inadequate crew coordination prior to landing between the pilot and copilot, and the improperly set stabilizer trim.
Factual narrative
On December 9, 2001, at 1645 central standard time, a Dassault Falcon 100, N202DN, piloted by a commercial pilot, sustained substantial damage during a hard landing on runway 15 (5,002 feet by 100 feet, dry/asphalt) at the Lawrence Municipal Airport (LWC), Lawrence, Kansas. Visual meteorological conditions prevailed at the time of the accident. The business flight was operating on an instrument flight rules flight plan under the provisions of 14 CFR Part 91. The pilot and copilot reported no injuries. The cross country flight originated at Madison, Mississippi, at 1535, and was en route to Lawrence, Kansas. In his written statement, the pilot said that the copilot was flying a visual approach to runway 15 with the pilot backing him up in the left seat. The pilot said, "With gear down and full flaps at approximately 15 to 20 feet above the runway and 115 KTS, the nose abruptly dropped and there was no elevator effectiveness with the yoke pulled back to the mechanical stop." The pilot said, "After landing, I noticed that the stabilizer trim indicated full nose down in the cockpit and, upon exterior inspection, the stab was in that position." In his written statement, the copilot said, "I made my turn to base and proceeded to make my turn to final. No problems with the controllability were noted at this time. The turn to final was made and the airplane was lined up with the runway on final approach with normal glide path. My altitude was dropping normally and my airspeed was approx[imately] 140 knots." The copilot said, "When it got time to pull the power back to idle for landing our airspeed was approx[imately] 110 knots and power was reduced. At that point in time the nose of the aircraft seemed to pitch over towards the runway and increase speed. I pulled back on the yoke to raise the nose and at that same instance the pilot recognized the pitch over and pulled back on the yoke at the same time. The yoke did not seem to pull all of the way to its full extent of travel and felt to mechanically stop at about 3/4 the way travel. Even with both pilot's pulling on the yoke it seemed unresponsive and failed to raise the nose back to a proper landing attitude. The aircraft hit the runway very hard and came to a stop on the runway." A Federal Aviation Administration inspector examined the airplane at the Lawrence Municipal Airport. The left main landing gear strut was broken upward and had penetrated the top wing skin. The leading edge of the left wing was broken loose. The inboard portions of both wings showed skin wrinkles. There were bends and buckles in the fuselage beginning at the wings trailing edges and running forward to the cabin door. The stabilizer was positioned at 4 degrees nose down. An inspection of the flight control system revealed no anomalies. An examination of the engine, engine controls, and other airplane systems revealed no anomalies. A conformity check of the autopilot and flight control system, conducted on January 9, 2002, revealed no anomalies. The pilot said that the copilot was flying a visual approach to runway 15 at the Lawrence Municipal Airport, Lawrence, Kansas. The pilot said, "With gear down and full flaps at approximately 15 to 20 feet above the runway and 115 KTS, the nose abruptly dropped and there was no elevator effectiveness with the yoke pulled back to the mechanical stop." The pilot said, "After landing, I noticed that the stabilizer trim indicated full nose down in the cockpit and, upon exterior inspection, the stab was in that position." The copilot said, "I made my turn to base and proceeded to make my turn to final. No problems with the controllability were noted at this time. The turn to final was made and the airplane was lined up with the runway on final approach with normal glide path. My altitude was dropping normally and my airspeed was approx[imately] 140 knots." The copilot said, "When it got time to pull the power back to idle for landing our airspeed was approx[imately] 110 knots and power was reduced. At that point in time the nose of the aircraft seemed to pitch over towards the runway and increase speed. I pulled back on the yoke to raise the nose and at that same instance the pilot recognized the pitch over and pulled back on the yoke at the same time. The yoke did not seem to pull all of the way to its full extent of travel and felt to mechanically stop at about 3/4 the way travel. Even with both pilot's pulling on the yoke it seemed unresponsive and failed to raise the nose back to a proper landing attitude. The aircraft hit the runway very hard and came to a stop on the runway." A preliminary inspection of the airplane showed the stabilizer positioned at 4 degrees nose down. An examination of the airplane's systems revealed no anomalies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_CHI02LA047.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 (go-around, autopilot). All research papers
- arXiv 2025 · arXiv preprint ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- arXiv 2024 · arXiv preprint A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
- arXiv 2022 · arXiv preprint Experimental Flight Testing of a Fault-Tolerant Adaptive Autopilot for Fixed-Wing Aircraft
This paper presents an adaptive autopilot for fixed-wing aircraft and compares its performance with a fixed-gain autopilot.