Accident Details
Aircraft Information
Registered Owner (Current)
Analysis
On February 19, 2025, about 0828 mountain standard time, a Lancair 360 Mk II, N3602M, was destroyed, and a Cessna 172S, N463ER, sustained minor damage when they were involved in a mid-air collision near Marana Regional Airport (AVQ), Marana, Arizona. The pilot and passenger in the Lancair were fatally injured, the student pilot and flight instructor in the Cessna were not injured. The Lancair was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The Cessna was operated as a Title 14 CFR Part 91 instructional flight.
The flight instructor onboard the Cessna stated that the purpose of the flight was to perform a cross-country flight and departed from Chandler Municipal Airport, Chandler, Arizona. Upon arriving to AVQ, they entered the airport traffic pattern and performed a touch and go on runway 12 and remained within the pattern. During this time the Lancair entered the traffic pattern from the northwest. Upon its initial approach to runway 12, the Lancair performed a go around due to conflicting traffic and remained within the traffic pattern behind the Cessna.
While the Cessna was on downwind, the flight instructor announced over the Common Traffic Advisory Frequency (CTAF) that they were going to do a stop and go on the runway, to perform a short field landing and a short field takeoff. The flight instructor stated that they landed uneventfully and while in the process of taking off, they heard the Lancair pilot announce on the CTAF that he was going around again. The flight instructor stated that she looked at ADS-B information displayed on her iPad and saw the Lancair converging towards their airplane from behind. As the instructor was “keying up the radio” to ask the Lancair pilot if they saw them, both airplanes collided. The flight instructor took control of the Cessna from the student and remained within the pattern for an uneventful landing on runway 12. The Lancair impacted terrain near a taxiway and became engulfed in flames.
A review of airport surveillance video (see figure 1) and preliminary ADS-B data revealed that the collision between the Lancair and the Cessna occurred over the intersection of runway 12/30 and runway 3/21 at AVQ about 150 ft above ground level (AGL).
Figure 1: Composite footage of a north-facing airport security camera showing the collision.
Review of recorded CTAF communication (see figure 2) revealed that about 0825:14, the student pilot announced their intentions to perform a stop and go landing. At 0825:41, the Lancair transmitted “traffic on base are you a touch and go?” to which the flight instructor replied, “we are a stop and go”. At 0826:05, the pilot of the Lancair advised that they were turning left base and shortly after the student pilot advised that they were on final for a stop and go on runway 12. About 0827:51, the pilot of the Lancair advised they were on a one mile final and about 27 seconds later announced that they were “going around again”. About 0828:41, the Cessna student pilot announced that they were on the upwind, followed by the flight instructor stating “Lancair Zero Two Mike” followed by an audible gasp. About ten seconds later the Cessna declared an emergency.
Figure 2: Recorded ADS-B data with CTAF communication annotations.
Examination of the accident site revealed that the Lancair came to rest on a heading of 100° magnetic, upright on the edge of a drainage culvert and taxiway. The wreckage sustained significant fire damage. A small debris field was found on runway 12 and stretched over a 300 ft by 100 ft area towards the airport segmented circle and contained fragmented pieces from the left wing tip, left aileron, aileron trim tab, and outboard wing skin of the Lancair. All major structural components of the airplane were located throughout the wreckage debris path. The wreckage was recovered to a secure location for further examination.
The Cessna sustained minor damage the propeller.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# WPR25FA097