SEA05CA035 · Cessna 310J
Cessna 310J · Accident: hard landing
From Auburn Municipal Airport (S50) to Davenport Municipal Airport (68S)
Event
- NTSB case
- SEA05CA035
- 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 310J
- Aircraft type
- Cessna 310
- 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
- N310RA
- Operator
- Richard W. Alldredge · private individual
- Onboard fatalities
- Unknown
- Route
- From Auburn Municipal Airport (S50), Auburn, WATo Davenport Municipal Airport (68S), Davenport, WA
- 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
- Hard landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Airspeed, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight encountered light mixed icing during descent. The airplane was in icing conditions for about 15 minutes. The pilot used the de-icing boots during the icing encounter and cycled the boots for the last time on downwind leg for landing. During the landing flare, he reduced power over the threshold about 15 feet agl, and the airplane stalled at a higher than normal airspeed resulting in a hard landing. The pilot stated that the accident could have been prevented by keeping power and airspeed up until touchdown when landing an airplane which has encountered icing conditions and retained some airframe ice.
Probable cause
The pilot's failure to maintain adequate airspeed during landing with airframe ice, which resulted in an inadvertent stall and hard landing. Factors were the icing conditions and the airframe ice.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05CA035
- Event ID
- 20050127X00111
- Case number
- SEA05CA035
- 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. 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: b11344844fc4675d37af1a478908d927d9f17d705dd8c658399938e441070328; retrieved 2026-09-22T06:23:09.096Z.