20250219001202A

Accident · Destroyed

FAA accident report · Reinath Michael S LANCAIR 360 MK II · Marana, AZ · February 19, 2025

Date
February 19, 2025 · 08:28 local
Place
Marana, AZ
Airport
Marana Regional
Phase of flight
Other, Specify
Operating rules
General operating rules (Part 91)
Collision
Midair collision
Damage
Destroyed
Aircraft
N3602M
NTSB investigation
NTSBWPR25FA097
Reported as
Reinath Michael S Lancair 360 MK II
Reported engine
Lycoming HIO-360 series
People aboard
2
Fatal injuries
2
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
1,659 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

The Cessna 172S initially departed from chandler municipal airport (chd) as a part 61 instructional flight with a student pilot performing an initial cross-country flight. The C172S entered the pattern from the north for a left downwind to runway 12. The student pilot announced on the common traffic advisory frequency (CTAF) that they would be performing a touch-and-go on runway 12. After a successful touch-and-go, the Cessna rejoined the pattern. The second time around the pattern, on downwind, the student pilot announced on CTAF that they would be performing a “stop-and-go.”

The Lancair 360 mk ii initially departed eagle roost airpark (27AZ) heading towards Marana, AZ as a part 91 flight. Once in the area, the aircraft entered the pattern from the north for a left downwind to runway 12. The Lancair entered the pattern at a high rate of speed with a non-standard, left, 270-degree turn, to avoid another aircraft already in the pattern. The pilot did not extend his downwind to maintain separation with the aircraft between him and the C172S which resulted in a go-around on the first landing attempt. The Lancair, proceeded to continue in the pattern behind the C172S, again without extending the downwind to maintain separation. This resulted in a second go-around call on CTAF. The Lancair proceeded to pass directly overhead with no offset, overtaking the C172S on runway 12.

