Zone

Crash of a Honda HA-420 HondaJet in Mesa: 5 killed

Date & Time: Nov 5, 2024 at 1639 LT
Type of aircraft:
Registration:
N57HP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mesa - Provo
MSN:
420-00033
YOM:
2016
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
During the takeoff roll on runway 22L at Mesa-Falcon Field Airport, after completing a distance of about 3,400 feet and at a speed of 133 knots, the crew decided to abort the takeoff procedure and initiated an emergency braking maneuver. Unable to stop within the remaining distance, the airplane overran, went through the perimeter fence, hit a car moving around on North Greenfield Road and eventually came to rest against trees, bursting into flames. A passenger was rescued while four other occupants, two passengers and both pilots were killed. The car's driver was also killed. The accident occurred in good weather conditions.

Crash of a Piper PA-31T1 Cheyenne I near Ely: 2 killed

Date & Time: Dec 15, 2012 at 1000 LT
Type of aircraft:
Registration:
N93CN
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Mesa - Portland
MSN:
31-8004029
YOM:
1980
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
6336
Aircraft flight hours:
5725
Circumstances:
The private pilot and passenger departed on the 875-nautical-mile cross-country flight and leveled off at a cruise altitude of 24,000 feet mean seal level, which, based on the radar data, was accomplished with the use of the autopilot. About 1 hour 40 minutes after departure, the pilot contacted air traffic control personnel to request that he would “like to leave frequency for a couple of minutes.” No further radio transmissions were made. About 20 seconds after the last transmission, the airplane banked to the right, continued in a spiral while rapidly descending, and subsequently broke apart. At no time during the flight did the pilot indicate that he was experiencing difficulty or request assistance. Just prior to departing from the flight path, the pilot made an entry of the engine parameters in a flight log, which appeared to be consistent with his other entries indicating the airplane was not experiencing any difficulties. Portions of the wings, along with the horizontal stabilizers and elevators, separated during the breakup sequence. Analysis of the fracture surfaces, along with the debris field distribution and radar data, revealed that the rapid descent resulted in an exceedance of the design stress limits of the airplane and led to an in-flight structural failure. The airplane sustained extensive damage after ground impact, and examination of the engine components and surviving primary airframe components did not reveal any mechanical malfunctions or failures that would have precluded normal operation. The airplane was flying on a flight path that the pilot was familiar with over largely unpopulated hilly terrain at the time of the upset. The clouds were well below his cruising altitude, giving the pilot reliable external visual cues should the airplane have experienced a failure of either the flight instruments or autopilot. Further, no turbulence was reported in the area. The airplane was equipped with a supplemental oxygen system, which the pilot likely had his mask plugged into and available in the unstowed position behind his seat; the passenger’s mask was stowed under her seat. The airplane’s autopilot could be disengaged by the pilot by depressing the appropriate mode switch, pushing the autopilot disengage switch on the control wheel, or turning off the autopilot switch on the control head. All autopilot servos were also equipped with a clutch mechanism that allowed the servo to be manually overridden by the pilot at any time. It is likely that the reason the pilot requested to “leave the frequency” was to leave his seat and attend to something in the airplane. While leaving his seat, it is plausible he inadvertently disconnected the autopilot and was unable to recover by the time he realized the deviation had occurred.
Probable cause:
The pilot’s failure to regain airplane control following a sudden rapid descent during cruise flight, which resulted in an exceedance of the design stress limits of the aircraft and led to an in-flight structural failure.
Final Report:

Crash of a Rockwell Grand Commander 690A near Mesa: 6 killed

Date & Time: Nov 23, 2011 at 1831 LT
Operator:
Registration:
N690SM
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Mesa - Safford
MSN:
690-11337
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
2500
Captain / Total hours on type:
951.00
Aircraft flight hours:
8188
Circumstances:
The aircraft was destroyed when it impacted terrain in the Superstition Mountains near Apache Junction, Arizona. The commercial pilot and the five passengers were fatally injured. The airplane was registered to Ponderosa Aviation, Inc. (PAI) and operated by PAI under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as a personal flight. Night visual meteorological conditions (VMC) prevailed, and no flight plan was filed. The airplane had departed Falcon Field (FFZ), Mesa, Arizona, about 1825 and was destined for Safford Regional Airport (SAD), Safford, Arizona. PAI’s director of maintenance (DOM) and the director of operations (DO), who were co owners of PAI along with the president, conducted a personal flight from SAD to FFZ. The DO flew the leg from SAD to FFZ under visual flight rules (VFR) in night VMC. After arriving at FFZ and in preparation for the flight back to SAD, the DOM moved to the left front seat to act as the pilot flying. The airplane departed FFZ about 12 minutes after it arrived. According to a witness, engine start and taxi-out appeared normal. Review of the recorded communications between the pilot and the FFZ tower air traffic controllers revealed that when the pilot requested taxi clearance, he advised the ground controller that he was planning an "eastbound departure." The flight was cleared for takeoff on runway 4R, and the pilot was instructed to maintain runway heading until advised, due to an inbound aircraft. About 90 seconds later, when the airplane was about 1.1 miles from the departure end of the runway, the tower local controller issued a "right turn approved" advisory to the flight, which the pilot acknowledged. Radar data revealed that the airplane flew the runway heading for about 1.5 miles then began a right turn toward SAD and climbed through an altitude of about 2,600 feet mean sea level (msl). About 1828, after it momentarily climbed to an altitude of 4,700 feet, the airplane descended to an altitude of 4,500 feet, where it remained and tracked in an essentially straight line until it impacted the mountain. The last radar return was received at 1830:56 and was approximately coincident with the impact location. The impact location was near the top of a steep mountain that projected to over 5,000 feet msl. Witnesses reported seeing a fireball, and law enforcement helicopters were dispatched.
Probable cause:
The pilot's failure to maintain a safe ground track and altitude combination for the moonless night visual flight rules flight, which resulted in controlled flight into terrain. Contributing to the accident were the pilot's complacency and lack of situational awareness and his failure to use air traffic control visual flight rules flight following or minimum safe altitude warning services. Also contributing to the accident was the airplane's lack of onboard terrain awareness and warning system equipment.
Final Report:

