FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25FA097 · Lancair 360 Mk. II

19 Feb 2025 · Marana, AZ, United States

Lancair 360 Mk. II and Bird Acquisition Cessna 172 S · Accident: midair collision on approach

Report a problem

Event

NTSB case
WPR25FA097
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Lancair 360 Mk. II

Aircraft type
Lancair 360
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3602M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eagle Roost Airpark (27AZ), Aguila, AZTo Marana Regional Airport (AVQ), Marana, AZ
Aircraft age
About 24 years (built 2001)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Aircraft 2 · Cessna 172 S

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N463ER
Onboard fatalities
Unknown
Route
From Chandler Municipal Airport (CHD), Chandler, AZTo Marana Regional Airport (AVQ), Marana, AZ
Aircraft age
About 10 years (built 2015)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Not recorded
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR25FA097
Event ID
20250219199723
Case number
WPR25FA097
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 93dece024c2c86b5ead09a941ed5e86ba6800df41406df3998c00f331aee5e63; retrieved 2026-09-13T18:12:25.246Z.