by 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 October 10 through November 14, 2024, there were twenty-three pilot deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Student Pilot through ATP, and there were nine out of state pilots, and two military pilots that committed these deviations. Of the twenty-three deviations reported, there was a need to issue seventeen Brashers.
Note: A controller will 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.
Pilots need to listen carefully to ATC instructions and comply with them, and if you can’t comply, tell ATC why you can’t. Also, when flying in controlled airspace, pilots should never be creative but talk to ATC before they do something that differs 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 fly with care and forethought, don’t be part of the problem.
The details of the deviations this month are as follows:
IFR DEVIATION (4)
10/7 Route Deviation
ATP/CFI Pilot
Out of Texas
Albuquerque Center (ZAB)
The airplane had been cleared via after SSKEE direct GUP direct KJAS. The controller observed the aircraft was off course and asked where they were navigating. The pilot stated they were direct JAS. The aircraft did not fly the routing as cleared. The event occurred near Wolf Crossing in Coconino County. A Brasher was issued.
10/14 Flight Plan Deviation
Comm/CFI Pilot
Albuquerque Center (ZAB)
The aircraft was inbound to CGZ, and the controller advised the pilot that radar services were terminated and that he should close his flight plan via the frequency he was on or through flight service. The pilot acknowledged the clearance, but ZAB ATC did not receive the aircraft’s cancellation. A Brasher was issued. Later the pilot stated that he canceled through ForeFlight.
10/17 Route Deviation
Private Pilot
Out of Utah
Albuquerque Center (ZAB)
The aircraft had been cleared via direct to PRC. The controller observed the aircraft was off course and asked the aircraft where they were navigating. The pilot advised they were flying direct PEVYU (an initial approach fix to PRC). The aircraft had made an unauthorized turn direct to PEVYU. A Brasher was issued.
10/24 Departure Deviation
ATP Pilot
Out of Virginia
Phoenix TRACON (P50)
The pilot deviation was reported by the TRACON when the pilot didn’t comply with the Scottsdale LALUZ Departure Procedure. A Brasher was issued.
CLASS BRAVO AIRSPACE DEVIATION (3)
10/14 Entering Class Bravo Airspace Without Authorization
Student Pilot
Phoenix TRACON (P50)
The Piper violated the Phoenix Class Bravo Airspace approximately 16 miles northwest of the PXR VOR at 6,600 MSL in the 6,000-9,000 foot box. A Brasher given.
10/30 Entering Class Bravo Airspace Without Authorization Military Pilot
Phoenix TRACON (P50)
The pilot deviation was reported by the Phoenix TRACON when two Blackhawk helicopters entered the Phoenix Class Bravo Airspace without authorization. A Brasher was issued by the San Tan Sector Controller.
11/5 Entering Class Bravo Airspace Without Authorization
Comm/CFI Pilot
Out of Texas
Phoenix TRACON (P50
The Cirrus violated the Phoenix Class Bravo Airspace in the 7,000-9,000 block northeast of Sky Harbor airport. The pilot had climbed from 8,100-9,200 feet, then descended back down to 7,800 feet in the 8,000-9,000 block. A Brasher issued.
CLASS DELTA AIRSPACE DEVIATION (7)
10/10 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Mesa Falcon Field (FFZ)
The deviation was reported by Falcon Field when the Cessna entered the Falcon Field Class Delta Airspace without first establishing two-way radio communications. The Brasher was issued by Chandler (CHD).
10/12 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Comm/CFI Pilot
Mesa Falcon Field (FFZ)
The aircraft entered the Falcon Field Class Delta Airspace without first establishing two-way radio communications. A Brasher was issued.
10/16 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Pilot Certificate Unknown
Out of California
Flagstaff (FLG)
The Cessna called inbound from the west and was given entry instructions. The airplane did not acknowledge, and ATC reached out multiple times on all frequencies, and guard. The Cessna tried to make a radio check as well. The Cessna switched to making calls in the blind on the downwind. The Cessna then called on ground and was given taxi instructions. At the end of the runway, the Cessna again made a CTAF formatted transmission and departed to the southwest. ATC tried to reach out again with no response.
10/22 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Out of Alaska
Prescott (PRC)
The pilot deviation was reported by the Prescott ATC when a Cessna entered the Prescott Class Delta Airspace without first establishing two-way radio communications.
10/24 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
ATP/CFI Pilot
Out of Colorado
Flagstaff (FLG)
The pilot deviation was reported by the Flagstaff ATC when a Piper entered the Flagstaff Class Delta Airspace without first establishing two-way radio communications. A Brasher was issued
10/25 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Military Pilot
Mesa Falcon Field (FFZ)
The pilot deviation was reported by the Phoenix TRACON when a T38 entered the Falcon Field Class Delta Airspace without first establishing two-way radio communications. The pilot, and instructor of the T38, declined to give name, phone number, and pilot certificate number. They informed ATC that they are in training from Shepard Air Force Base.
10/27 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Out of North Dakota
Mesa Falcon Field (FFZ)
The pilot deviation was reported by Falcon Field ATC when a Husky entered the Falcon Field Class Delta Airspace without first establishing two-way radio communications.
RUNWAY INCURSION (3)
10/20 Entering A Runway Without Authorization
Private Pilot
Phoeniz/Mesa GatewayAirport (IWA)
The pilot deviation was reported by Gateway Airport (IWA) when a Grumman Tiger entered the Center Runway and departed without ATC authorization while a Piper was on short final.
10/22 Entering A Runway Without Authorization
Comm/CFI Pilot
Prescott (PRC)
A Cessna was instructed to taxi back to the ramp via TWY D, a left turn onto RWY12, TWY F3, TWY F. The Cessna read back the taxi instructions correctly. A tower controller then noticed the Cessna turn right onto TWY D3 towards RWY 21L, and told the Ground Controller (GC). GC instructed the Cessna to stop and turn around. The tower controller had to cancel the takeoff clearance of an Embry Riddle airplane because the Cessna was in the Runway Safety Area. The Cessna then told the GC the instructions that they had received and read them back correctly. GC told the Cessna that that was correct, but they had just turned onto TWY D3 and almost onto the active runway, and then issued them the Brasher warning.
11/1 Entering A Runway Without Authorization
Comm/CFI Pilot
Prescott (PRC)
A Cessna had conducted a touch and go to Runway 21L, and on the upwind, the Local Controller (LC) instructed them to turn crosswind over the campus. There was no response. The controller attempted to contact The Cessna multiple times with no response as the Cessna proceeded to fly a downwind and base turn to Runway 21L. ATC advised that a light gun signal was used to instruct the Cessna to make a full stop and also to exit the runway. The Cessna conducted a touch and go. The instructor pilot of Cessna contacted the controller while in the downwind again and advised that they had not been able to hear anything in the cockpit. A Brasher was issued.
AIR TRAFFIC CONTROL INSTRUCTIONS (4)
10/2 Failure To Follow Air Traffic Control Instructions
Pilot Certification Unknown
Phoenix Sky Harbor (PHX)
The pilot deviation was reported by Phoenix Sky Harbor when the Pilatus failed to follow the ATC assigned departure headings.
10/25 Failure To Follow Air Traffic Control Instructions
Comm/CFI Pilot
Prescott Airport (PRC)
The Cessna was instructed to follow another Cessna ahead in the downwind. The pilot reported the aircraft was in sight and would follow. They then turned base inside of the aircraft they were told to follow. The controller told them to "Go around and over fly the runway." The controller gave them the Brasher warning after they landed.
10/29 Failure To Follow Air Traffic Control Instructions
Private Pilot
Out of California
Phoenix TRACON (P50)
The Beechcraft was on departure from Mesa Falcon Field (FFZ), and were given 3,000 MSL as the initial altitude, however the Pilot climbed to 5,000 feet. The controller had to stop an air-carrier’s descent because of the Beech's climb. A Brasher was issued.
11/4 Failure To Follow Air Traffic Control Instructions (& NMAC)
ATP/CFI Pilot
Phoenix Deer Valley Airport (DVT)
A Piper was on the upwind for RWY 25L, and a Cessna was on the upwind for RWY 25R. At approximately 1NM upwind, The Cessna began drifting south into the upwind of RWY 25L. At approximately 1.7NM upwind the Cessna's target overlapped the Piper’s. Closest proximity was 0.03 NM and 100 feet. At the same time the Piper informed the controller that there was an a/c near them on their ADS-B. The controller acknowledged, and stated they could not see the altitude due to the targets overlapping, but suggested the Piper maintain their current altitude. The Piper advised the controller they were going to continue climbing, and wanted to report it as a Near Miss, and advised the controller the aircraft was turning towards them. The controller stated, "Traffic alert use caution." The controller stated they issued this statement but did not know what else to do or say as far as a traffic alert goes because the Piper had the a/c in sight. A Brasher was issued to the Cessna.
TFR DEVIATIONS (2)
10/24 Entering A TFR Without Authorization
Private Pilot
Phoenix TRACON (P50)
The Cessna was observed operating in the vicinity of Pegasus airpark on a 1200 transponder code inside the 30 mile VIP TFR. A Phoenix/Mesa Gateway airport (IWA) controller reached out, and was able to contact the aircraft, and advise them to make a full stop. They also issued the Brasher.
10/25 Entering A TFR Without Authorization
ATP Pilot
Phoenix TRACON (P50)
A Bonanza entered the 30 mile VIP TFR, and no communication was established with ATC. They were identified, and contact was initiated with Mesa Falcon Field (FFZ) about 5 miles after entering the TFR. FFZ had them return to the Phoenix TRACON NAJAVO sector controller, and the NAVAJO controller identified them by assigning a discrete code. The aircraft continued on to land at Falcon Field (FFZ), and FFZ issued the Brasher statement.