ARIZONA SAFETY ADVISORY GROUP

AUGUST THRU SEPTEMBER

PILOT DEVIATIONS

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 August 8 thru September 9 there were nine deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Student Pilot thru ATP, and there were six out of state pilots.

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 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.

I would hope that pilots would get the message to be more careful in their flying. Some of these 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 would like to think that the information being presented here is valuable to all pilots, and it will make them safer pilots.

Pilots must be alert, and listen carefully to ATC instructions and comply with them, and if they can’t comply, tell ATC why they can’t. 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.

In summary, the general aviation deviations this reporting period are:


1 Phoenix Class Bravo Airspace Deviation 1 Class Delta Airspace Deviation
6 ATC Instructions 1 Runway Incursion

No Brasher No Brasher 1 Brasher 1 Brasher

The details of the deviations this month are as follows.

PHOENIX CLASS BRAVO AIRSPACE DEVIATION (1)

August 14 Entering Phoenix Class Bravo Airspace Without First Having Authorization Private Pilot
Out Of Nevada
Phoenix TRACON  (P50)

The pilot violated the Class Bravo airspace in the 4,000-9,000 and 5,000-9,000 box approximately 16 miles east of PHX after departing Chandler. The pilot stated they had an electrical issue, but did not declare an emergency.  He did elect to return to Chandler, and didn’t conflict with any other traffic.


CLASS DELTA AIRSPACE DEVIATION (1)

August 20 Entering The Class Delta Airspace Without First Establishing Two away Communications
Private Pilot
Chandler Municipal Airport (CHD)

On initial contact the pilot stated they were 10NM north of the airport when in fact they were already on a 3NM final to the RWY, and were in conflict with a VFR aircraft in the pattern. The pilot had entered the Chandler Class D Airspace without first establishing communication or obtaining ATC approval.

AIR TRAFFIC CONTROL INSTRUCTION DEVIATIONS (6)

August 5 Failure To Follow ATC Instructions ATP Pilot
Out Of Kansas Albuquerque Center  (ZAB)

The Citation Jet was northwest bound on the KEENS3 departure to WLVRN via PKE to WOTRO, at FL320. The pilot turned right at WLVRN towards WOTRO, and had entered the GLADDEN ATCAA which was active up to FL400. The pilot acknowledged that they had mistakenly left out the PKE intersection when inputting the route after the clearance.

August 5 Failure To Follow ATC Instructions Comm/CFI Pilot
Mesa Falcon Field Airport (FFZ)

The Lancair was cleared for take-off on the SACAT4 departure, and to maintain 3,000 ft, and remain IFR. At the departure end of the runway the aircraft had drifted to the parallel upwind runway. The controller was trying to advise the pilot the deviation, but there was no response until the 3rd or 4th try. The pilot was also squawking a VFR code, and the controller was trying to advise the pilot of the proper SQUAWK code. Additionally, the pilot climbed above the altitude issued, they had climbed to 3,400 ft. The controller was also trying to have the pilot descend to the correct altitude, but pilot was not listening.  Coordination with the Phoenix TRACON, and the Chandler Airport had to be made to maintain the airspace safety.

August 7 Failure To Follow ATC Instructions ATP Pilot
Out Of Louisiana Phoenix TRACON   (P50)

A Challenger departing PHX on the ECLPS1 departure, and flew the RWY Heading instead of complying with the SID. The Challenger was observed more than 2 miles off the departure end of the RWY at 2.2 miles and 600 feet in trail of another aircraft on the MRBIL departure. The SANTAN controller issued an instruction to separate the aircraft. A Brasher was issued by the SANTAN Controller.

August 19 Failure To Follow ATC Instructions No Pilot Information Tucson TRACON  (U90)

The aircraft departed Tucson International VFR northwest bound, and was instructed by ATC to maintain at or below 5,000 feet until further advised. The pilot climbed to 5,900 without ATC clearance, and causing a potential conflict with two F-16’s.

August 27 Failure To Follow ATC Instructions ATP Pilot
Out Of California
Mesa Falcon Field   (FFZ)

The pilot entered the Falcon Field Class Delta Airspace from the Northwest at 2,800 ft indicating
170 KTS without communicating with ATC. The controller reached out to the aircraft without getting a response. A second controller also reached out to the aircraft without getting a response. Four miles north of the field on a southeast heading the aircraft reached out to the second controller, and was immediately told to remain outside of the Class Delta Airspace. The aircraft asked if the airport was closed, and the controller issued a northbound instruction to avoid multiple aircraft on the extended
left downwind for the runway. The aircraft was then transferred back to the first controller, and the aircraft was 9-1/2 mile north for the runway, ATC instructed the aircraft to maintain at or above 3,000 ft until advised. On a 5-1/2 mile final the aircraft had descended to 2,800 ft, and ATC instructed them to climb to 3,000 ft, and issued an altimeter setting.

August 31 Failure To Follow ATC Instructions No Pilot Information
Unknown Location But Out Of Arizona Scottsdale Airport  (SDL)

A Light Jet was issued an IFR clearance by the Scottsdale ATC. The aircraft was taxiing to the runway, and they notified the tower that they would be ready at the end of the runway. The tower responded that the facility was closing, and the pilot would need to contact the Phoenix TRACON Departure for their IFR release, and issued them the frequency. Scottsdale made their closing broadcast. The airplane departed Scottsdale without contacting the Phoenix TRACON, and did not obtain an IFR release 2 minutes after the Scottsdale tower had closed.

RUNWAY INCURSION (1)

August 4 Taxiing Onto A Runway Without Authorization Student Pilot
Out of Utah
Mesa-Gateway Airport (IWA)

The Piper said he was holding short of the center runway at taxiway PAPA for pattern work, and was instructed cross the center runway at PAPA, and hold short of the right runway, and was issued a frequency change to the controller for the right runway. The Piper was observed holding in position on the center runway at the approach end. A GALAXY was inbound on a three mile visual final IFR approach for the center runway. Both controllers attempted to contact the Piper with no response initially. The GALAXY was sent around when it was on a two mile final, and was instructed to offset to the right of the runway, and continue in the traffic pattern. The Piper was taxied down the center runway to taxiway K, and issued the Brasher. The Piper taxied back to the ramp.