by Jim Timm

 

These pilot deviations need to be examined to determine if a common threat exists that should be addressed to help reduce the number of deviations that occur and thus enhance aviation safety.

In the time period from August 12 through September 15 there were sixteen pilot deviations recorded by the FAA SDL FSDO. These deviations were committed by all pilot certificate levels, from student to ATP, and of the sixteen deviations made, there was a need to issue eight Brashers. This month there were also eight out-of-state pilots committing pilot deviations. The number of deviations was about the same as the last reporting period.

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 their thoughts for their future interaction with Flight Standards.

Pay attention to ATC instructions and follow them, and if you can’t comply, tell ATC why you can’t. Just don’t try to be creative out there without first talking to ATC, and always be aware of what type of airspace you are flying in, or may be about to enter, and what may be expected of you. Always fly with care and forethought.

The details of the deviations this month are as follows:

 

IFR DEVIATION

9/13      IFR Altitude Deviation

             UNK Pilot Certification

             From Mexico

             Albuquerque Center Airspace

At 0238z, the Albuquerque Center controller cleared the aircraft to descend to and maintain FL380. The aircraft read back the clearance correctly. At 0242z, Albuquerque Center observed the aircraft was below the assigned altitude and re-cleared the aircraft to FL380. The aircraft had made an unauthorized descent to 37,600 feet which resulted in a loss of separation with an air carrier, who was level at FL370. Event occurred near Bagdad. A Brasher was issued.

 

CLASS DELTA AIRSPACE DEVIATIONS

8/11      Entering Class Delta Airspace Without First Establishing Communication

Commercial/CFI Pilot

Scottsdale Tower

The Piper was 5 miles southeast of the airport northbound approaching the airport’s Delta Airspace boundary and entered the Delta Airspace without first establishing radio communications. The Piper turned to exit the airspace, and then re-entered the Delta Airspace. The controller reached out multiple times to determine if the Piper was on the frequency but got no response. Another aircraft was inbound on the visual approach for runway 21, and the controller had to hold the aircraft at their altitude and called out the Piper traffic in order to deconflict the inbound aircraft and the Piper airplane. The inbound aircraft reported the Piper traffic in sight and began a descent. Once radio communication was established with the Piper, they were given the Brasher notice.

 

8/14      Entering Class Delta Airspace Without First Establishing Communication

Private Pilot

From California

Deer Valley Tower

The Cessna entered the Deer Valley (DVT) class D airspace without establishing two-way radio communications. There was no loss of separation, however, the tower supervisor called the Phoenix TRACON to have them issue a Brasher warning to the Cessna. DVT was never in contact with the Cessna.

 

8/29      Entering Class Delta Airspace Without First Establishing Communication

Private Pilot

Gateway Tower (IWA)

The Piper aircraft entered the Gateway Delta Airspace from the northwest and proceeded across the 2-mile final approaches to Gateway and proceeded west bound and exited the Delta Airspace at 3,000 MSL without ever establishing communications with IWA ATCT. The Chandler Tower issued a Brasher notice to the Piper

 

8/30      Entering Class Delta Airspace Without First Establishing Communication

Private Pilot

From California

Gateway Tower (IWA)

The aircraft entered the Gateway Delta Airspace from the northwest at 2,500 MSL and proceeded abeam a 2-mile final for runway 12R, then turned westbound, and exited the airspace.

 

AIR TRAFFIC CONTROL INSTRUCTIONS

8/15      Failure to follow the Air Traffic Control Instructions.

Private Pilot (From Sedona)

Mesa Falcon Field (FFZ)

The Cessna was inbound from the north, and the controller gave instructions to cross over the field for a right down wind for RWY 4R. The Cessna was cleared to land on RWY 4R. However, the aircraft overshot the final by an extreme amount, and executed a go-around, and he was instructed to maintain an altitude of 1,900 feet to stay below the traffic in the left-hand pattern at 2,400 feet. The pilot read back the instruction but continued to climb as high as 2,200 feet before finally descending after being told to descend to or below 2,000 feet three times. Two aircraft on the left downwind were turned to avoid a potential conflict. Once the Cessna had landed, the pilot didn’t know where he was supposed to go. He then said he was supposed to go to the north side, and was instructed to hold short of RWY 4R at taxiway D5, but turned the wrong way on taxiway Delta, and had to be stopped by Ground Control at D6, causing an aircraft on RWY 4R to roll out long to taxiway D8 because the Cessna was blocking the Delta 6 intersection. After another 15 minutes of touring the airport, trying to figure out where he was parked, the Cessna shut down, and the pilot was given a phone number to call. A Brasher was issued after the initial landing

 

