Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

November 13, 2019 · Cessna 172 E · N3958S

Toms River, NJ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 13, 2019
Injury Outcomes
2 injuries (2 minor injuries), 1 uninjured
Location
Toms River, NJ
Aircraft
Cessna 172 E (1964)
Tail Number
N3958S
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA20LA034

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.

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

Full Narrative

On November 13, 2019, about 1330 eastern daylight time, a Cessna 172E, N3958S, and a Cessna 172N, N2148E, were both substantially damaged when they were involved in an accident at Ocean County Airport (MJX), Toms River, New Jersey. The flight instructor and student pilot aboard the Cessna 172E sustained minor injuries and the pilot aboard the Cessna 172N was not injured. Both airplanes were operating under the provisions of Title 14 Code of Federal Regulations Part 91. The pilot of the Cessna 172N stated that, as he approached MJX, he announced on the common traffic advisory frequency (CTAF) that he was at an altitude of 3,500 ft about 12 miles west of the airport. He reported that his intention was to perform a simulated engine-out maneuver over the airport then “spiral down to set up for [the] left base” leg of the traffic pattern for runway 32. When he was about 5 miles away, he reported his location and repeated his intentions. When he arrived at the airport, he was about 1,200 ft, and “observed no activity at the field out of the ordinary” and that it was “quiet.” He performed a spiraling descent and set up for a left base traffic pattern entry to runway 32. At an altitude of about 20 ft above the ground, he set the flaps to 20° then “felt a thump and sudden roll to the right.” He subsequently landed in the grass beside the runway and saw another airplane taxiing on the runway. The flight instructor and student pilot aboard the Cessna 172E stated that they announced their position on the CTAF as they turned onto the downwind, base, and final legs of the traffic pattern for runway 32 at MJX. While on short final approach to the runway, about 100 ft above the ground, they noted “…something was going wrong with the aerodynamics of the airplane” and that “it was at this moment we saw a wheel crash into our windshield.” They landed the airplane and saw the other airplane landing in the grass to their right. They exited the runway and taxied to the ramp, parked the airplane, and inspected it for damage. A Federal Aviation Administration inspector examined both airplanes and noted that the Comm 1 radio in the Cessna 172N was tuned to 122.80 with a frequency of 122.70 in the standby position. According to the FAA Airport Directory, the CTAF for MJX was 122.7. The inspector also reported the Cessna 172N received substantial damage to the right wing while the Cessna 172E received substantial damage to the right wing and vertical stabilizer. Title 14 CFR 91.113 states that “when weather conditions permit, regardless of whether an operation is conducted under instrument flight rules [IFR] or visual flight rules [VFR], vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft. (g) Landing. When two or more aircraft are approaching an airport for the purpose of landing, the aircraft at the lower altitude has the right-of-way, but it shall not take advantage of this rule to cut in front of another which is on final approach to land or to overtake that aircraft. In addition, the FAA Airplane Flying Handbook stated the following: “All pilots must be alert to the potential for midair collision and impending loss of separation. The general operating and flight rules in 14 CFR part 91 set forth the concept of "See and Avoid." This concept requires that vigilance shall be maintained at all times by each person operating an aircraft regardless of whether the operation is conducted under IFR or VFR.…Most of these accidents/incidents occur within 5 miles of an airport and/or near navigation aids.” The pilots did not report any mechanical malfunctions or failures of the airplane that would have precluded normal operation prior to the accident.

Flight

Event TypeAccident
Event Time13:30 EST
Nearest AirportOcean County (0nm S)
Runway32
Runway Length3599 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 E
Tail NumberN3958S
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-300 SER · Reciprocating · 145 | Lycoming · O-320 SERIES · Reciprocating
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries), 1 uninjured
Fatal0
Serious0
Minor2
Uninjured1
Total3
Crew 1Age 24 · First Class · Minor
Crew 2Third Class · Minor
Crew 3Age 57 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind340° @ 14 kt, gusting 19 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter30.36 inHg
Observation Time13:30
Weather SourceWFAC

Appendix: Source Data