NOVEMBER 2024 AVIATION ACCIDENT & INCIDENT SUMMARY
By Jim Timm
The following are the reports of aviation accidents, and incidents that have occurred in Arizona from
mid October thru mid November. We hope to use the following detailed accident/incident information
to develop safety programs, briefings, and posters/flyers that would help pilots learn from the
mistakes being made by others, and be able to take the necessary action to prevent them from
having similar occurrences.
The Accident/Incident report is not very good this time. The number of occurrences was a bit high, but
of most concern was an incident that claimed the lives of five persons, four in the aircraft , and one a
passing vehicle. We all need to continue to do what we can to prevent accidents, and these more
pleasant temperatures we have been enjoying may also encourage more people to fly.
In continuing with the expanded scope of the report, we’re using information from the Aviation Safety
Network (ASN), FAA, NTSB, and APA Members. This more inclusive information source suits our
purpose of trying to get an idea of what is happening out there so we can help make flying safer.
In the mean time, here are the results from the above sources.
Date: October 12, 2024
Source: FAA Incident
Location: Mesa Falcon Field (FFZ)
Type: Cessna 414
Injuries: 2 Uninjured
Commercial Pilot
FLAT TIRE
During high speed taxing on the runway the aircraft got a flat tire causing damage to the fender. the
aircraft was towed back to the parking ramp without further incident. The damage was minor.
Date: October 17 , 2024
Source: FAA Incident
Location: Tucson Ryan Field (RYN)
Type: GlaStar LSA
Injuries: UNK
ATP/CFI Pilot
LOSS OF CONTROL LANDING
While doing touch and goes the aircraft ground looped, and blew out a main tire. No other aircraft
were involved.
Date: October 19 , 2024
Source: FAA Incident
Location: 18 NM East of Phoenix/Mesa Gateway Airport (IWA)
Type: Piper PA-28R-200 Arrow
Injuries: 1 Uninjured
Private Pilot
FUEL STARVATION
Because of the engine issues a gear up landing was made on a road 18 NM east of Phoenix/Mesa
Gateway Airport (IWA). The damage to the prop, and wing was assessed to be minor.
Date: October 23, 2024
Source: FAA Incident
Location: Scottsdale (SDL)
Type: Cessna 441 Conquest II
Injuries: 1 Uninjured
Private Pilot
LOSS OF CONTROL ON TAKEOFF
On departure the aircraft went off the runway, and into some rocks. The damage was assessed to be
minor.
Date: October 27, 2024
Source: ASN
Location: Sait George, Utah
Type: Cirrus SR20 G6
Injuries: 3 Minor Injuries
Private Pilot
OFF AIRPORT LANDING
After departing Saint George Municipal Airport (SGU) the Cirrus made an off-airport landing about 5
mi south of the airport, and the aircraft was completely destroyed by fire. They had refueled at Saint
George, and the airplane was unable to establish a climb after takeoff, and it appeared the pilot was
attempting to return to Saint George.
Date: October 31, 2024
Source: ASN, FAA
Location: Prescott
Type: Piper PA-28-300 Cherokee Six
Injuries: 1 Uninjured
Private Pilot
ENGINE FIRE
The aircraft crashed in a field three miles east of Prescott (PRC) due to an engine fire, and smoke in
the cockpit.
Date: November 4, 2024
Source: FAA Incident
Location: Scottsdale (SDL)
Type: Aviat S-2C (Pitts Airplane)
Injuries: 1 Uninjured
ATP Pilot
LOSS OF CONTROL
The aircraft went off the runway, and into the gravel. Airport operations helped remove it from the
gravel, and no damage was incurred.
Date: November 5, 2024
Source: APA, ASN, FAA, NTSB
Location: Mesa Falcon Field (FFZ)
Type: Honda HA-420 Honda Jet
Injuries: 5 Fatalities 1 Serious Injury
Private Pilot
OVER RAN RUNWAY
A Honda Jet was destroyed when it crashed during an aborted takeoff attempt at Mesa Falcon Field
Airport (FFZ).
Four occupants of the aircraft, and the driver of a vehicle on Greenfield Rd. perished, and a person
on the airplane was seriously injured. ADS-B data suggests the airplane had accelerated to about 133
knots groundspeed before it aborted the takeoff roughly 3400 ft down the runway. The airplane was
unable to stop, overrun the end of the runway, and went through the airport perimeter fence before
crashing into a vehicle on North Greenfield Road, and a post crash fire ensued. The estimated
distance between the end of the departure runway and the aircraft final resting position was 700 ft.
Date: November 5, 2024
Source: FAA Incident
Location: Mesa Falcon Field (FFZ)
Type: Piper PA- ???
Injuries: 1 Uninjured
Student Pilot
LOSS OF CONTROL LANDING
The student landed and went off the runway into the unpaved area between the runways. Airport
Operations towed the aircraft to parking, and no damage was reported to the either the aircraft or
airport.
Date: November 7, 2024
Source: FAA
Location: Prescott (PRC)
Type: Cessna 172
Injuries: 2 Uninjured
Pilot Certification Unknown
TAXIED INTO FENCE
While taxing in a non-movement area the Cessna’s right wing struck a fence, and the aircraft
sustained substantial damage.
Date: November 8, 2024
Source: FAA Incident
Location: Casa Grande (CGZ)
Type: Piper PA-44-180
Injuries: 2 Uninjured
Pilot Certification unknown
GEAR UP LANDING
The Piper Seminole made a gear up landing, and the damage was minor.
Date: November 9, 2024
Source: FAA Incident
Location: Phoenix/Mesa Gateway Airport (IWA)
Type: Cessna T240 (Columbia 400)
Injuries: 1 Uninjured
Pilot Certification Unknown
RUNWAY EXCURSION
A major portion of the runway was closed, but the Cessna Columbia elected to land on the short open
portion of the runway. However, the aircraft rolled into the closed portion of the runway impacting
runway lights. The resultant damage was minor in nature.
Date: November 17, 2024
Source: ASN
Location: Near Cordes Lakes
Type: Cessna 172L
Injuries: 2 Minor Injuries
Pilot Certification Unknown
INFLIGHT LOSS OF POWER
The aircraft departed Phoenix Deer Valley Airport (DVT), and crashed during an attempted forced
landing following an inflight loss of engine power near Cordes Lakes.
OCTOBER - NOVEMBER
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 October 10 thru November 14, 2024 there were twenty-three pilot
deviations reported by the FAA SDL FSDO. These deviations were committed by pilots with
certificates ranging from Student Pilot thru ATP, and there were nine out of state pilots, and two
military pilots that committed these deviations. Of the twenty-three deviations reported, there was a
need to issue seventeen Brashers.
Note: A controller will 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.
Pilots need to listen carefully to ATC instructions and comply with them, and if you can’t comply, tell
ATC why you can’t. Also, when flying in controlled airspace, pilots should never be creative, but 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, don’t be part of the problem.
The details of the deviations this month are as follows:
IFR DEVIATIONS (4)
10/7 Route Deviation
ATP/CFI Pilot
Out of Texas
Albuquerque Center (ZAB)
The airplane had been cleared via after SSKEE direct GUP direct KJAS. The controller observed the aircraft
was off course and asked where they were navigating. The pilot stated they were direct JAS. The aircraft
did not fly the routing as cleared. The event occurred near Wolf Crossing in Coconino County. A Brasher was
issued.
10/14 Flight Plan Deviation
Comm/CFI Pilot
Albuquerque Center (ZAB)
The aircraft was inbound to CGZ, and the controller advised the pilot that radar services were
terminated and that he should close his flight plan via through the frequency he was on or through
flight service. The pilot acknowledged the clearance, but ZAB ATC did not receive the aircraft’s
cancellation. A Brasher was issued. Later the pilot stated that he canceled through ForeFlight.
10/17 Route Deviation
Private Pilot
Out of Utah
Albuquerque Center (ZAB)
The aircraft had been cleared via direct to PRC. The controller observed the aircraft was off course
and asked aircraft where they were navigating. The pilot advised they were flying direct PEVYU (an
initial approach fix to PRC). The aircraft had made an unauthorized turn direct to PEVYU. A Brasher
was issued.
10/24 Departure Deviation
ATP Pilot
Out of Virginia
Phoenix TRACON (P50)
The pilot deviation was reported by the TRACON when the pilot didn’t comply with the Scottsdale
LALUZ Departure Procedure. A Brasher was issued.
CLASS BRAVO AIRSPACE DEVIATION (3)
10/14 Entering Class Bravo Airspace Without Authorization
Student Pilot
Phoenix TRACON (P50)
The Piper violated the Phoenix Class Bravo Airspace approximately 16 miles northwest of the PXR
VOR at 6,600 MSL in the 6,000-9,000 foot box. A Brasher given.
10/30 Entering Class Bravo Airspace Without Authorization
Military Pilot
Phoenix TRACON (P50)
The pilot deviation was reported by the Phoenix TRACON when two Blackhawk helicopters entered
the Phoenix Class Bravo Airspace without authorization. A Brasher was issued by the San Tan
Sector Controller.
11/5 Entering Class Bravo Airspace Without Authorization
Comm/CFI Pilot
Out of Texas
Phoenix TRACON (P50
The Cirrus violated the Phoenix Class Bravo Airspace in the 7,000-9,000 block northeast of Sky
Harbor airport. The pilot had climbed from 8,100-9,200 feet, then descended back down to 7,800 feet
in the 8,000-9,000 block. A Brasher issued.
CLASS DELTA AIRSPACE DEVIATION (7)
10/10 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Mesa Falcon Field (FFZ)
The deviation was reported by Falcon Field when the Cessna entered the Falcon Field Class Delta
Airspace without first establishing two-way radio communications. The Brasher was issued by the
Chandler (CHD).
10/12 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Comm/CFI Pilot
Mesa Falcon Field (FFZ)
The aircraft entered the Falcon Field Class Delta Airspace without first establishing two-way radio
communications. A Brasher was issued.
10/16 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Pilot Certificate Unknown
Out of California
Flagstaff (FLG)
The Cessna called inbound from the west, and was given entry instructions. The airplane did not
acknowledge, and ATC reached out multiple times on all frequencies, and guard. The Cessna tried
to make a radio check as well. The Cessna switched to making calls in the blind on the downwind.
The Cessna then called on ground and was given taxi instructions. At the end of the runway, the
Cessna again made a CTAF formatted transmission and departed to the southwest. ATC tried to
reach out again with no response.
10/22 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Out of Alaska
Prescott (PRC)
The pilot deviation was reported by the Prescott ATC when a Cessna entered the Prescott Class
Delta Airspace without first establishing two-way radio communications.
10/24 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
ATP/CFI Pilot
Out of Colorado
Flagstaff (FLG)
The pilot deviation was reported by the Flagstaff ATC when a Piper entered the Flagstaff Class
Delta Airspace without first establishing two-way radio communications. A Brasher was issued
10/25 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Military Pilot
Mesa Falcon Field (FFZ)
The pilot deviation was reported by the Phoenix TRACON when a T38 entered the Falcon Field Class
Delta Airspace without first establishing two-way radio communications. The pilot, and instructor of
the T38 declined to give name, phone number, and pilot certificate number. They informed ATC that
they are in training from Shepard Air Force Base.
10/27 Entering Class Delta Airspace Without First Establishing Two-Way Radio Communication
Private Pilot
Out of North Dakota
Mesa Falcon Field (FFZ)
The pilot deviation was reported by Falcon Field ATC when a Husky entered the Falcon Field Class
Delta Airspace without first establishing two-way radio communications.
RUNWAY INCURSION (3)
10/20 Entering A Runway Without Authorization
Private Pilot
Phoeniz/Mesa GatewayAirport (IWA)
The pilot deviation was reported by Gateway Airport (IWA) when a Grumman Tiger entered the Center
Runway, and departed without ATC authorization while a Piper was on short final
10/22 Entering A Runway Without Authorization
Comm/CFI Pilot
Prescott (PRC)
A Cessna was instructed to taxi back to the ramp via TWY D, a left turn onto RWY12, TWY F3, TWY
F. The Cessna read back the taxi instructions correctly. A tower controller then noticed the Cessna
turn right onto TWY D3 towards RWY 21L, and told the Ground Controller (GC). GC instructed the Cessna to stop, and turn around. The tower controller had to cancel the takeoff clearance of an
Embry Riddle airplane because the Cessna was in the Runway Safety Area. The Cessna then told the
GC the instructions that they had received, and read them back correctly. GC told the Cessna that
that was correct, but they had just turned onto TWY D3 and almost onto the active runway, and
then issued them the Brasher warning.
11/1 Entering A Runway Without Authorization
Comm/CFI Pilot
Prescott (PRC)
A Cessna had conducted a touch and go to Runway 21L, and on the upwind, the Local Controller
(LC) instructed them to turn crosswind over the campus. There was no response. The controller
attempted to contact The Cessna multiple times with no response as the Cessna proceeded to fly a
downwind and base turn to Runway 21L. ATC advised that a light gun signal was used to instruct the
Cessna to make a full stop and also to exit the runway. The Cessna conducted a touch and go. The
instructor pilot of Cessna contacted the controller while in the downwind again and advised that
they had not been able to hear anything in the cockpit. A Brasher was issued.
AIR TRAFFIC CONTROL INSTRUCTIONS (4)
10/2 Failure To Follow Air Traffic Control Instructions
Pilot Certification Unknown
Phoenix Sky Harbor (PHX)
The pilot deviation was reported by Phoenix Sky Harbor when the Pilatus failed to follow the ATC
assigned departure headings.
10/25 Failure To Follow Air Traffic Control Instructions
Comm/CFI Pilot
Prescott Airport (PRC)
The Cessna was instructed to follow another Cessna ahead in the downwind. The pilot reported the
aircraft was in sight, and would follow. They then turned base inside of the aircraft they were told to
follow. The controller told them to "Go around and over fly the runway." The controller gave them the
Brasher warning after they landed.
10/29 Failure To Follow Air Traffic Control Instructions
Private Pilot
Out of California
Phoenix TRACON (P50)The Beechcraft was on departure from Mesa Falcon Field (FFZ), and were given 3,000 MSL as the
initial altitude, however the Pilot climbed to 5,000 feet. The controller had to stop an air-carrier’s
descent because of the Beech's climb. A Brasher was issued.
11/4 Failure To Follow Air Traffic Control Instructions (& NMAC)
ATP/CFI Pilot
Phoenix Deer Valley Airport (DVT)
A Piper was on the upwind for RWY 25L, and a Cessna was on the upwind for RWY 25R. At
approximately 1NM upwind, The Cessna began drifting south into the upwind of RWY 25L. At
approximately 1.7NM upwind the Cessna's target overlapped the Piper’s. Closest proximity was 0.03
NM and 100 feet. At the same time The Piper informed the controller that there was an a/c near them
on their ADS-B. The controller acknowledged, and stated they could not see the altitude due to the
targets overlapping, but suggested the Piper maintain their current altitude. The Piper advised the
controller they were going to continue climbing, and wanted to report it as a Near Miss, and advised
the controller the aircraft was turning towards them. The controller stated, "Traffic alert use caution".
The controller stated they issued this statement but did not know what else to do or say as far as a
traffic alert goes because the Piper had the a/c in sight. A Brasher was issued to the Cessna.
TFR DEVIATIONS (2)
10/24 Entering A TFR Without Authorization
Private Pilot
Phoenix TRACON (P50)
The Cessna was observed operating in the vicinity of Pegasus airpark on a 1200 transponder code
inside the 30 mile VIP TFR. A Phoenix/Mesa Gateway airport (IWA) controller reached out, and was
able to contact the aircraft, and advise them to make a full stop. They also issued the Brasher.
10/25 Entering A TFR Without Authorization
ATP Pilot
Phoenix TRACON (P50)
A Bonanza entered the 30 mile VIP TFR, and no communication was established with ATC. They were
identified, and contact was initiated with Mesa Falcon Field (FFZ) about 5 miles after entering the TFR. FFZ
had them return to the Phoenix TRACON NAJAVO sector controller, and the NAVAJO controller identified
them by assigning a discrete code. The aircraft continued on to land at Falcon Field (FFZ), and FFZ issued
the Brasher statement.
