# Accident 20150104001019A: Beech 35-A33, Angwin, CA, January 4, 2015

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 4, 2015, 12:40 local time
- Place: Angwin, CA
- Airport: Angwin
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.5783° N, 122.4356° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.5783&lon=-122.4356&mi=10
- Aircraft: N907Q, a cancelled registration (https://openairdocs.org/deregistered/N907Q-2018-04-24) (OpenAirDocs)
- Registry model: Beech 35-A33 (registry code 1151404, https://openairdocs.org/model/beech-35-a33) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: BEECH 35-A33
- Reported engine: CONT MOTOR I0-470 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 15,181 total, 3,200 in this make and model, 19 in the last 90 days
- NTSB investigation: [NTSB WPR15CA076](https://openairdocs.org/ntsb/WPR15CA076) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20150104001019A

## Narrative

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

PILOT OVERSHOT BASE TO FINAL TURN AND LOST CONTROL OF AIRCRAFT TRYING TO CORRECT.  AIRCRAFT DEPARTED RUNWAY AND CRASHED THROUGH AIRPORT PARAMETER FENCE.

## 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 WPR15CA076](https://openairdocs.org/ntsb/WPR15CA076), Jan 4, 2015: Beech 35 A33 (N907Q), Angwin, CA, substantial damage. Probable cause: The pilot's improper approach to landing and his failure to perform a go-around, which resulted in a runway overshoot, and collision with a fence.

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.