Cessna 172 and Cessna 172 mid-air collision near Toms River, New Jersey, November 13, 2019
On November 13, 2019 at about 6:30 pm local time, 2 aircraft, Cessna 172 (N3958S) and Cessna 172 (N2148E), were involved in a mid-air collision near Toms River, New Jersey (Ocean County airport). 2 people had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 13, 2019 · about 6:30 pm local time
- Place
- Toms River, New Jersey · Ocean County · map
- Type
- Accident · mid-air collision
- Injuries
- 2 people had minor injuries; 1 other was unhurt.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cessna 172 E, built 1964 · all 172s on the register
- Registration
- N3958S · no longer on the register · serial 17251158
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
- Aircraft 2
- Cessna 172 N, built 1978 · all 172s on the register
- Registration
- N2148E · no longer on the register · serial 17271169
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Cessna 172 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Cessna 172 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Cessna 172 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during landing defining event
The NTSB's findings
- Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Not specified
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not specified
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
- Flight time: 1,300 hours in all; 20 in this make and model; 250 in the last 90 days; 90 in the last 30 days; 1,220 as pilot in command; 1,000 on instruments
- Last flight review: March 22, 2019
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: minor injuries
Dual student
- Certificate: student
- Flight time: 60 hours in all; 40 in this make and model; 5 in the last 90 days; 2 in the last 30 days
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,299 lb
- Landing gear: fixed
- Engine: Continental O-300 SER (piston); 0 hours total
The flight
- Departed from: MJX Toms River NJ
- Flight plan: none
- Runway 32, 3,599 ft by 75 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 340° at 14 knots, gusting 19
- Visibility: 10 statute miles
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
- Altimeter: 30.36 inHg
- Observation at 1:30 pm from MJX
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
The factual record for the Cessna 172 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during landing defining event
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not specified
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instrument: airplane
- Flight time: 3,935.7 hours in all; 51.7 in this make and model; 6.4 in the last 90 days
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,299 lb
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: 17N Cross Keys Airport NJ at 5:00 pm
- Destination: MJX Toms River NJ
- Flight plan: VFR
- Runway 32, 3,599 ft by 75 ft
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.