# Accident 20000907039699A: Hughes 269C, Rancho Murieta, CA, September 7, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 7, 2000, 10:20 local time
- Place: Rancho Murieta, CA
- Damage: No damage
- Location: 38.5093° N, 121.1198° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.5093&lon=-121.1198&mi=10
- Aircraft: N50638, a cancelled registration (https://openairdocs.org/deregistered/N50638-2001-03-22) (OpenAirDocs)
- Registry model: Hughes 269C (registry code 4470504, https://openairdocs.org/model/hughes-269c) (OpenAirDocs)
- Reported make and model: HUGHES 269C
- NTSB investigation: [NTSB LAX00LA328](https://openairdocs.org/ntsb/LAX00LA328) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000907039699A

## Narrative

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

(-23)HELICOPTER STRUCK HIGH TENSION POWER LINES, SUBSEQUENTLY CRASHED IN A FIELD AND BURNED. INJURIES WERE FATAL TO THE PILOT.

## 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 LAX00LA328](https://openairdocs.org/ntsb/LAX00LA328), Sep 7, 2000: Hughes 269C (N50638), Rancho Murieta, CA, destroyed, 1 fatal. Probable cause: The pilot's inadequate visual lookout during cruise, which subsequently led to a wire strike.

## Other reports on N50638 (1)

Matched to the same aircraft by N-number and date.

- [Accident 19831117057999A](https://openairdocs.org/incident/19831117057999A), Nov 17, 1983: Hughes 269C (N50638), Freer, TX, Substantial damage. Crash occurred during emergency landing. Pilot claims power loss but investigation revealed no discrepancy.

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.