SEA82DA091 · Cessna 170A
Cessna 170A · Accident: hard landing
From 8S8 · Oregon City, OR to 8S8 · Oregon City, OR
Event
- NTSB case
- SEA82DA091
- 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
- 0
- 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 170A
- 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
- N9560A
- Operator
- Larry J Voss · private individual
- Onboard fatalities
- Unknown
- Route
- From 8S8 · Oregon City, ORTo 8S8 · Oregon City, OR
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Level off, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD JUST COMPLETED HIS BFR. ON A RETURN FLIGHT TO HIS ORIGINAL DEPARTURE POINT, HE ENTERED THE TRAFFIC PATTERN FOR A LANDING IN CALM WIND CONDITIONS. HE STATED THAT WHEN HE WAS ABOUT 25 FT ABOVE THE RUNWAY ON FINAL APPROACH, HE ENTERED AN AREA OF DEAD AIR. HE REPORTED THAT HE TRIED TO "POWER OUT", BUT THE AIRCRAFT TOUCHED DOWN HARD. THE RIGHT GEAR COLLAPSED AND THE PILOT LOST CONTROL OF THE AIRCRAFT. THE PILOT REPORTED THAT THE PLANE SLID OFF THE LEFT SIDE OF THE RUNWAY AND BROADSIDED A LARGE PINE TREE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA82DA091
- Event ID
- 20020917X04099
- Case number
- SEA82DA091
- 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: dbbaefa6d3a12836f466b2db48cbe25317056ee09a5d1c8d6f360a2168fddbaf; retrieved 2026-09-24T02:55:59.829Z.