8/31      Failure to follow the Air Traffic Control Instructions.

Student Pilot

Mesa Falcon Field (FFZ)

The Piper was given right traffic on departure, but made left traffic instead, and no other traffic was involved. Upon landing, the Piper could not give a proper read back for the hold short instructions, and after crossing the runway, the Piper was told to contact ground, but instead, taxied into the ramp without contacting ground control.

 

MOVEMENT AREA DEVIATIONS

8/8      Moving in A Movement Area Without Authorization

Commercial Pilot

From Minnesota

Gateway Airport (IWA)

The pilot deviation was reported by the IWA Tower when the airplane entered a closed portion of taxiway Kilo without ATC authorization.

 

8/12      Moving in A Movement Area Without Authorization

Private Pilot

Chandler (CHD)

The Cessna taxied without talking to the Ground Controller. The Cessna made a call on the Tower frequency as if the Tower was closed. Later the Cessna pilot stated he had the ATIS, but that Foreflight said the tower was closed. A Brasher was issued prior to his departure.

 

8/14      Moving in A Movement Area Without Authorization

Commercial Pilot

Tucson (TUS)

The Cessna advised Ground Control that they were at taxiway ALPHA three, and then ALPHA two, and were ready to go. The Cessna was actually on taxiway DELTA. Ground Control asked if the Cessna had received a taxi clearance, to which they responded, “Clearance had been given to them”. The Cessna was then informed they needed a clearance to taxi to the runway and were given the Brasher warning.

 

RUNWAY INCURSIONS

8/2      Entering a runway without ATC authorization.

Student Pilot

Gateway Airport (IWA)

The Piper landed on RWY 30L and was issued runway exit instructions to exit at taxiway Kilo. In exiting the runway, the Piper passed the runway edge line, however, they did not clear the hold short line on Kilo, thus not officially clearing RWY 30L. A Cessna was issued a departure clearance on RWY 30L at taxiway Lima. As the Cessna began its departure rollout it was recognized that the Piper was not clear at taxiway Kilo, and the tower canceled The Cessna takeoff clearance after it had rolled approximately 50 feet down the runway. The Cessna was instructed to hold position on the runway, and once the Piper had cleared the runway the tower reissued a departure clearance to the Cessna. The closest distance between the two aircraft was approximately 3,000 feet. 

 

8/13      Entering a runway without ATC authorization.

Commercial/CFI Pilot

Gateway Airport (IWA)

A Piper aircraft conducted a touch and go to runway 30C without ATC authorization. The Piper was on a VFR instrument approach to runway 30C, and the controller cleared the Piper for a low approach to runway 30C. The pilot read back, cleared for the option. The controller corrected the Piper and cleared them for a low approach only due to an air carrier that was departing runway 30C ahead of them. The Piper read the clearance back correctly, however, the Piper conducted a touch and go instead of a low approach behind the air carrier.

 

8/14      Entering a runway without ATC authorization.

Commercial/CFI Pilot

From North Carolina

Phoenix Deer Valley (DVT)

The pilot deviation was reported by the Deer Valley Tower when the Cessna crossed the hold short line of runway 7L without ATC authorization.

 

8/19      Entering a runway without ATC authorization.

UNK Pilot Certification

From Utah

Scottsdale Airport (SDL)

The pilot deviation was reported by the Scottsdale Tower when the aircraft entered runway 21 without ATC authorization.

 

9/2      Entering a runway without ATC authorization.

ATP/CFI Pilot

From Florida

Gateway Airport (IWA)

The pilot deviation was reported by the Gateway Tower when the Cessna landed on runway 30L without ATC authorization.

 

9/4      Entering a runway without ATC authorization.

Private Pilot

From Alabama

Phoenix Deer Valley Airport (DVT)

The Mooney was instructed to taxi to runway 7R at intersection C2. The aircraft taxied as instructed but went past the hold short line for runway 7R at C2 but was still short of the runway edge line. The ground controller noticed the aircraft had crossed the hold short lines, and coordinated with the local south controller, and then taxied the airplane onto the runway, and back off at C3, and then back to runway 7R at C2. The aircraft was issued the Brasher by the ground controller once they were off the runway. No other aircraft were impacted.

Please login to add a comment.