by Jim Timm


These pilot deviations need to be examined to determine if a common threat exists that we should address to help reduce the number of deviations that occur, and thus enhance aviation safety.

In the reporting period from July 14 through August 10 there were ten pilot deviations reported by the FAA SDL FSDO office. 

These deviations were committed by pilot certificate levels ranging from Student through ATP, and of these ten deviations reported, there was a need to issue seven Brashers. In this period’s report there were also two out-of-state pilots that committed deviations.

Note: A controller will issue a Brasher notification 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 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. 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. Know what airport runway markings mean and comply with them. Please fly with care and forethought.

The details of the deviations this month are as follows:




7/12      IFR Standard Instrument Departure (SID)

             Private Pilot

             Out of Oklahoma

             Albuquerque Center (ZAB)

The TBM had been cleared via the MAYSA7 departure. The Albuquerque controller observed the TBM turn about 20 degrees off course, and the controller vectored the aircraft to keep it from violating the GLADDEN MOA protected airspace. A few minutes later the ZAB Controller again observed the TBM turn about 20 degrees off course and the controller again vectored the aircraft away from the BAGDAD MOA. This unauthorized turn resulted in the TBM violating the 3-mile protected airspace of the BAGDAD MOA. The event occurred near Wickenburg and a Brasher was issued. 


7/28 IFR - Route


Albuquerque Center (ZAB)

The Lear Jet had been cleared from Scottsdale (SDL) via the JUDTH7 Route. The JUDTH7 instructs the aircraft to proceed, after GBN, direct to JUDTH. After the Lear Jet had passed GBN, the ZAB controller observed the aircraft was off course and turned the Lear away from the restricted area 2301E. The Lear Jet made an unauthorized turn resulting in the aircraft violating the 3-mile protected airspace of restricted area R2301E. The event occurred near Gila Bend, and a Brasher was issued.


8/2 IFR Standard Instrument Departure (SID)

ATP Pilot

Albuquerque Center (ZAB)

The Diamond DA50 had been cleared via the MAYSA7 until RRSTA. Before arriving at RRSTA, the ZAB Controller observed the airplane make an approximate 35 degree left turn. The controller quickly turned aircraft back 30 degrees to the right. The DA50 had made an unauthorized turn which resulted in the aircraft violating the 3 mile protected airspace of the BAGDAD Special Use Airspace (SUA), which was active. The aircraft got within 0.75 miles of the area. The event occurred near Willow Spring in Yavapai County. A Brasher was issued.




7/19 Entering Class Delta Airspace Without First Establishing Communication

Student Pilot

Williams Gateway (IWA)

The Piper entered the IWA Class D Airspace without first establishing two-way communications. There was no loss of separation with other aircraft, and the controller requested that the Phoenix TRACON (P50) issue the pilot a Brasher.


7/26 Entering Class Delta Airspace Without First Establishing Communication

Student Pilot

Phoenix Deer Valley Airport (DVT)

The pilot deviation was reported by the DVT tower when the Piper aircraft entered the DVT Class D Airspace without first establishing two-way radio communications.




7/12 Taking Off On A Runway Without Authorization

Private Pilot

Scottsdale Municipal Airport (SDL)

A Cessna called the controller and advised that they were at Taxiway Alpha 16 and ready for departure. After approximately a one minute delay, the controller instructed the Cessna to hold short of Runway 21, and the read back was correct. The pilot later asked the controller if they wanted them to hold short of Runway 21, and the controller answered affirmative, hold short of Runway 21. The Cessna then taxied onto Runway 21, and held in position on the runway. The controller asked the Cessna if they were the one on the runway, and the pilot answered in the affirmative. The controller then cleared the Cessna for takeoff on Runway 21, and issued the Brasher warning after they were airborne.


7/22 Entering a Runway Without Authorization

 ATP Pilot

Out of California

Scottsdale Airport (SDL)

The Challenger 350 Jet and a Cessna were holding short of Runway 21 at A16. The controller issued the Cessna a takeoff clearance. The read back was partially blocked by another aircraft transmitting. The controller asked the aircraft calling to say again but there was no response. The tower supervisor observed the Challenger crossing the hold short line and entering the runway, and he alerted the controller. The controller issued instructions for the Challenger to taxi across the runway. The controller issued a Brasher Warning to the Challenger after they had departed.




8/3 Entering a TFR Without Authorization

Private Pilot

Phoenix TRACON (P50)

The aircraft was on a 1200 transponder code and flew out of radar coverage, but the callsign was obtained from ADS-B. The aircraft had flown into an active TFR, FDC 3/3479, for firefighting at 6,000 feet which was located NE of PHX.




7/30 Landing On The Wrong Runway

Commercial/CFI Pilot 

Williams Gateway Airport (IWA)

The Cessna was cleared to land on RWY 30R, but the aircraft was observed landing on RWY 30C. Ground Control issued a Brasher to the pilot.




7/18 Failure To Follow Taxi Instructions

ATP Pilot

Prescott Municipal Airport (PRC)

The aircraft was instructed by Ground Control to cross Runway 21L on Taxiway Charlie 4, and the read back was correct. After crossing Runway 21L, the aircraft turned onto Taxiway Delta without an ATC clearance, and conflicted with an aircraft that was already on Taxiway Delta.

Please login to add a comment.