CHI06CA156 · Cessna 182N
Cessna 182N · Accident: loss of control in flight during landing
From Hector International Airport (FAR) to Cooperstown Municipal Airport (S32)
Event
- NTSB case
- CHI06CA156
- 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 182N
- Aircraft type
- Cessna 182
- 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
- N9073G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hector International Airport (FAR), Fargo, NDTo Cooperstown Municipal Airport (S32), Cooperstown, ND
- 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 › Altitude, inadequate
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Directional 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 airplane contacted the terrain following a loss of directional control while landing. The pilot reported that while touching down on runway 31, a "burst" of wind from the left pushed the airplane to the right side of the runway. The pilot reported he added full left rudder, aileron, and power in an attempt to perform an aborted landing. The pilot stated the airplane did not gain sufficient altitude during the aborted landing. The airplane came to rest upon contacting vegetation along the side of the runway. Wind conditions reported 49 miles away at 1456 were from 230 degrees at 8 knots. The pilot reported that the local winds were from 220 degrees at 10 knots. The density altitude at the time of the accident was approximately 3,000 feet.
Probable cause
The pilot's inadequate compensation for the wind conditions which resulted in a loss of directional control while landing. Factors associated with the accident were the crosswind condition, the high vegetation which the airplane contacted, and the high density altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06CA156
- Event ID
- 20060707X00889
- Case number
- CHI06CA156
- 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: 539490aa8be81f6e15a99e6c86e148801f5b3f04a3eace0dbe9909b9d845827b; retrieved 2026-09-22T04:44:33.682Z.