Casualties unknown

Midair Collision Between Two Cessna 172s During Practice and Arrival (N6376F)

ST Paul, MN, US

On July 7, 1992, a Cessna 172N (registration N6376F) operated by Wings, Inc. was involved in an aviation accident near ST Paul, MN. Investigators recorded the probable cause as: INADEQUATE VISUAL LOOKOUT BY THE PLOTS OF BOTH AIRPLANES, WHICH RESULTED IN THEIR FAILURE TO SEE-AND-AVOID CONFLICTING TRAFFIC, AND FAILURE OF THE RELIEVING CONTROLLERS TO USE THE RADAR DISPLAY TO IDENTIFY AND SEQUENCE AN AIRPLANE ENTERING THE PATTERN. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 3 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

Two Cessna 172s, N6376F and N5279R, collided midair near an airport. N6376F was practicing touch-and-go landings with a student and instructor; N5279R was arriving transporting blood. The collision occurred after a series of communications and controller handoffs.

Incident Overview

At 1640 CDT, a Cessna 172, registration N5279R (79R), reported 7 miles southeast for landing. The aircraft was transporting blood for the Red Cross. Meanwhile, another Cessna 172, N6376F (76F), was practicing touch-and-go landings with a student and a certified flight instructor (CFI).

Air Traffic Control Communications

The tower controller observed a target in that vicinity using D-Brite radar and instructed 79R to enter a left downwind for Runway 12 and report 2 miles southeast. At 1643, the controller was relieved by a developmental controller (DC) and a full performance controller (FPC). During the briefing, the departing controller informed the relief team of the positions of aircraft in the traffic pattern and that 79R was inbound from the southeast, but did not show them its position on radar.

At 1644:55, 79R made a radio call stating the aircraft was "practically straight east of the airport." 79R was told again to report on downwind but never did so. Both controllers were working several aircraft; they neither sighted 79R nor used radar to locate it.

Collision Sequence

At 1647:06, 79R called turning base for Runway 12. At that time, 79R was tracking inside the flight path of 76F, as 76F was in a left turn to final approach for Runway 14. Approximately 25 seconds later, the two aircraft converged, collided, and then crashed to the ground.

All Cessna 172 accidents →

Frequently asked questions

What happened in the 7 Jul 1992 Cessna 172N accident near ST Paul, MN?

Two Cessna 172s, N6376F and N5279R, collided midair near an airport. N6376F was practicing touch-and-go landings with a student and instructor; N5279R was arriving transporting blood. The collision occurred after a series of communications and controller handoffs.

What aircraft was involved and where did it happen?

The accident on 7 Jul 1992 involved a Cessna 172N, registration N6376F, operated by Wings, Inc., at ST Paul, MN.

What was the probable cause of the accident?

INADEQUATE VISUAL LOOKOUT BY THE PLOTS OF BOTH AIRPLANES, WHICH RESULTED IN THEIR FAILURE TO SEE-AND-AVOID CONFLICTING TRAFFIC, AND FAILURE OF THE RELIEVING CONTROLLERS TO USE THE RADAR DISPLAY TO IDENTIFY AND SEQUENCE AN AIRPLANE ENTERING THE PATTERN. FACTORS RELATED TO THE ACCIDENT WERE: AN INADEQUATE BRIEFING BY…

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001211X15101. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.