SEA86FA033 · Mooney M20K
Sunwest Aviation Mooney M20K · Accident: in flight collision with object en route
From Portland Hillsboro Airport (HIO) to King County International Airport - Boeing Field (BFI)
Event
- NTSB case
- SEA86FA033
- 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
- 4 · 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
- Instrument Meteorological Cond
Mooney M20K
- Aircraft type
- Mooney M20
- 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
- N1152T
- Operator
- Sunwest Aviation
- Onboard fatalities
- Unknown
- Route
- From Portland Hillsboro Airport (HIO), Hillsboro, ORTo King County International Airport - Boeing Field (BFI), SEATLE, 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
- En route · cruise
- 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
- Wire, transmission
- 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 › In-flight planning/decision, improper
- Pilot in command › Preflight briefing service, disregarded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE WEATHER BRIEFER INFORMED THE PILOT THAT VFR WAS NOT RECOMMENDED DUE TO CURRENT/FORECAST CONDTIONS. THE NON INSTRUMENT RATED PILOT THEN FILED A VFR FLIGHT PLAN RESPONDING THAT HE WAS IFR RATED AND WOULD FILE INFLIGHT IF NECESSARY. WITNESSES REPORTED OBSERVING THE AIRCRAFT CRUISING NORTHBOUND OVER I-5 AT A MODERATE SPEED AND LOW ALTITUDE BENEATH THE CLOUDS. WEATHER CONDITIONS IN THE VICINITY OF THE ACCIDENT SITE WERE DESCRIBED AS 300 FOOT CEILING AND 1 MILE VISIBILITY. DARK NIGHT CONDITIONS EXISTED WHEN THE AIRCRAFT STRUCK POWER LINE 75 FEET ABOVE THE I-5 MEDIAN AND 6 NAUTICAL MILES SOUTH OF THE DESTINATION AIRPORT. IN SPITE OF DETERIORATING WEATHER CONDITIONS THE PILOT MADE NO ATTEMPT TO DIVERT ALONG HIS ROUTE OF FLIGHT TO A MORE FAVORABLE DESTINATION. AN ENTRY REFERRING TO 'SCUD FLYING' WAS NOTED IN THE PILOT'S LOGBOOK.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA86FA033
- Event ID
- 20001214X38493
- Case number
- SEA86FA033
- 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 1985-12-30.
- API snapshot SHA-256: deff7aa4a4a5c09bf98938832d40cba5e9c7703995e8d80245e2e0b6c26cd693; retrieved 2026-09-21T04:43:10.519Z.