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 10 through May 14 there were nineteen deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Private Pilot through ATP, and there were six out of state pilots, two Military, and two foreign pilots of the nineteen deviations reported, and there 5 Brashers issued.
Note: Many pilot deviations are resolved during a discussion between the controller and the pilot at the time of the occurrence. However, a controller may issue a Brasher notification to a pilot when further FAA action might be taken, and the controller is thus giving the airman the opportunity to make note of the occurrence, collect information and gather their thoughts for their future interaction with FAA Flight Standards.
I would like to think that many pilots are getting the message to be more careful in their flying and perhaps some of the deviations could be attributed to out of state pilots that may not be accustomed to flying in some of the complex/crowded airspace that we have in Arizona.
I hope that the information being presented has been valuable to all pilots out there and will make them safer pilots.
Pilots must listen carefully to ATC instructions and comply with them and if they can’t comply tell ATC why they can’t. Also, when flying in controlled airspace, pilots should never do something on their own but always talk to ATC before they do anything that may differ 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 observe the airport and runway markings and signs and obey them. Always fly with care and forethought, and don’t be part of the problem.
The details of the deviations this month are as follows.
IFR DEVIATIONS (2)
May 1: Not Flying the Departure Procedure as Published
ATP Pilot
Out of Minnesota
Phoenix TRACON (P50)
On the DVT3 departure the aircraft flew the runway heading causing the controller to take action and correct the error. Pilot said he turned to avoid traffic and failed to notify ATC.
May 7: Taking Off Without Getting a release for Takeoff
Foreign Pilot
Tucson TRACON U90)
The pilot received an IFR clearance and was issued a hold for release. The pilot did not read back the hold for release instructions and was not corrected. The pilot was called again and received an updated clearance and was told to standby. The pilot then departed without an IFR release.
PHOENIX CLASS BRAVO AIRSPACE DEVIATIONS (2)
April 17: Entering Class Bravo Airspace Without First Having Authorization
No Pilot Information
Out Of New Mexico
Phoenix TRACON (P50)
The aircraft climbed into the Phoenix Class B Airspace without first obtaining an ATC clearance or establishing two-way radio communication.
May 1: Entering Class Bravo Airspace Without First Having Authorization
Private Pilot
Out Of Canada
Phoenix TRACON (P50)
The aircraft climbed into the Phoenix Class Bravo Airspace without a clearance. The aircraft had entered the 2700'-9000' block of Class Bravo Airspace and conflicted with an air carrier. No traffic call or traffic alert was issued. The air carrier reported they were responding to a TCAS Resolution Alert and climbed 100’.
CLASS DELTA AIRSPACE DEVIATIONS (5)
April 22: Entering Class Delta Airspace Without First Having Authorization or Communication
Private Pilot
Out Of Texas
Phoenix Deer Valley Airport (DVT)
The aircraft departed Scottsdale Airport and called the Phoenix TRACON, and they were identified, and were told to climb to 3,500, and to continue and contact the Deer Valley tower. They didn’t call anyone but continued to their intended destination, Glendale (GEU). Deer Valley Airport Issued the pilot a Brasher notice for entering their Class Delta Airspace without first obtaining an ATC clearance or establishing two-way radio communication with Deer Valley.
May 3: Entering Class Delta Airspace Without First Having Authorization or Communication
No Pilot Information
Scottsdale Airport (SDL)
The aircraft entered the SDL Class D airspace without first obtaining an ATC authorization or establishing two-way radio communication.
May 6: Entering Class Delta Airspace Without First Having Authorization or Communication
No Pilot Information
Scottsdale Airport (SDL)
A jet was awaiting departure at Scottsdale. An airspace intruder was noted in the Scottsdale Class Delta Airspace and was not in radio contact with either the tower or the Phoenix TRACON. The jet was cleared for takeoff with a turn after rotation. The jet responded that they had a Resolution Alert, they were clear of the traffic, and they were switching to the departure frequency. The Phoenix TRACON advised they would be issuing a Brasher to the intruding aircraft.
May 7: Entering Class Delta Airspace Without First Having Authorization or Communication
ATP Pilot
Mesa Gateway Airport (IWA)
The aircraft entered the Gateway Class Delta Airspace without first having ATC authorization or establishing two-way communication. IWA attempted to establish communication, with no response.
May 9: Entering Class Delta Airspace Without First Having Authorization or Communication
Private Pilot
Chandler Municipal Airport (CHD)
The aircraft called multiple times 3 miles east of the field but the tower never established communications due to radio saturation. The aircraft then entered the Chandler Delta Airspace and proceeded to fly a left base without ATC instructions. The aircraft then established communications, and they were told to fly south. Once they landed, they were issued a Brasher by ground control.
ALTITUDE DEVIATION (1)
April 14: Deviation from Assigned Altitude
No Pilot Information
Phoenix TRACON (P50)
The aircraft departed Scottsdale with an instruction to turn right to a heading of 285°. The aircraft checked in with departure control in a left turn southbound. Departure immediately issued a low altitude alert, and a climb to 6,000 feet and a turn back to a 360° heading. During the climb, the aircraft climbed as high as 6,300 feet and descended as low as 5,600 feet before leveling off.
AIR TRAFFIC CONTROL INSTRUCTION DEVIATIONS (5)
April 12: Failure to Follow ATC Instructions
Commercial Pilot
Phoenix Deer Valley Airport (DVT)
The aircraft entered the Deer Valley airspace without ATC authorization or establishing two-way communication. ATC attempted numerous times to contact the aircraft but they continued inbound flying to a short final before contacting ATC.
April 18: Failure To Follow ATC Instructions
Military Pilot
Albuquerque Center (ZAB)
A flight of F35's, checked in with Albuquerque Center, level at FL250, and requested FL350. Center clears them to FL300 with a good response. The flight then made a new request to FL370 to which the center controller says that they have their request. There was other traffic level at FL320. The flight of F 35’s had climbed above FL300. The center controller sees this and clears the flight to maintain FL300 immediately. The flight had climbed to FL312 and then descends quickly. There was a loss of separation, and the closest proximity was 4.91 miles and 800 feet. No traffic calls or safety alerts were issued.
April 25: Failure to Follow ATC Instructions
Military Pilot
Mesa Gateway Airport (IWA)
The T-38 departed Gateway Airport and was issued a runway heading by the tower. The aircraft said they were on the runway heading and then started a righthand turn. The controller reissued a 120° heading after having some initial communication difficulty. There does not appear to be a loss of separation with terrain or other aircraft.
April 30: Failure To Follow ATC Instructions
Commercial Pilot
Tucson TRACON (U90)
The jump aircraft was told by the controller to turn back to remain in the jump area. The pilot appeared to not turn southbound and was issued a heading of 120° multiple times by the controller. The controller continued to work other traffic and then noticed the jump airplane had turned southwest bound, off the 120° heading assigned. Pilot reported they had to turn back inbound but did not advise the controller. The controller issued the Brasher statement to the pilot.
May 10: Failure To Follow ATC Instructions
ATP Pilot
Out of Minnesota
Phoenix TRACON (P50)
An aircraft was arriving at PHX on the EAGUL6 STAR RWY 08 transition, and the crossing restriction at QUENY is 10,000. An air carrier was departed PHX on the QUAKY1 SID, climbing to 9,000. Traffic was issued to both aircraft. The arriving aircraft descended below 10,000 to 9,700. A traffic alert was issued to the arrival and they were told to climb to 10,000. Both aircraft had each other in sight. The air carrier reported responding to a TCAS Resolution Alert and descended from 8,600 to 8,200. The pilot of the arrival aircraft did not report a TCAS RA on the frequency, but the pilot confirmed they did climb to 10,200 from a TCAS RA. Separation was not lost, and both aircraft proceeded on course without further incident.
RUNWAY INCURSIONS (2)
April 24: Taxiing On a taxiway Without Authorization
Commercial Pilot
Out of California
Prescott Airport (PRC)
The aircraft landed, and exited at TWY T, and the aircraft began taxiing without instructions from ground control. The pilot was still on the tower frequency, and the controller informed the pilot to stop and contact ground control. The pilot stopped and contacted ground control and then when approved taxied to the ramp without incident. A Brasher was given on the ground control frequency.
May 6: Taxiing onto a Runway Without Authorization
Private Pilot
Out of Texas
Tucson Ryan Field (RYN)
A Piper was holding short of Runway 33 waiting to depart on Runway 6R. The Controller instructed the Piper to taxi onto Runway 33, and hold short of Runway 6, and advised them of landing traffic. The read back was correct but the Piper taxied past the hold short line of Runway 6R. The controller issued a go around to the airplane turning to final for the same runway.
RESTRICTED AIRSPACE INCURSION (1)
May 7: Flying In Restricted Airspace Without Approval
ATP Pilot
Phoenix TRACON (P50)
The airplane entered Restricted Airspace R2310A @ 4,700 feet. R2310A was active from 10,000 feet and below and ATC had advised the aircraft that the restricted area was active prior to them violating the airspace.
TFR INCURSION (1)
April 4: Flying in a TFR Without Approval
Private Pilot
Scottsdale Airport (SDL)
The aircraft appears to have departed from Flagstaff and flew southbound into the active VIP TFR. The pilot stated that he was unaware of the TFR and after contacting Scottsdale he was given a discrete beacon code and transferred to PHX Approach on 120.7. Scottsdale had an active VIP TFR in effect and the pilot had entered the TFR without authorization.