aviation_accident_summary_october_2018.jpg

  

by Jim Timm

 

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

In the period from April 15 through May 12 there were nineteen pilot deviations recorded by the FAA SDL FSDO. These deviations were committed by student, private, commercial, CFIs, and ATP pilots. Of the nineteen deviations made, there was only a need to issue two Brashers, and they both were for runway incursions. It was interesting to note that this month there were only three out of state and two foreign pilots committing pilot deviations. Overall, the number of deviations were down this reporting period.

A controller will issue a Brasher notification when further FAA action will be taken, and the controller is giving the airman the opportunity to make note of the occurrence, and collect their thoughts for 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 do something without advising them. Always know what type of airspace you are flying in, or may be about to enter, and please fly with more care and forethought.

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

Five IFR Deviations

Three Class Delta Airspace Deviations

Three Air Traffic Control Instruction Deviations

One Wrong Surface alignment Deviation

Seven Runway Incursions

The details of the deviations this month are as follows:

 

IFR DEVIATIONS

 

4/7        Route (SID) Deviation

Unknown Pilot Certification

Scottsdale (SDL)

The pilot deviation was reported by the Phoenix TRACON when the aircraft did not fly the assigned departure heading.

 

4/15 Altitude Deviation

Private Pilot

Albuquerque Center (ZAB)

At 2217z, the controller climbed the Beechcraft to FL210. At 2224z, the controller amended the request to the Beechcraft to climb to FL190. At 2228z, traffic was issued to the Beechcraft and to a Cessna who was at FL200. At 2230:18z, the Beechcraft was observed climbing at FL191. At 2230:39z, the controller issued a traffic alert and issued a request for the Beechcraft to descend to FL190 immediately. The Beechcraft was observed as high as FL193 and passed behind the Cessna. Closest proximity was 3.28 NM and 700ft. The Beechcraft pilot stated that when he was issued the traffic call, he looked out the window for the traffic and did not see the other aircraft.

 

4/30 Altitude (STAR) Deviation

Private Pilot

Nevada Pilot

Phoenix TRACON

The Beechcraft had descended below his assigned altitude of 11,000 feet. The pilot stated he was descending via the STAR (the DSERT TWO ARRIVAL does not have a descend via the STAR). The Beechcraft’s descent below 11,000 feet resulted in a loss of separation with a Piper northbound at 10,000 feet. The closest proximity was 2.02 NM and 300 feet vertical.

 

5/2 Altitude Deviation

Unknown Pilot Certification

Foreign Pilot (Mexico)

Tucson

The Piper aircraft was assigned a descent to 11,000 feet and told to expect a Visual Approach to RWY 29R at Tucson. The aircraft had descended below 11,000 feet. ATC observed the aircraft below 11,000 feet and issued him a Low Altitude Alert. The aircraft stated he thought he had been cleared for a Visual Approach. The aircraft’s descent below 11,000 feet resulted in a loss of separation with terrain/obstacles.

 

5/9 Altitude Deviation

Unknown Pilot Certification

Albuquerque Center (ZAB)

The Albuquerque Center Controller had cleared the aircraft to climb to, and maintain 10,000 feet. The aircraft read back the clearance correctly. At 1602z, Albuquerque Center observed the aircraft above the assigned altitude and re-issued 10,000 feet. The aircraft had made an unauthorized climb to 11,000 feet which resulted in a loss of separation with another aircraft that was at 11,000 feet. The event occurred near Casa Grande. A Brasher was NOT issued. Closest observed proximity was 4.09 NM and 800 ft.

 

CLASS DELTA AIRSPACE DEVIATIONS

 

4/15 Entering Class Delta Airspace Without Obtaining Prior Authorization

Private Pilot

Mesa (FFZ)

A Pilot deviation was reported by the Falcon Field tower when an aircraft entered the

Falcon Field Air Space without an ATC clearance. (Note: Pilot had an excursion in 12/2021 that substantially damaged a former similar aircraft, and the registration records indicate the pilot may have traveled here to purchase another similar aircraft.)

 

4/29 Entering Class Delta Airspace Without Obtaining Prior Authorization

Private Pilot

California Pilot

Phoenix (DVT)

The pilot deviation was reported by the Phoenix Deer Valley Tower when the aircraft entered the DVT Class Delta Airspace without obtaining an ATC clearance.

 

5/1 Entering Class Delta Airspace Without Obtaining Prior Authorization

Unknown Pilot Certification

California Pilot

Phoenix (DVT)

The pilot deviation was reported by the Phoenix Deer Valley Tower when the aircraft entered the DVT Class Delta Airspace without obtaining an ATC clearance.

 

AIR TRAFFIC CONTROL INSTRUCTIONS

 

4/14 Failure to follow the Air Traffic Control Instructions.

ATP/CFI Pilot

Phoenix TRACON

