# Incident 20191113019452I: Cessna 172N, Berkeley Townsh, NJ, November 13, 2019

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 13, 2019, 13:00 local time
- Place: Berkeley Townsh, NJ
- Damage: Minor damage
- Collision: Midair collision
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 39.9208° N, 74.2961° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.9208&lon=-74.2961&mi=10
- Aircraft: N2148E, a cancelled registration (https://openairdocs.org/deregistered/N2148E-2024-07-20) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- Pilot flight hours: 3,935 total, 51 in this make and model, 6 in the last 90 days
- NTSB investigation: [NTSB ERA20LA034](https://openairdocs.org/ntsb/ERA20LA034) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20191113019452I

## Narrative

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

CESSNA 172N, N2148E, S/N 17271169, AND A CESSNA 172E, N3958S, S/N 17251158 COLLIDED WHILE ATTEMPTING TO LAND ON RUNWAY 32 AT OCEAN COUNTY AIRPORT (MJX), BERKELEY TOWNSHIP, NEW JERSEY AT APPROXIMATELY 1:00PM LOCAL TIME.  N2148E DEPARTED CROSS KEYS AIRPORT (17N) WITH ONE PILOT AT APPROXIMATELY 12:20PM, AS THE PILOT WAS SCHEDULED TO PERFORM SIMULATED ENGINE OUT TRAINING AT MJX.  N3958S DEPARTED MJX WITH A FLIGHT INSTRUCTOR AND STUDENT PILOT AT APPROXIMATELY 12:15PM AND WAS CONDUCTING FLIGHT TRAINING IN THE PATTERN AT MJX.  WEATHER CONDITIONS WERE VFR AND AS FOLLOWS: WINDS 340@14G19, VISIBILITY 10 CLEAR.

THE PILOT FOR N2148E REPORTED HE FELT A THUMP AND A SUDDEN ROLL TO THE RIGHT AT APPROXIMATELY 50 FEET AGL WHILE ATTEMPTING TO LAND ON RUNWAY 32, BUT WAS ABLE TO CONTROL THE AIRCRAFT AND LANDED IN THE GRASSY AREA TO THE RIGHT OF RUNWAY 32.  THE PILOT/FLIGHT INSTRUCTOR FOR N3958S FELT SOMETHING WRONG WITH THE AERODYNAMICS OF THE AIRPLANE AT APPROXIMATELY 50 FEET AGL, AND IMMEDIATELY FELT AN IMPACT AND SAW A WHEEL CRASH INTO THE WINDSHIELD.  THE WINDSHIELD BROKE AND THE AIRFLOW SENT PIECES OF PLEXIGLASS INTO THE COCKPIT, BUT THE PILOT LANDED THE AIRCRAFT ON RUNWAY 32.  ONE MINOR INJURY WAS NOTED WITH THE PILOT DUE TO CUTS ON HIS FACE FROM THE PLEXIGLASS.  BOTH AIRCRAFT TAXIED TO THE RAMP WITHOUT ASSISTANCE.

N2148E INCURRED MINOR DAMAGE TO THE RIGHT WING LEADING EDGE, LOWER RIGHT FUSELAGE JUST AFT OF THE ENGINE COWLING, AND TO THE RIGHT HORIZONTAL STAB, UNDERSIDE, WHILE N3958S SUSTAINED SUBSTANTIAL DAMAGE TO THE VERTICAL STABILIZER, RIGHT AILERON, AND THE FLAP WAS TORN FROM THE INBOARD ATTACH POINTS.  IN ADDITION, STRUCTURAL DAMAGE WAS NOTED ON THE AFT UPPER RIGHT HAND WING JUST ABOVE THE INBOARD FLAP TRACK, AND THE WINDSHIELD WAS BROKEN IN SEVERAL PIECES AND MINOR DAMAGE TO THE RIGHT WING LEADING EDGE.

## Other aircraft in the event

- N3958S, Cessna 172E: [Accident 20191113018862A](https://openairdocs.org/incident/20191113018862A)

## 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 ERA20LA034](https://openairdocs.org/ntsb/ERA20LA034), Nov 13, 2019: Cessna 172 (N2148E), Toms River, NJ, substantial damage. Probable cause: The failure of the Cessna 172N pilot to see and avoid a second airplane while maneuvering in the traffic pattern, which resulted in a midair collision. Contributing to the accident was the failure of…

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.