Crash of a Rockwell Grand Commander 690A in Cortez: 1 killed

Date & Time: Jan 3, 2004 at 1212 LT
Operator:
Registration:
N700SR
Flight Type:
Survivors:
No
Schedule:
Mesa – Cortez
MSN:
690-11164
YOM:
1974
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1872
Captain / Total hours on type:
91.00
Aircraft flight hours:
7506
Circumstances:
The pilot executed the VOR approach to runway 21. He was heard to report passing the VORTAC outbound for the procedure turn, and crossing the VORTAC (final approach fix) inbound. Witnesses said they saw the airplane emerge from the overcast slightly high and fast. They said the airplane entered a steep left bank and turned about 90 degrees before disappearing in a snow shower northeast of the airport. They heard no unusual engine noises. Another witness near the accident site saw the airplane in a steep bank and at low altitude, "just above the power lines." Based on the witness location, the airplane had turned about 270 degrees. The witness said the wings "wobbled" and the nose "dipped," then the left wing dropped and the airplane descended to the ground "almost vertically." Members of the County Sheriff's Posse, who were at a gunnery range just north of the airport, reported hearing an airplane pass over at low altitude. One posse member said he heard "an engine pitch change." He did not see the airplane because it was "snowing heavily," nor did he hear the impact. An examination of the airplane revealed no anomalies. At the time of the accident, the weather at the destination airport was few clouds 300 feet, 900 feet broken, 3,200 feet overcast; visibility, 1/2 statute and snow; temperature, 32 degrees F.; dew point, 32 degrees F.; wind, 290 degrees at 10 knots, gusting to 15 knots; altimeter, 29.71 inches.
Probable cause:
The pilot's inadequate planned approach and his failure to maintain airspeed which resulted in a stall. Contributing factors were low altitude flight maneuvering in an attempt to lose excessive altitude and realign the airplane for landing, and his failure to perform a missed approach, and the snow fall.
Final Report:

Crash of a Cessna T303 Crusader in Mesa

Date & Time: May 13, 1985 at 1943 LT
Type of aircraft:
Registration:
N4661V
Flight Type:
Survivors:
Yes
Schedule:
Scottsdale - Mesa
MSN:
303-00276
YOM:
1983
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2665
Captain / Total hours on type:
32.00
Aircraft flight hours:
59
Circumstances:
Pilot took off from Scottsdale at 1934 mst for a 13 nm flight to reposition the aircraft to home base. Within minutes the pilot advised ATC that he was 6 miles out with minimum fuel and requested no delay. He then asked for clearance to runway 22R and was cleared to land on runway 22R, at 1943 mst the pilot advised the tower that he was not going to make the runway. Both engines had stopped due to fuel exhaustion and the pilot made a forced landing 1/4 mile from the approach end of runway 22R in a level dirt area. The pilot reported the aircraft contained 120 lbs of fuel upon departure from Scottsdale and no low fuel warning was received. The pilot's operating handbook states the low fuel warning light should illuminate when there is less than 60 gallons of fuel in either tank or when there is less than 120 gallons total fuel on board. The manual also stated the aircraft burns 170 gph at 70 percent power. The pilot, sole on board, was seriously injured.
Probable cause:
Occurrence #1: loss of engine power (total) - nonmechanical
Phase of operation: approach - vfr pattern - final approach
Findings
1. (c) preflight planning/preparation - improper - pilot in command
2. (f) fluid, fuel - exhaustion
3. (c) fuel supply - inadequate - pilot in command
----------
Occurrence #2: forced landing
Phase of operation: descent - emergency
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: landing - flare/touchdown
Findings
4. (f) terrain condition - open field
5. (f) light condition - dusk
Final Report:

Crash of a Lockheed PV-2D Harpoon in Mesa