As the C172S was performing a short field takeoff after the stop and go, the CFI noted on ADS-B, that the Lancair seemed to be directly above them. The CFI began to call the Lancair on CTAF when the outer 19 inches of the C172S’ propeller contacted the left wing tip, and aileron of the Lancair at roughly 150 ft above ground level (AGL) over the intersection of runway 12/30 and runway 3/21 at kavq about (32°24'32.1"n, 111°12'58.7"w). This caused the Lancair to roll to the left, out of control. The Lancair collided with terrain at 32°24’29.4” n, 111°12’50.4” w, on a heading of 100°. The wreckage came to rest 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 300FT by 100FT 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.

The Cessna was able to land on runway 12 after the collision and taxied to parking under its own power. The Cessna was examined by investigators on 02/21/2025 at kavq. Leading edge damage was noted to the outboard 19 inches of both propeller blades and both blade tips were bent forward. Non-volatile memory cards were found installed in the undamaged G1000 avionics suite and were removed and downloaded by investigators. The data extracted included 1 session from February 19th, 2025. The accident flight recording began at 0715:51 MST and ended at 0836:55 MST. Investigators noted no other damage to the Cessna.

Corrective action: no corrective action was necessary. It was determined that the Lancair 360 mk ii PIC was at fault but ultimately perished in the accident.

Comments: it was determined that the Lancair pilot did not comply with 14 CFR §91.113(b) by not giving way to the C172S and not passing over the C172S unless it was well clear and §91.113(f) by not altering its course to the right while overtaking the C172S.

As the FAA filed it

THE CESSNA 172S INITIALLY DEPARTED FROM CHANDLER MUNICIPAL AIRPORT (CHD) AS A PART 61 INSTRUCTIONAL FLIGHT WITH A STUDENT PILOT PERFORMING AN INITIAL CROSS-COUNTRY FLIGHT. THE C172S ENTERED THE PATTERN FROM THE NORTH FOR A LEFT DOWNWIND TO RUNWAY 12. THE STUDENT PILOT ANNOUNCED ON THE COMMON TRAFFIC ADVISORY FREQUENCY (CTAF) THAT THEY WOULD BE PERFORMING A TOUCH-AND-GO ON RUNWAY 12. AFTER A SUCCESSFUL TOUCH-AND-GO, THE CESSNA REJOINED THE PATTERN. THE SECOND TIME AROUND THE PATTERN, ON DOWNWIND, THE STUDENT PILOT ANNOUNCED ON CTAF THAT THEY WOULD BE PERFORMING A “STOP-AND-GO.”

THE LANCAIR 360 MK II INITIALLY DEPARTED EAGLE ROOST AIRPARK (27AZ) HEADING TOWARDS MARANA, AZ AS A PART 91 FLIGHT. ONCE IN THE AREA, THE AIRCRAFT ENTERED THE PATTERN FROM THE NORTH FOR A LEFT DOWNWIND TO RUNWAY 12. THE LANCAIR ENTERED THE PATTERN AT A HIGH RATE OF SPEED WITH A NON-STANDARD, LEFT, 270-DEGREE TURN, TO AVOID ANOTHER AIRCRAFT ALREADY IN THE PATTERN. THE PILOT DID NOT EXTEND HIS DOWNWIND TO MAINTAIN SEPARATION WITH THE AIRCRAFT BETWEEN HIM AND THE C172S WHICH RESULTED IN A GO-AROUND ON THE FIRST LANDING ATTEMPT. THE LANCAIR, PROCEEDED TO CONTINUE IN THE PATTERN BEHIND THE C172S, AGAIN WITHOUT EXTENDING THE DOWNWIND TO MAINTAIN SEPARATION. THIS RESULTED IN A SECOND GO-AROUND CALL ON CTAF. THE LANCAIR PROCEEDED TO PASS DIRECTLY OVERHEAD WITH NO OFFSET, OVERTAKING THE C172S ON RUNWAY 12.

AS THE C172S WAS PERFORMING A SHORT FIELD TAKEOFF AFTER THE STOP AND GO, THE CFI NOTED ON ADS-B, THAT THE LANCAIR SEEMED TO BE DIRECTLY ABOVE THEM. THE CFI BEGAN TO CALL THE LANCAIR ON CTAF WHEN THE OUTER 19 INCHES OF THE C172S’ PROPELLER CONTACTED THE LEFT WING TIP, AND AILERON OF THE LANCAIR AT ROUGHLY 150 FT ABOVE GROUND LEVEL (AGL) OVER THE INTERSECTION OF RUNWAY 12/30 AND RUNWAY 3/21 AT KAVQ ABOUT (32°24'32.1"N, 111°12'58.7"W). THIS CAUSED THE LANCAIR TO ROLL TO THE LEFT, OUT OF CONTROL. THE LANCAIR COLLIDED WITH TERRAIN AT 32°24’29.4” N, 111°12’50.4” W, ON A HEADING OF 100°. THE WRECKAGE CAME TO REST 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 300FT BY 100FT 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.

THE CESSNA WAS ABLE TO LAND ON RUNWAY 12 AFTER THE COLLISION AND TAXIED TO PARKING UNDER ITS OWN POWER. THE CESSNA WAS EXAMINED BY INVESTIGATORS ON 02/21/2025 AT KAVQ. LEADING EDGE DAMAGE WAS NOTED TO THE OUTBOARD 19 INCHES OF BOTH PROPELLER BLADES AND BOTH BLADE TIPS WERE BENT FORWARD. NON-VOLATILE MEMORY CARDS WERE FOUND INSTALLED IN THE UNDAMAGED G1000 AVIONICS SUITE AND WERE REMOVED AND DOWNLOADED BY INVESTIGATORS. THE DATA EXTRACTED INCLUDED 1 SESSION FROM FEBRUARY 19TH, 2025. THE ACCIDENT FLIGHT RECORDING BEGAN AT 0715:51 MST AND ENDED AT 0836:55 MST. INVESTIGATORS NOTED NO OTHER DAMAGE TO THE CESSNA.

CORRECTIVE ACTION: NO CORRECTIVE ACTION WAS NECESSARY. IT WAS DETERMINED THAT THE LANCAIR 360 MK II PIC WAS AT FAULT BUT ULTIMATELY PERISHED IN THE ACCIDENT.

COMMENTS: IT WAS DETERMINED THAT THE LANCAIR PILOT DID NOT COMPLY WITH 14 CFR §91.113(B) BY NOT GIVING WAY TO THE C172S AND NOT PASSING OVER THE C172S UNLESS IT WAS WELL CLEAR AND §91.113(F) BY NOT ALTERING ITS COURSE TO THE RIGHT WHILE OVERTAKING THE C172S.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other aircraft in the event · 1

Each aircraft in a collision has its own report.