San Juan Airlines Beech B-99A accident
Beech B-99A · Accident: in flight collision with object while maneuvering
From Bellingham International Airport (BLI) to Orcas Island Airport (ORS)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- SEA89FA006
- 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
- Charter & commuter
- 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 B-99A
- Aircraft type
- Beechcraft B-99
- 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
- N803BA
- Operator
- San Juan Airlines
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Bellingham International Airport (BLI), Bellingham, WATo Orcas Island Airport (ORS), ORCAS ISLAND, 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 135: Air Taxi & Commuter
- 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
- Maneuvering · turn to reverse direction
- 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
- Substantial
Cause areas
- Pilot in command › Flight into known adverse weather, attempted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE CREW ELECTED TO DEPART THE AIRPORT UNDER A SPECIAL VFR CLEARANCE. WX AT THE DEPARTURE AIRPORT WAS 700 FT OVC WITH VISIBILITY 1 AND 1/4 MILES. THE DESTINATION AIRPORT WAS WITHIN 25 NAUTICAL MILES OF THE DEPARTURE AIRPORT AND WAS REPORTING A BKN CEILING OF 6 TO 800 FT AND 3 MILES VISIBILITY. THE CREW WAS IN THE PROCESS OF OBTAINING AN IFR CLEARANCE WHEN THE PILOT ON THE CONTROLS OBSERVED TREES IN THE FLIGHT PATH. THE AIRCRAFT COLLIDED WITH TREES DURING A CLIMBING RIGHT TURN. THE CREW SUBSEQUENTLY OBTAINED AN IFR CLEARANCE AND RETURNED TO THE DEPARTURE AIRPORT UNEVENTFULLY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA89FA006
- Event ID
- 20001213X27166
- Case number
- SEA89FA006
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 3e4f7ee3128e366c2f4f2c5de477a062bd3edc18632e591b9e7bbe83a121c5e8; retrieved 2026-09-18T19:18:01.963Z.
- The NTSB's operator name is blank for N803BA; the operator shown is the name the NTSB records it doing business as.