ARIZONA SAFETY ADVISORY GROUP
DECEMBER 2025 AVIATION ACCIDENT & INCIDENT SUMMARY
By Jim Timm
The following are the reports of aviation accidents, and incidents that have occurred in Arizona from mid November thru December. We hope to use the following detailed accident/incident information to develop safety programs, briefings, and posters/flyers that would help pilots learn from the mistakes being made by others, and be able to take the necessary action to prevent them from having similaroccurrences.
The Accident/Incident report is short this time as there were only six accidents reported this time.
In continuing with the expanded scope of the report, we’re using information from the Aviation Safety Network (ASN), FAA, NTSB, and APA Members. This more inclusive information source should suit our purpose of trying to get an idea of what is happening out there so we can help make flying safer.
In the mean time, here are the results from the above sources.
Date: November 15, 2025
Source: FAA Incident
Location: Scottsdale Airport (SDL)
Type: Carbon Cub FX-3
Injuries: 2 Uninjured
Commercial Pilot
STRUCK TAXIWAY LIGHT LANDING
While landing the airplane struck a taxiway light on rollout. and then departed and went around, and landed without incident.
Date: November 17 2025
Source: Member, ASN, FAA
Location: Near Mesa Falcon Field (FFZ)
Type: Piper PA 28-181
Injuries: 2 Uninjured
Flight Instructor & Student pilot
LOSS OF POWER
After a training flight they returned to Falcon Field, and conducted 3 touch and go landings and during a go around, as they were preparing for the approach, an un-commanded reduction of power occurred. The flight instructor took control of the airplane and was unable to restore engine power. He made a forced landing, and about 100 yards into the landing roll, the right wing collided with a cinder block fence and the airplane came to rest. The airplane sustained substantial damage.
Date: December 1, 2025
Source: ASN
Location: Williams Clark Memorial Field, (CMR)
Type: Cessna T210N
Injuries: 1 Uninjured
No Pilot Information
GEAR UP LANDING
The Centurion departed Las Cruces Municipal Airport in New Mexico, and landed with the gear up
at Clark Memorial Field at Williams.
Date: December 7, 2025
Source: FAA Incident
Location: Near Phoenix Deer Valley Airport
Type: Ultra magic M-160 Balloon
Injuries: 5 Uninjured
Commercial Pilot
ROUGH LANDING
The balloon crash landed in a parking lot missing cars, and a nearby power line causing no damage. The passengers were shaken up but uninjured.
Date: December 9, 2025
Source: ASN, FAA
Location: Glendale Airport (GEU)
Type: Piper PA 30-160 Twin Commanche
Injuries: 2 Uninjured
Commercial/CFI Pilot
LANDING GEAR COLLAPSE
The airplane departed Litchfield, and suffered a gear collapse on landing at Glendale.
Date: December 10, 2025
Source: Member, ASN, FAA
Location: Tucson Ryan Field (RYN)
Type: Titan T-51 Mustang
Injuries: 1 Uninjured
No Pilot Information
NOSE OVER ON LANDING
The Titan T51 Mustang was damaged during a nose over while landing after a test flight.
Date: December 14, 2025
Source: ASN
Location: Phoenix Deer Valley (DVT)
Type: Waco RNF
Injuries: 1 Uninjured
No Pilot Information
COLLISION DURING TAXI
A Waco RNF struck the rear of a Cirrus SR20 during taxi at the Phoenix Deer Valley Airport.
NOVEMBER - DECEMBER
PILOT DEVIATIONS
Jim Timm
These pilot deviations need to be examined to determine if a common thread exists that we should address to help reduce the number of deviations that continue to occur, and thus enhance aviation safety.
In the reporting period from November 15 thru December 11 there were twenty-five deviations
reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Student Pilot thru ATP, and there were five out of state pilots, and two military pilots of the twenty-five deviations reported, and there were 12 Brashers issued.
Note: Most of these pilot deviations were resolved during a discussion between the controller, and the pilot at the time of the occurrence. However, a controller may issue a Brasher notification to a pilot when further FAA action will be taken, and the controller is thus giving the airman the opportunity to make note of the occurrence, collect information, and their thoughts for their future interaction with FAA Flight Standards.
I wish pilots would get the message to be more careful in their flying. Perhaps some of these
deviations could be attributed to out of state pilots that may not be accustomed to flying in some of the complex/crowded airspace that we have in Arizona.
I would certainly like to think that the information presented has been valuable to all pilots out there, and will make them safer pilots.
Pilots must listen carefully to ATC instructions and comply with them, and if they can’t comply, tell ATC why they can’t. Also, when flying in controlled airspace, pilots should never do something on their own, but always talk to ATC before they do anything that may differ from the instructions given. Pilots must always be aware of what type of airspace they are flying in, or may be about to enter, and know what may be expected of them. Always observe the airport, and runway markings, and signs and obey them. Fly with care and forethought, and don’t be part of the problem.
In summary, the general aviation deviations this reporting period are:
4 IFR Deviations 3 Brashers
4 Class Delta Airspace Deviations 1 Brasher
2 ATC Instructions 1 Brasher
8 Runway Incursions 5 Brashers
1 NORDO 1 Brasher
6 Surface Incidents 1 Brasher
The details of the deviations this month are as follows:
IFR DEVIATIONS (4)
11/16 IFR NORDO Deviation
ATP Pilot
Out Of Colorado
Albuquerque Center (ZAB)
The Albuquerque Center controller issued a frequency change to the Cirrus, and the aircraft never checked in. Denver Center was notified, and the aircraft was NORDO for about 30 mins. Attempts were made to reach the aircraft on several Albuquerque Center frequencies. Albuquerque asked the Denver Center to issue a Brasher warning to the pilot when he checked in with them.
11/20 IFR Altitude
ATP Pilot
Albuquerque Center (ZAB)
The aircraft was coming off of PHX and should have been climbing to FL210 but was observed out of FL217. When the ATCS inquired, the pilot stated they were climbing to FL260. The Event happened west of Sky Harbor, and the Brasher warning was issued.
11/22 IFR ATC Communications
ATP/CFI Pilot
Out of New Jersey
Phoenix TRACON (P50)
The Falcon Jet was given a visual approach clearance to the runway at Scottsdale. The pilot responded with cleared visual approach but didn't use their callsign. The controller tried to get the pilot to read the instructions back again but the pilot said they didn't have time for this. The Falcon was transferred to the Scottsdale tower, and was given the Brasher.
11/26 IFR ATC Instructions
Military Pilot
Phoenix TRACON (P50)
The UH60 helicopter was at Sedona, and called the Phoenix TRACON for his IFR clearance. The UH60 was instructed twice to Hold for release, however the UH60 did not read back the instruction, and subsequently departed the Sedona airport on their IFR flight plan without ATC authorization.
CLASS DELTA AIRSPACE DEVIATIONS (4)
11/11 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
ATP Pilot
Mesa Falcon Field (FFZ)
The flight of 3 RV8’s entered the Falcon Field Class D airspace without communication. The lead RV8 finally contacted FFZ on a 3-mile final. At the time there were 9 other aircraft in the pattern, and ATC had to take action to accommodate the RV8’s.
11/11 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Unknown Pilot Certification
Out Of Alaska
Goodyear Airport (GYR)
The R66 Helicopter transitioned the Goodyear Delta Airspace 1 NM south of the runway from the east to the west with another helicopter without establishing communications.
11/11 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Goodyear Airport (GYR)
Based on ADS-B information a second R66 helicopter, in formation with the above helicopter, also violated the Goodyear Class Delta Airspace.
11/11 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Tucson Ryan Field (RYN)
The Piper was inbound on the ILS approach into Ryan Field, and the Ryan controller noticed that the Piper had entered into the Ryan Class Delta Airspace without first establishing radio communications. The controller then contacted the Tucson RAPCON, and asked them to switch the Piper to the Ryan frequency. The Ryan controller then reached out to the Piper when they were on a 2 NM final, and the Piper responded with their intentions. The controller sent the Piper around, and issued the Brasher.
ATC INSTRUCTIONS (2)
11/13 Failure to Follow ATC Instructions
Unknown Pilot Certification
Mesa Gateway Airport (IWA)
The Piper was instructed to extend their downwind leg with a good read back. However the Piper was then observed turning base for the runway, and the controller issued a go around to the Piper.
12/7 Failure to Follow ATC Instructions
Comm/CFI Pilot
Mesa Falcon Field Airport (FFZ)
A Cessna was instructed to line up and wait on the runway, and the Cessna acknowledged, and correctly read back the instructions. A Thrush that was holding short of the runway was then instructed to cross the runway. The controller then observed the Cessna starting to roll, and the controller immediately reached out to the Cessna and instructed them to cancel their takeoff. The Cessna did not respond, so the Controller again reached out to them, and advised them to cancel their takeoff. The Cessna did acknowledge the second time, and exited runway. The Cessna was then instructed to contact Ground Control, and Ground control issued the Brasher.
RUNWAY INCURSIONS (8)
11/6 Entering A Runway Without Authorization
Private Pilot
Mesa Falcon Field (FFZ)
The Piper was issued a Line Up And Wait instructions to permit a runway crossing downfield. After initiating the runway crossing, the controller observed the Piper starting their takeoff roll. The controller instructed the Piper to "Cancel takeoff clearance”, and the pilot responded with, “What?", and continued to takeoff. the Piper became airborne 1500' from the RWY threshold while the crossing aircraft was clearing the RWY at midfield, approx 800' downfield from the point of the Pipers point of rotation. An overflight did NOT occur, and the crossing aircraft was clear of the runway environment when the Piper overflew the crossing point.
11/10 Entering A Runway Without Authorization
Private Pilot
Out Of Tennessee
Tucson International Airport (TUS)
Ground Control instructed the Cirrus to taxi via a taxiway to the Runway, and after a few attempts, the read back was correct. The Cirrus taxied via the taxiway and, crossed the hold short line, and entered the runway. Ground Control instructed the pilot to make a 180 to clear the runway. No other traffic was involved.
11/11 Entering A Runway Without Authorization
Comm/CFI Pilot
Tucson International Airport (TUS)
The Cirrus was given a taxi clearance to the runway, and to hold short of the runway by Ground Control, and the read back was correct. The controller noticed that the Cirrus had taxied onto the runway without a clearance, and was then issued the Brasher warning.
11/11 Entering A Wrong Runway
Private Pilot
Out Of Michigan
Phoenix Deer Valley Airport (DVT)
The Mooney was cleared to land on RWY 7L by the controller, but the aircraft landed on RWY 7R. After landing the aircraft was told to exit the runway, and was given the Brasher by the Ground Controller.
11/26 Entering A Wrong Runway
Military Pilot
Tucson Ryan Field (RYN)
The UH60 Helicopter contacted Ryan Tower to taxi to RWY 33 for departure to the southeast. The
controller taxied the UH60 to RWY 15 to provide them with a departure heading that would be more on course since there was an aircraft holding short of RWY 33. The UH60 entered RWY 15 without requesting a departure, and stopped at a hover. The controller gave them a departure clearance since they were in the RWY area, and no conflicts would have arose from their departure. A Brasher was issued.
11/26 Entering A Runway Without Authorization.
unknown Pilot Certification
Mesa Falcon Field (FFZ)
The pilot deviation was reported when the Piper crossed the hold short line of the runway without ATC authorization.
12/2 Entering A Runway Without Authorization
Comm/CFI Pilot
Phoenix Deer Valley Airport (DVT)
A Piper attempted to call the tower for a departure while holding short of the runway. The controller did not respond as they were talking to other aircraft at that time. The Piper then keyed up, and asked to confirm if they were cleared for takeoff. At this point the Training Instructor stepped in as they observed the aircraft crossing the hold short bars. The Training Instructor told them to hold position, and then proceeded to send two Cessna’s around. The Piper was then cleared for takeoff, and they continued in the pattern. After they landed the Piper was issued the Brasher Warning.
12/3 Entering A Runway Without Authorization
Student Pilot
Tucson Ryan Field (RYN)
A Cessna contacted the tower for a departure, and the tower told them to hold short of the RWY. The Cessna read back the instructions but continued taxiing past the hold short bars onto the runway. Because of the runway intrusion, the tower had to send a Piper around when they were within one mile on a final. A Brasher was issued.
NO RADIO (NORDO) (1)
12/7 No Radio Deviation
Commercial Pilot
Albuquerque Center (ZAB)
The Albuquerque Center Controller recognized that the Skyvan was in a climb off Eloy but had not
established radio communications prior to leaving 5,000 feet as required per the Letter Of Agreement. The controller issued a safety alert to a Cessna who was at 8’000 feet NW bound. The Skyvan then responded, and reported the traffic insight. Later the pilot called Albuquerque and stated that they attempted to contact Albuquerque Center leaving 4,000 but did not get a response. He believed that they have a radio issue with the aircraft and would not be using it until the radio has been looked at. A Brasher was issued.
SURFACE INCIDENTS (6)
11/5 Taxiing On A Movement Area Without Authorization
Private Pilot
Tucson Ryan Field (RYN)
The Cessna pilot called Ground Control requesting to taxi. Ground Control asked the Cessna to say their direction of flight, but got no response. Ground Control tried a radio check with the aircraft, and still didn’t get a response. The Cessna transmitted, “Ryan Ground, Cessna taxi to Runway 6R”. The Cessna then taxied out onto the taxiway system to the run up area north of Taxiway Bravo (see diagram). Ground Control attempted to make contact with the Cessna pilot several times with no response. Ground Control asked an Ops. vehicle that was on frequency to intercept the aircraft, and have the pilot call ATC. The Cessna contacted Ground Control after the Ops personnel got in touch with them, and advised Ground Control that the Cessna’s radio had been turned down.
11/10 Taxiing On A Movement Area Without Authorization
Comm/CFI Pilot
Phoenix Goodyear Airport (GYR)
The Cessna’s taxi instructions were read back correctly, but the Cessna began taxiing the opposite direction down the taxiway towards the parking ramp without establishing two-way communications with Ground Control.
11/25 Taxiing On A Movement Area Without Authorization
Private Pilot
Tucson Ryan Field (RYN)
The Sport Cruiser exited the runway, and began taxiing themselves without establishing two-way
communications, and receiving a taxi clearance from Ground Control.
12/3 Taxiing On A Movement Area Without Authorization
Comm/CFI Pilot
Mesa Gateway Airport (IWA)
The Piper was instructed to taxi via Bravo, and hold short of Taxiway Kilo for traffic exiting 30L onto Kilo. The read back was correct, but the Piper taxied through the intersection passing Kilo.
12/6 Entering A Movement Area Without Authorization
Tug with an aircraft in tow
Phoenix Sky Harbor (PHX)
The deviation was reported when a tug with an aircraft in tow entered a taxiway without ATC
authorization.
12/9 Taxiing On A Movement Area Without Authorization
Student Pilot
Mesa Gateway Airport (IWA)
The Piper landed on the center Runway, and the controller instructed the Piper to exit on Taxiway Charlie 4. The read back was correct. But without receiving taxi instructions the Piper turned left onto the taxiway, and began to taxi. The controller issued the Brasher warning.
