FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX97LA257 · Fronsman ROTORWAY EXEC ROTORWAY E

18 Jul 1997 · Lakeport, CA, United States

Fronsman ROTORWAY EXEC ROTORWAY E · Accident: airframe, component or system failure while maneuvering

From 102 to an unrecorded destination

Report a problem

Event

NTSB case
LAX97LA257
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

Fronsman ROTORWAY EXEC ROTORWAY E

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
N6323F
Operator
Unknown
Onboard fatalities
Unknown
Route
From 102To 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
Maneuvering · hover in ground effect
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
Airframe, component or system failure
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

  • Engine compartment › Fire
  • Lubricating system › Undetermined

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

NTSB narrative

The pilot said he was practicing hover operations, when the oil pressure began to decrease. By the time he had landed at his parking ramp, the oil pressure was at zero. As he exited the helicopter, the pilot noticed smoke and flames coming from the right side of the engine compartment. He was unsuccessful in extinguishing the fire with a portable fire extinguisher, and the helicopter was destroyed in the subsequent ground fire. The pilot had completed a condition inspection of the experimental helicopter immediately before the flight.

Probable cause

an undetermined failure of the oil system (lines or filter), while hovering, which resulted in an engine compartment fire that erupted and subsequently destroyed the helicopter after it was landed.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX97LA257
Event ID
20001208X08441
Case number
LAX97LA257
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: 312a188e8a48aee0d635f5b578b4ee8cce07103b290e2fba9f61ddcbc697c28d; retrieved 2026-09-22T19:06:41.667Z.