ERA20LA034 · Cessna 172 E
Cessna 172 E and Cessna 172 N · Accident: midair collision during landing
Event
- NTSB case
- ERA20LA034
- 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
Aircraft 1 · Cessna 172 E
- Aircraft type
- Cessna 172
- 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
- N3958S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ocean County Airport (MJX), Toms River, NJTo not recorded
- Aircraft age
- About 55 years (built 1964)
- 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
- Landing
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Cessna 172 N
- Aircraft type
- Cessna 172
- 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
- N2148E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cross Keys Airport (17N), Cross Keys, NJTo Ocean County Airport (MJX), Toms River, NJ
- Aircraft age
- About 41 years (built 1978)
- 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
- Landing
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Two airplanes, a Cessna 172E and a Cessna 172N, collided in midair while in the traffic pattern over the approach end of the runway. The pilot of the Cessna 172E announced his position while on downwind, base, and final approach to landing. The pilot of the Cessna 172N approached the airport and announced his intention on the common traffic advisory frequency to practice a simulated engine-out maneuver followed by a descent to set up for left base leg of the traffic pattern for runway 32. While about 100 ft over the approach end of the runway, the airplanes collided, with the Cessna 172N striking the Cessna 172E from above. Both airplanes landed safely, but an examination revealed that both incurred substantial damage to their right wings. The radio in the Cessna 172N was found tuned to the wrong frequency. It is likely that the pilot of the Cessna 172N thought he switched the radio to the correct frequency and failed to maintain an adequate visual lookout, which resulted in a midair collision on short final. Because his radio was tuned to the wrong frequency, his transmissions were not heard by other pilots in the vicinity of the airport and he was not able to hear other traffic callouts.
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 the Cessna 172N pilot to tune his radio to the correct traffic advisory frequency for the destination airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA034
- Event ID
- 20191113X45317
- Case number
- ERA20LA034
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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: 78e96939bfcbec4a303733fe79a6e03ef23b6e77e66d40291decab37f37fb9f8; retrieved 2026-09-13T18:33:54.957Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: departure. 17N is Cross Keys Airport; the city slot contains the airport name rather than the city, which is Cross Keys, NJ.