# Accident 20120409007019A: Cessna 172S, Daytona Beach, FL, April 9, 2012

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 9, 2012, 13:25 local time
- Place: Daytona Beach, FL
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 29.2489° N, 81.1361° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=29.2489&lon=-81.1361&mi=10
- Aircraft: N375LP, a cancelled registration (https://openairdocs.org/deregistered/N375LP-2013-05-17) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- NTSB investigation: [NTSB ERA12LA274](https://openairdocs.org/ntsb/ERA12LA274) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120409007019A

## Narrative

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

APPOXIMITLY 10 MINUTES INTO FLIGHT PIC HEARD A BANG AND THE ENGINE STARTED MISSING. PIC ATTEMPTED TO RETURN TO DAB BUT ENGINE STOPPED PRODUCING POWER AND HAD TO LAND IN AN OPEN FIELD.

## 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 ERA12LA274](https://openairdocs.org/ntsb/ERA12LA274), Apr 9, 2012: Cessna 172S (N375LP), Daytona Beach, FL, substantial damage. Probable cause: A total loss of engine power due to a catastrophic engine failure, the origin of which could not be determined during postaccident examination.

## Other reports on N375LP (2)

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

- [Accident 20080420834739A](https://openairdocs.org/incident/20080420834739A), Apr 20, 2008: Cessna 172S (N375LP), Daytona Beach, FL, Substantial damage. (-23) Pilot departed to practice at nearby new smyrna Beach airport (evb). Upon returning to Daytona, the ATIS "z" reported runway 25 in use. On final approach…
- [Accident 20041217032989A](https://openairdocs.org/incident/20041217032989A), Dec 17, 2004: Cessna 172S (N375LP), Lakeland, FL, Substantial damage. (-23) N375LP on landing runway 9 at Lakeland airport, FL lost directional control, exited runway on left side, hit taxiway sign with substantial damage to the…

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.