Crash of a Piper PA-31-350 Navajo Chieftain in Flagstaff: 1 killed

Date & Time: Sep 21, 1990 at 0545 LT
Operator:
Registration:
N3558
Flight Type:
Survivors:
No
Schedule:
Phoenix - Flagstaff
MSN:
31-8052072
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5000
Captain / Total hours on type:
2500.00
Aircraft flight hours:
5293
Circumstances:
The aircraft was on a night flight from Phoenix to Flagstaff, AZ, to deliver cargo in accordance with an air taxi delivery schedule. Before reaching Flagstaff, the pilot canceled his IFR clearance and proceeded VFR. He encountered lowering cigs and rw. During the approach, he extended the landing gear and partially extended the wing flaps. Subsequently, the aircraft hit trees and crashed in an unpopulated area about 2.5 miles south-southeast of the airport at an elevation of about 6,800 feet; airport elevation was 7,011 feet. Initial impact occurred while the aircraft was in a right 20° bank (toward runway 03). Weather data at the company dispatch was not current and did not depict the adverse local conditions near the destination airport. The pilot, sole on board, was killed.
Probable cause:
VFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain proper altitude during the approach to land. Factors related to the accident were: darkness, the adverse weather conditions, and failure of company/operator/management personnel to provide current weather.
Final Report:

Crash of a Boeing 737-204 in Tucson

Date & Time: Dec 30, 1989 at 1910 LT
Type of aircraft:
Operator:
Registration:
N198AW
Survivors:
Yes
Schedule:
Phoenix - Tucson
MSN:
19710
YOM:
1968
Location:
Crew on board:
5
Crew fatalities:
Pax on board:
125
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10600
Captain / Total hours on type:
3970.00
Aircraft flight hours:
62466
Aircraft flight cycles:
38827
Circumstances:
During approach, a fire erupted in the wheel well of the 22-year old airplane. The fire burned thru the hydraulic lines rendering the a, b, and standby hydraulic systems inoperative. The crew landed the airplane using the emergency manual reversion flight control system. However, the airplane was unable to stop on the runway because of the previous failures of the check valves in the backup hydraulic accumulator pressure systems for the #2 thrust reverser and the inboard pair of wheel brakes. During the 2 minutes rollout, the airplane traversed 14,000 feet, overran the runway end, and collided with a concrete structure which collapsed the nose gear. The airplane had recently undergone a 'C' check during which the operator's mechanics failed to observe and repair an electric wire which had been chafing against a hydraulic line. On the accident flight the energized wire arced, punctured the line, and ignited the escaping hydraulic fluid. The hydraulic check valves had failed earlier due to mechanical wear.
Probable cause:
Failure of the operator's maintenance personnel to detect an electrical wire which had chafed against a hydraulic line and which eventually arced causing a leak in the hydraulic line and subsequent fire and hydraulic system failure. In addition, previous wear of check valves in the backup hydraulic systems prevented the airplane from stopping on the runway. A contributing factor was the airplane manufacturer's inadequate guidance for maintaining the hydraulic components.
Final Report:

Crash of a McDonnell Douglas MD-82 in Detroit: 156 killed