Date & Time: May 1, 1985 at 1557 LT
Type of aircraft:
Registration:
N7415C
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mesa - Mesa
MSN:
15-1608
YOM:
1945
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11750
Captain / Total hours on type:
220.00
Circumstances:
Following a dual engine change, the pilot test flew the aircraft. On initial climb, at about 500 feet agl, both engines began backfiring violently and lost power. According to the pilot, power sufficient for flight could not be obtained, and a forced landing was made about 0.75 miles from the airport. The landing occurred in open desert terrain and the aircraft was substantially damaged. The pilot acknowledged that he did not check the position of the control handles for the superchargers during either his preflight or pre-takeoff inspections. And the blowers had been inadvertently left set to the high blower position. According to the pilot, the checklist which he was using for the aircraft did not address the position of the blowers because for the past 15 years it had been company policy to 'wire the blowers to the low blower position.' Both occupants escaped uninjured.
Probable cause:
Occurrence #1: loss of engine power (partial) - nonmechanical
Phase of operation: takeoff - roll/run
Findings
1. (c) checklist - inaccurate - pilot in command
2. (c) powerplant controls - improper - pilot in command
----------
Occurrence #2: forced landing
Phase of operation: descent - emergency
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: landing - flare/touchdown
Findings
3. Airport facilities,runway/landing area condition - none suitable
4. Terrain condition - rough/uneven
Final Report:

Crash of a Beechcraft 65 Queen Air in Jennings: 1 killed

Date & Time: Apr 5, 1984 at 1045 LT
Type of aircraft:
Operator:
Registration:
N6RG
Flight Type:
Survivors:
No
Schedule:
New Roads - Mesa
MSN:
LC-199
YOM:
1966
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
A popping or backfiring sound was heard by several people who later observed the aircraft flying at low altitude on what appeared to be a final approach to runway 13 at Jennings Airport (located about 75 miles southwest of the departure point.) No radios were onboard the aircraft so no distress calls were made. Because of the wind this would have been a downwind landing. The aircraft then aborted the approach due to an aircraft landing from the opposite direction and appeared to start a left turn onto abase leg when it stalled, pitched nose down and impacted the ground with its landing gear and flaps extended. Wreckage examination revealed that all 3 blades of the right prop were bent smoothly and symmetrically rearward. However, no preimpact failure or malfunction of the right engine was found. There were no entries in the aircraft's logbook from 7/1/78 until 4/3/84 when the aircraft was inspected for the ferry flight. The pilot was not multi-engine rated and had not flown this type aircraft in about 10 years. The pilot's commercial certificate was revoked on 11/21/81. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: loss of engine power
Phase of operation: unknown
Findings
1. (c) reason for occurrence undetermined
----------
Occurrence #2: loss of control - in flight
Phase of operation: approach - VFR pattern - base turn
Findings
2. Procedures/directives - not followed - pilot in command
3. (f) qualification - pilot in command
4. (f) overconfidence in personal ability - pilot in command
5. Precautionary landing - initiated - pilot in command
6. Go-around - performed - pilot in command
7. (c) airspeed (VMC) - not maintained - pilot in command
8. (c) stall - inadvertent - pilot in command
9. (c) inadequate transition/upgrade training - pilot in command
10. (f) lack of recent experience - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: approach - VFR pattern - base turn
Final Report:

Crash of a Douglas C-54S Skymaster in Mesa

Date & Time: May 15, 1979 at 1455 LT
Type of aircraft:
Operator:
Registration:
N44905
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mesa - Chandler
MSN:
22159
YOM:
1945
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12127
Captain / Total hours on type:
4399.00
Circumstances:
During the takeoff roll at Mesa-Falcon Field Airport, the crew started the rotation but the aircraft did not liftoff. It overran, struck a 10 feet high dirt bank, crossed a road where it hit a truck and eventually came to rest in flames in an orange grove. Both pilots, en route to Chandler-Stellar Airpark on a test flight, were seriously injured and the aircraft was destroyed by fire.
Probable cause:
Collision with dirt bank on takeoff due to inadequate preflight preparation. The following contributing factors were reported:
- Failed to abort takeoff,
- Failed to use the checklist,
- Gust locks engaged.
Final Report:

Crash of a Lockheed L-1049H Super Constellation in Mesa: 6 killed

Date & Time: May 11, 1975 at 1640 LT
Registration:
N45516
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Mesa - Kansas City
MSN:
4840
YOM:
1958
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
12300
Captain / Total hours on type:
170.00
Circumstances:
Just after liftoff, while in initial climb, all four engines lost power. The captain attempted an emergency landing in a desert area when the airplane struck trees and crashed in flames few miles from the airport. The aircraft was totally destroyed by a post crash fire and all six occupants were killed. They were on their way to Kansas City to deliver the aircraft.
Probable cause:
Inadequate preflight preparation on part of the pilot-in-command. The following contributing factors were reported:
- Inadequate supervision of flight,
- Collision with trees,
- Engine structure and powerplant denotation,
- High obstructions,
- Overheated,
- Ran out of ADI fluid,
- All engines damaged internally.
Final Report: