ARIZONA SAFETY ADVISORY GROUP
SEPTEMBER THRU OCTOBER
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 September 10 thru October 15 there were twelve deviations reported by
the FAA SDL FSDO. Of the twelve deviations there were 9 Brashers issued. These deviations were
committed by pilots with certificates ranging from Private Pilot thru ATP, and there were four out of
state pilots, and one Military pilot.
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 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 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. 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 (IFR) 1 Brasher
1 Phoenix Class Bravo Airspace Deviation 1 Brasher
8 ATC Instructions 6 Brashers
1 Runway Incursion 1 Brasher
1 Restricted Airspace Deviation No Brasher
The details of the deviations this month are as follows.
ALTITUDE (IFR) DEVIATION (1)
September 16
Flying At An Unassigned Altitude
No Pilot Information
Albuquerque Center (ZAB)
The Albuquerque Center information was showing the routing KSDL, YOTES6, JARPA, ALS, DUUZE,
HLC, PWE, /, KIAD in their machine. The controller noticed the aircraft was turning off course, and
questioned the pilot. The pilot said he was going direct to a fix called MARME, then SPRINGFIELD.
Controller coordinated with other areas and eventually the aircraft was put on the correct routing. The
airplane was issued the Brasher warning.
PHOENIX CLASS BRAVO AIRSPACE DEVIATION (1)
September 21
Entering Phoenix Class Bravo Airspace Without First Having Authorization
Private Pilot
Phoenix TRACON (P50)
The aircraft entered the Class B airspace without a clearance approximately 5.5 miles south of PHX
at 5,000 Feet. The aircraft continued southeast bound climbing to 7,500 feet in Class B Airspace
without contacting a controller. A Brasher issued
AIR TRAFFIC CONTROL INSTRUCTION DEVIATIONS (8)
September 11
Failure To Follow ATC Instructions
Private Pilot
Mesa Falcon Field (FFZ)
The aircraft entered the airspace from the northeast, and repeatedly ignored instructions from the
controller. The aircraft landed at Falcon Field, and was given the Brasher warning on Ground Control.
The pilot called, and said he was unfamiliar with the area, and became disorientated. He didn’t join
the downwind as instructed, and crossed a final at pattern altitude without instructions. He was told to
fly on a heading, but then turned without permission, and almost cut off landing traffic.
September 13
Failure To Follow ATC Instructions
Commercial Pilot
Scottsdale Airport (SDL)
The aircraft was on a one mile final when the controller issued a landing clearance. The aircraft
requested a missed approach, and the controller issued a go-around clearance and it was read back
correctly. The aircraft then flew through the final approach corridor, and exited the airspace, and made
a 180-degree turn to return to land. The controller then instructed the aircraft to enter a midfield right
downwind, and expedite the decent to pattern altitude for traffic, and then issued a traffic advisory.
The aircraft did not descend, and did not response to several transmissions. The controller finally got
the aircraft to respond, and amended the instructions to a right base to avoid traffic. The aircraft
eventually landed without further issue. On Ground Control, the controller issued several instructions,
and the aircraft then changed frequencies without permission. They refused to follow instructions, and
told Ground Control what they were going to do instead. Eventually Ground Control taxied the aircraft
to the run up area and issued the Brasher warning. During a conversation with the tower supervisor,
the pilot said they were a licensed pilot but could not provide a complete pilot certificate number only
a partial number, and promised to call the tower back. She said she did not comply with ATC
instructions because she was unfamiliar with the airspace, and the CFI onboard was no help.
September 17
Failure To Follow ATC Instructions
Comml/CFI Pilot
Albuquerque Center (ZAB)
The Piper Cherokee was flying the practice approach RNAV RWY23 into Coolidge, and the controller
observed the Piper turn north rather than flying the missed approach which put them below the MIA in
the area. The controller issued a low altitude alert, and instructed the Piper to rejoin the missed
approach, and the Piper complied. A Brasher warning was issued. The pilot said there was VFR
traffic circling to land for a touch and go. He turned to the north to avoid the traffic. The Piper
attempted to contact Center when they heard Center calling them.
September 20
Failure To Follow ATC Instructions
ATP Pilot
Out Of Florida
Phoenix TRACON (P50)
A Bombardier Challenger was assigned an altitude of 5,000, and was looking for Scottsdale for a
visual approach. The pilot descended on their own to 4,600, without a clearance to do so. It was
unknown if any Minimum Vectoring Altitudes were violated.
September 21
Failure To Follow ATC Instructions
ATP Pilot
Out of Colorado
Phoenix TRACON (P50)
The controller gave a Beech Premier a turn back on course, and an amended altitude to maintain
FL370 with a good read back. Traffic was an air carrier that was level at FL380. An Albuquerque
Controller had the Premier to climb above FL370, and the controller immediately instructed them to
maintain FL370 and to turn 20 degrees right to provide a loss of separation with traffic. On the pilot
phone call, the pilot said they forgot to put FL370 into their Flight Management System. A Brasher
Warning was issued.
September 24
Failure To Follow ATC Instructions
No Pilot Information
Albuquerque Center (ZAB)
A Phoenix TRACON Controller advised the Albuquerque Center Controller that an aircraft was spilling
out of the GLOBE SAA. The Albuquerque controller advised that the airplane had spilled out earlier,
and a Brasher warning had been issued. The pilot said they knew they were close to the edge and
were being pinched by the weather. They were trying to complete a low altitude exercise before
climbing to a higher altitude above the weather. Pilot was apologetic for spilling out.
September 27
Failure To Follow ATC Instructions
ATP Pilot
Out Of California
Albuquerque Center (ZAB)
The Hawker was issued a crossing restriction to cross ELLDA at FL300 which the pilot read back
correctly. The aircraft was at FL300, and requested FL160. The controller advised the aircraft to
contact LA Center, which the pilot read back. Immediately after the read back the Hawker was seen
descending out of FL300. Multiple attempts were made to amend the aircraft's altitude to FL280,
which was successful. The LA Center issued the pilot the Brasher warning.
ATC received a call at the Office Manager In Charge (OMIC) desk, and the Hawker thought that since
he was cleared for the arrival, that he could descend on that arrival. OMIC explained that ATC
assigns altitudes when aircraft are flying arrivals. Pilot also stated that they "request 160", they were
letting ATC know they were descending. OMIC explained that a "request" is taken as a request by
ATC. All altitudes need to be issued by ATC. There seemed to be a lot of confusion on being cleared
for the arrival and being cleared to descend via that arrival.
September 30
Failure To Follow ATC Instructions
Military Pilot
Tucson TRACON (U90)
Two F-16’s were on radar vectors for the initial at Tucson International, and the lead F-16 was told to
maintain 6,000. A Citation was on radar vectors behind the F-16s at 7,000. The F-16s were observed
climbing on their own, and the controller observed the climb and told them to turn and descend back
to 6,000. The F-16s were observed at 6,500 vertical and 3.5 miles was observed lateral with the
Citation. The lead pilot called and was transferred to the recorded line. He was asked for his name,
and he refused to give it, and also only gave the duty desk phone number at the 162nd guard unit.
RUNWAY INCURSION (1)
September 13
Taxing Without ATC Instructions
No Pilot Information
Out Of Oregon
Phoenix Phoenix Sky Harbor (PHX)
A Cessna Citation was issued instructions to cross RWY 25L at the TWY H7 intersection, then to taxi
to RWY 25R via TWY F by the South Controller. The Citation read back the instructions correctly, and
the Citation was observed turning onto TWY F after crossing RWY 25L at H7. Another aircraft was
then issued a takeoff clearance on RWY 25R. As the other aircraft was departing, an alert was
triggered due to a target on TWY F10. The South controller immediately instructed the Citation to
stop, and pilot stated that he had stopped. The Citation was observed past the hold short lines for
RWY 25R at F10 intersection. It was unknown if the Citation crossed or encroached over the RWY
25R edge line as the other aircraft rolled by on it’s departure. There was no time to issue a traffic
advisory to the other aircraft or cancel it’s takeoff clearance. A Brasher warning issued to the Citation
on the Ground South frequency.
RESTRICTED AIRSPACE DEVIATION (1)
September 9
Flight Into Restricted Airspace
Private Pilot
Out Of North Carolina
Phoenix TRACON (P50)
An Experimental Aircraft departed VFR from Mesa Gateway Airport, and the aircraft entered
Restricted Airspace R2310A without authorization. R2310A was active at the time and ATC had
advised the aircraft that the restricted airspace was active.
NEAR MIDAIR COLLISION’S (NMAC)
There were two Near Mid Air Collision incidents reported during the period from September 10, 2026
thru October 15, 2026. One occurred on September 22, and the other occurred on September 26,
2026.
Date: September 22, 2026
Location: Phoenix Deer Valley Airport (DVT)
A controller reported that they believed they saw a black, and multi-rotor UAS, orbiting in the
downwind. They stated that a Piper Cherokee had passed within 5 feet of the suspected UAS.
Subsequently the controller, and the Cherokee reported the UAS in the same location. No evasive
maneuvers were reported by the reporting aircraft.
Date: September 26, 2026
Location: Phoenix Sky Harbor Airport (PHX)
An Embraer Regional Jet was on a 5 mile final to the runway, and at 3,200 feet they reported a drone
that passed 50' directly in front of them going from left to right.