On May 30, 1999, a Cessna 172P (registration N66018) operated by Southwest Flight Center was involved in an aviation accident near Mesa, AZ. No fatalities were reported. Investigators recorded the probable cause as: The failure of the tower (local) air traffic controller to issue a landing sequence to the climbing, high wing Cessna 172 aircraft, and the controller's failure to maintain visual separation between the two aircraft on downwind leg. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 2 related events involving the same aircraft type or operator are linked below.
A midair collision occurred between two aircraft on downwind leg of a touch-and-go pattern at a tower-controlled airport. Both aircraft landed safely. The controller had not issued a landing sequence to one aircraft due to confusion.
Incident Description
During daylight hours with high scattered clouds and visibility of 40 statute miles, a midair collision took place while both aircraft were on the downwind leg of the touch-and-go landing pattern at a tower-controlled airport. The high-wing aircraft, which had completed three touch-and-go patterns, climbed up under the low-wing aircraft prior to the collision. Despite the collision, both aircraft landed safely.
Investigation Findings
The investigation revealed that the pilot of the high-wing aircraft had not been issued a landing sequence or a traffic advisory by the air traffic controller. The pilot believed he was following another high-wing aircraft that was well ahead on the downwind leg. The local air traffic controller acknowledged that he had become confused with the sequence of landing aircraft and had not issued a landing sequence or traffic advisory to this aircraft. At the time of the incident, there were six aircraft in the landing pattern and five more awaiting departure.
Probable Cause
No probable cause was stated in the investigation source.
What happened in the 30 May 1999 Cessna 172P accident near Mesa, AZ?
A midair collision occurred between two aircraft on downwind leg of a touch-and-go pattern at a tower-controlled airport. Both aircraft landed safely. The controller had not issued a landing sequence to one aircraft due to confusion.
Were there any fatalities in the 30 May 1999 Cessna 172P accident?
No fatalities were recorded in this accident.
What aircraft was involved and where did it happen?
The accident on 30 May 1999 involved a Cessna 172P, registration N66018, operated by Southwest Flight Center, at Mesa, AZ.
What was the probable cause of the accident?
The failure of the tower (local) air traffic controller to issue a landing sequence to the climbing, high wing Cessna 172 aircraft, and the controller's failure to maintain visual separation between the two aircraft on downwind leg.
A SkyWalk Join't 3 paraglider crashed into the ground near Las Vizcachas, Chile, on September 1, 2024. The pilot and passenger sustained serious spinal…
PARAPENTE (ULTRALIVIANO NO MOTORIZADO)·2024-09-01DGAC Chile
A Cessna 172N struck electrical cables while on final approach to land at Aucó Aerodrome in Chile. The pilot was uninjured, but the aircraft sustained damage…
A Bombardier DHC-8-402 suffered a tail strike during landing at Puerto Williams on September 9, 2024. All 76 occupants were unharmed, but the aircraft…
A MYD JS-MD 3 glider veered off the runway and struck a wall at Vitacura Aerodrome on January 6, 2025. The pilot was uninjured, but the aircraft sustained…
A recreational paraglider flight in Puchuncaví, Chile, ended with the pilot sustaining serious injuries after a rapid descent and impact with a hillside on…
PARAPENTE (ULTRALIVIANO NO MOTORIZADO)·2025-03-29DGAC Chile
A Tecnam P2006T landed on its belly at an aerodrome in Poland after the crew failed to confirm landing gear deployment. The incident resulted in no injuries…