Skip to content

Atlas / NTSB / CEN12CA465

NTSB CAROL · Event

Event CEN12CA465

2012-07-21 Oshkosh, Wisconsin, United States Airport · OSH Serious 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot’s excessive airspeed at touchdown and his loss of control of the airplane during the landing roll.

Factual narrative

The airplane was arriving at EAA AirVenture when the accident occurred. During AirVenture, the 6,300 foot long taxiway that parallels the right side of runway 36 is designated as runway 36R and is used for takeoffs and landings as determined by the control tower. In addition, there are four colored dots placed on runway 36L and pilots are issued landing instructions in reference to the dots. The pilot reported he was cleared to land on runway 36R, abeam the “yellow dot” which was on runway 36L. The yellow dot was located 2,900 feet from the runway threshold. The pilot stated he was concentrating on touching down at the yellow dot and he forced the airplane onto the runway at too fast of an airspeed. The airplane bounced two or three times and traveled off the right side of the runway/taxiway into the grass where it contacted a taxiway light. The pilot stated the brakes were ineffective due to the speed and the grass. The airplane continued across a service road where it contacted six heavy military vehicles that were among a row of parked vehicles. Both wings and the firewall were substantially damaged. The pilot stated there was nothing mechanically wrong with the airplane. The pilot stated that, during landing, he was concentrating on touching down at a particular location, and he forced the airplane onto the runway at an airspeed that was too fast. The airplane bounced two or three times and traveled off the right side of the runway/taxiway into the grass where it contacted a taxiway light. The pilot stated that the brakes were ineffective due to the speed and the grass. The airplane continued across a service road where it contacted six heavy military vehicles that were among a row of parked vehicles. Both wings and the firewall were substantially damaged. The pilot stated that there was nothing mechanically wrong with the airplane. 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).

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

Verbatim from NTSB's published report. Source file NTSB_2012_CEN12CA465.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 (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.

Browse the full corpus — academia portal ↗