# Accident 20070319005059A: Mooney M20K, Marysville, CA, March 19, 2007

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 19, 2007, 14:40 local time
- Place: Marysville, CA
- Airport: Yuba County Airport
- Damage: Destroyed
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 39.1075° N, 121.5717° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.1075&lon=-121.5717&mi=10
- Aircraft: N231KZ, a cancelled registration (https://openairdocs.org/deregistered/N231KZ-2014-09-16) (OpenAirDocs)
- Registry model: Mooney M20K (registry code 5870220, https://openairdocs.org/model/mooney-m20k) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20K
- Fatal injuries: 0
- NTSB investigation: [NTSB SEA07LA079](https://openairdocs.org/ntsb/SEA07LA079) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070319005059A

## Narrative

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

(-23) AIRCRAFT MADE CONTACT WITH APPROACH LIGHTS AT THE MYV AIRPORT, TAKING OUT THREE SETS OF LIGHTS. MADE GROUND CONTACT ABOUT 700 FEET SHORT OF RUNWAY 14 AT MYV, BOUNCED ACROSS A DRAINAGE DITCH BEFORE STRIKING WATER CANAL BERM AND DRIVING LANDING GEAR THROUGH THE WINGS.

## 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 SEA07LA079](https://openairdocs.org/ntsb/SEA07LA079), Mar 19, 2007: Mooney M20K (N231KZ), Marysville, CA, substantial damage. Probable cause: The failure of the pilot to maintain a proper glidepath while on final approach and his failure to maintain clearance, which resulted in an undershoot and subsequent collision with the runway's…

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.