# Accident 20120726016359A: Piper PA-12, Middle Township, NJ, July 26, 2012

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 26, 2012, 16:20 local time
- Place: Middle Township, NJ
- Damage: Substantial damage
- Phase of flight: Other, Specify
- Operating rules: General operating rules (Part 91)
- Operator: J3JJ
- Location: 39.0650° N, 74.9094° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.0650&lon=-74.9094&mi=10
- Aircraft: N4361M, registered now (https://openairdocs.org/aircraft/N4361M) (OpenAirDocs)
- Registry model: Piper PA-12 (registry code 7101202, https://openairdocs.org/model/piper-pa-12) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA-12
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 843 total, 184 in this make and model, 301 in the last 90 days
- NTSB investigation: [NTSB ERA12LA482](https://openairdocs.org/ntsb/ERA12LA482) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120726016359A

## Narrative

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

THE PILOT WAS FINISHING THE DAY OF BANNER TOWING, AND WAS PLANNING TO DROP THE BANNER, THEN ENTER THE TRAFFIC PATTERN TO RETURN FOR A LANDING. AFTER DROPPING THE BANNER, THE PILOT STARTED THE CLIMB BACK TO TRAFFIC PATTERN ALTITUDE. AS THE AIRCRAFT PITCHED UP, AND FULL POWER WAS ADDED, THE ENGINE HESITATED, THEN RETURNED TO NORMAL. AS THE PILOT STARTED A CLIMBING LEFT TURN TOWARD THE DOWNWIND LEG, THE ENGINE QUIT. THE PILOT THEN MADE A RIGHT TURN BACK TOWARD LANDING STRIP IN AN ATTEMPT TO LAND, BUT NOT ENOUGH ALTITUDE WAS AVAILABLE, AND THE AIRCRAFT LANDED IN THE TREES.THE AIRCRAFT WAS STUCK IN THE TREES ABOUT 70 FEET IN HEIGHT. EVENTUALLY THE OWNER USED A TREE SERVICE TO CLEAR THE AREA, AND LOWER THE AIRCRAFT TO BE EXAMINED. UPON EXAMINATION AT THE SITE, IT WAS OBSERVED THAT THE AIRCRAFT RECEIVED SUBSTANTIAL DAMAGE TO THE ENGINE AREA ON THE LEFT SIDE. THE FIREWALL WAS BENT. SOME DAMAGE TO THE INNER LEADING EDGE OF BOTH WINGS. THE PROPELLER WAS BROKEN OFF AT THE FLANGE ON THE ENGINE CRANK.FUEL TANKS WERE NOT BREACHED. FUEL RECOVERED FROM THE LEFT WING TANK WAS LESS THAN TWO (2) GALLONS. THE RIGHT WING TANK WAS EMPTY.THE AIRCRAFT WAS THEN BROUGHT BACK TO THE OPERATOR'S HANGAR FOR FURTHER EXAMINATION.COMPRESSION CHECK RESULTS WERE:#1 75/80,#2 79/80, #3 65/80, #4 79/80.MIXTURE, CARB HEAT, THROTTLE CABLES WERE ALL CONTINUOUS. CARBURETOR FUEL SCREEN WAS CLEAR OF ANY BLOCKAGE. TACHOMETER TIME SHOWED 794.9. ENGINE WAS RECENTLY OVERHAULED. THERE DOESN'T SEEM TO BE ANY MECHANICAL ISSUES WITH THE AIRCRAFT.FUEL AT THE OPERATOR'S FUEL TANKS ON THE FIELD, WHERE THE AIRCRAFT LAST RECEIVED FUEL, WAS CHECKED FOR WATER/ CONTAMINATION. NO WATER/CONTAMINATION NOTED.

## 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 ERA12LA482](https://openairdocs.org/ntsb/ERA12LA482), Jul 26, 2012: Piper PA-12 (N4361M), Green Creek, NJ, substantial damage. Probable cause: The pilot's inadequate fuel planning, which resulted in a total loss of engine power due to fuel starvation while maneuvering.

## Other reports on N4361M (1)

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

- [Accident 20080726841099A](https://openairdocs.org/incident/20080726841099A), Jul 26, 2008: Piper PA12 (N4361M), Middle Townshi, NJ, Substantial damage. (-23) On July 26, 2008, about 17:40 eastern daylight time, a Piper PA-12, registered as N4361M, was substantially damaged when it impacted a clothes pole and a…

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.