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 March 15 through April 9 there were seven deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with certificates ranging from Private Pilot through Commercial/CFI, and there were four out of state pilots of the seven deviations reported, and there wasn’t a Brasher issued.

Note: These pilot deviations were 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 think more of the pilots have gotten the message to be more careful in their flying. Perhaps 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 certainly like to think that the information 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. Fly with care and forethought, and don’t be part of the problem.

The details of the deviations this month are as follows.

 

PHOENIX CLASS BRAVO AIRSPACE DEVIATIONS (3)

 

March 16   Entering Class Bravo Airspace Without First Having Authorization

             No Pilot Information

             Phoenix Sky Harbor Tower (PHX)

The aircraft entered the Phoenix Class Bravo Airspace without first contacting ATC and obtaining a clearance and establishing two-way radio communication.

 

March 22 Entering Class Bravo Airspace Without First Having Authorization

Private Pilot

Out Of California

Phoenix TRACON (P50)

The aircraft departed from Scottsdale VFR and requested flight following. They were given a transponder code but never entered it into the transponder. They climbed to 4,800 feet and entered the Phoenix Class Bravo Airspace without a clearance.

 

March 27 Entering Class Bravo Airspace Without First Having Authorization

Private Pilot

Phoenix Sky Harbor Tower (PHX)

The aircraft was identified through their ADSB and had entered the PHX Class Bravo Airspace without first establishing communication and without an authorization.

 

AIR TRAFFIC CONTROL INSTRUCTION DEVIATIONS (4)

 

March 19 Failure to Follow ATC Instructions

Commercial/CFI Pilot

Out Of South Dakota

Mesa Falcon Field (FFZ)

The pilot was expected to turn on final and remain on final for the assigned runway. However, the pilot elected to leave the final and make 360 turn that crossed a parallel runway final.

 

March 21 Failure to Follow ATC Instructions

Private Pilot

Mesa Falcon Field (FFZ)

The pilot was instructed to follow the traffic downwind and ahead but instead turned on a base and didn’t follow the traffic ahead.

 

March 23 Failure to Follow ATC Instructions

Private Pilot

Out Of Kansas

Phoenix TRACON (P50)

The aircraft did not fly the DVT3 departure as published, and the pilot turned right instead of left.

 

March 26 Failure to Follow ATC Instructions

Commercial Pilot

Out Of Texas

Scottsdale Municipal Airport (SDL)

The aircraft departed Scottsdale and checked in on the RWY heading. The controller confirmed they were assigned the Scottsdale Departure Procedure and they said they were. They were then issued a 300° heading. But the aircraft turned to a 260° track and had to be reissued the 300° heading.

Please login to add a comment.