Date & Time: Aug 16, 1987 at 2045 LT
Type of aircraft:
Operator:
Registration:
N312RC
Flight Phase:
Survivors:
Yes
Schedule:
Saginaw - Detroit - Phoenix - Santa Ana
MSN:
48090
YOM:
1981
Flight number:
NW255
Crew on board:
6
Crew fatalities:
Pax on board:
149
Pax fatalities:
Other fatalities:
Total fatalities:
156
Captain / Total flying hours:
20859
Captain / Total hours on type:
1359.00
Copilot / Total flying hours:
8044
Copilot / Total hours on type:
1604
Aircraft flight hours:
14928
Circumstances:
A McDonnell Douglas DC-9-82 operating Northwest Airlines flight 255 was destroyed when it crashed onto a road during takeoff from Detroit-Metropolitan Wayne County Airport, Michigan, USA. Just one of the 155 occupants survived the accident. Additionally, Two persons on the ground were killed. Flight NW255 was a regularly scheduled passenger flight between Saginaw, Michigan and Santa Ana, California, with en route stops at Detroit and Phoenix, Arizona. About 18:53, flight 255 departed Saginaw and about 19:42 arrived at its gate at Detroit. About 20:32, flight 255 departed the gate with 149 passengers and 6 crewmembers on board. During the pushback, the flightcrew accomplished the BEFORE (engine) START portion of the airplane checklist, and, at 20:33, they began starting the engines. The flight was then cleared to "taxi via the ramp, hold short of (taxiway) delta and expect runway three center [3C] (for takeoff)..." The ground controller amended the clearance, stating that the flight had to exit the ramp at taxiway Charlie. The crew was requested to change radio frequencies. The first officer repeated the taxi clearance, but he did not repeat the new radio frequency nor did he tune the radio to the new frequency. At 20:37, the captain asked the first officer if they could use runway 3C for takeoff as they had initially expected 21L or 21R. After consulting the Runway Takeoff Weight Chart Manual, the first officer told the captain runway 3C could be used for takeoff. During the taxi out, the captain missed the turnoff at taxiway C. When the first officer contacted ground control, the ground controller redirected them to taxi to runway 3C and again requested that they change radio frequencies. The first officer repeated the new frequency, changed over, and contacted the east ground controller. The east ground controller gave the flight a new taxi route to runway 3C, told them that windshear alerts were in effect, and that the altimeter setting was 29.85 inHg. The flightcrew acknowledged receipt of the information. At 20:42, the local controller cleared flight 255 to taxi into position on runway 3C and to hold. He told the flight there would be a 3-minute delay in order to get the required "in-trail separation behind traffic just departing." At 20:44:04, flight 255 was cleared for takeoff. Engine power began increasing at 20:44:21. The flightcrew could not engage the autothrottle system at first, but, at 20:44:38, they did engage the system, and the first officer called 100 knots at 20:44:45. At 20:44:57, the first officer called "Rotate." Eight seconds later, the stall warning stick shaker activated, accompanied by voice warnings of the supplemental stall recognition system (SSRS). The takeoff warning system indicating that the airplane was not configured properly for takeoff, did not sound at any time prior or during takeoff. After flight 255 became airborne it began rolling to the left and right before the left wing hit a light pole in a rental car lot. After impacting the light pole, flight 255 continued to roll to the left, continued across the car lot, struck a light pole in a second rental car lot, and struck the side wall of the roof of the auto rental facility in the second rental car lot. The airplane continued rolling to the left when it impacted the ground on a road outside the airport boundary. The airplane continued to slide along the road, struck a railroad embankment, and disintegrated as it slid along the ground. Fires erupted in airplane components scattered along the wreckage path. Three occupied vehicles on the road and numerous vacant vehicles in the auto rental parking lot along the airplane's path were destroyed by impact forces and or fire. One passenger, a 4-year-old child was injured seriously.
Probable cause:
The flight crew's failure to use the taxi checklist to ensure that the flaps and slats were extended for take-off. Contributing the accident was the absence of electrical power to the airplane take-off warning system which thus did not warn the flight crew that the airplane was not configured properly for take-off. The reason for the absence of electrical power could not be determined.
Final Report:

Crash of a Cessna 441 Conquest in Flagstaff: 2 killed

Date & Time: Feb 20, 1987 at 1845 LT
Type of aircraft:
Operator:
Registration:
N6858S
Flight Type:
Survivors:
No
Schedule:
Phoenix - Flagstaff
MSN:
441-0253
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2311
Captain / Total hours on type:
24.00
Aircraft flight hours:
3349
Circumstances:
The aircraft was on an emergency medical service (ems/medevac) flight with a pilot and a flight nurse aboard to transport a maternity patient from Flagstaff to Phoenix. During a night arrival, the pilot began a VOR-A approach in IMC, then he reported a problem with his avionics and elected to make a missed approach. During the missed approach, he said that he 'lost' an inverter, then reported the gyros were inoperative. Radar vectors were being provided when he stated 'we have big trouble here.' Soon thereafter, radar and radio contacts were lost and the aircraft crashed approximately 7 miles southeast of the airport. During impact, the aircraft made a deep crater and was demolished. No preimpact engine or airframe failure was found. An investigation revealed the #2 (copilot's) attitude indicator was inoperative on the previous flight. A discrepancy report was taken to the avionics department, but the requested entry was not made in the aircraft form-4. The pilot took off before corrective action was taken. The operations manual requested 1,000 hours multi-engine time as pic and training by esignated cfi's. The pilot had approximately 837 hours multi-engine time, recorded 9 training flights in N6858S with non-designated instructors, completed a part 135 flight check on 2/17/88. Both occupants were killed.
Probable cause:
Occurrence #1: airframe/component/system failure/malfunction
Phase of operation: approach
Findings
1. Maintenance, recordkeeping - improper
2. Procedures/directives - not followed
3. (f) inadequate surveillance of operation - company/operator mgmt
4. (c) electrical system - undetermined
5. Electrical system, inverter - inoperative
6. Flight/nav instruments, attitude indicator - inoperative
----------
Occurrence #2: loss of control - in flight
Phase of operation: approach
Findings
7. (f) light condition - dark night
8. (f) weather condition - low ceiling
9. (f) weather condition - snow
10. (c) aircraft handling - not maintained - pilot in command
11. (c) spatial disorientation - pilot in command
12. (f) lack of total experience in type of aircraft - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Piper PA-31-325 Navajo C/R in Junction

