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 April 12, 2024, through May 9, 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, including one Military pilot, and there were eleven out of state pilots that committed these deviations. Of the thirty-one deviations reported, there was a need to issue seven 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.
The details of the deviations this month are as follows:
IFR DEVIATION (8)
4/1 IFR Altitude Deviation
Private Pilot
Albuquerque Center (ZAB)
The controller observed the SR22 above 5,000 feet and asked the aircraft to verify level at 5,000 feet. The aircraft responded, “we climbed a little bit, but going back to 5,000 feet”. The SR22 made an unauthorized climb to 5,200 feet which resulted in a loss of separation with another aircraft who was level at 6,000 feet.
4/3 IFR Procedures Deviation
Unknown Pilot Certification
Tucson TRACON (U90)
The pilot deviation was reported by the Tucson TRACON when the Citation didn’t fly the RNAV procedure as published which resulted in a loss of separation with terrain/obstacles.
4/9 IFR SID Deviation
Unknown Pilot Certification
Out of Kansas
Phoenix TRACON (P50)
The Dassault Falcon didn’t fly the FORPE 1 departure procedure as published resulting in a loss of separation with parallel runway departure traffic.
4/12 IFR Altitude Deviation
Commercial/CFI Pilot
Albuquerque Center (ZAB)
The Piper was descending from 8,000 feet to 5,000 feet, and the controller cleared the Piper for the VOR5 approach to CGZ. The aircraft read back the clearance correctly. The center controller then cleared the Piper to the CGZ advisory frequency. Later the controller observed the Piper stopped it’s descent at 6,300 feet and begin a climb. The Piper then made an unauthorized climb to 8,300 feet. The controller issued a Brasher. Pilot stated that they were put into the stack at the VOR and that they had to climb to 8,500 feet, due to the stack.
4/20 IFR Altitude Deviation
Private Pilot
Out of Texas
Albuquerque Center (ZAB)
The Lancair was level at 5,000 feet, and the controller cleared the airplane to descend and maintain 4,600 feet. The Lancair read back 4,000 feet which was not recognized by the controller. The center controller observed the Lancair below 4,600 feet and issued a low altitude warning because the aircraft was in a 4,600 Minimum Instrument Area (MIA) box, and then they had entered a 4,500 foot MIA box. The Lancair had descended to 4,100 feet before climbing back up.
4/24 IFR Procedures Deviation
Unknown Pilot Certification
Prescott Tower (PRC)
The deviation was reported by the Phoenix TRACON when the Glasair didn’t fly the procedure turn as required by the approach plate.
4/25 IFR Standard Instrument Departure (SID) Deviation
Private Pilot
Out of Tennessee
Phoenix TRACON (P50)
The Cessna 182 did not fly the MESA 1 departure as published. There was no loss of separation, but a Brasher was issued.
5/3 IFR Altitude Deviation
Private Pilot
Out of Indiana
Albuquerque Center (ZAB)
The Albuquerque Center Controller observed the Cessna 182 was above their assigned altitude and asked the aircraft to verify their flight level. The Cessna responded, “we're descending back down”. The 182 had made an unauthorized climb to 7,300 feet which resulted in a loss of separation with another aircraft who was level at 8,000 feet. A Brasher was issued.
CLASS DELTA AIRSPACE DEVIATIONS (5)
4/8 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
ATP/CFI Pilot
Out of Texas
Phoenix Deer Valley (DVT)
The pilot deviation was reported by DVT when the Cessna entered the DVT Class Delta Airspace without first establishing two-way radio communications.
4/8 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Student Pilot
Phoenix Deer Valley (DVT)
The pilot deviation was reported by DVT when the Cessna 172 entered the DVT Class Delta Airspace without first establishing two-way radio communications. There was no loss of separation.
4/27 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Commercial Pilot
Out of Idaho
Phoenix Deer Valley (DVT)
The Cessna 180 entered the DVT airspace from the north without first establishing two-way radio communications with ATC. The aircraft made a turn to the NE and exited the airspace, and appeared to land at Carefree Sky Ranch. No aircraft were impacted, and no traffic advisories were required. The aircraft information was obtained via ADS-B.
4/28 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Commercial Pilot
Out of Ohio
Phoenix Deer Valley (DVT)
The Cessna 182 entered DVT's class D airspace from the east at the pattern altitude of 2500' MSL. The Cessna never made contact with DVT, and became a conflict with multiple aircraft in the airspace. The Cessna never established two-way radio communication, and exited the airspace to the southwest.
4/29 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Commercial/CFI Pilot
Out of Washington
Mesa Falcon Field Airport (FFZ)
The RV8 entered the FFZ airspace from the east without a clearance from ATC. The controller reached out and was able to get in contact with the aircraft. The RV8 was instructed to enter a left downwind for the runway. Approaching midfield, the the aircraft executed a 360° turn on their own. Instructions were given to other aircraft to avoid the RV8.
CLASS CHARLIE AIRSPACE DEVIATION (1)
4/29 Entering Class Charlie Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Tucson TRACON (U90)
The pilot deviation was reported by the Tucson RAPCON when the Cessna 172 pilot never contacted Tucson Departure as instructed by the Ryan Tower, and violated the Tucson Class Charlie Airspace while en route to Marana (AVQ).
RUNWAY INCURSIONS (7)
4/6 Entering The Runway Without Authorization
Commercial/CFI Pilot
Prescott Airport (PRC)
The pilot deviation was reported by Prescott ATC when the Cessna 172 entered a runway without authorization. Ground control issued the Brasher warning. There was no loss of separation.
4/10 Started Takeoff From Runway Without Authorization
Private Pilot
Goodyear Airport (GYR)
The pilot deviation was reported by the Goodyear ATC when the Cirrus SR20 began it’s departure roll without ATC authorization while another aircraft was departing from an intersection farther down field.
4/11 Started Takeoff From Runway Without Authorization
Private Pilot
Out of Nevada
Phoenix Deer Valley (DVT)
The Cirrus SR22, began a takeoff roll without ATC authorization, resulting in a loss of separation with another aircraft crossing the runway. The controller has issued the SR22 a line up and wait instruction with a good readback. Ground control had coordinated for an aircraft to cross the runway which the controller had approved. The aircraft was crossing the runway when the SR22 began it’s takeoff roll. The controller instructed the SR22 to stop, and the pilot read back, “Cleared for takeoff”. The controller again instructed the SR22 to stop, and the aircraft stopped prior to the next intersection.
4/12 Landing On The Wrong Surface
Private Pilot
Out of California
Phoeniz/Mesa Gateway (IWA)
The deviation was reported by Gateway ATC when the Grumman Tiger was cleared to land on Runway 12R, but was observed landing on Taxiway Bravo, and overflying an aircraft on the taxiway.
4/12 Taxied Past The Runway Hold Short lines
Military Pilot
Tucson International (TUS)
The F16 was instructed to hold short of Runway 22, and the pilot read back the hold short instructions, but later crossed Runway 22 without authorization. No other aircraft were involved.
4/17 Taxiing Onto The Runway Without Authorization
ATP Pilot
Prescott (PRC)
The Cessna 337 was instructed to hold short of the runway, and it was observed by both the Ground Controller and the Operations Supervisor to be pulling past the hold bars, and continuing into the runway. The controller had a Cessna 172 on final for the same runway that they had to send around. A Brasher was issued.
4/19 Driving Onto A Runway Without Authorization
No Pilot
Mesa Falcon Field (FFZ)
An airport vehicle crossed the runway Hold Short Lines without authorization resulting in the need to send an aircraft on final to go around.
AIR TRAFFIC CONTROL INSTRUCTIONS (1)
4/16 Failure To Follow Air Traffic Control Instructions
Commercial Pilot
Out of New Mexico
Phoenix Deer Valley (DVT)
The IFR Bonanza, contacted the DVT south controller approximately 3 miles southeast of the airport inbound at 5000’, and descending. the south controller instructed pilot to begin a left turn and enter right downwind for runway 7R. Pilot read back the instruction but omitted the runway assignment. The Bonanza continued inbound directly toward the airport, and the controller instructed pilot to widen out to the southwest to which the pilot turned northbound into the north controllers airspace. The south controller instructed the Bonanza to maintain at or above 3000', make left traffic and the tower would call the aircraft's base turn. The pilot didn't fully acknowledge the instruction. Without approval from the south controller, the Bonanza turned their base leg approximately 3 miles from the airport. The south controller then cleared the Bonanza to land on runway 7R and issued "go-around" instructions to the preceding aircraft on about a 1 mile final to ensure proper separation would exist at touchdown. The Bonanza landed on runway 7R, exited the runway and taxied to parking without further incident. A Brasher was issued.
RESTRICTED AIRSPACE (1)
4/19 Entering Restricted Air Space Without Authorization
ATP/CFI Pilot
Albuquerque Center (ZAB)
The Marchetti S211 had been cleared to fly in the GLOBE ATCAA at 15,000 feet to FL310. The Marchetti, who was at 16,800 feet, violated restricted area R2310B which was active 17,000 feet and below. When advised of the violation, the Marchetti turned out of, and climbed above the restricted area. A Brasher was issued.