ARIZONA SAFETY ADVISORY GROUP

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.

PROBLEM UNKNOWN

WING STRIKE TAXIING

NEAR MIDAIR COLLISION’S (NMAC)

There were two Near Mid Air Collision incidents with UAS reported during the period fromMay 15, 2025 thru June 10, 2026, both occurred on May 16.

Date: May 16, 2026

Location: Phoenix Sky Harbor Airport (PHX)

The issue in this NMAC is the unofficial flight of a UAS.

An air carrier reported a UAS on departure from PHX, and no evasive maneuver was needed. There was no impact to the airport operation. The incident was reported to the Airport Police

Date: May 16, 2026

Location: Phoenix Sky Harbor Airport (PHX)

The issue in this NMAC is the unofficial flight of a UAS.

An A320 reported seeing a drone while on final at PHX. The pilot reported they were at 500 AGL and the drone passed 20-40 feet above them

 MAY - JUNE
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 May 15 thru June 10 there were twenty deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Student Pilot thru ATP, and there were ten out of state 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 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 deviationsbcould be attributed to out of state pilots that may not be accustomed to flying in some of the complex/bcrowded 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 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 IFR Deviation 1 Brasher
2 Phoenix Class Bravo Airspace Deviations No Brashers
3 Class Delta Airspace Deviations 2 Brashers
9 ATC Instructions 4 Brashers
3 Runway Incursions No Brashers 

2 Restricted Airspace Incursion 1 Brasher

The details of the deviations this month are as follows.

IFR DEVIATIONS (1)

June 4

Not Flying The IFR Flight Route as Provided
ATP Pilot
Out of Ohio
Yuma International (NYL)

PHOENIX CLASS BRAVO AIRSPACE DEVIATIONS (2)

May 20

Entering Phoenix Class Bravo Airspace Without First Having Authorization
No Pilot Information
Phoenix Sky Harbor Airport (PHX)

The Sirrus departed Glendale Airport, and climbed into the Phoenix Class B Airspace without first obtaining an ATC clearance or establishing two-way radio communication. This resulted in an air carrier having to respond to a TCAS Resolution Alert while on a final to PHX.

May 22

Entering Phoenix Class Bravo Airspace Without First Having Authorization
Private Pilot
Phoenix TRACON (P50)

The Cessna flew into the Phoenix Class Bravo Airspace without a clearance. The aircraft had entered the 4000'-9000' block of Class Bravo Airspace at 4600 feet.

CLASS DELTA AIRSPACE DEVIATIONS (3)

May 17

Entering The Falcon Field Class Delta Airspace Without First Having Authorization or Communication.

Commercial PilotOut Of Nevada

Mesa Falcon Field Airport (FFZ)

The helicopter entered the Falcon Field Class Delta without either authorization or communication, and the tower made numerous attempts to establish communications. Contact was finally made thru the FBO. The pilot was attempting to establish communications on the improper frequency.

May 19

Entering The Deer Valley Class Delta Airspace Without First Having Authorization or
Communication
Private Pilot
Out of
California
Phoenix Deer Valley Airport (DVT)

While enroute to Scottsdale from the Southwest the aircraft flew thru the Deer Valley Class Delta
Airspace without authorization. Because the aircraft was in contact with Scottsdale ATC, Scottsdale was asked to issue a Brasher to the aircraft

May 22

Entering The Goodyear Class Delta Airspace Without First Having Authorization or
Communication.
Commercial Pilot
Goodyear Airport (GYR)

The aircraft entered the Goodyear Class Delta Airspace Without First Having Authorization or Communication, but after entering the delta airspace they decided to contact Ground Control for a clearance. Ground Control immediately advised them to contact the Tower for a clearance. The aircraft then made a 360° turn which placed them into close proximity of a departing aircraft. A traffic warning was issued, and the two aircraft passed within one mile of each other. Communication was established with the offending aircraft, and they were instructed to enter a left down wind traffic pattern, and report at the midfield point. When the aircraft was turning on a final approach they were issued a Brasher warning, and that Ground Control would give them the contact information.

