by Jim Timm
In the time period from December 10, 2021, through January 13, 2022, there were thirteen general aviation pilot deviations recorded by the FAA SDL FSDO. These deviations were committed by private, commercial, CFIs, and ATPs. Of the thirteen deviations made, there was a need to only issue three Brashers.
Note: a Brasher is a notice that is issued when further FAA action will be taken.
The number of pilot deviations/incursions were down a bit this month, and some of these deviations just shouldn’t have happened. Runway deviations of all kinds seemed to be the predominate issue this reporting period. Pay attention to ATC instructions and follow them, and if you can’t, tell ATC why you can’t.
Always know what type of airspace you are flying in, or may be about to enter, and please fly with more care and forethought.
In summary, the general aviation deviations this reporting period are:
Two IFR Route Deviations
One Class Bravo Airspace Deviation
Three Class Delta Airspace Deviations
Six Runway Incursions
One Failure to Follow ATC Instructions
The details of the deviations this month are as follows:
IFR ROUTE DEVIATIONS
12/23 Unauthorized IFR Route Deviation.
Falcon Field (FFZ)
The aircraft was departing Falcon Field (FFZ) climbing to 3000 feet on an instrument departure procedure, and they made an unauthorized turn into descending opposite direction traffic. ATC stopped the descending traffic’s decent, and got the errant aircraft turned in the correct direction, and both aircraft then continued on their course of flight. The errant aircraft was issued a Brasher warning by the PHX TRACON.
1/6 Unauthorized IFR Route Deviation.
The aircraft departed Phoenix (PHX) on an instrument departure procedure and commenced a right-hand turn without authorization from the Tower or the TRACON. The aircraft was switched to the departure controller who stopped the aircraft’s climb at 7000 feet, which was 1000 feet below an arrival aircraft who had been stopped at 8000 feet. No loss of separation had occurred. The pilot was issued a Brasher by the Phoenix TRACON.
CLASS BRAVO AIRSPACE DEVIATION
12/12 Entering PHX Bravo Airspace Without A Clearance
The aircraft entered the PHX Class B Airspace in the area of Glendale without ATC authorization. The aircraft’s climb into the Bravo Airspace resulted in an inbound air carrier receiving a TCAS Resolution Alert while descending to land at Sky Harbor.
CLASS DELTA AIRSPACE DEVIATIONS
12/16 Entering Delta Airspace Without First Establishing Radio Communications.
Falcon Field (FFZ)
The aircraft entered the FFZ airspace from the south without establishing radio communications and continued to fly northbound at 3000 feet. The tower controller attempted to establish communications without success, and the aircraft departed the airspace to the north. ATC was unable to contact the pilot.
12/26 Entering Delta Airspace Without First Establishing Radio Communications.
The aircraft violated the Gateway airspace northbound, and then violated the Falcon Field airspace northbound. The flight did not result in any traffic conflicts. The aircraft was tagged as a violator and a notice for identification was issued, and the Scottsdale tower called and said they were talking to the aircraft. Scottsdale was relayed instructions to issue a Brasher notice and have the pilot contact Falcon Field.
1/11 Entering Delta Airspace Without First Establishing Radio Communications.
The aircraft entered Scottsdale Class D airspace without establishing two way radio communications. There was no loss of separation.
12/13 Crossed Hold Short Line Without Authorization.
Ground Control (GC) instructed the aircraft to taxi via Taxiway Delta to Runway 11L, and the read back was correct. The aircraft then asked GC for progressive taxi instructions because they were unfamiliar. GC instructed the aircraft to taxi straight ahead and they would see the hold bars after passing a hump. The aircraft taxied as instructed but taxied across the hold short line. GC advised the pilot that they had crossed the hold short lines and to hold position. The pilot stated that the had their head down. No other traffic was involved.
12/16 Departed the Runway Without ATC Permission.
Williams Gateway (IWA)
The tower had cleared the aircraft to land on Runway 12C, and the pilot read back cleared to land Runway 12C. The aircraft touched down on Runway 12C and then took off. The tower asked the aircraft if they were going around, and they replied that they were doing a touch and go.
12/21 Crossed Hold Short Line Without Authorization.
Ground Control (GC) instructed the airplane to taxi via Taxiways Alpha and Delta to Runway 22R, and the read back was correct. The aircraft had taxied correctly, but when they reached Runway 22R they announced on the tower frequency that they were taking Runway 22R. There was no response from the tower. The tower then observed the aircraft to then cross the hold short line of Runway 22R and the tower then advised the pilot that they had crossed the hold short line. No other traffic was affected.
1/5 Entered the Runway Without ATC Authorization.
The airplane called the tower controller and said he was holding short of Runway 21L. The controller instructed the aircraft to hold short of Runway 21L. The pilot did not respond on the frequency, but the aircraft taxied forward onto Runway 21L. The tower instructed the aircraft to stop and issued a go around to an aircraft that was inside of a 1/4 mile final.
1/5 Landing On A Runway Without ATC Authorization.
The helicopter called the tower controller inbound to TUS requesting to go to the Atlantic Ramp. The controller advised that landing would be at their own risk and instructed the helicopter to report landing assured. The helicopter asked if they could do a long base to Runway 21 and remain short of the runway. The controller approved, however, the helicopter touched down on Runway 21 instead of on the Atlantic Ramp. No other traffic was involved.
1/6 Landing on A Runway Without ATC Authorization.
The Aircraft was inbounded from the south and the tower controller instructed them to enter a left downwind for Runway 22L. The aircraft entered downwind, and the controller cleared them to land Runway 22L. The aircraft requested Runway 22R. the controller canceled the Runway 22L landing clearance and cleared the aircraft to land on Runway 22R. The read back was correct, however, the aircraft landed on Runway 22L. No other traffic was involved.
FALURE TO FOLLOW ATC INSTRUCTIONS
12/18 Aircraft Attempted To Land At The Wrong Airport.
The aircraft was 14 miles northeast of Goodyear (GYR), and the aircraft was cleared for a visual approach to Runway 3. The aircraft at that time was also 7 miles northeast of Glendale (GEU) airport. The aircraft descended for and turned for a right base to Runway 1 at GEU instead of GYR. The tower controller at GYR noticed the aircraft was turning into the wrong airport and quickly alerted the aircraft of the error and instructed the pilot to correct to GYR. There was VFR traffic in the pattern at GEU that was in direct conflict with the aircraft, and the GEU traffic was given alternate instructions by GEU tower controller.