CHI99LA091
1999-03-10 · BATTLE CREEK, Michigan, United States · None · 1 aircraft · Status: Completed
Airport BTL
N989AV has since been reassigned. It is now registered to a different aircraft (PIPER PA 46-350P, built 2021), which was not involved in this event.
Aircraft involved
Probable cause & findings
the loss of directional control by the pilot. Factors to the accident were the lack of total experience of the pilot, the snow covered runway condition, the snowbank, and the flight instructor not verifying the runway snow removal with the Duty Instructor prior to releasing the student pilot for solo operations.
Factual narrative
On March 10, 1999, at 0902 eastern standard time, a Cessna 172R, N989AV, piloted by a student pilot, sustained substantial damage after a loss of control and collision with a snowbank during landing roll on Runway 31 (4,835 feet by 100 feet, snow covered/asphalt) at the W.K. Kellogg Airport, Battle Creek, Michigan. Visual meteorological conditions prevailed at the time of the accident. The solo instructional flight was operating under the provisions of 14 CFR Part 91. The flight was not operating on a flight plan. The pilot reported no injuries. The flight originated at the W.K. Kellogg Airport at approximately 0855 for the local flight. According to the pilot's written statement, the approach to the runway was uneventful and that the airplane touchdown was a couple of feet left of the centerline. The pilot stated that, "I immediately noticed that the aircraft was starting to skid to the left. I immediately pushed the right rudder but there seemed to be no response to move it back to the right." The pilot reported that as the aircraft slid to the left, into the deeper snow, the airplane pivoted to the left, the propeller impacted the snowbank, and the airplane nosed over coming to rest inverted. A witness to the accident described the runway condition as, "Runway 31 appeared to have been ploughed but was covered in snow with no blacktop [visible]." Inspection of the wreckage revealed no anomalies with the airframe, flight controls, or engine. The pilot had a total time of 15.4 hours, of which 13.8 hours were dual instruction and 1.6 hours were pilot-in-command. The accident flight was the pilot's third solo flight. According to a written statement provided by the International Pilot Training Centre of Western Michigan University, the Duty Instructor for that morning had determined that the runway conditions should be checked before students could solo. The Duty Instructor placed a notification in the dispatch room stating, "No solos until the runway has been checked." The student pilot's instructor made the decision not to sign the student off for solo until the runway conditions improved and were checked. Later in the morning, the school's dispatch was notified by an instructor, who was flying in the traffic pattern, that, "...solo operation would not be a problem if one did not lock up the brakes." The student's flight instructor did not communicate with the Duty Instructor about the runway conditions, and released the student pilot for solo operations. The pilot reported the airplane touchdown a couple of feet left of the centerline. He stated,... 'I immediately noticed that the aircraft was starting to skid to the left. I immediately pushed the right rudder but there seemed to be no response to move it back to the right.' The pilot reported that as the aircraft slid to the left, into the deeper snow, the airplane pivoted to the left, the propeller impacted the snowbank, and the airplane nosed over coming to rest inverted. A witness to the accident described the runway condition as, 'Runway 31 appeared to have been ploughed but was covered in snow with no blacktop [visible].' Inspection of the wreckage revealed no anomalies with the airframe, flight controls, or engine. The pilot had a total time of 15.4 hours, of which 13.8 hours were dual instruction and 1.6 hours were pilot-in-command. The accident flight was the pilot's third flight as pilot-in-command. The Duty Instructor for that morning had determined that the runway conditions should be checked before students could solo. The Duty Instructor placed a notification in the dispatch room stating, 'No solos until the runway has been checked.' The student pilot's instructor made the decision not to sign the student off for solo until the runway conditions improved and were checked. Later in the morning, the school's dispatch was notified by an instructor, who was flying in the traffic pattern, that, '...solo operation would not be a problem if one did not lock up the brakes.' The student's flight instructor did not communicate with the Duty Instructor about the runway conditions, and released the student pilot for solo operations. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_CHI99LA091.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 (loss of control). All research papers
- 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 …
- NTSB Aircraft Accident Reports 2022 · Accident report Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation) ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.