Date & Time: Dec 29, 1985 at 1630 LT
Type of aircraft:
Operator:
Registration:
N27842
Flight Type:
Survivors:
Yes
Schedule:
Junction - Phoenix
MSN:
31-7912055
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3200
Captain / Total hours on type:
420.00
Aircraft flight hours:
1490
Circumstances:
During initial climb after takeoff the pilot noticed oil streaming out from the oil filler access door on the right engine cowling. He elected to continue climbing and make a teardrop turn back to the airport and land in the opposite direction from which he had departed. He announced his intentions on unicom radio. Another pilot responded that he was presently on the runway but would clear it as soon as possible. The subject pilot then decided to make a go around. During this time the right front seat passenger stated he observed flames in the right engine cowl. The pilot shut down the engine and feathered the propeller. He added full power to the left engine and retracted the landing gear and flaps. He was unable to maintain altitude and decided to make a forced landing straight ahead in an open field. He had to pull up once to avoid a power line and maneuver to avoid an antenna. He made a successful forced landing and all occupants exited. The flames quickly spread and the aircraft was consumed by ground fire.
Probable cause:
Occurrence #1: loss of engine power (partial) - nonmechanical
Phase of operation: takeoff - initial climb
Findings
1. (c) lubricating system - open
2. (c) aircraft preflight - inadequate - pilot in command
3. (c) fluid, oil - loss, partial
4. (c) procedures/directives - improper - pilot in command
----------
Occurrence #2: fire
Phase of operation: descent - emergency
Findings
5. (c) remedial action - not understood - pilot in command
----------
Occurrence #3: forced landing
Phase of operation: descent - emergency
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) near Genoa: 1 killed

Date & Time: Dec 13, 1984 at 0200 LT
Operator:
Registration:
N9781Q
Flight Phase:
Survivors:
No
Site:
Schedule:
Phoenix - Carson City
MSN:
61-0409-145
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6100
Captain / Total hours on type:
2000.00
Aircraft flight hours:
1788
Circumstances:
The pilot had flown from Carson City, NV to Shreveport, LA on 12/10/84 for business. At 1530 on 12/12/84, he departed on a flight to Corona, CA with refueling stops at Albuquerque, NM and Phoenix, AZ. He departed Phoenix at 2100, but encountered weather and returned to Phoenix where he refueled again and obtained a lengthy weather briefing. He then elected to return to his home airport at Carson City and took off at 2351. When the aircraft did not arrive, a search was initiated. Radar data revealed an unidentified target that disappeared near Genoa, NV. During a search in that area, the wreckage was found where the aircraft had crashed near the top of a mountain about 5 miles north of the pilot's home. The elevation was approximately 9,050 feet. Impact occurred on a westerly heading, about 2 hours before moonset, on the shaded side of the mountain, in a near wings level attitude. No preimpact/mechanical malfunction/failure was found, both engines/propellers showed evidence of power. The pilot's wife said he sometimes flew over their house to let her know he would be home soon. Complete autopsy/tox check not possible.
Probable cause:
Occurrence #1: in flight collision with terrain/water
Phase of operation: descent
Findings
1. (c) reason for occurrence undetermined
2. Light condition - dark night
3. Terrain condition - mountainous/hilly
4. Proper altitude - not maintained
Final Report:

Crash of a Boeing KC-135A-BN Stratotanker near Luke AFB: 4 killed

