# Accident 19960617014159A: Amtr GOSHAWK, Livermore, CA, June 17, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 17, 1996, 16:35 local time
- Place: Livermore, CA
- Damage: Destroyed
- Phase of flight: Descent
- Operating rules: General operating rules (Part 91)
- Location: 37.6795° N, 121.7505° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.6795&lon=-121.7505&mi=10
- Aircraft: N345RM, a cancelled registration (https://openairdocs.org/deregistered/N345RM-2013-07-08) (OpenAirDocs)
- Registry model: Moore E R GOSHAWK 350 (registry code 056128Z, https://openairdocs.org/model/moore-e-r-goshawk-350) (OpenAirDocs)
- Registry engine: Lycoming AEIO-540 series (registry code 41568, https://openairdocs.org/engine/lycoming-aeio-540-series) (OpenAirDocs)
- Reported make and model: AMTR GOSHAWK
- Reported engine: LYC IO540P1A5
- Fatal injuries: 0
- Pilot flight hours: 3,000 total, 10 in this make and model, 50 in the last 90 days
- NTSB investigation: [NTSB LAX96LA232](https://openairdocs.org/ntsb/LAX96LA232) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960617014159A

## Narrative

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

LOST RUDDER CONTROL. SNAPROLLED INTO SPIN. BAILED OUT. LANDED MINOR INJURY. RUDDER CABLE BROKE DUE OVER STRESS.

## 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 LAX96LA232](https://openairdocs.org/ntsb/LAX96LA232), Jun 17, 1996: Moore Goshawk 350 (N345RM), Livermore, CA, destroyed. Probable cause: an overstress failure of the left rudder cable.

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.