The pilot deviation was reported by the Phoenix TRACON when the aircraft failed to maintain an altitude assigned by ATC in the Chandler Airport (CHD) area.

 

4/16 Failure to follow the Air Traffic Control Instructions In a Movement Area.

Private Pilot

Phoenix Gateway (IWA)

The aircraft landed on Runway 12C, and was holding short of Runway 12R on Taxiway K. The Tower Controller instructed the aircraft to cross Runway 12R and contact Ground Control. The pilot read back was correct. The aircraft crossed Runway 12R and attempted to call Ground Control but Ground Control was on the landline coordinating. The aircraft continued taxiing straight ahead crossing Taxiway B, and onto a closed portion of Taxiway K.

 

5/6 Failure to follow the Air Traffic Control Instructions.

Unknown Pilot Certification

Mesa (FFZ)

The pilot deviation was reported by the Falcon Field (FFZ) Tower when the aircraft did not follow Air Traffic Control Pattern Instructions.

 

RUNWAY INCURSIONS

 

4/12 Entering a runway without ATC authorization.

Private Pilot

Prescott (PRC)

Ground Control had instructed a Piper aircraft to taxi via taxiway B4 and hold short of RWY 3R at taxiway C4 for a RWY 30 departure, and the pilot read back was correct. The Tower had cleared a commuter aircraft for takeoff on RWY 3R. Ground Control observed the taxing Piper aircraft not slowing down and instructed them to stop. The aircraft had crossed the RWY 3R hold line but stopped short of the RWY 3R edge line on taxiway C4. The closest estimated proximity when the commuter aircraft passed Taxiway C4 was approximately 50-55 feet lateral.

 

4/13 Entering a runway without ATC authorization.

Student Pilot

Phoenix Goodyear (GYR)

A Piper aircraft called the Tower and advised that they were ready. The Tower instructed the Piper to hold short of Runway 21, and the read back was correct. The Piper taxied across the hold short line, and stopped short of the runway edge line, and then asked the Tower if they were supposed to hold short of the runway or get on it. The Tower issued a go around to an aircraft that was on a 1 mile final. The Tower then cleared the Piper for takeoff.

 

4/14 Entering a runway without ATC authorization.

Commercial/CFI Pilot

Prescott (PRC)

A Cessna on a 1/2 mile final for RWY 21L was sent around due to an aircraft that was in a line up and wait position on the runway. The aircraft on the runway had been instructed to hold short of RWY 21L, and they read the clearance back correctly. The Cessna did not overfly the aircraft on the runway, and the aircraft on the runway was instructed to exit RWY 21L at taxiway D6, and Ground Control issued a Brasher warning to the aircraft.

 

4/14 Entering a runway without ATC authorization.

Private Pilot

Chandler (CHD)

The Piper aircraft called Ground Control for taxi instructions to RWY 4L, instructions were given, and the read back was correct. The Piper aircraft entered taxiway A at taxiway M, and instead of turning right, they kept going straight ahead onto RWY 4L at taxiway M. Ground Control became aware of the situation, and alerted the Tower Controller, and advised the Piper to immediately exit RWY 4L. The Tower controller sent an aircraft around that was on a 1/4 mile final, and the Piper was able to exit RWY 4L before the aircraft on final crossed the RWY 4L threshold.

 

4/16 Departing a runway without ATC authorization.

Commercial/CFI Pilot

Mesa (FFZ)

A Piper aircraft called the Tower Controller while holding short of Runway 4R, and advised that they were ready for departure. The Tower instructed the Piper to line up and wait on Runway 4R, and advised them of traffic that would cross downfield. The Piper read back was, “cleared for takeoff Runway 4R”. The Tower did not catch the incorrect read back, and the Controller instructed another aircraft to cross Runway 4R at Taxiway Charlie. The Controller then observed the Piper aircraft departing, and quickly canceled the crossing clearance before the aircraft had crossed the hold short bars of Runway 4R. The Tower advised the Piper when they were airborne that they had not been cleared for takeoff.

 

4/18 Entering a runway without ATC authorization.

Unknown Pilot Certification

Canadian Pilot

Phoenix (IWA)

A Beechcraft was given instructions to hold short of RWY 30L, and the read back was correct. Another aircraft departed down field, and the Beechcraft was observed on the runway holding in position during the departure. The Beechcraft was then cleared for takeoff, and when switched to Departure Control, the Tower Controller instructed the Departure Controller to give a Brasher Warning to the Beechcraft.

 

5/2 Crossing a runway without ATC authorization.

Unknown Pilot Certification

Tucson (TUS)

The aircraft crossed runway 29L without ATC authorization.

 

WRONG SURFACE ALIGNMENT

 

4/15 Aligned with the wrong surface for landing.

Private Pilot

Texas Pilot

Phoenix (PHX)

The pilot deviation was reported by the Phoenix TRACON when the aircraft flew through the runway 25L final and conflicted with traffic to runway 26.

Please login to add a comment.