AIR TRAFFIC CONTROL INSTRUCTION DEVIATIONS (9)

May 16

Failure To Follow ATC Instructions
Commercial Pilot
Phoenix TRACON (P50)

The Cessna departed Chandler, and was assigned a runway heading, and climbed to 3,000 feet. On initial contact the aircraft was issued a climb to 7,000 feet. The Cessna began a turn southbound still at 2,200 feet, Queried by ATC of their intentions, the Cessna pilot advised they were going direct to Stanfield. ATC issued a low altitude warning, and an immediate climb to 6,000 feet. The MVA in the area was 3,000.

May 19

Failure To Follow ATC Instructions
Student Pilot
Phoenix Deer Valley Airport (DVT)

The solo student pilot advised the controller that he was ready for departure, and the controller instructed the pilot to hold short of the runway. The pilot repeated to hold short of the runway, but
taxied onto the runway. The controller instructed the pilot to taxi off the runway at the next taxiway, and once clear of the runway, the controller issued the Brasher Warning. No other aircraft were affected by this event.

May 20

Failure To Follow ATC Instructions
Commercial Pilot
Albuquerque Center (ZAB)

A Beechcraft was issued VERNO direct IFADE, descend and maintain 11,000. Briefing was given by an initial controller, and a second controller would advise of the route and altitude. Later the second controller issued "cross IFADE at or above 11,000 cleared the RNAV RWY21 approach into JTC." The pilot then proceeded direct to IFADE which caused the pilot to enter into an Minimum Instrument Area of 12,000. The second controller issued a Brasher Warning.

May 21

Failure To Follow ATC Instructions
Commercial Pilot
Out Of Texas
Albuquerque Center (ZAB)

A TBM700 on the LALUZ6 departure was supposed to fly a 320° heading on departure, but was turning direct to FORPE. The Biltmore controller noticed the unorthodox turn, and immediately issued a low altitude alert, since the aircraft was at approximately at 3000 ft in a 3600 Minimum Vectoring Area. Once the aircraft was above the 3600 MVA, the Biltmore controller vectored the aircraft and eventually gave the pilot a clearance on course.

May 23 Failure To Follow ATC Instructions
ATP Pilot
Out of Florida
Phoenix TRACON (P50)

A Gulfstream departed Scottsdale on the LALUZ6 departure. The departure controller instructs the pilot to turn right to a heading of 335° when off the runway. The Gulfstream became airborne and turned left southbound.

May 24

Failure To Follow ATC Instructions
No Pilot Information
Albuquerque Center (ZAB)

A Gulfstream checked in with a restriction to cross SCOLE at FL250. The aircraft was high at SCOLE descending out of FL335 for FL250, and the controller questioned the pilot again confirming he had the restriction. The pilot confirmed his restriction again, SCOLE at FL250. The controller confirmed the aircraft would not make his restriction, and then issued a descent to FL250 once the aircraft was over SCOLE. A point was made out to the controller before an airspace violation happened. The Brasher warning was issued to the pilot.

May 25 Failure To Follow ATC Instructions
ATP Pilot
Out Of California
Phoenix TRACON (P50)

The controller requested if the Citation had Scottsdale Airport in sight, and pointed out both Phoenix Deer Valley airport, and Scottsdale airports. After the pilot confirmed they had Scottsdale in sight, they were issued a visual approach clearance to the Scottsdale runway, and they were switched to the Scottsdale tower. The Citation then turned and descended into the Deer Valley Class D Airspace. The controller advised Scottsdale to break them out, and the pilot was then set up again for the runway at Scottsdale.

May 28

Failure To Follow ATC Instructions
ATP Pilot
Out Of Texas
Phoenix TRACON (P50)

The Falcon jet failed to make the turn at the KUCOO intersection as instructed on the arrival. ATC had to instruct the Falcon twice to turn to a heading of 080°. The Falcon was issued a 230° heading when cleared for the visual approach but the Falcon flew a 250° heading, and did not join the final until 1 mile from the runway.

