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 September 13 through October 10, 2024, there 11 pilot deviations were reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Private Pilot through ATP, with only one out of state pilot, and one foreign pilot. Out the 11 deviations reported, two Brashers were issued.
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.
The details of the deviations this month are as follows:
IFR DEVIATION (2)
9/26 Route Deviation
Comm/CFI Pilot
Albuquerque Center (ZAB)
The airplane was cleared to KTUS as filed and given a climb to 7,000 feet, which was read back correctly. The filed route was P08, PICLI, V16, TUS, KTUS. As the airplane was climbing through 5,300 feet, they made a left turn of approximately 120 degrees without a clearance in a Minimum Instrument Altitude area (MIA) of 6,500 feet. The controller questioned the pilot, but did not issue a safety alert. The pilot said they were correcting, and the controller advised that as filed was direct PICLI and asked where the pilot where he was headed now. The pilot said they were on the victor airway to TUS. The controller advised the pilot that they were 3 miles east of the airway and that they were below the MIA so he couldn't give them vectors until they were above 6,500 feet. Shortly after, the Aircraft was observed above the MIA. Later when the instructor pilot called in he stated that his student had put the wrong routing into the GPS and that he wanted to see if the student would catch it, but he waited too long to step in.
10/3 Route Deviation
Private Pilot
Phoenix TRACON (P50)
The pilot deviation was reported by the Phoenix TRACON when the departing Honda Jet turned northbound prior to the SACAT intersection which resulted in a loss of separation with an aircraft inbound to Phoenix Sky Harbor.
CLASS BRAVO AIRSPACE DEVIATION (1)
10/2 Entering Class Bravo Airspace Without Authorization
Commercial/CFI Pilot
Phoenix TRACON (P50)
The airplane entered the Phoenix Class Bravo Airspace without authorization. There was no loss of separation.
CLASS CHARLIE AIRSPACE DEVIATION (1)
10/1 Entering Class Charlie Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Tucson TRACON (U90)
The pilot deviation was reported by the Tucson TRACON when the airplane was observed crossing the U.S. / Mexico border on a VFR transponder code and heading northbound. The aircraft continued northbound and violated both the inner and outer core of the Tucson Class Charlie Airspace.
CLASS DELTA AIRSPACE DEVIATION (1)
8/30 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Out Of Austria (Phoenix- based airplane partnership)
Phoenix Deer Valley (DVT)
The deviation was reported by Deer Valley when the Piper entered the Phoenix Deer Valley Class Delta Airspace without first establishing two-way radio communications. There was no loss of separation.
RUNWAY INCURSION (2)
9/30 Crossing A Runway Without Authorization
Commercial Pilot
Phoenix/Mesa Gateway Airport (IWA)
The controller observed the Piper crossing the hold short line and entering the runway, and the controller had to issue a go around to another aircraft on an approximate 1/4 mile final. The Piper continued across the runway. The controller reached out to Piper and received a response after the second attempt. The controller issued the Brasher warning.
10/3 Entering A Runway Without Authorization
Student Pilot
Tucson Ryan Field (RYN)
The pilot deviation was reported by the Ryan Field controller when the Cessna crossed the Hold Short Line of the runway without ATC authorization.
AIR TRAFFIC CONTROL INSTRUCTIONS (2)
9/12 Failure To Follow Air Traffic Control Instructions
ATP/CFI Pilot
Phoenix Deer Valley Airport (DVT)
The pilot deviation was reported by a Deer Valley controller when the Piper didn’t fly the departure instructions issued by ATC, and as a result conflicted with local traffic.
10/4 Failure To Follow Air Traffic Control Instructions
Pilot Certification Unknown
Flagstaff Airport (FLG)
The pilot deviation was reported by a Flagstaff controller when a Cessna turned right base in front of and below, another aircraft, causing that aircraft to respond to a TCAS Resolution Alert. A Brasher warning was issued.
SURFACE INCIDENT (1)
9/28 Movement On A Taxiway Without Authorization
ATP Pilot
Out of Montana
Tucson Ryan Field (RYN)
The pilot deviation was reported by Ryan Field when a Beechcraft Baron entered Taxiway B without ATC authorization. There was no loss of separation reported.
VEHICLE DEVIATION (1)
9/25 Movement Of A Vehicle On A Controlled Surface
Pilot - Not Applicable
Prescott Municipal Airport (PRC)
An FBO Vehicle deviation was reported by the Prescott tower when a car entered the active runway without ATC authorization while a Cessna was on a landing roll. The estimated closest proximity was 160 feet.