FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17LA059 · Cessna 210 N

20 Dec 2016 · Longville, MN, United States

Cessna 210 N · Accident: windshear or thunderstorm on approach

From Winsted Municipal Airport (10D) to Longville Municipal Airport (XVG)

Report a problem

Event

NTSB case
CEN17LA059
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 210 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
N80RB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Winsted Municipal Airport (10D), Winsted, MNTo Longville Municipal Airport (XVG), Longville, MN
Aircraft age
About 34 years (built 1982)
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
Approach
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
Windshear or thunderstorm
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, while on final approach to runway 31, the airplane flew through windy conditions and a "severe down wind shear." He said that the wind "drove" the airplane into the runway, and the airplane bounced a couple times. The left main landing gear contacted the snow and the airplane exited the runway, which resulted in substantial damage to the lower fuselage. The pilot indicated that there were no mechanical malfunctions or failures with the airplane. About 20 minutes before the accident, the recorded wind at the airport was 260° at 11 kts, gusting to 19 kts.

Probable cause

The in-flight encounter with wind shear and gusting wind conditions, which resulted in a bounced landing and runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA059
Event ID
20161221X21120
Case number
CEN17LA059
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. 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: 59360975b9ac1e66e079508d08332bc4163d460cb8c2178fcd3ec644078905ac; retrieved 2026-09-16T04:54:33.003Z.