FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hilo Bay Air Bell 206B accident

15 Apr 1987 · Laupahoehoe, HI, United States

Bell 206B · Accident: loss of control in flight while maneuvering

From Hilo International Airport (ITO) to an unrecorded destination

Report a problem

Event

NTSB case
LAX87LA178
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
1 · 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
Visual 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
N370AH
Operator
Hilo Bay Air
Onboard fatalities
Unknown
Route
From Hilo International Airport (ITO), Hilo, HITo 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 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 · hover
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
Loss of control in flight
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, inadequate
  • Pilot in command › Proper altitude, not maintained

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

NTSB narrative

THE PILOT OF THE BELL 206B AND HIS THREE PASSENGERS ARRIVED OVER A BEACHED BARGE THAT THEY WERE TO LAND ON. THE PILOT HOVERED OVER THE BARGE IN A LEFT QUARTERING TAILWIND OF ABOUT 10 KNOTS AND OVER A MODERATE SEA WITH WAVES BREAKING AGAINST THE BARGE. THE TWO REAR SEAT PASSENGERS WERE DEPLANED WITHOUT INCIDENT THROUGH THE RIGHT REAR DOOR AS THE HELICOPTER HOVERED WITH THE RIGHT SKID RESTING ON A STRUCTURE ON THE BARGE. AFTERWARD, ONE OF THE DEPLANED PASSENGERS OBSERVED A WAVE BREAK AGAINST THE BARGE AND WATER SPRAYING UPWARD ONTO THE HELICOPTER. BOTH DEPLANED PASSENGERS OBSERVED THE HELICOPTER ROLL LEFT AND IMPACT THE WATER. THERE WAS NO EVIDENCE THAT FLOTATION GEAR WAS AVAILABLE TO THE CREW OR PASSENGERS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX87LA178
Event ID
20001213X30716
Case number
LAX87LA178
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: 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: 9c5a2f7a40e7569e44e233a71e1460613d2f2a517bd57dc2355e99f7f0d2207f; retrieved 2026-09-18T14:14:37.967Z.