FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA210 · Cessna 170B

15 Jun 2025 · Fort Morgan, CO, United States

Cessna 170B · Accident: loss of control on ground during landing

From Greeley–Weld County Airport (GXY) to Fort Morgan Municipal Airport (FMM)

Report a problem

Event

NTSB case
CEN25LA210
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 170B

Aircraft type
Cessna 170
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
N1996C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Greeley–Weld County Airport (GXY), Greeley, COTo Fort Morgan Municipal Airport (FMM), Fort Morgan, CO
Aircraft age
About 72 years (built 1953)
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
Loss of control on ground
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
  • Environmental issues › Conditions/weather/phenomena

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 was conducting a full stall (3-point) landing in the tailwheel-equipped airplane. The pilot reported that after touchdown a wind gust from the right caused the airplane to roll left and ground loop. The fuselage and left wing were substantially damaged during the ground loop when the left landing gear collapsed. Based on the reported wind direction and speed at the airport, there was likely a right crosswind component of about 6 to 9 knots at the time of the accident. The pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane.

Probable cause

The pilot’s failure to maintain directional control of the tailwheel-equipped airplane during a gusty crosswind landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA210
Event ID
20250618200350
Case number
CEN25LA210
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: 5aa30e14e9d00c5bbd62628304ea50001dae776ffc655c82819791138991d916; retrieved 2026-09-16T19:58:52.481Z.