Skip to content

Atlas / NTSB / CEN12LA495

NTSB CAROL · Event

Event CEN12LA495

2012-07-29 Lakeview, Arkansas, United States Airport · 3M0 None 1 aircraft Status: Completed

Registry · N462CP

FAA Aircraft Registry record.

Make / Model

CIRRUS DESIGN SR22

Year of manufacture

2008 · 4 years old at event

TCDS

A00009CH · CIRRUS DESIGN CORP

Engine

CONT MOTOR IO-550-N (310 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20080922

ADS-B equipped

Yes — Mode-S A5A149

Registrant of record

PONOZZO DONALD A

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot’s loss of control during the takeoff roll for reasons that could not be determined because postaccident examination of the airplane did not reveal any anomalies that would have precluded normal operation.

Factual narrative

On July 29, 2012, about 1430 central daylight time, a Cirrus SR22 airplane, N462CP, veered right during the takeoff roll and impacted trees near Gastons Airport (3M0), Lakeview, Arkansas. The private rated pilot and two passengers were not injured and the airplane was substantially damaged. The airplane was owned and operated by RTJ Aircraft, Inc., Wilmington, Delaware, under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Day visual meteorological conditions prevailed for the flight, which operated without a flight plan. The flight was originating from 3M0 at the time of the accident. The pilot reported to the Federal Aviation Administration (FAA) inspector that during the takeoff roll the airplane pulled to the right. He was unable to correct the right turn and the airplane impacted a fence and trees before coming to a stop. Examination of the wreckage revealed that the outboard section of the left wing impacted a tree and was severed from the rest of wing; the remaining section, near the wing root, remained with the fuselage. A small outboard section of the right wing was separated during impact with the tree. The grass runway surface had the airplane’s tracks leading to the right, into the trees and fence. No obstacles or airplane debris were noted on the runway surface. The National Transportation Safety Board (NTSB) and a technical representative from the airframe manufacturer examined the airplane at a salvage yard. Examination of the airplane did not reveal any pre-impact mechanical malfunctions. The airplane’s Recoverable Data Module (RDM) and flight display’s data cards were removed and sent to the NTSB Vehicle Recorder Laboratory in Washington, D.C., for download. The display’s data cards did not contain any suitable data. The RDM records numerous airplane parameters. The RDM normally records both left and right brake temperatures; however, data for the left brake was absent on the RDM. The temperature data for the right brake started at about 105 degrees F, and rose to a maximum of about 120 degrees Fahrenheit (F). Other than the missing left brake temperature readings, no other abnormalities were noted. During the takeoff roll on a grass runway, the airplane veered right and impacted trees and a fence. A check of the runway surface did not reveal any obstacles or reasons for the right turn. Examination of the airplane did not reveal any preimpact malfunctions with the airplane’s controls. The airplane was equipped with a Recoverable Data Module (RDM,) which records various aircraft parameters, including brake temperatures. The right brake temperature started at about 105 degrees Fahrenheit (F) and rose to a high of about 120 degrees F. The left brake temperature was not captured by the RDM, suggesting that the temperature sensor was not working at the time of the accident. Without the left brake sensor reading, a comparison of the left and right brake temperatures cannot be made; therefore, it cannot be determined if the pilot inadvertently applied the right brake during the takeoff roll. 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 Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C

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