CEN12LA495 · Cirrus Design Corp SR22
RTJ Aircraft Cirrus Design Corp SR22 · Accident: loss of control on ground during takeoff
From Gastons Airport (3M0) to Gastons Airport (3M0)
Event
- NTSB case
- CEN12LA495
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N462CP
- Operator
- RTJ Aircraft
- Onboard fatalities
- Unknown
- Route
- From Gastons Airport (3M0), Lakeview, ARTo Gastons Airport (3M0), Lakeview, AR
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA495
- Event ID
- 20120731X35733
- Case number
- CEN12LA495
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 5cbdedbefaed7b28ba242fbbf6f3c9a38a75e0624df268f9271fa73c0ba69711; retrieved 2026-09-15T19:07:59.102Z.