DEN01LA131 · Cessna T210M
Cessna T210M · Accident: loss of control in flight during landing
From Provo Municipal Airport (PVU) to U77 · Spanish Fork, UT
Event
- NTSB case
- DEN01LA131
- 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 T210M
- 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
- N6798B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo U77 · Spanish Fork, UT
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was on a left downwind leg for landing on runway 30 when the pilot noticed a strong 90 degree southwest crosswind. On final approach, the airplane was in "a serious side slip configuration (aileron hard left, right rudder)." The left wheel touched down. Just before the right wheel touched down, a strong wind gust from the southwest lifted the airplane back into the air, and the pilot decided to abort the landing. He added full power and lowered the nose since the stall warning was sounding. He felt the airplane touch down twice in dirt, and bounce twice. Thereafter, his only recollection of the accident was spinning around and coming to a halt in a ditch. The recorded winds at a location 6 nautical miles northwest of the accident site were from 230 degrees at 14 knots gusting to 18 knots.
Probable cause
the pilot's inadequate compensation for the wind conditions which resulted in a loss of control during landing. A contributing factor was the gusty crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN01LA131
- Event ID
- 20010808X01633
- Case number
- DEN01LA131
- 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. 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: e07743837c1b7d488cc6e633662d96a7c1082ce8eeaac0bd23f4563984d0c906; retrieved 2026-09-21T19:53:34.767Z.