FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11CA675 · Cessna T210R

29 Sept 2011 · Lamar, MO, United States

State of Missouri Cessna T210R · Accident: runway excursion during landing

From Jefferson City Memorial Airport (JEF) to Lamar Municipal Airport (LLU)

Report a problem

Event

NTSB case
CEN11CA675
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 T210R

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
N84MC
Onboard fatalities
Unknown
Route
From Jefferson City Memorial Airport (JEF), Jefferson City, MOTo Lamar Municipal Airport (LLU), Lamar, MO
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
Landing · landing roll
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

  • 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

According to the pilot, the windsock indicated the wind was from 290 degrees in excess of 15 knots when he landed on runway 21. He stated that the airplane encountered windshear as it approached the runway. The shift in the wind and the increase in speed resulted in the airplane floating down the runway prior to touching down. The pilot reported he was unable to stop the airplane with the brakes and it traveled off the end of the runway where it nosed over upon encountering an embankment. The airplane sustained substantial damage to the empennage and wings. The pilot stated he elected not to perform a go-around due to powerlines near the departure end of the runway.

Probable cause

The pilot's inadequate compensation for the wind condition, resulting in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11CA675
Event ID
20110930X30511
Case number
CEN11CA675
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: ec21028bfbe0a6d15337dc67a2b4da632ac42af4ddbe80097fee3e498989d14e; retrieved 2026-09-15T16:48:03.333Z.