FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX90LA321 · Brantly Helicopter B-2B

12 Sept 1990 · Novato, CA, United States

Brantly Helicopter B-2B · Accident: in flight collision with terrain/water en route

Report a problem

Event

NTSB case
LAX90LA321
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
General aviation
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

Brantly Helicopter B-2B

Aircraft type
Brantly B-2
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
N2159W
Operator
Rosenberg, Kenneth P. · private individual
Onboard fatalities
Unknown
Route
From not recordedTo 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 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 · descent
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
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 › Altitude, misjudged
  • Pilot in command › Autorotation, improper
  • Pilot in command › Proper descent rate, excessive

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

NTSB narrative

WHILE ON AN ADDED RATING FLIGHT TEST THE FAA DESIGNATED EXAMINER CALLED FOR A SIMULATED ENG FAILURE. THE PRIVATE PILOT APPLICANT IMMEDIATELY LOWERED THE COLLECTIVE AND BEGAN A 180 DEGREE TURN INTO THE WIND. WHEN THE HELICOPTER WAS ABOUT 160 DEGREES INTO THE TURN AND WAS ABOUT 50 FEET ABOVE THE GROUND THE PILOT BEGAN THE POWER RECOVERY BUT DUE TO THE HIGH SINK RATE THE SKIDS STRUCK THE SOFT DIRT OF A FRESHLY PLOWED FIELD CAUSING THE HELICOPTER TO ROLL TO THE RIGHT AND THE MAIN ROTOR BLADES TO STRIKE THE GROUND.

Probable cause

THE PILOT'S IMPROPER EXECUTION OF THE AUTOROTATION. CONTRIBUTING TO THIS ACCIDENT WAS THE EXCESSIVE SINK RATE AND MISJUDGING OF THE ALTITUDE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX90LA321
Event ID
20001212X24305
Case number
LAX90LA321
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: c4369daa29dd9265d7afea9e77bc6d7e56f83b1846075312bf4fde8191197bbb; retrieved 2026-09-23T05:19:24.283Z.