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 report from March 10 through April 13 there were thirty-one pilot deviations reported by the FAA SDL FSDO. These deviations were committed by pilot certificate levels from Student through ATP/CFI, and of these thirty-one deviations reported, there was a need to issue nine Brashers. In this month’s report there were also thirteen out-of-state pilots that committed the deviations. The number of Brashers reported was certainly down for the number of deviations committed this period.
It should be noted that this month’s report includes eight incidents that occurred during the period from 2/18 to 3/10 that didn’t get included in last month’s report, but are now covered in this report. In this limited period there were also three Brashers recorded.
Note, a controller will issue a Brasher notification when further FAA action will be taken, and the controller is thus giving the airman the opportunity to make note of the occurrence, and 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 rather, 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/22 IFR Route
Private Pilot
Out of Arkansas
Phoenix TRACON
On departure, the Citation immediately turned northbound counter to his assigned Standard Instrument Departure routing. A Brasher warning was issued by the TRACON SANTAN sector. There were no conflicts with any other aircraft or loss of separation.
3/9 IFR Route
ATP Pilot
Out of Texas
Albuquerque Center (ZAB)
At 1918z, the Center Controller cleared the Bombardier Challenger to turn 10 degrees left for traffic. At 1924z, the controller cleared the Challenger “direct San Simon.” Aircraft read back the clearance correctly. San Simon (SSO) was NOT on the Challenger's flight plan. The Challenger turned about 40 degrees off course. The Challenger accepted, and acted on a clearance without getting clarification on what the identifier was for San Simon or where to rejoin the routing that the aircraft had been previously cleared for. This unauthorized turn resulted in the Challenger violating the RUSTLER MOA which was active, up to FL500. A Brasher was issued.
3/13 IFR Route
Private Pilot
Phoenix TRACON
The pilot deviation was reported by the TRACON when the Piper did not fly the MESA ONE Departure as published.
3/16 IFR Altitude
UNK Pilot Certification
Albuquerque Center (ZAB)
At 2204z, a Super King Air called Albuquerque Center, VFR, for an IFR clearance to SGU (St. George, UT). The Center Controller advised the King Air that he was currently under an active military area, and they could only get him up to 10,000 feet until he was clear of the MOA. At 2207z, the controller cleared the King Air to maintain his own terrain obstruction clearance up to 10,000 feet and issued the IFR clearance to maintain 10,000 feet. The King Air read back the clearance correctly. At 2208z, the King Air asked the Center if he was supposed to climb to FL220. At this point the King Air had already made an unauthorized climb to 10,800 feet. This climb violated the JACKAL MOA. A Brasher was issued.
3/17 IFR NORDO
ATP/CFI Pilot
Albuquerque Center (ZAB)
AT 2027z, The Albuquerque Center Controller cleared the Bombardier Challenger to contact Albuquerque Center on 132.45. Aircraft read back the clearance correctly, but the Challenger did not check in on the new frequency nor answer any of the subsequent attempts made at that time to establish communications. The Challenger remained out of contact with ATC until 2101z, when a Los Angeles Center Controller established communications. A Brasher issued by the LA Center at 2107z
3/20 IFR Route
ATP/CFI Pilot
Albuquerque Center (ZAB)
The Pilatus had been cleared, “after JARPA direct to LARKS for the LARKS2 arrival”. At 1933z, as the aircraft had just passed JARPA, the Center Controller observed the Pilatus was off course, and asked where they were navigating. The Pilatus responded, “ALS”. The Pilatus had made an unauthorized turn of about 15 degrees and was not proceeding as cleared. A Brasher was issued. The pilot admitted the error, and that he had been cleared via JARPA then LARKS.
3/29 IFR Altitude
UNK Pilot Certification
Phoenix TRACON
The Learjet climbed above his assigned altitude of 9,000 feet. The climb above the assigned altitude conflicted with VFR traffic in the vicinity of Phoenix Sky Harbor.
4/4 IFR Altitude
UNK Pilot Certification
Tucson TRACON
The pilot deviation was reported by the Tucson TRACON when a Learjet climbed above it’s assigned altitude and caused a loss of separation with other aircraft.
CLASS DELTA AIRSPACE DEVIATION
2/28 Entering Class Delta Airspace Without First Establishing Communication
ATP/CFI Pilot
Out of New Jersey
Williams Gateway Tower (IWA)
A Cessna was observed entering the Gateway Class Delta Airspace from the northwest and was heading southeast. After attempting to establish contact, the Gateway tower contacted the Falcon Field tower who was still in communication with the Cessna. Communications was established between the Cessna and Gateway after the aircraft was approximately 4 miles into the Gateway Class Delta Airspace. The Cessna’s mode C transponder code was verified with the Phoenix TRACON, and the Cessna was instructed to fly east and exit the airspace due to other inbound traffic.
3/4 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Out of California
Chandler Airport Tower (CHD)
The helicopter was observed entering the Chandler Class Delta Airspace 4 nautical miles north of the airport, and the Chandler Tower attempted to reach out to the helicopter as it was entering the Delta Airspace. After the helicopter was one mile into the Delta Airspace they established communications with the tower, and they were cleared to land at the Helo Pad. There was no loss of separation with other traffic, and a Brasher was issued to the pilot by ground control.
3/7 Entering Class Delta Airspace Without First Establishing Communication
ATP/CFI Pilot
Williams Gateway Tower (IWA)
The aircraft was on a course to Mesa Falcon Field from the southeast above the Gateway Class Delta Airspace, however, the aircraft descended into the Gateway Class Delta Airspace two miles miles north of the airport. The aircraft was not in conflict with any traffic. The Phoenix TRACON advised Gateway that the aircraft was NORDO, and asked if Gateway had talked to them. The TRACON instructed Falcon Field to issue a possible pilot deviation to the aircraft.
3/10 Entering Class Delta Airspace Without First Establishing Communication
Commercial Pilot
Phoenix Deer Valley Airport Tower (DVT)
The pilot deviation was reported by the Deer Valley Tower when the aircraft entered the Deer Valley Class Delta Airspace without first establishing two-way communications with the tower.
3/27 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Out of Washington
Phoenix Deer Valley Airport Tower (DVT)
The pilot deviation was reported by the Deer Valley Tower when the aircraft entered the Deer Valley Class Delta Airspace without first establishing two-way radio communications with the tower.
3/31 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Out of Nevada
Phoenix Deer Valley Airport Tower (DVT)
The aircraft entered the Deer Valley Class Delta Airspace 4.4 miles north-northeast, and was heading southbound. Both of Deer Valley’s north and south controllers reached out to the aircraft without getting a response. The aircraft never made contact with the Deer Valley tower before turning back northbound and exited the delta airspace to the northwest. The Deer Valley north controller had to cap a Cessna’s altitude while it was operating in the pattern to avoid a conflict with the errant aircraft. No further incident had occurred.
4/1 Entering Class Delta Airspace Without First Establishing Communication
Sport Pilot
Mesa Falcon Field Airport Tower (FFZ)
The aircraft transitioned through the Falcon Field Class Delta Airspace from the east to the northwest at 2,900 feet. The pattern altitude is 2,400 feet. The aircraft made no attempt to contact the tower for the transition. A Basher was issued.
4/2 Entering Class Delta Airspace Without First Establishing Communication
Private Pilot
Out of Nevada
Phoenix Deer Valley Airport Tower (DVT)
The pilot deviation was reported by the Deer Valley Tower when the Cessna entered the Deer Valley Class Delta Airspace without first establishing two-way radio communications.
ATC INSTRUCTIONS
3/7 Failure To Comply With ATC Instructions
UNK Pilot Certification
Out of Utah
Phoenix Deer Valley Airport Tower (DVT)
The pilot deviation was reported by the Deer Valley Tower when the helicopter did not comply with the altitude assigned by ATC.
RUNWAY INCURSION
3/17 Entering A Runway Without Authorization
Private Pilot
Out of New Mexico
Tucson International Airport (TUS)
The Piper did not follow taxi instructions, and crossed the hold short line of Runway 11L without ATC authorization. Ground Control (GC) instructed the Piper to taxi to Runway 11L via Taxiway Delta, and hold short of Runway 21. The read back was correct. GC instructed the Piper to cross Runway 21 and hold short of Taxiway Delta 2 for opposite direction traffic. The Piper read back hold at Taxiway Delta 2. The Piper passed Taxiway Delta 2 and GC instructed the aircraft to make two 180s and hold short of Taxiway Delta 2. The Piper read back taxi. GC instructed the Piper to taxi to Runway 11L via Delta after traffic had passed. The Piper was still past Taxiway Delta 2 and GC instructed them to make another 180. GC amended the taxi instructions to Runway 11L via Taxiways Delta, Alpha and Alpha 3. The Piper made the wrong turn at Taxiway Alpha and held short of Runway 21. GC instructed them to make a 180 and follow a Challenger via Taxiways Alpha and Alpha 3. The Piper read back follow the Challenger. The Piper did not follow the Challenger but turned onto Taxiway Delta and crossed the hold short line of Runway 11L.
3/19 Entering A Runway Without Authorization
Private Pilot
Out of North Dakota
Tucson International Airport (TUS)
The Light Jet entered Runway 11L at Taxiway Delta without ATC authorization. The Controller transmitted asking if the jet was ready with no response. The controller then transmitted again, asking the jet if they were up with no response. The Jet then transmitted saying “cleared for takeoff Runway 11L” as they entered Runway 11L. The controller then issued a takeoff clearance for Runway 11L and advised the aircraft they needed to wait for a clearance next time. No other traffic was involved. A Brasher was issued.
3/20 Entering A Runway Without Authorization
Commercial Pilot
Out of California
Scottsdale Tower (SDL)
The pilot deviation was reported by the Scottsdale Tower when the Beechcraft crossed the Runway 21 hold short line without ATC authorization.
3/20 Entering A Runway Without Authorization
No Pilot Certification Available
Chandler Tower (SDL)
A vehicle was observed entering RWY 22R on the north side of the runway near Taxiway Hotel and drove down to the approach end of the runway, then turned around and exited at the departure end of the runway. All this was done without communicating with ATC.
3/26 Entering A Runway Without Authorization
No Pilot Certification Available
Phoenix Sky Harbor Tower (PHX)
A pedestrian crossed Runway 25R from Taxiway Foxtrot 12 to the western edge of Taxiway Echo 12 with an air carrier on final.
3/28 Entering A Runway Without Authorization
Private Pilot
Out of Minnesota
Mesa Falcon Field (FFZ)
The pilot deviation was reported by the Falcon Field Tower when an aircraft landed on Runway 22R without ATC authorization.
3/29 Entering A Runway Without Authorization
Private Pilot
Phoenix Deer Valley Tower (DVT)
The Cessna entered Taxiway Charlie and started it’s departure roll without ATC authorization. Ground Control (GC) had instructed the Cessna to taxi via Taxiway Delta for a Runway 7R departure, then to continue taxi via Taxiway Delta 1. The pilot read back the runway assignment, taxied to Taxiway Delta 1, and advised they were ready for departure. The controller cleared the Cessna for takeoff on Runway 7R. The read back was correct but the Cessna turned onto Taxiway Charlie and started it’s departure roll. The Controller instructed the aircraft to stop. No other traffic was involved.
4/7 Entering A Runway Without Authorization
Student Pilot
Mesa Falcon Field (FFZ)
The Cessna was holding short of RWY 4L, and called ready for departure. The North Controller responded with the instruction “Hold short RWY 4L, landing traffic”, and the Cessna read it back correctly. The Cessna then Taxied out onto the runway with an aircraft on a 1 mile final. The controller saw the Cessna on the runway, and told the Piper on final to go around. The Cessna exited the runway without further incident.
SURFACE INCIDENT
3/11 Entering A Taxiway Without Authorization
Unknown Pilot Certification
Phoenix Sky Harbor Airport (PHX)
An unspecified vehicle, or person, entered Taxiway Delta without ATC authorization.
3/19 Entering A Taxiway Without Authorization
Private Pilot
Mesa Falcon Field Airport (FFZ)
The pilot deviation was reported by the Falcon Field tower when a Cessna entered Taxiways Echo, and Echo 1 without ATC authorization.
MOVEMENT AREA
3/8 Entering A Movement Area Without Authorization
Private Pilot
Williams Gateway Airport (IWA)
The aircraft was instructed to taxi via TWY Y and to hold short of TWY G. The aircraft was observed to be on TWY B from TWY Y2.
WRONG SURFACE LANDING
3/9 Landing On The Wrong Runway
Private Pilot
Phoenix Deer Valley Airport (DVT)
A VFR Cessna was in the left traffic pattern for runway 7L. When the Cessna completed their left base to final turn, the aircraft had overshot the final for 7L, and misaligned for, and landed on runway 7R. A VFR Piper was on right base for runway 7R when the pilot advised the South Controller that they were initiating a go-around maneuver when the pilot observed the Cessna was on final and landing on runway 7R. No direct overflight occurred between any of the aircraft.
4/8 Landing On The Wrong Surface
Private Pilot
Prescott Airport (PRC)
The VFR Aircraft was cleared to land on Runway 3L, however, they aligned with and landed on a closed portion of Taxiway C. There were no other aircraft or vehicles involved.
NORDO INCIDENT
3/13 Departure Without Radio Communications
Private Pilot
Out of Montana
Tucson International Airport (TUS)
A departing Mooney was given a left turn to “A” mountain, and then on course (A left downwind departure), and the Mooney was told to maintain at or below 4000, but there was no response to the controllers’ instructions. The Mooney was then told to turn left to a heading of 270°, and there was still no response. The controller called the traffic to a Tecnam Twin, and a Vans RV, and they turned to avoid the departing traffic, and they also reported the Mooney in sight. The Tucson TRACON called the Tucson Tower to determine if the Mooney was talking with them, and if they had the twin in sight. The Tucson TRACON was asked to issue a Brasher warning.