NYC08LA142 · Piper PA32 260
Cooper Electrical Controls Piper PA32 260 · Accident: loss of engine power (total) during takeoff
From New Albany Union County Airport (M72) to Roscoe Turner Airport (CRX)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC08LA142
- 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
- Unknown
- 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 PA32 260
- Aircraft type
- Piper PA32
- 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
- N3304W
- Operator
- Cooper Electrical Controls
- Onboard fatalities
- Unknown
- Route
- From New Albany Union County Airport (M72), New Albany, MSTo Roscoe Turner Airport (CRX), Corinth, MS
- Aircraft age
- Not recorded
- 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
- Takeoff
- 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
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial Narrative disagrees
Cause areas
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After a normal preflight inspection and engine run-up, the pilot departed from a 3,900-foot-long, asphalt runway. The airplane lifted off normally and had climbed to an altitude of about 75 feet above the runway, when it began to sputter and then lost power. The airplane touched down hard on the remaining runway, before going off the end, and coming to a stop about 50 feet beyond the runway. A post crash fire consumed a majority of the fuselage, and the right wing. Examination of the engine did not identify evidence of any mechanical malfunctions. The airplane had been flown for 1.3 hours since it was refueled to its maximum capacity of 84 gallons, 9 days prior to the accident. Fuel recovered from the airplane’s left wing was absent of contamination.
Probable cause
A loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08LA142
- Event ID
- 20080417X00511
- Case number
- NYC08LA142
- 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, coordinates. 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: 3755f9779ab0a9ecb605003f55957784fa24b75e14b57d071415b189fdec25e1; retrieved 2026-09-15T09:33:29.199Z.