SEA04LA087 · Cessna 185A
Cessna 185A · Accident: loss of control on ground/water during landing
From Polson Airport (8S1) to 8S1
Event
- NTSB case
- SEA04LA087
- 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 185A
- Aircraft type
- Cessna 185
- 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
- N1624H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Polson Airport (8S1), Polson, MTTo 8S1
- 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 · landing roll
- 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 on ground/water
- 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
On the day of the accident, the pilot was performing a series of touch-and-go landings in variable gusty wind conditions in order to "...maintain proficiency on a gusty day." After three successful touch-and-go landings, he pilot decided to make the next landing a full-stop termination of the flight. During the subject landing, the wind shifted from a quartering headwind to a quartering tailwind, and although the touchdown was uneventful, during the landing roll the aircraft suddenly started turning toward the side of the runway. Although the pilot applied control inputs in an attempt to keep the aircraft on the runway, his inputs were not adequate to overcome the effects of the varying wind conditions, and therefore the aircraft departed the side of the runway. The pilot then added full power in order to regain control and execute a go-around. During that sequence of events, the aircraft's left wing contacted the ground and the left horizontal stabilizer impacted a runway marker. The pilot was then able to complete the go-around, whereupon he flew a normal traffic pattern and retuned for a subsequent full-stop landing. He discovered the damage to the airframe after taxiing to his hanger and shutting the aircraft down. There was no evidence of any anomaly in the flight control or wheel brake systems.
Probable cause
The pilot's inadequate compensation for the changing wind conditions at the time of the landing. Factors include gusty, variable, crosswinds, and a runway marker near the edge of the runway the pilot was landing on.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04LA087
- Event ID
- 20040524X00648
- Case number
- SEA04LA087
- 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: 7de7b23a902d5e302bc543d1352cbcf43de0317a23b62932e07fea3f69dc2114; retrieved 2026-09-22T07:33:00.151Z.