# Accident 20130119000879A: Cessna 172F, Marysville, CA, January 19, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 19, 2013, 16:00 local time
- Place: Marysville, CA
- Damage: Substantial damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 39.0978° N, 121.5697° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.0978&lon=-121.5697&mi=10
- Aircraft: N5208F, registered now (https://openairdocs.org/aircraft/N5208F) (OpenAirDocs)
- Registry model: Cessna 172F (registry code 2072414, https://openairdocs.org/model/cessna-172f) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172F
- Reported engine: CONT MOTOR 0-300 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 1
- NTSB investigation: [NTSB WPR13LA098](https://openairdocs.org/ntsb/WPR13LA098) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130119000879A

## Narrative

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

DURING CLIMB OUT FROM MYV THE ENGINE LOST POWER. THE CFI MADE AN EMERGENCY LANDING IN A FIELD OFF THE AIRPORT. UPON TOUCH DOWN THE AIRCRAFT FLIPPED OVER.

## 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 WPR13LA098](https://openairdocs.org/ntsb/WPR13LA098), Jan 20, 2013: Cessna 172F (N5208F), Marysville, CA, substantial damage. Probable cause: A total loss of engine power during initial climb due to fuel starvation, which resulted from maintenance personnel’s improper installation of the fuel selector handle. Contributing to the accident…

## Other reports on N5208F (1)

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

- [Incident 19960211003599I](https://openairdocs.org/incident/19960211003599I), Feb 11, 1996: Cessna 172F (N5208F), Sacramento, CA. Narrative: not a pilot deviation. Preliminary report-- may be changed on receipt of additional data. The pilot was practicing takeoffs and landings when a…

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.