Date & Time: Mar 13, 1982 at 1050 LT
Type of aircraft:
Operator:
Registration:
57-1489
Flight Type:
Survivors:
No
Schedule:
Phoenix - Luke AFB
MSN:
17560/169
YOM:
1958
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3604
Captain / Total hours on type:
370.00
Aircraft flight hours:
10650
Circumstances:
The KC-135A aircraft departed Phoenix-Sky Harbor International Airport at 0755 MST for a scheduled 3-hour and 30-minute flight. After completing the navigation leg, the aircraft descended into the Phoenix area for transition at Luke AFB. After completing one TACAN approach at Luke AFB, the KC-135A aircraft was vectored to Phoenix-Sky Harbor International Airport for an ILS touch-and-go landing. The aircraft was then vectored back to the final approach course for a TACAN runway 03 left approach at Luke AFB. The KC-135A aircraft was cleared for the approach to Luke AFB, and after the final approach fix radio call, a midair collision occurred with a Grumman American Yankee civilian aircraft. The empennage of the KC-135A separated, rendering the aircraft incapable of flight and it was destroyed upon ground impact. The Grumman American Yankee aircraft was destroyed during the midair collision. The four crew members in the KC-135A and the two civilians in the Grumman American Yankee were fatalities.
Crew:
LT Col James N. Floor,
Lt Col Ted L. Beam,
Maj Truman R. Young Jr.,
T/Sgt Donald J. Plough.
Probable cause:
The USAF KC-135 was on an IFR flight plan and executing a TACAN 03L approach to Luke AFB. The AA-1 had departed Sky Harbour Airport and had been released by phoenix TRSA. The AA-1 was heading westerly in airspace designated as a special traffic area and was required to have been at or below 2,000 ft msl. A pilot of another aircraft who was trailing the AA-1 stated that a low broken cloud cover was encountered and he had to descend to about 2,000 ft to remain 500 ft below the bases. He stated the pilot of the AA-1 did not descend but appeared to be skimming along in and out of the bases of the clouds. He noticed the KC-135 descending through the cloud deck followed immediately by the collision. The collision occurred about 5 mi south of Luke AFB at an altitude of 2,500 ft msl. The logbook of the AA-1 pilot indicated this was his first trip to the phoenix area. Luke AFB was depicted on the north side of the sectional chart only. VOR airway #16 was split along an e-w line with the northern and southern halves being depicted on each side of the chart.

Occurrence #1: midair collision
Phase of operation: cruise - normal
Findings
1. En route charts - inadequate
2. (c) vfr procedures - improper - pilot in command AA-1
3. (f) lack of familiarity with geographic area - pilot in command AA-1
Final Report:

Crash of a Rockwell Grand Commander 680FL in Phoenix

Date & Time: May 29, 1979 at 1717 LT
Operator:
Registration:
N783EF
Flight Type:
Survivors:
Yes
Schedule:
Las Vegas - Phoenix
MSN:
680-1392-51
YOM:
1964
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2255
Captain / Total hours on type:
100.00
Circumstances:
On final approach to Phoenix-Sky Harbor Airport, while completing a cargo flight from Las Vegas, both engines lost power. The crew attempted an emergency landing when the airplane lost height and crashed short of runway threshold. The aircraft was damaged beyond repair and both pilots were seriously injured.
Probable cause:
Controlled collision with ground on final approach after the airplane encountered vortex turbulences. The following contributing factors were reported:
- Fuel starvation,
- Failure of both engines,
- Forced landing off airport on land,
- Violent wingrock on final uncovered fuel sump pickups allowing air to enter fuel lines.
Final Report:

Crash of a Cessna 340 in Phoenix: 1 killed

Date & Time: Sep 27, 1974 at 1040 LT
Type of aircraft:
Registration:
N9950F
Survivors:
No
Schedule:
San Diego – Phoenix
MSN:
340-0177
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3504
Circumstances:
On final approach to Phoenix-Sky Harbor Airport, the right engine failed. The pilot lost control of the airplane that lost height, struck power cables and crashed in flames onto a house. The pilot, sole on board, was killed and the aircraft was destroyed by a post crash fire.
Probable cause:
Engine failure caused by a mismanagement of fuel. The following contributing factors were reported:
- Failed to follow approved procedures,
- Fuel starvation,
- Failed to maintain flying speed,
- Improper emergency procedures,
- Inadequate preflight preparation,
- Failed to use checklist,
- High obstructions,
- Complete engine failure,
- Fuel selector on auxiliary tanks,
- Propeller not feathered.
Final Report:

Crash of a MBB HFB-320 Hansa Jet in Phoenix

Date & Time: Mar 9, 1973 at 2024 LT
Type of aircraft:
Operator:
Registration:
N320MC
Survivors:
Yes
Schedule:
San Francisco - San Diego - Phoenix - Santa Fe
MSN:
1034
YOM:
1968
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11672
Captain / Total hours on type:
1200.00
Circumstances:
The crew was completing a flight from San Francisco to Santa Fe with intermediate stops in San Diego and Phoenix. At Sky Harbor Airport, the airplane landed on its belly, slid for several dozen yards and came to rest in flames. While all seven occupants escaped uninjured, the aircraft was destroyed.
Probable cause:
On approach, the crew failed to use the checklist and forgot to extend the landing gear.
Final Report: