CEN22LA262 · Cessna P210N
Cessna P210N · Accident: collision during takeoff/landing
From an unrecorded airport to Cleburne Regional Airport (CPT)
Event
- NTSB case
- CEN22LA262
- 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
- Event fatalities
- Unknown
- 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 P210N
- 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
- N7361K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Cleburne Regional Airport (CPT), Cleburne, TX
- Aircraft age
- About 43 years (built 1979)
- 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
- Collision during takeoff/landing
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was conducting a third maintenance test flight after a new engine had been installed with the airplane’s co-owner and two other passengers on board. The airplane was full of fuel and no preflight weight and balance calculations were completed. During the takeoff roll, the pilot rotated about 51 kts, which was 20 knots below normal rotation speed, and the airplane became airborne briefly before it settled back on the runway. The pilot then added nose up trim, rotated at 55 kts, and climbed slowly. The pilot continued to climb the airplane when the co-owner heard the stall warning horn. The pilot made a left turn to avoid terrain at the south end of the runway and then setup for a forced landing as the airplane was unable to maintain altitude. During the forced landing, the airplane impacted trees and terrain. The airplane sustained substantial damage to the fuselage and both wings. The pilot reported that the airplane was overweight and that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation. A postaccident weight and balance calculation determined that the airplane was about 359 lbs over the maximum takeoff weight.
Probable cause
The pilot's failure to complete proper preflight performance planning and his operation of the airplane outside of the manufacturer's specified weight and balance limitations, which resulted in the airplane’s inability to maintain altitude and an impact with trees and terrain during an attempted forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA262
- Event ID
- 20220623105319
- Case number
- CEN22LA262
- 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, cause areas. 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: f058b448ecbe1ab7039137a01d78b2764ae822f061911ae690a64b73a24e3252; retrieved 2026-09-16T15:22:22.213Z.