CEN09CA569 · Cessna T210 N
Cessna T210 N · Accident: runway excursion during takeoff
From Tulsa Riverside Airport (RVS) to 0R3 · Abbeville, LA
Event
- NTSB case
- CEN09CA569
- 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
Cessna T210 N
- Aircraft type
- Cessna 210
- 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
- N6442Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (RVS), Tulsa, OKTo 0R3 · Abbeville, LA
- 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 · rejected 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
- Runway excursion
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was on a takeoff roll from a 4,208-foot-long paved runway. At rotation speed the yoke was unresponsive and the pilot was unable to pull the yoke back for liftoff. The pilot said that he immediately looked down and confirmed that the gust lock was not installed and aborted the takeoff. The airplane exited the runway at the departure end and the pilot performed an intentional ground loop to avoid crashing through the airport boundary fence. There was substantial damage to the airplane, but no injuries to the private pilot, who was the only occupant. The two Federal Aviation Administration inspectors who responded to the accident scene confirmed continuity of the flight controls and did not find any precrash anomalies that would have prevented normal operations.
Probable cause
A temporary loss of elevator pitch control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA569
- Event ID
- 20090908X51901
- Case number
- CEN09CA569
- 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, coordinates. 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: 8ae38e725110b994b54530d3478e34c5c046d4f1a90d383898ab68f8fe0d2d17; retrieved 2026-09-15T12:55:15.991Z.