Skip to content

Atlas / NTSB / CEN20LA372

NTSB CAROL · Event

Event CEN20LA372

2020-08-30 Ray, Michigan, United States Airport · 57D Minor 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot’s loss of directional control on takeoff.

Factual narrative

On August 30, 2020, about 1200 eastern daylight time, a Cessna 414 airplane, N698D, was substantially damaged when it was involved in an accident at Ray Community Airport (57D), near Ray, Michigan. The pilot received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the purpose of the flight was to reposition the airplane for an annual inspection and installation of automatic dependent surveillance – broadcast (ADS-B), equipment. The preflight inspection and engine run-up were normal, and the brakes operated normally during taxi. The pilot stated that he gently applied full power, everything seemed good, and the airplane started to slowly accelerate. He stated that about a third of the way down the runway, about 50 mph, the airplane suddenly started to steer right, which he attempted to counteract with left rudder input. His heels were on the floor to avoid inadvertent brake application during takeoff. After another 1-2 seconds, he decided to abort the takeoff; he applied the brakes and shut down the engines. At this time, the airplane was already partially in the grass. The airplane traveled into the grass, turned 90º to the left, and the landing gear collapsed. A witness, who was a pilot with multiengine experience, including experience in twin engine Cessna airplanes, reported seeing the airplane taxi onto runway 28 for departure. He noted that the airplane did not use the displaced threshold as available runway for the takeoff, and it taxied up past the end of the displaced threshold. He reported that the airplane then stopped on the runway and the engines went to full power. The airplane accelerated and started to veer to the left and then overcorrected to the right at which point it was going to exit the runway. The nose of the airplane came up and the airplane attempted to fly in ground effect with both wings “wallowing near stall.” One wing eventually dropped, and the airplane pancaked sideways near the end of runway 28 in the grass field. The airplane sustained substantial damage including crush damage to its forward fuselage and separation of the nose landing gear. A comprehensive determination of the airplane’s mechanical integrity prior to the accident could not be determined due to the damage to the damage to the forward fuselage and nose landing gear; however, no apparent pre-impact defects were noted. The pilot reported that the preflight, taxi, and run-up were normal and that the brakes of the twin-engine airplane operated normally. He reported that during takeoff, the airplane suddenly veered to the right, which he attempted to counteract with left rudder input. He ultimately decided to abort the takeoff, but, according to the pilot, the airplane was already partially in the grass. It travelled through the grass, turned 90° to the left, and the landing gear collapsed. A pilot-rated witness reported seeing the airplane taxi onto the runway and that the airplane did not use the displaced threshold as available runway for takeoff. The airplane stopped on the runway and then the engines went to full power. During the takeoff roll, the airplane veered left, then overcorrected to the right, at which time the airplane was going to exit the runway. The airplane became airborne and attempted to fly in ground effect with the wings “wallowing near stall.” One wing dropped and the airplane impacted the ground. The fuselage sustained substantial damage. Examination of the airplane was limited due to impact damage; however, there were no preimpact anomalies noted that would have precluded normal operations. Based on the available information, the pilot lost directional control of the airplane during takeoff. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained
  • Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot

Verbatim from NTSB's published report. Source file NTSB_2020_CEN20LA372.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