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 September 15 through October 12 there were 24 pilot deviations reported by the FAA SDL FSDO office.
These deviations were committed by pilot certificate levels ranging from student thru ATP, and in this reporting period there were also eight out of state pilots that committed the deviations. Of these 24 deviations reported, there was a need to issue seven Brashers.
Note, a controller will issue a Brasher notification when further FAA action will be taken, and the controller is thus giving the pilot 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. Always fly with care and forethought.
The details of the deviations this month are as follows:
IFR DEVIATION (6)
9/13 IFR SID Deviation
Commercial/CFI Pilot
Phoenix TRACON (P50)
The pilot deviation was reported by the Phoenix TRACON when the aircraft didn’t fly the DVT 3 departure as published. There was no loss of separation.
9/19 IFR NORDO
Private Pilot
Out Of Missouri
Albuquerque Center (ZAB)
At 17:24 the Albuquerque Center controller cleared the aircraft to contact Albuquerque Center on 127.67. The aircraft did not respond to that call, nor any subsequent attempts made by ATC. The aircraft remained out of contact with ATC until 1843z, when the LA Center established communications and issued the Brasher Warning.
9/19 IFR Standard Instrument Departure (SID) Deviation
Private Pilot
Phoenix TRACON (P50)
The aircraft departed from Mesa Falcon Field and should have been on the MESA 1 departure but it didn’t fly the Mesa 1 SID correctly.
9/22 IFR Standard Instrument Departure (SID) Deviation
Private Pilot
Phoenix TRACON (P50)
The aircraft departed Mesa Falcon Field (FFZ) IFR, entered a Minimum Vectoring Altitude (MVA) area, and the Phoenix TRACON San Tan controller issued a Low Altitude Alert with an expeditious climb request. The aircraft quickly climbed above the MVA and continued on their flight. FFZ ATCT advised they had issued the MESA 1 Departure, however, the aircraft didn’t fly the departure procedure, rather they flew the runway heading northeast directly into the higher MVA area. Once it was discovered that this was a possible pilot deviation, the aircraft was well outside the Phoenix TRACON airspace, and a request was then made to Albuquerque Center to issue a Brasher to the pilot.
10/4 IFR Route Deviation
ATP Pilot
Out of California
Albuquerque Center (ZAB)
The Cessna Citation had made an unauthorized turn of about 50 degrees. The event occurred near Wellton, AZ, and a Brasher was issued. The pilot stated that this is a common route for the aircraft and it is a stored routing in the Flight Management System (FMS) they used and should have been good.
10/8 IFR Standard Instrument Departure (SID) Deviation
ATP Pilot
Out of California
Phoenix TRACON (P50)
The aircraft departed Scottsdale airport IFR and was issued the MARICOPA 1 departure by ATC. The aircraft didn’t comply with the departure, and the controller had to give them vectors to avoid terrain.
CLASS BRAVO DEVIATION (1)
9/23 Entering Class Bravo Airspace Without First Obtaining A Clearance
Private Pilot
Out of Texas
Phoenix TRACON (P50)
The aircraft was flying VFR from the south toward Mesa Falcon Field (FFZ), and they had climbed into the Class Bravo Airspace without a clearance. The controller asked them if they were familiar with the Bravo Airspace, and the pilot said no. The controller then vectored the aircraft to descend them out of the Bravo Airspace, and the aircraft continued on to FFZ without further incident.
CLASS DELTA DEVIATIONS (3)
9/22 Entering Class Delta Airspace Without First Establishing Communication
Student Pilot
Phoenix Deer Valley Airport (DVT)
The errant aircraft entered the Deer Valley Class D Airspace from the North without first establishing communication with DVT. A Cessna was in closed traffic for RWY 7L and ATC had to turn them to the NE to avoid the errant aircraft. The Cessna reported the errant aircraft in sight. Unfortunately, the errant aircraft was in communication with the Scottsdale tower.
9/22 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Mesa Gateway Airport (IWA)
The Piper aircraft was inbound from the North and descended into the Gateway Class Delta Airspace southbound and over the top of the airport at 3,500 feet MSL. The local controller attempted to contact the aircraft, but was unable to establish two-way radio communications. The aircraft appeared to be inbound for the Chandler airport. The Gateway Tower contacted the Chandler Tower and requested that they issue the pilot the Brasher statement once they were in communication with the aircraft.
9/29 Entering Class Delta Airspace Without First Establishing Communication
Student Pilot
Mesa Falcon Field (FFZ)
A Piper aircraft was observed entering the Falcon Field (FFZ) Delta Airspace from the south at 3,100 feet without permission from FFZ. The FFZ controller had to issue a turn to another aircraft to avoid the errant Piper. The Piper was then observed turning southbound towards the Gateway (IWA) airspace. The FFZ controller contacted the IWA tower and verified that the errant Piper was on their frequency, and asked them to give the Brasher notice to the Piper due to the airspace violation.
TFR DEVIATIONS (3)
9/8 Entering a TFR Without Authorization
Commercial Pilot
Out of Oklahoma
Albuquerque Center (ZAB)
A report from the Tonto National Forest Aviation Officer reported that a Cessna with a known tail number violated an active firefighting TFR (NOTAM 03/5101). There was no radar data to support the report. The event occurred near Payson, and a Brasher was NOT issued.
9/16 Entering a TFR Without Authorization
Comm/CFI Pilot
Out of New York
Albuquerque Center (ZAB)
The pilot deviation was reported by the Airspace Coordinator that an R66 helicopter violated firefighting TFR 03/0452. One of the Air Attack aircraft identified the violator and visually got the tail number. The event occurred near Tucson, and a Brasher was NOT issued.
9/28 Entering a VIP TFR Without Authorization
Private Pilot
Out of Virginia
Phoenix TRACON (P50)
The Beechcraft violated the VIP 30-mile TFR. The aircraft departed Pegasus Airpark (5AZ3) on a 1200 code. After about 5 minutes ATC was able to contact the pilot, and the controller gave them an appropriate transponder code.
AIR TRAFFIC CONTROL INSTRUCTIONS (3)
9/14 Failure to follow Air Traffic Control Instructions
ATP/CFI Pilot
Mesa Falcon Field Airport (FFZ)
The pilot deviation was reported by FFZ when the aircraft did not follow the departure instructions assigned by ATC.
10/1 Failure to follow Air Traffic Control Instructions
Private Pilot
Tucson Ryan Field Airport (RYN)
The Piper Tri-Pacer made an early right turn after becoming airborne, and conflicted with a Cessna 172 in the downwind.
10/4 Failure to follow Air Traffic Control Instructions
ATP/CFI Pilot
Out of California
Scottsdale Airport (SDL)
The Cessna was repeatedly given holding, and pattern entry instructions, and failed to understand them even after the controller repeated the instructions multiple times. He was issued a downwind entry, and flew through the final causing a Resolution Alert for another aircraft. The problematic Cessna was issued a Brasher for his inability to follow instructions.
RUNWAY INCURSIONS (5)
9/11 Failure to expeditiously clear a runway after landing
Comm/CFI Pilot
Phoenix Deer Valley Airport (DVT)
The Pilatus failed to clear the runway after landing with a Cirrus on short final. The Pilatus landed on Runway 25L and was instructed to turn left on Taxiway Charlie 7, and taxi via Taxiway Delta 6 to the ramp, but there was no response from the Pilatus. The Local Control (LC) issued the instructions again and continued trying to get in contact with the Pilatus with no response. The Pilatus had turned left on Taxiway Charlie 7, and stopped prior to crossing the hold short line of the runway. Ground Control (GC) also tried to reach out to the Pilatus but got no response. LC issued a go around to the Cirrus on an approximate 1/4 mile final. The Pilatus then contacted GC for taxi instructions to the ramp. GC issued taxi instructions and also the Brasher warning.
9/12 Taking off on a runway without ATC authorization.
Comm/CFI Pilot
Mesa Gateway Airport (IWA)
The Piper departed Runway 30R without ATC authorization. The controller cleared the Piper to land on Runway 30R. The read-back was correct., and the Piper conducted a touch and go and departed Runway 30R instead of making a full stop. No other traffic was involved.
9/15 Entering a runway without ATC authorization
Comm/CFI Pilot
Scottsdale Airport (SDL)
The errant Cessna entered Runway 21 without ATC authorization. The controller had two Cessna aircraft on frequency, and the errant Cessna called the controller and advised they were ready for departure. The controller instructed the errant Cessna to hold short of Runway 21 and the read-back was correct. The controller then cleared the other Cessna for takeoff and it departed. The controller attempted to issue additional instructions to the departing Cessna and said your right turn out to the north is approved, expedite your climb. The errant Cessna read back “Runway 21 cleared for takeoff expediting climb”. The controller did not catch the read back of cleared for takeoff. The errant Cessna entered Runway 21 and lined up for departure. The controller asked who the aircraft was on Runway 21 and the errant Cessna advised it was them. LC instructed the Cessna to exit Runway 21 at Taxiway Alpha 13 and advised them of another Cessna on an approximate 1/2 mile final.
9/24 Entering a runway without ATC authorization
Private Pilot
Phoenix Deer Valley Airport (DVT)
The Piper called ground control for departure on runway 25R. The Piper read back the proper hold short instructions after being corrected to use call sign with hold instructions. The Piper then proceeded onto runway 25R and appeared to be holding in position on runway 25R. Another Piper was inside a half mile final for runway 25R, and was sent around, and offset to the right of runway 25R. The errant Piper was instructed to taxi down runway 25R and exit at A10. No other aircraft were impacted.
10/6 Entering a runway without ATC authorization
Student Pilot
Chandler Airport (CHD)
A VFR solo student pilot was cleared for a touch-and-go on Runway 4L; however, they aligned with and landed on Runway 4R. The student flew within 0.5 miles of another VFR aircraft, which was turning base for Runway 4R.
LANDING ON A TAXIWAY (1)
9/27 Landed On A Closed Taxiway
Private Pilot
Tucson Ryan Field Airport (RYN)
The pilot was sequenced number three to follow traffic for RWY 6R. The pilot had his traffic in sight, but lost them on short final, and the pilot landed on TWY A, which was NOTAMed closed. There were no personnel or equipment on TWY A at the time of the event.
In a phone call afterwards, the pilot stated that he knew that many things were closed per the ATIS, except for RWY 6R, and got confused when he lost sight of his traffic but didn't say anything.
SURFACE INCIDENT (LANDED ON A TAXIWAY) (1)
8/9 Failure to Follow ATC Instructions
Private Pilot
Prescott Airport (PRC)
The VFR Super Cub was cleared to land on Runway 21R, however they aligned with and landed on Taxiway A. Personnel and equipment were present in the run-up area for Runway 21R adjacent to Taxiway A. The facility reported an overflight did not occur.
PEDESTRIAN ON RUNWAY (1)
10/11 Pedestrian got on the Runway.
Phoenix International Airport (PHX)
Phoenix Air Traffic Control Tower advised that an unauthorized pedestrian was observed on Runway 8/26. Operations were suspended for 6 minutes while the airport Police Department apprehended the individual, and normal operations could be resumed.