# Accident 19981004028249A: Amtr MINI500, Moorepark, CA, October 4, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 4, 1998, 15:15 local time
- Place: Moorepark, CA
- Damage: Destroyed
- Phase of flight: Low Level Operations
- Operating rules: General operating rules (Part 91)
- Location: 34.1897° N, 119.1707° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.1897&lon=-119.1707&mi=10
- Aircraft: N418MB, a cancelled registration (https://openairdocs.org/deregistered/N418MB-2000-05-01) (OpenAirDocs)
- Registry model: Burson William M MINI 500 (registry code 05604NG, https://openairdocs.org/model/burson-william-m-mini-500) (OpenAirDocs)
- Reported make and model: AMTR MINI500
- Reported engine: ROTAX ROTAX582
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 100 total
- NTSB investigation: [NTSB LAX99LA004](https://openairdocs.org/ntsb/LAX99LA004) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19981004028249A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.19) ON OCTOBER 4, 1998, AT AN UNKNOWN TIME, A BURSON MINI 500, N418MB, CRASHED IN HILLY TERRAIN NEAR MOORPARK CALIFORNIA. THE AIRCRAFT WAS DESTROYED, AND THE PRIVATE PILOT, SOLE OCCUPANT, SUFFERED FATAL INJURIES. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE AFTERNOON OF THE FLIGHT AND NO FLIGHT PLAN WAS FILED, NOR WERE ANY ATC SERVICES PROVIDED. THE PILOT'S DAUGHTER REPORTED THAT SHE ACCOMPANIED THE PILOT TO THE TAKEOFF/LANDING SITE AND HELPED REINSTALL THE MAIN ROTOR BLADES, WHICH HAD BEEN REMOVED TO TRAILER THE HELICOPTER. SHE STATED THAT HER FATHER REPORTED THAT HE WOULD FLY OVER THE PARK WHERE SHE WAS PLAYING BALL, AND WOULD SUBSEQUENTLY FLY OVER THE FAMILY RESIDENCE, IN APPROXIMATELY 45 MINUTES. SHE LEFT THE SITE AT 1417. THE DAUGHTER FURTHER RECALLED THAT THE PILOT REPORTED THAT HE WOULD BE FLYING FOR 1 1/2 TO 2 HOURS. SHE NEVER SAW OR HEARD HIM FLY OVER THE PARK, AND HE WAS NOT SEEN OVER THE FAMILY HOUSE. THE PILOT'S WIFE REPORTED THE PILOT AS MISSING AND AN ALNOT WAS ISSUED AT 2040. THE VENTURA COUNTY SHERIFF LOCATED THE WRECKAGE AT 0300 ON OCTOBER 5, 1998.                                                                                                               (4.)THE HELICOPTER DID NOT RETURN FROM AN AFTERNOON LOCAL AREA FLIGHT AND THE WRECKAGE WAS LOCATED EARLY THE FOLLOWING MORNING. BOTH MAIN ROTOR BLADES, THE TAIL ROTOR ASSEMBLY, THE TAIL BOOM, AND A SECTION OF THE TAIL ROTOR DRIVE SHAFT WERE FOUND IN A DEBRIS FIELD APPROXIMATELY 1/8 MILE FROM THE FUSELAGE WRECKAGE.  BOTH MAIN ROTOR BLADES SEPARATED FROM THE HUB OUTBOARD OF THE ROOT DOUBLER AND EXHIBITED LEADING EDGE DAMAGE NEAR THE TIP AND DOWNWARD BENDING. ADDITIONALLY, THE 'A' BLADE WAS BENT SMOOTHLY AFT APPROXIMATELY 30 DEGREES OVER ITS SPAN.  THE TAIL BOOM WAS SEPARATED FROM THE FUSELAGE APPROXIMATELY 2 FEET FORWARD OF THE TAIL ROTOR GEARBOX.  THE SEPARATION EXHIBITED A DIAGONAL SLICING APPEARANCE FROM UPPER FORWARD TO LOWER AFT ON THE BOOM.  THE TAIL ROTOR DRIVE SHAFT WAS SEPARATED AT THE SAME FUSELAGE STATION AS THE TAIL BOOM, AND THE SHAFT HAD A DENTED APPEARANCE WHICH RESEMBLED THE LEADING EDGE RADIUS OF THE MAIN ROTOR BLADE.  THE MAIN ROTOR MAST EXHIBITED A MAST-BUMPING DENT ON ONE SIDE OF THE MAST AT THE HUB ATTACHMENT BUT NO SIMILAR DENT ON THE OPPOSITE SIDE.  EXAMINATION OF THE AIRCRAFT DID NOT REVEAL ANY MECHANICAL MALFUNCTION OF THE ENGINE OR FLIGHT CONTROL SYSTEM.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX99LA004](https://openairdocs.org/ntsb/LAX99LA004), Oct 4, 1998: Burson Revolution Mini 500 (N418MB), Moorpark, CA, destroyed, 1 fatal. Probable cause: The improper use of the cyclic flight control by the pilot, which resulted in low g flight load condition, which resulted in rotor disk divergence (mast bumping), and the main rotor blade striking…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.