June 6

Failure To Follow ATC Instructions
Commercial Pilot
Prescott Municipal Airport (PRC)

The Cessna was inbound to the airport, and was given a pattern entry of left base to a 5-mile final to the runway which was correctly read back. The Cessna then proceeded directly to the tower to enter the traffic pattern. The aircraft was issued a Brasher Warning by ground control.

RUNWAY INCURSIONS (3)

May 16

Taxiing On A taxiway Without Authorization
No Pilot Information
Prescott Airport (PRC)

A Cessna had finished their runup, and asked if the regional jet in front of them was ready, but the controller advised them the regional jet had a wait time of 8 minutes. The Cessna said they wanted a full-length departure, and they didn't want to wait until the regional jet departed. Ground advised them to hold short of RWY 21L at Charlie 6, and they would eventually get them across the runway to taxiway Delta, and set them up for a full-length departure from Delta 7. The Cessna read back of hold short instructions was not legible. Ground control re issued the hold short instructions. Again the read back was illegible. Ground Control sees them passing hold bars to the runway, and gives a "Hold Position" instruction, and coordinates a valid crossing with the tower controller. No aircraft were on short final for 21L, and a safe runway crossing was given by the tower controller. The Cessna was then taxied in position for the runway full-length departure from Delta 7.

May 19

Taxiing Onto A Runway Without Authorization
ATP Pilot
Out of California
Mesa Falcon Field (FFZ)

The pilot of the Cessna was on the north side of the airport, and was assigned the south RWY for takeoff, and was told to hold short of the north RWY at E6 with a correct read back. The pilot was advised to run up in the run up area for the north RWY. The Pilot advised Ground Control the run up was complete, and Ground Control instructed the pilot to continue taxiing and monitor tower 119.7. The Cessna crossed the north RWY without a clearance to cross. The north tower controller saw the aircraft moving and instantly sent a C-172 that was on approach to the north RWY to go around.

May 21

Taxiing Onto A Runway Without Authorization
No Pilot Information
Phoenix Deer Valley Airport (DVT)

Ground Control was issuing progressive taxi instructions to a Cessna. The pilot was holding short of the runway, and Ground Control instructed the Cessna to cross the runway at Taxiway C11, but the intention was that the aircraft was to stop at the runway hold short line, and wait for tower instructions to cross the runway. The pilot read back, was to cross the runway, and the pilot crossed the runway, and continued taxiing. ATC observed the pilot crossing the hold short line of the runway, and the tower controller issued a go around to a Maul that was on a short final. The ground controller had instructed the pilot to hold short of Runway 7L, but the pilot did not read back the hold short of Runway 7L instruction. Ground control advised the pilot that they had entered an active runway.

RESTRICTED AIRSPACE INCURSION (2)

May 18

Flying In Restricted Airspace Without Approval
Commercial Pilot
Out Of Alaska
Albuquerque Center (ZAB)

LUF RAPCON called Albuquerque Center, and said they had a MODE C intruder in the restricted area R2301E at 8500. The LUF RAPCON asked if they would track the aircraft and if he calls Albuquerque Center, Brasher the pilot for violating the airspace. The aircraft was a C-180, VFR, who called the Albuquerque Center sector 42 controller later, and he was informed they had violated the restricted airspace. A Brasher warning was issued.

May 29

Flying In Restricted Airspace Without Approval

Commercial Pilot
Out Of New Mexico
Albuquerque Center (ZAB)

The TBM pilot was flying at FL260 direct to JUDTH, and KMYF when the controller gave them a reroute to fly after JUDTH - J2 - IPL - KMYF, with a good read back, to avoid the active restricted airspace R2301W which was active at FL500, and below. The pilot overflew J2, and needed to be turned to the right to avoid R2301W. The aircraft flew within approximately 1.68 miles of the R2301W boundary, which was within the 3 miles of the protected airspace.