ERA23LA356 · Piper PA-12
Piper PA-12 · Accident: fuel exhaustion en route
From Grand Strand Airport (CRE) to an unrecorded destination
Event
- NTSB case
- ERA23LA356
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-12
- Aircraft type
- Piper PA-12
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3036M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Strand Airport (CRE), Myrtle Beach, SCTo not recorded
- Aircraft age
- About 76 years (built 1947)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Fuel exhaustion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said he refueled the airplane the day before the accident and checked the fuel level during his preflight inspection the following morning. As he was conducting his second banner-tow of the day over the coastline, about 2 hours 30 minutes into the flight the engine suddenly stopped producing power. The pilot made a forced landing in the ocean just offshore of the beach, which resulted in substantial damage to the fuselage. Postaccident examination of the airplane revealed that while the crankshaft would not rotate more than 180 degrees, this was likely due to corrosion that was the result of exposure to saltwater during the forced landing. Internal inspection of the engine via a borescope revealed no obvious mechanical deficiencies or malfunctions that would have precluded the engine from operating at the time of the accident. Although the pilot reported departing with 33 usable gallons of fuel, the postaccident examination found no evidence of fuel leaks and both fuel tanks were intact and empty of fuel. As such, the engine most likely lost power due to fuel exhaustion.
Probable cause
The pilot’s inadequate fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA356
- Event ID
- 20230831192976
- Case number
- ERA23LA356
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e7c67087b1e1db1cb8b9094d22442fc789f28c7f3f851d75e950d2400f8b3a5d; retrieved 2026-09-16T18:04:15.017Z.