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 February 16, 2024, through March 14, 2024, there were 26 pilot deviations reported by the FAA SDL FSDO office. These deviations were committed by pilots with certificates ranging from Student Pilot through ATP, and there were nine out of state pilots that committed these deviations. Of the twenty-six deviations reported, there was a need to issue ten 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 follow 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.
The details of the deviations this month are as follows:
IFR DEVIATION (8)
2/18 IFR SID Deviation
Private Pilot
Out of Texas
Phoenix TRACON (P50)
The pilot deviation was reported by P50 when the Malibu didn’t fly the DVT3 departure as published.
2/23 IFR SID Deviation
Private Pilot
Out of New Mexico
Phoenix TRACON (P50)
The TBM-700 departed from Deer Valley (DVT) but didn’t fly the published departure procedure. The controller attempted to correct them by turning them immediately to a 360° heading, however they continued eastbound, and climbed above their assigned altitude of 6,000 ft to 6,800 ft. The controller eventually got the TBM to turn around to a northwest heading, and away from the Scottsdale traffic. The TBM was climbed to an assigned altitude and sent on course.
2/15 IFR Route Deviation
Unknown Pilot Certification
SoCal (SCT)
The SR20 missed the turn after PSP intersection onto V388. They continued off course until entering an 11,000 Minimum Vectoring Altitude area at 10,000. ATC issued instructions for them to turn out of the higher terrain area. The Brasher statement was later issued by SCT.
2/19 IFR Route Deviation
Private Pilot
Out of Colorado
Phoenix Sky Harbor (PHX)
The SR-22 was issued a heading of 010° at the departure end of RWY 7R, and the aircraft was instructed to contact departure, and a correct read back was received. The aircraft was observed making a climbing left turn flying back over the airport. After appropriate coordination with the TRACON, the aircraft was then issued a northbound heading of 010° on its intended departure course.
2/23 IFR Route Deviation
ATP Pilot
Albuquerque Center (ZAB)
The ZAB controller observed the Honda Jet off course and turned the aircraft to a 345° heading. The aircraft did not fly the routing as cleared which resulted in the aircraft violating the 3-mile protected airspace of the GLADDEN ATCAA which was active FL400 and below. A Brasher was issued.
2/27 IFR Altitude Deviation
ATP Pilot
Out of Massachusetts
Phoenix TRACON (P50)
The deviation was reported when the Challenger 350 climbed above his assigned altitude. There was no loss of separation.
3/10 IFR Altitude Deviation
Comm./CFIPilot
Phoenix TRACON (P50)
The Cessna was flying IFR at 12,000 ft, and the pilot said he descended to 11,500 because he noted the OAT and the clouds ahead of him, and wanted to avoid icing. The controller advised the pilot that he must inform ATC if he needs something other than the assigned instructions. A Brasher was issued.
2/21 IFR NORDO
Comm./CFI Pilot
Albuquerque Center (ZAB)
The Piper was at 5,000 feet on assigned heading of 190°. The Albuquerque controller cleared the Piper direct Stanfield and the aircraft did not reply to that call. The controller cleared the Piper to contact ZAB on 125.4. The aircraft did not respond to that call, nor any of the subsequent attempts made by both the Phoenix TRACON or ZAB. Later the Piper called the ZAB controller and was issued a low altitude alert and a climb to 7,000 feet, and a Brasher was issued.
CLASS BRAVO AIRSPACE DEVIATIONS (2)
2/13 Entering Class Bravo Airspace Without First Obtaining A Clearance
Comm,/CFI Pilot
Out of California
Phoenix TRACON (P50)
The SR22 called the TRACON Biltmore Controller for VFR flight following to southern California. The pilot was told to remain clear of DVT’s Delta airspace and Phoenix Class Bravo Airspace. The pilot acknowledged the instruction, but the SR22 climbed into Phoenix Class Bravo airspace without a clearance to do so. The Biltmore Controller read the pilot the Brasher notice.
2/22 Entering Class Bravo Airspace Without First Obtaining a Clearance
Unknown Pilot Certification
Phoenix TRACON (P50)
The pilot deviation was reported when the Cessna entered the Phoenix Class Bravo Airspace without authorization.
CLASS DELTA DEVIATIONS (5)
2/3 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Chandler Airport (CHD)
The controller noticed the Cessna in the Chandler Delta Airspace 2 miles west of the airport. With the initial call, the controller reached out to the aircraft. The aircraft responded and was issued landing sequence instructions. The aircraft landed without incident, and there was no conflict with other aircraft. A Brasher was issued.
2/15 Entering Class Delta Airspace Without First Establishing Communication
ATP Pilot
Mesa Falcon Field (FFZ)
The pilot deviation was reported by FFZ tower when the helicopter entered the FFZ Class Delta Airspace without first establishing two-way radio communications.
3/1 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Out of Nevada
Mesa Falcon Field (FFZ)
The Cessna entered the FFZ Class Delta Airspace without first establishing two-way radio communications which resulted in a near mid-air collision with local traffic.
3/3 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Mesa Falcon Field (FFZ)
The pilot deviation was reported on the FFZ Emergency Frequencies when the Piper Cherokee entered the FFZ Class Delta Airspace without establishing two-way radio communications.
3/7 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Mesa Falcon Field (FFZ)
The pilot deviation was reported by the FFZ tower when the SR-22 entered the FFZ Class Delta Airspace without establishing two-way radio communications.
ATC INSTRUCTIONS (7)
2/15 Not Complying With ATC Instructions
Commercial Pilot
Mesa Falcon Field (FFZ)
The pilot deviation was reportedly FFZ when the SR-22 didn’t fly his assigned heading.
2/16 Not Complying With ATC Instructions
ATP/CFI Pilot
Out of Texas
Mesa Falcon Field (FFZ)
The pilot deviation was reported by the FFZ tower when the Cessna didn’t follow ATC instructions.
2/22 Not Complying With ATC Instructions
Private Pilot
Mesa Falcon Field (FFZ)
The Bonanza entered Taxiway Bravo without ATC authorization. The Bonanza landed on Runway 22L and was instructed by the controller to continue with no delay to Taxiway Delta 5 and contact Ground Control. The Beech read back “Contacting Ground.” The Bonanza turned right on Taxiway Bravo instead of going down to turn left on Taxiway Delta 5. The controller asked the pilot what they were doing, and instructed them to continue down the Runway to Taxiway Delta 5. The Bonanza turned back onto the runway and continued down to Taxiway Delta 5.
2/23 Not Complying With ATC Instructions
Private Pilot
Out of Colorado
Mesa Falcon Field (FFZ)
The pilot deviation was reported by FFZ when the aircraft entered Taxiway Delta 5, and taxied to parking without ATC authorization.
2/18 Not Complying With ATC Instructions
Comm./CFI Pilot
Phoenix TRACON (P50)
The Piper was VFR, and receiving flight following on their way to Lake Havasu. The TRACON Willy Controller instructed the Piper to maintain 6,000 ft, but the Piper climbed to 7,000 ft. The controller told them again to maintain 6,000 ft. but the Piper continued climbing, and did not listen to ATC instructions. The Piper was issued the Brasher warning.
2/28 Not Complying With ATC Instructions
Private Pilot
Out of Colorado
Phoenix/Mesa Gateway Airport (IWA)
The pilot deviation was reported by IWA when the Cessna entered taxiways Bravo and Yankee 2 without ATC authorization. Ground Control instructed the pilot to stop because they hadn’t received taxi instructions, and issued the Brasher warning.
3/4 Not Complying with ATC Instructions
Unknown Pilot Certification
Scottsdale Airport (SDL)
The pilot deviation was reported by SDL Tower when the regional jet turned left on taxiway Alpha without ATC authorization.
RUNWAY INCURSIONS (4)
2/14 Entering A Runway Without Authorization
Mesa Falcon Field (FFZ)
A police SUV entered a taxiway and crossed a runway without permission or radio communication.
2/18 Taxied past The Runway Hold Short Bars
Private Pilot
Tucson International Airport (TUS)
Ground Control taxied the SR-22 to RWY 12 at Taxiway A4, but the airplane crossed the Hold Short Bars prior to contacting the tower controller for departure. The SR-22 departed and was given a Brasher warning.
2/24 Taxied past The Runway Hold Short Bars
Private Pilot
Tucson International Airport (TUS)
Ground Control (GC) taxied the Cessna to Runway 12, and the read back was correct. The Cessna had taxied across the runway hold short line and also the runway edge line, and onto Runway 12. GC instructed the Cessna to make a 180° turn and exit the runway. GC issued the Brasher warning.
2/22 Attempting To Takeoff On The Wrong Runway
Student Pilot
Tucson Ryan Field (RYN)
The Piper was cleared for takeoff on RWY 6R, but started to takeoff on RWY 33. The tower canceled the takeoff clearance, and the aircraft safely got off the runway at taxiway D3.