# NTSB NYC75FHD43: Piper PA-28R, N41331, Lindenwold, NJ, May 7, 1975

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Closed
- Date: May 7, 1975
- Place: Lindenwold, NJ · LINDENWOLD, NJ
- Location: 39.8188° N, 74.9900° W: Placed by OpenAirDocs: center of Lindenwold, NJ, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.8188&lon=-74.9900&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Highest injury: Serious injuries
- Injuries: 1 serious
- Status: Completed, report August 20, 1975
- Report: Brief approved by the director
- NTSB case key (mKey): 149205
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC75FHD43
- Page: https://openairdocs.org/ntsb/NYC75FHD43

## NTSB brief

```
----------------------------------------------------------------------------------------------------------------------------
 FILE    DATE          LOCATION          AIRCRAFT DATA       INJURIES       FLIGHT                        PILOT DATA
                                                               F  S M/N     PURPOSE
----------------------------------------------------------------------------------------------------------------------------
3-1874   75/5/7    LINDENWOLD,NJ       PIPER PA-28R        CR-  0  1  0  NONCOMMERCIAL             PRIVATE,FL.INSTR., AGE
        TIME - 0930                    N41331              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  30, 3800 TOTAL HOURS, 700
                                       DAMAGE-DESTROYED    OT-  0  0  0                            IN TYPE, INSTRUMENT
                                                                                                   RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          ALBION,NJ                   BRIDGEPORT,NJ
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           COLLIDED WITH: TREES                                     LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           POWERPLANT - ENGINE STRUCTURE: MASTER AND CONNECTING RODS
           MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE
           TERRAIN - HIGH OBSTRUCTIONS
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
        REMARKS- NR 1 CONNECTING ROD BOLTS BKN,FRONT MAIN BEAR FUSED TO MAIN AREA.MFG UN DTMN ORIGIN OF FAIL.
```

## Aircraft

- Registration: [N41331](https://openairdocs.org/aircraft/N41331), registered now, S/N 28R-7435169, built 1974 (OpenAirDocs)
- Reported make and model: PIPER PA-28R
- Registry model: [Piper PA-28R-200](https://openairdocs.org/model/piper-pa-28r-200) (registry code 7102811) (OpenAirDocs)
- Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs)
- Category: Airplane
- Engines: reciprocating
- Damage: Destroyed

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19750507020499A](https://openairdocs.org/incident/19750507020499A), May 7, 1975: Piper PA28R200, Lindenwold, NJ, Destroyed. Nr 1 connecting rod bolts bkn,front main bear fused to main area. Mfg un dtmn origin of fail.

## Other investigations on N41331 (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 LAX96LA331](https://openairdocs.org/ntsb/LAX96LA331), Sep 7, 1996: Piper PA-28R-200 (N41331), Oxnard, CA, substantial damage. Probable cause: the instructor's inadequate supervision of the flight, and his delay in taking the controls and initiating a go-around. The student pilot's failure to maintain runway alignment and the proximity of…

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.

---
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.