FTW01LA080 · Cessna 210D
Cessna 210D · Accident: loss of control in flight during landing
From Alice International Airport (ALI) to Lawton Fort Sill Regional Airport (LAW)
Event
- NTSB case
- FTW01LA080
- 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 210D
- 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
- N210HS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Alice International Airport (ALI), Alice, TXTo Lawton Fort Sill Regional Airport (LAW), Lawton, OK
- 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 · flare/touchdown
- First occurrenceThe 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 in flight
- 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
- Pilot in command › Aircraft control, not maintained
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 obtained weather information prior to the flight, en route, and on final approach for the landing. The pilot reported that when the airplane was cleared for the landing on runway 35, the tower controller reported the wind from 310 degrees at 25 knots, and during the landing flare/touchdown, the controller stated "the wind was changing rapidly and was now from 270." The pilot reported that "at touchdown the crosswind overcame my ability to keep the aircraft straight." The left wing tip struck the runway, and the airplane exited the runway and came to rest upright in the grass between the runway and a taxiway. The pilot rated passenger reported the airplane was number two to land behind another aircraft that reported a loss of 10 knots airspeed at touchdown. Approximately one hour after the accident, the weather observation at the airport reported the wind from 300 degrees at 23 knots with gust to 31 knots.
Probable cause
the pilot's failure to maintain aircraft control during the landing flare/touchdown. A contributing factor was the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01LA080
- Event ID
- 20010319X00600
- Case number
- FTW01LA080
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: abca56edf548926c8ff35754b6f8c7ac4be26d218c05253c4727b9579bdf5eba; retrieved 2026-09-22T12:06:00.845Z.