NYC97LA124 · Piper PA-28-140
Piper PA-28-140 · Accident: partial loss of engine power (mechanical failure) during initial climb
From N81 to Kentmorr Airpark (3W3)
Event
- NTSB case
- NYC97LA124
- 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-28-140
- Aircraft type
- Piper PA-28
- 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
- N43464
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From N81To Kentmorr Airpark (3W3), KENT ISLAND, MD
- 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
- Initial climb
- First occurrenceThe 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
- Partial loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Exhaust system, muffler › Blocked(partial)
Approximate · Estimated position: the centre of Hammonton, NJ, the place the record names. Not the accident site.
NTSB narrative
The pilot stated that he checked the fuel quantity and the magnetos prior to takeoff, and the engine 'ran perfect.' After takeoff, about 180 feet above the ground, the engine lost power. He attempted to restart the engine, but was unsuccessful. He then attempted to return to the airport, but the airplane collided with trees. A witness stated the airplane entered a 30 degree bank after the pilot announced engine trouble over the radio. Examination of the engine revealed the inside of the muffler was deteriorated and baffles were restricting the exhaust flow. An FAA Inspector stated the airport was surrounded by forced landing areas, to include an open field at the departure end of the runway.
Probable cause
A loss of engine power due to a partially blocked engine muffler.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA124
- Event ID
- 20001208X08228
- Case number
- NYC97LA124
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 9745c2f1a723d98d957478e053f78cf3f65b81beda098d01f653543bdb43124e; retrieved 2026-09-21T12:01:22.778Z.