ARIZONA SAFETY ADVISORY GROUP
AUGUST 2026 AVIATION ACCIDENT/INCIDENT SUMMARY
By Jim Timm
The following are the reports of aviation accidents/incidents that have occurred in Arizona from mid June thru early August.
We hope to use the following detailed accident 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 a similar occurrence.
The Accident/Incident report is a bit longer than usual because the July meeting of ASAG was eliminated because if the EAA AirVenture program in Oshkosh, Wisconsin, and many in the aviation community were there in attendance. As a result there are 12 accident/incidents presented in this report.
In continuing with the expanded scope of this report, we’re using information from the Aviation Safety Network (ASN), NTSB, FAA and APA Members. Hopefully the information from these sources will 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: June 13, 2026
Source: APA Member, ASN, FAA, NTSB
Location: Marana Airport (AVQ)
Type: Cessna 208B Grand Caravan
Injuries: 1 Uninjured, 1 Fatality
Comm/CFI Pilot
INATTENTION TO PROP
The aircraft was parked at the ramp after landing when an employee of SkyDive Marana exited and sustained fatal injuries after he walked into the propeller which was still running
Date: June 18, 2026
Source: ASN
Location: Chandler Municipal Airport (CHD)
Type: Cessna 172M
Injuries: 1Uninjured
Pilot Info: No Pilot Information
HARD LANDING
Then airplane departed Tucson Ryan Field and landed hard on the runway at Chandler Municipal Airport which resulted in a flat tire, and a propeller strike.
Date: June 20, 2026
Source: ASN, FAA Incident
Location: Tucson International Airport (TUS)
Type:Piper PA-28-181
Injuries: 2 Uninjured
Pilot Info: Private Pilot
TAXIING ISSUE
The Piper was taxiing to park when its the right wing stuck the propeller of aircraft which was parked, and unoccupied.
Date: June 25,2026
Source: ASN, FAA
Location: Near Dome, AZ
Type: Beechcraft S35 Bonanza
Injuries: 3 Uninjured
Pilot Info: Private Pilot
ENGINE POWER ISSUE
The Bonanza departed Eagle Roost Airpark, and experienced engine issues, and hit brush while attempting an emergency landing near Dome, Arizona. (Dome is a Ghost town located in southeast
Arizona near Yuma)
Date: July 5, 2026
Source: ASN, FAA
Location: Near Salome
Type: Piper PA-28-140
Injuries: 2 Uninjured
Pilot Info: Private Pilot
ENGINE FAILURE
The Cherokee experienced an engine failure, and made a forced landing in a field near Salome.
Date: July 11, 2026
Source: ASN, FAA Incident
Location: Overgaarg-Mogollon Airpark
Type: Lancair Legacy 2000
Injuries: 1 Uninjured
Pilot Info: No Pilot information
GEAR UP LANDING
The aircraft departed Sedona, and made a gear up landing at the Mogollon Airpark airport.
Date: July 12, 2026
Source: ASN, FAA
Location: Glendale Municipal Airport (GEU)
Type: Remos GX
Injuries: 2 Uninjured
No Pilot Information
CONTROL LINKAGE FAILURE
The student pilot was practicing landings at Glendale Airport, and during the initial climb, the airplane’s pitch control was “delayed.” After taking the flight controls the instructor observed that the airplane did not respond to pitch control inputs. The flight instructor was able to maneuver the airplane using the ailerons, rudder, full nose up pitch trim, and engine power. During the final approach to the runway, the airplane lost altitude and impacted terrain, resulting in substantial
damage to the airplane’s fuselage. Examination of the airplane revealed that the rear elevator control rod had fractured about three inches forward of the elevator quick disconnect. According to maintenance records, the elevator control rod had accrued 445 hours in service.
Date: July 12, 2026
Source: ASN, FAA Incident
Location: Goodyear Municipal Airport (GYR)
Type: Cirrus SR 20 G6
Injuries: 3 Uninjured
No Pilot Information
TAIL STRIKE
The Cirrus had departed Ak Chin airport, and while landing at Goodyear the airplane incurred a tail strike.
Date: July 25, 2026
Source: ASN, FAA Incident
Location: Prescott Municipal Airport (PRC)
Type: Harmon Rockett II
Injuries: 2 Uninjured
No Pilot Information
PROP STRIKE
The airplane bounced on landing, and incurred a propeller strike.
Date: July 26
Source: FAA Incident
Location: Buckeye Airport (BXK)
Type: Cirrus SR20
Injuries: 1 Uninjured
Pilot Info.: Private Pilot
OVERRAN RUNWAY
During landing the airplane rolled off the end of the runway into the dirt.
Date: July 28, 2026
Source: ASN, FAA, NTSB
Location: Chandler Municipal Airport (CHD)
Type: Piper PA-28-180 Cherokee C
Injuries: 1 Fatal
No Pilot Information
LOSS OF POWER
The Piper Cherokee crashed shortly after taking off at Chandler Municipal Airport.
Date: August 1, 2026
Source: FAA Incident
Location: Mesa Falcon Field
Type: Zenith 601
Injuries: 1 Uninjured
Pilot Info.: Comm Pilot
RUNWAY EXCURSION
Aircraft went off the runway because of an improper flap selection for the cross wind.
NEAR MIDAIR COLLISION’S (NMAC)
There were two Near Mid Air Collision incidents reported during the period from June 12, 2025 thru August 7, 2026. One occurred on June 16, and the other occurred on July 21,2026.
Date: June 16, 2026
Location: Scottsdale Airport (SDL)
A helicopter was transitioning the Scottsdale Class Delta Airspace VFR at 3,000 feet. A Citation was issued a takeoff clearance with a right hand turn to a heading of 285°, and to an altitude of 5,000 feet. The controller verified that the helicopter was transitioning southwest bound, and would remain west of the RWY centerline. The controller advised the Citation, that was now climbing to 5,000 feet, of the helicopters presence. The helicopter asked the controller if they should remain at their present altitude or if they should descend. The controller advised that the Citation which was taking off was climbing to 5,000 feet, and an altitude change was at the helicopter’s discretion. The Citation began their right hand turn, and crossed in front of the helicopter. The helicopter advised the controller that the Citation just “cut” right in front of them.
Date: July 21, 2026
Location: Scottsdale Airport (SDL)
An IFR R44 helicopter departed on the MRRIC1 obstacle departure. The helicopter lifted off and immediately turned right, and also changed frequency without ATC approval. At the time there were 2 other aircraft in the right downwind. The controller trainee initiated a traffic advisory to all aircraft, and the IFR helicopter did not respond, but continued it’s climb. The 2 aircraft in the right downwind were in level flight at 2,500 feet, and within 1/4 of a mile of each other. The leading aircraft turned, and climbed 200 feet to avoid the helicopter.
ARIZONA SAFETY ADVISORY GROUP
JUNE - AUGUST
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 June 12 thru August 7 there were nineteen deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Private Pilot thru ATP, and there were nine out of state pilots, and two foreign pilots.
Note; Many pilot deviations are 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 would hope that pilots would get the message to be more careful in their flying. Some of 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 like to think that the information being presented here is valuable to all pilots, and it will make them safer pilots.
Pilots must be alert, and 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. Always fly with care and forethought, and don’t be part of the
problem.
In summary, the general aviation deviations this reporting period are:
1 Altitude Deviation No Brasher
5 Phoenix Class Bravo Airspace Deviations 2 Brasher
2 Class Delta Airspace Deviations 2 Brasher
4 ATC Instructions 2 Brashers
4 Runway Incursions 2 Brashers
1 Restricted Airspace Incursion No Brasher
2 Un-known Deviations No Brashers
The details of the deviations this month are as follows.
ALTITUDE DEVIATION (1)
July 29 Descending below assigned altitude.
ATP Pilot
Phoenix TRACON (P50)
The Gulfstream was inbound to Scottsdale (SDL), and was given a descent clearance to 5,300, and was told to report the airport in sight. The pilot never reported the airport in sight, and continued the descent in the 5,300 Minimum Vectoring Area. As soon as the aircraft descended below 5,300, the controller issued a safety alert with an immediate climb clearance. The aircraft climbed to 5,300, reported the airport in sight, and was cleared for the visual approach at SDL, and they landed without incident.
PHOENIX CLASS BRAVO AIRSPACE DEVIATIONS (5)
June 15 Entering Phoenix Class Bravo Airspace Without First Having Authorization
Private Pilot
Phoenix TRACON (P50)
The Cessna departed the Glendale Airport VFR, and climbed into the PHX Class B airspace without ATC clearance or establishing two-way radio communication.
June 19 Entering Phoenix Class Bravo Airspace Without First Having Authorization
Private Pilot
Mesa Falcon Field (FFZ)
The Aero Commander departed Falcon Field (FFZ), and turned westbound, and climbed to 3200ft in the 2700ft shelf of the Phoenix Class B Airspace. The Aero Commander then called the TRACON Willy sector controller to get flight following to it’s destination. The controller noticed what the aircraft was doing, and advised the aircraft to descend and turn southbound. The aircraft complied, and they were issued a Brasher by the controller. Prior to departing Falcon Field, the aircraft pilot called the Phoenix TRACON to get a clearance out of Falcon Field, and they were advised that they needed to call Falcon Field tower to get a clearance out of their airspace, and to call the TRACON once southbound. The pilot was advised multiple times to remain outside of the Phoenix Class B Airspace as well as to fly southbound because of the PHX finals. The Pilot had requested a Bravo clearance from the FFZ Tower but they said they could not do that but would give him an expedited frequency change so he could get his Bravo clearance. He was told to fly runway heading by FFZ,
and was not given an expedited frequency change. His destination was to the west of FFZ, and after reviewing the charts, next time he will fly farther south before turning westbound.
July 9 Entering Phoenix Class Bravo Airspace Without First Having Authorization
Commercial Pilot
Phoenix TRACON (P50)
The aircraft entered the Phoenix Class B Airspace without ATC clearance or communication, causing a potential conflict with air carrier traffic on the base leg to final.
July 29 Entering Phoenix Class Bravo Airspace Without First Having Authorization
Foreign Pilot
Phoenix TRACON (P50)
The Airplane called the Biltmore sector controller for flight following at 6,000 feet inside the 3,400 block of the Phoenix Class B Airspace without a Class B clearance. The Biltmore controller gave the aircraft a squawk code and verified their altitude. The Brasher warning was given by the Santan sector controller and the aircraft continued on to their destination without further incident.
July 31 Entering Phoenix Class Bravo Airspace Without First Having Authorization
No Pilot Information
Phoenix TRACON (P50)
The aircraft entered the Phoenix Class B Airspace without a clearance. The aircraft departed Phoenix Deer Valley airport VFR, and contacted ATC for flight following. The aircraft entered the Phoenix Class B Airspace without an ATC clearance. They were advised they needed to descend, and remain below the Bravo Airspace.
CLASS DELTA AIRSPACE DEVIATIONS (2)
June 30 Entering The Class Delta Airspace Without First Establishing Two away
Communications
Private Pilot
Out Of California
Goodyear Municipal Airport (GYR)
An aircraft departed Glendale airport and proceeded southwest entering the the Goodyear airspace at 2,200 ft. The aircraft turned west along the Freeway climbing to approximately 2,600. The tower controller had aircraft on the downwind, and base to the RWY at approximately 2,000 ft. Traffic was given about the errant aircraft. Ground Control reached out to Luke AFB to see if they were talking to the errant aircraft, but they were not. Luke called back to say they had picked him up westbound enroute to Fresno. Ground Control requested that Luke give the Brasher Statement and the Goodyear Tower phone number to the aircraft. Luke Approach delivered the Brasher warning to the aircraft shortly after the incident.
July 6 Entering The Class Delta Airspace Without First Establishing Two away
Communications
ATP Pilot
Mesa Falcon Field Airport (FFZ)
The Falcon Field Tower Controller was working both RWY’s, and a Piper Archer was on an extended right downwind. When the Archer was 1 mile east of the western Falcon Field airspace boundary, the Piper requested a base turn for traffic. The Phoenix TRACON, and Gateway (IWA) had an Embraer Business jet on a long final at 2500 MSL on final to IWA. No coordination had been received by Falcon Field from the Phoenix TRACON or Gateway regarding the flight. Both aircraft landed safely, and IWA issued a Brasher to the the Embraer pilot. The Embraer pilot confirmed that they had the
Piper Archer in sight.
AIR TRAFFIC CONTROL INSTRUCTION DEVIATIONS (4)
June 16 Failure To Follow ATC Instructions
ATP Pilot
Phoenix TRACON (P50)
The aircraft descended on the BRUSR ONE Arrival to 7000 feet at the BRIEZ waypoint. The crossing restriction for BRIEZ is at or above 8000 feet, and at or below 9000 feet. The aircraft in that corridor are allowed to climb to 7000 feet. Additionally, the aircraft failed to turn at KUCOO to a 079°degree track and the VERDE controller initiated radar vectors at that time. On a phone conversation, pilot in command advised the Tower they had the aircraft in the wrong mode, and then admitted to the late turn at KUCOO as well.
June 26 Failure To Follow ATC Instructions
No Pilot Information
Tucson International Airport (TUS)
The aircraft flew through the LIBBY Ground Control Approach without authorization. The aircraft called departure control for a VFR beacon code into Tucson international, and Departure control called Libby Army Air Force Base (FHU) for a point out. FHU requested departure control to issue the Brasher warning, and call FHU after landing. No other traffic was affected., and the aircraft landed at Tucson safely without further incident.
July 17 Failure To Follow ATC Instructions
ATP Pilot
Out Of Idaho
Phoenix Deer Valley Airport (DVT)
The Beechcraft King Air departed Deer Valley Airport on the DVT departure, which requires a climbing northwest bound turn. The aircraft did not fly the departure as published, but continued on the RWY heading eastbound. The pilot flew into a 4,000 ft. Minimum Vectoring Altitude (MVA) at 3,300 ft., then flew into a 4,300 ft. MVA at 3,900 ft. No safety alert was issued by the TRACON Biltmore sector controller, and The Pilot In Command also penetrated the Scottsdale Class Delta Airspace.
July 26 Failure To Follow ATC Instructions
Private Pilot
Out Of Texas
Chandler Municipal Airport (CHD)
The aircraft was southeast of the Chandler airport, and was told to begin a descent, and to turn northbound to make left traffic for RWY 22L. He continued heading southwest for 2 more miles, and didn’t descend. When the Tower Controller prompted him to turn north and make left traffic for 22L again, he turned north, and then crossed the extended centerline two miles upwind of the runways. The Tower Controller saw this, and reached out, and told him to continue now in right traffic to 22R, and gave him traffic of a Cessna in the downwind that he was going to follow. Then, when told to
follow that traffic that he said he had in sight. He started his base, turning into the Cessna he was told to follow. The controller was then required to have him make an immediate left turn back into the downwind. The pilot then landed safely and was issued a Brasher by ground control.
RUNWAY INCURSIONS (4)
June 24 Taxiing On A taxiway Without Authorization
Private Pilot
Out Of Mexico
Phoenix Sky Harbor (PHX)
The Cessna attempted to depart Sky Harbor on RWY 25L without a departure clearance. The aircraft proceeded onto the RWY, and started the departure roll. This was immediately caught by the controller, and the controller cancelled the take-off clearance, and the aircraft exited the RWY. No other aircraft were impacted, and there was no loss of separation. A Brasher issued.
June 27 Taxiing Onto A Runway Without Authorization
Private Pilot
Out of California
Goodyear (GYR)
The Cessna was observed about 4 NM southwest of the Goodyear Class Delta Airspace at 1,600 MSL, and heading northeast. After observing they were not altering their heading to avoid the Class Delta Airspace, the controller attempted to establish two way communication on the Goodyear Tower frequency with no response. Two attempts were made on the guard emergency frequency, 121.5, for them to contact the Goodyear Tower without success. They came within approximately one mile of departing traffic on RWY 21. The Cessna then established a final approach to RWY 3, but RWY 21 was in use. The Cessna landed with no clearance or acknowledgment. The Tower had given the errant aircraft a steady green light to land, and when off the RWY Ground Control gave the aircraft a steady red light to stop. Shortly after, the aircraft contacted Ground Control and received instructions to park at the FBO. When asked if they heard the the Tower transmissions or if he was as aware that they landed the opposite direction of traffic without a clearance, he stated that he thought the Tower was closed.
July 1 Taxiing Onto A Runway Without Authorization
ATP Pilot
Out Of Texas
Scottsdale Municipal Airport (SDL)
The Gulfstream was holding, and was was told to cross the runway to A12. The read back was correct, but the aircraft then taxied onto the runway. Ground Control quickly corrected the aircraft, and the Gulfstream then exited the runway behind a holding Cherokee. There was traffic on a 1-1/2 mile final. Ground Control worked quickly to clear the taxiway and runway of both aircraft. Ground Control issued a Brasher warning to the Gulfstream.
July 17 Taxiing Onto A Runway Without Authorization
ATP Pilot
Out Of California
Scottsdale Municipal Airport (SDL)
At Scottsdale, a Hawker jet crossed the hold short line of the runway without ATC authorization. Ground Control (GC) instructed the Pilot to taxi via Taxiway Alpha to Runway 21. The pilot read back taxi via Taxiway Alpha. The Pilot taxied via Taxiway Alpha and crossed the hold short line of Runway 21. A business jet on final advised the controller that they were going around while on an approximate 1/4 mile final. The Pilot of the Hawker told Ground Control that they were holding short of the runway, and Ground Control instructed them to contact the tower controller. The Hawker Pilot then contacted
the tower controller, and said they were holding short of the runway. The controller advised the Hawker pilot that they were awaiting an IFR release. The other business jet on a final advised the tower controller that they initiated the go around because the Hawker had crossed the hold short line of the runway. A second aircraft initiated a go around outside of a 1/2 mile final.
RESTRICTED AIRSPACE DEVIATION (1)
June 11 Flight Into Restricted Airspace
Commercial/CFI Pilot
Tucson TRACON (U90)
An Arrival Radar controller called an Albuquerque Center Sector controller to point out that a flight was climbing north of the Tomahawk airspace to 14,500. The Albuquerque controller approved, but pointed out that they wanted to protect 11,000 and below for an Embraer E170 holding at 12,000. The Arrival Radar controller asked the flight if they are familiar with the Tomahawk airspace, and the flight responded yes. The Arrival controller instructed the flight to turn south, and remain inside the Tomahawk airspace, and continue the climb. The flight continued northbound and continued to climb.
The Arrival Radar controller issued a pilot deviation to the flight.
UN-DESIGNATED ISSUE DEVIATIONS (2)
July 9 Un-Designated Issue (Runway Incursion ?)
Private Pilot
Phoenix Deer Valley Airport (DVT)
The pilot of a Cessna crossed the threshold of Runway 7R (on a landing attempt for the wrong runway) without ATC authorization. The controller cleared the Cessna for a touch and go on Runway 7L. The readback was correct, but The pilot lined up for and crossed the threshold of Runway 7R. The controller issued a go around to the Cessna. The facility stated in the notes that the aircraft did not touch the pavement of the runway. No other traffic was involved.
July 22 Un-Designated Issue
No Pilot Designated
Out Of Massachusetts
No location of the deviation is specified
Aircraft type is AA-5 Grumman, and no other information is given.
