# Accident 20151124019539A: Cessna 305A, Sulphur, LA, November 24, 2015

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 24, 2015, 02:30 local time
- Place: Sulphur, LA
- Airport: Sou
- Damage: Destroyed
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 30.1314° N, 93.3761° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=30.1314&lon=-93.3761&mi=10
- Aircraft: N5312G, a cancelled registration (https://openairdocs.org/deregistered/N5312G-2018-05-10) (OpenAirDocs)
- Registry model: Cessna 305A (registry code 2074002, https://openairdocs.org/model/cessna-305a) (OpenAirDocs)
- Registry engine: Continental O-470 series (registry code 17026, https://openairdocs.org/engine/continental-o-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 305A
- Reported engine: CONT MOTOR O-470 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 2
- NTSB investigation: [NTSB CEN16LA064](https://openairdocs.org/ntsb/CEN16LA064) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20151124019539A

## Narrative

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

AIRCRAFT DOING TOUCH & GOES ON RUNWAY 15. AFTER LOW TURN TO UPWIND, ABOUT 100 FEET AGL AND STILL OVER AIRPORT PROPERTY, ENGINE QUIT. PILOT PLANNED TO LAND ON TAXIWAY BUT IMPACTED GROUND AND SLID THROUGH CHAIN LINK FENCE.

PILOT ALSO A&P WHO HAD INSTALLED AN ENGINE MONITOR ON THE AIRPLANE THE DAY BEFORE.

## 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 CEN16LA064](https://openairdocs.org/ntsb/CEN16LA064), Nov 24, 2015: Cessna 305A (N5312G), Sulphur, LA, substantial damage. Probable cause: The loss of engine power due to water and contaminants in the carburetor, which resulted in a forced landing to a wet field.

## Other reports on N5312G (4)

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

- [Accident 20100507034039A](https://openairdocs.org/incident/20100507034039A), May 7, 2010: Cessna 305A (N5312G), Fort Pierce, FL, Substantial damage. On may 07, 2010, at 1900 eastern daylight time, a Cessna CE-305 aircraft, N5312G, experienced the loss of directional control, immediately after landing, at…
- [Accident 19860703029839A](https://openairdocs.org/incident/19860703029839A), Jul 3, 1986: Cessna 305A (N5312G), Figure Eight La, AK, Substantial damage. Crash occurred after power failure when emergency landing was attempted on a lake.
- [Accident 19840927056869A](https://openairdocs.org/incident/19840927056869A), Sep 27, 1984: Cessna 305A (N5312G), Anchorage, AK, Substantial damage. Ground looped on rollout. 4th incident with control problem. Tailwheel spring leaf oversized, not firmly fastened.
- [Accident 19730123002839A](https://openairdocs.org/incident/19730123002839A), Jan 23, 1973: Cessna 305A (N5312G), Anchorage, AK, Substantial damage. Plt planned to lnd within the 700FT threshold extension. Lndd 4FT short. Gr collapsed.

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.