SEA86LA186 · Cessna 210
Cessna 210 · Accident: in flight collision with object during initial climb
From Yakima, WA to an unrecorded destination
Event
- NTSB case
- SEA86LA186
- 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 210
- Aircraft type
- Cessna 210
- 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
- N1782X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yakima, WATo not recorded
- 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
- Initial climb
- 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
- In flight collision with object
- 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
- Utility pole
- 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 › Emergency procedure, initiated
- Pilot in command › Lift-off, misjudged
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE STRUCK A POST ON TAKE-OFF AND BROKE OFF THE MAIN LANDING GEAR WHEEL. THE PILOT PROCEEDED TO HILLSBORO, OREGON WHERE AN EMERGENCY LANDING WAS MADE ON A PAVED RUNWAY WITH THE LANDING GEAR STILL EXTENDED. THE STUB CAUGHT IN THE RUNWAY CAUSING THE AIRCRAFT TO VEER ONTO THE GRASS ON THE WING. THE PILOT REPORTED THAT HE HAD TRIMMED THE AIRCRAFT FOR A SHORT FIELD TAKE OFF AND CHECKED THE WINDSOCK BEFORE STARTING HIS TAKE OFF ROLL. LIFT OFF WAS ABOUT 1200 FEET DOWN THE 2400 FOOT GRASS RUNWAY. DURING INITIAL CLIMB THE AIRCRAFT SEEMED TO SETTLE A BIT BUT INDICATED AIRSPEED WAS MOVING FROM 70 TO 75 MPH. BEYOND THE DEPARTURE END OF THE RUNWAY WAS A 5 FOOT HIGH DIKE AND BEYOND THE DIKE A 4 FOOT POST. DURING CLIMB OUT A 'LOUD BANG' WAS HEARD. A VISUAL CHECK DISCLOSED THE RIGHT MAIN LANDING GEAR WHEEL WAS MISSING. THE LANDING GEAR WAS LEFT IN THE DOWN POSITION AND THE AIRCRAFT WAS FLOWN TO HILLSBORO, OREGON WHERE A LANDING WAS MADE. THE RIGHT WHEEL WAS FOUND AT THE DEPARTURE AIRPORT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA86LA186
- Event ID
- 20001213X34347
- Case number
- SEA86LA186
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1986-08-01.
- API snapshot SHA-256: b13398a77631e4a988ce675e3b574f33dd451cff4aa567eb51c55f8455a1f87a; retrieved 2026-09-23T14:12:15.703Z.