CHI08CA030 · Cessna 172M
Cessna 172M · Accident: loss of control in flight during landing
From Duluth International Airport (DLH) to Duluth International Airport (DLH)
Event
- NTSB case
- CHI08CA030
- 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 172M
- Aircraft type
- Cessna 172
- 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
- N4366R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Duluth International Airport (DLH), Duluth, MNTo Duluth International Airport (DLH), Duluth, MN
- 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 › Compensation for wind conditions, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was performing a crosswind landing during a local flight. While on final approach to runway 27 the airplane reportedly encountered "significant southerly winds and gusts." The pilot stated that just prior to touchdown his "landing control suddenly deteriorated" and he attempted to level the airplane before impacting the runway. The nose landing gear separated from the airplane during the impact, which resulted in substantial damage to the engine firewall. A weather observation, completed 6 minutes after the accident, indicated that the wind was from 210 degrees at 11 knots. Another observation, completed 31 minutes after the accident, indicated that the wind was from 190 degrees at 12 knots, gusting to 19 knots. The pilot reported that the accident could have been prevented if he had used runway 21, which would have reduced the crosswind component during landing.
Probable cause
The pilot's inadequate compensation for wind conditions during the landing approach. Contributing to the accident was the crosswind weather condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA030
- Event ID
- 20080103X00015
- Case number
- CHI08CA030
- 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: c22870dc78e0d0cf0e71a0e3b51cee5a5fc3e00d364eec5462d5d77bb2f66c1e; retrieved 2026-09-22T03:18:30.263Z.