FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA90FA021 · Beech B35

22 Nov 1989 · Bremerton, WA, United States

Beech B35 · Accident: in flight collision with object on approach

From Burley Municipal Airport (BYI) to Bremerton National Airport (PWT)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
SEA90FA021
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
2 · 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

Beech B35

Aircraft type
Beechcraft 35
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
N8918A
Operator
Bob Brooks
Onboard fatalities
Unknown
Route
From Burley Municipal Airport (BYI), Burley, IDTo Bremerton National Airport (PWT), Bremerton, 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
Approach · IFR initial approach
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
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 › Decision height, not used
  • Pilot in command › IFR procedure, improper
  • Pilot in command › Missed approach, not performed
  • Pilot in command › Proper alignment, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

DURING ARRIVAL, THE PLT WAS VECTORED FOR AN ILS RWY 19 APCH. AFTER BEING CLEARED FOR THE APCH, HE WAS AUTHORIZED TO CHANGE TO THE ADVISORY FREQ & WAS INSTRUCTED TO CONTACT SEATTLE APCH CTL TO CANCEL THE FLT PLAN, WHEN ON THE GND. THERE WAS NO FURTHER COMMUNICATION WITH THE ACFT. SUBSEQUENTLY, IT HIT TREES & CRASHED ABOUT 1 MI SOUTHEAST OF THE ARPT. RADAR DATA SHOWED THAT AS THE ACFT WAS APCHG THE ARPT FROM THE NORTH, ITS TRACK DEVIATED TO THE LEFT OF COURSE. THE PLT DID NOT REALIGN THE ACFT WITH THE ILS COURSE LINE & THE ACFT PASSED WELL TO THE LEFT OF THE RWY THRESHOLD. IMPACT WITH TREES WAS ALONG A COURSE OF 174 DEG. ELEVATION OF THE CRASH SITE WAS 482 FT. DECISION HEIGHT FOR THE PRECISION ILS APCH WAS 688 FT; MIN DESCENT ALT (MDA) FOR A CIRCLING APCH WAS 1220 FT. AT 1954 PST, THE WX AT BREMERTON WAS IN PART: 300 FT OVC, 3 MI VIS. AT 2034 PST (12 MIN AFTER THE ACDNT), THE WX HAD DETERIORATED TO PARTIAL OBSCN, 100 FT OVC, 2 MI VIS.

Probable cause

THE PILOT'S IMPROPER IFR PROCEDURE, HIS FAILURE TO MAINTAIN PROPER ALIGNMENT ON THE ILS APPROACH, AND HIS FAILURE TO INITIATE A MISSED APPROACHED AFTER REACHING THE LATERAL LIMITS OF THE ILS SYSTEM OR DECISION HEIGHT. DARKNESS AND DETERIORATING WEATHER WERE RELATED FACTORS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA90FA021
Event ID
20001213X29877
Case number
SEA90FA021
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 1989-11-23.
  • API snapshot SHA-256: a6711035e65aea45d8ebb7f5dabac9a4409fdeb8235c0540c4a272576f057b18; retrieved 2026-09-21T03:04:42.222Z.