Helinet Bell 206B accident
Bell 206B · Accident: in flight collision with terrain/water en route
From 056 · Novato, CA to San Francisco International Airport (SFO)
Event
- NTSB case
- LAX93FA093
- 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
- 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
Bell 206B
- Aircraft type
- Bell 206
- Category
- Helicopter
- 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
- N3202A
- Operator
- Helinet
- Onboard fatalities
- Unknown
- Route
- From 056 · Novato, CATo San Francisco International Airport (SFO), San Francisco, CA
- 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
- 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 terrain/water
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Flight into known adverse weather, continued
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A NIGHT CFR PART 135 CARGO FLIGHT, THE CERTIFICATED COMMERCIAL HELICOPTER PILOT AND A CREW MEMBER RECEIVED COMPANY INSTRUCTIONS TO DIVERT FROM THE INTENDED ROUTE OF FLIGHT TO ANOTHER DESTINATION. THE WEATHER CONDITIONS IN THE AREA INCLUDED AREAS OF LOW CEILINGS AND REDUCED VISIBILITY DUE TO RAIN. THE PILOT ATTEMPTED TO CROSS A COASTAL BAY IN A WESTERLY DIRECTION IN AN AREA OF LIMITED VISUAL CUES AND DECIDED TO REVERSE HIS COURSE. THE PILOT CONTINUED SOUTH AND AGAIN ATTEMPTED TO CROSS THE BAY NEAR A BRIDGE THAT SPANNED THE BAY. A WITNESS OBSERVED THE HELICOPTER DESCENDING BELOW THE LEVEL OF THE BRIDGE WHERE VISIBILITY WAS ABOUT 1/4 MILE IN RAIN. THE HELICOPTER STRUCK THE WATER ABOUT 1/2 MILE FROM THE SHORE AND ABOUT 400 YARDS SOUTH OF THE BRIDGE AND WAS DESTROYED. THE PILOT HAD OBTAINED A WEATHER BRIEFING THAT INCLUDED AREAS OF MARGINAL VFR DUE TO RAIN AND FOG, THUNDERSTORMS, AND SEVERAL AIRMETS AND SIGMETS.
Probable cause
THE PILOT'S CONTINUED FLIGHT INTO KNOWN ADVERSE WEATHER CONDITIONS AND CONTINUED VFR FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS. CONTRIBUTING TO THE ACCIDENT WERE DARK NIGHT LIGHT CONDITIONS AND RAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93FA093
- Event ID
- 20001211X11706
- Case number
- LAX93FA093
- 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 1993-01-13.
- API snapshot SHA-256: 9d90ec521001264daf5f1cd4c23d3fa67a5a63173b033f6de6ecfdf69fe38c8b; retrieved 2026-09-18T13:54:10.456Z.