Crash of a Cessna 421C Golden Eagle III off New Port Richey: 5 killed

Date & Time: Jul 8, 2009 at 1352 LT
Operator:
Registration:
N4467D
Flight Phase:
Survivors:
No
Schedule:
McKinney - Tampa
MSN:
421C-0634
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
1940
Aircraft flight hours:
4326
Circumstances:
Prior to the accident flight, the pilot indicated that he was aware of the thunderstorm activity along his route of flight and that he anticipated deviating around the weather as necessary. While enroute to his destination, the pilot requested and was provided both weather information and pilot reports from other aircraft by air traffic control (ATC). Upon encountering an area of thunderstorm activity that extended east-to-west across the route of flight, the pilot reported encountering significant turbulence, and then downdrafts of 2,000 feet per minute. He then requested a course reversal to exit the weather before he declared an emergency and advised ATC that the airplane was upside down. There were no further transmissions from the pilot and radar contact with the airplane was lost. Review of radar data revealed that the pilot had deviated south and then southwest when the airplane entered a strong and intense echo of extreme intensity. Visible imaging revealed that the echo was located in an area of a rapidly developing cumulonimbus cloud with a defined overshooting top, indicating the storm was in the mature stage or at its maximum intensity. Two debris fields were later discovered near the area where the cumulonimbus cloud had been observed. This was indicative that the airplane had penetrated the main core of the cumulonimbus cloud, which resulted in an inflight breakup of the airplane. Near the heavier echoes the airplane's airborne weather radar may have been unable to provide an accurate representation of the radar echoes along the aircraft's flight path; therefore the final penetration of the intense portion of the storm was likely unintentional.
Probable cause:
The pilot’s decision to operate into a known area of adverse weather, which resulted in the inadvertent penetration of a severe thunderstorm, a subsequent loss of control, and in-flight breakup of the airplane.
Final Report:

Crash of a Pilatus PC-12/45 in Raphine: 4 killed

Date & Time: Jul 5, 2009 at 1002 LT
Type of aircraft:
Registration:
N578DC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Teterboro - Tampa
MSN:
570
YOM:
2004
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1873
Captain / Total hours on type:
715.00
Aircraft flight hours:
723
Circumstances:
While in instrument meteorological conditions flying 800 feet above the airplane’s service ceiling (30,000 feet), with no icing conditions reported, the pilot reported to the air traffic controller that he, “...lost [his] panel.” With the autopilot most likely engaged, the airplane began a right roll about 36 seconds later. The airplane continued in a right roll that increased to 105 degrees, then rolled back to about 70 degrees, before the airplane entered a right descending turn. The airplane continued its descending turn until being lost from radar in the vicinity of the accident site. The airplane impacted in a nose-down attitude in an open field and was significantly fragmented. Postaccident inspection of the flight control system, engine, and propeller revealed no evidence of preimpact failure or malfunction. The flaps and landing gear were retracted and all trim settings were within the normal operating range. Additionally, the airplane was within weight and balance limitations for the flight. The cause of the pilot-reported panel failure could not be determined; however, the possibility of a total electrical failure was eliminated since the pilot maintained radio contact with the air traffic controller. Although the source of the instrumentation failure could not be determined, proper pilot corrective actions, identified in the pilot operating handbook, following the failure most likely would have restored flight information to the pilot’s electronic flight display. Additionally, a standby attitude gyro, compass, and the co-pilot’s electronic flight display units would be available for attitude reference information assuming they were operational.
Probable cause:
The pilot's failure to maintain control of the airplane while in instrument meteorological conditions following a reported instrumentation failure for undetermined reasons.
Final Report:

Crash of a Cessna 208B Caravan in Cross City

Date & Time: Sep 5, 2007 at 0533 LT
Type of aircraft:
Operator:
Registration:
N702PA
Flight Type:
Survivors:
Yes
Schedule:
Mobile - Tampa
MSN:
208-0702
YOM:
1998
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11732
Captain / Total hours on type:
5470.00
Aircraft flight hours:
7844
Circumstances:
The pilot stated that he was on a repositioning flight to Tampa, Florida. He was cruising at 11,000 feet msl when, with no warning or spool down time, the engine failed. The engine indications instantly went to zero. The pilot declared an emergency to the air traffic controller and was advised that the nearest airport was 29 miles away. He maneuvered the airplane toward the airport and went through the engine failure procedures. The attempts to restart the engine were unsuccessful. The pilot configured the airplane for best glide speed. After gliding for 22 miles, the airplane's altitude was about 300 feet msl. The pilot slowed the airplane to just above stall speed before impacting small pine trees pulling back on the yoke and stalling the airplane into the trees. The engine was examined at Pratt and Whitney of Canada, with Transportation Safety Board of Canada oversight. The engine compressor turbine blades were fractured at varying heights from the roots to approximately half of the span. Materials analysis determined the blade fractures to display impact damage and overheating. The primary cause of the blade fractures could not be determined. There were no other pre-impact anomalies or operational dysfunction observed to any of the engine components examined. Impact damage to the blade airfoils precluded determination of the original fracture mechanism.
Probable cause:
A total loss of engine power during cruise flight due to the fracture and separation of the compressor turbine blades for undetermined reasons. Contributing to the accident was the unsuitable terrain for a forced landing.
Final Report:

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

Date & Time: Nov 12, 1993 at 0629 LT
Registration:
N27687
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Orlando - Tampa
MSN:
31-7852107
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2465
Aircraft flight hours:
8393
Circumstances:
Cargo was not weighed and weight and balance calculations were not performed. The airplane was about 321 pounds over gross. While taxiing, a witness reported seeing black smoke trailing the left engine which had been worked on the night before the accident. Two cylinders were worked on and a fuel injector nozzle was cleaned. The climb after takeoff was 'low and slow' during which the airplane rolled left, pitched nose down, and impacted the ground coming to rest adjacent to a house. Examination of each engine revealed no evidence of internal mechanical failure or malfunction. Heat damage precluded testing of the magnetos, turbocharger components, and fuel servos of each engine. Examination of each propeller revealed no evidence of preimpact failure or malfunction. The fuel nozzles from the left engine were examined which revealed that they were blocked in various places due to contaminants. After the accident the faa performed a focused inspection of the operator revealing that the cargo was not being weighed, the chief pilot of the company was in name only, and load manifests were not being kept by the company. The pilot, sole on board, was killed.
Probable cause:
In flight loss of control for failure of the pilot-in-command to maintain vmc shortly after takeoff. Contributing to the accident was partial loss of engine power from the left engine due to partial blockage of several of the fuel injector nozzles. Also contributing to the accident was weight and balance exceeded by the pilot-in-command and inadequate surveillance by the company and by the FAA.
Final Report:

Crash of a Piper PA-31-310 Navajo in Panama City: 2 killed

Date & Time: Jun 26, 1990 at 0515 LT
Type of aircraft:
Registration:
N18PA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Panama City - Tampa
MSN:
31-7712068
YOM:
1977
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7524
Captain / Total hours on type:
600.00
Aircraft flight hours:
5993
Circumstances:
Witnesses described the takeoff as a long ground roll, slow climb, and engines not sounding normal. The airplane then settled into trees. Teardown of the left engine revealed water present in the fuel injector lines of #1, #3 and #5 cylinders. #3 nozzle plugged. Intake valves dark and sooty. Pistons 1, 3 and 5 had considerable amounts of dark carbon deposits. Teardown of right engine revealed extensive carbon buildups throughout. An engine test run was performed by the director of maintenance day before accident. Personnel formerly employed by the operator provided written statements of allegations pertaining to the general condition of company airplanes, falsification of maintenance records, and improper maintenance procedures being performed on company airplanes. Both occupants were killed.
Probable cause:
A loss of power on both engines during takeoff as a result of inadequate maintenance. In addition, the pilot failed to abort the takeoff.
Final Report:

Crash of a Rockwell Sabreliner 40R in Detroit

Date & Time: Feb 3, 1990 at 1540 LT
Type of aircraft:
Registration:
N50CD
Flight Type:
Survivors:
Yes
Schedule:
Tampa - Detroit
MSN:
282-42
YOM:
1965
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was completing a flight from Tampa to Detroit on behalf of the Detroit City Police. After landing on runway 15 at Coleman A. Young Airport, the airplane encountered difficulties to stop within the remaining distance, overran and came to rest. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 550 Citation II in Roxboro: 2 killed

Date & Time: Oct 1, 1989 at 2207 LT
Type of aircraft:
Operator:
Registration:
N53CC
Survivors:
No
Schedule:
Tampa - Roxboro
MSN:
550-0400
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7986
Captain / Total hours on type:
2643.00
Aircraft flight hours:
5111
Circumstances:
During arrival, flight was vectored for NDB runway 06 approach, and advised Raleigh-Durham weather was 500 feet overcast, visibility 3 miles with fog, wind from 140° at 12 knots, altimeter 30.01. After clearance for approach, aircraft crossed final approach fix (faf) at 2,100 feet msl. Radar service was terminated and frequency change was approved. When aircraft did not arrive, search was initiated. The wreckage was found about 2.5 miles southwest of runway 06, where aircraft hit trees and crashed. Elevation of crash site was about 600 feet msl. MDA for approach was 1,160 feet msl (with local altimeter setting; 1,260 feet with Raleigh-Durham setting). Exam revealed aircraft hit trees, while on runway heading in wings level attitude; configured for landing. No preimpact part failure/malfunction was found. Toxicological check of pic's blood showed 0.10 mg/l of diazepam and 0.09 mg/l of nordiazepam. Check of his urine showed metabolite of marijuana (11- nor-delta-9-tetrahydrocannabinol-9-carboxylic acid) at level of 0.117 mg/l. After surgery for malignant lymphoma (feb 89), pic was restored to flight status on 8/9/89 and cleared for pic duty one week later. He continued flying tho he received maintenance chemotherapy and associates noted that he tired easily. Both occupants were killed.
Probable cause:
Impairment of the pilot-in-command (pic) due to drugs/medication, chemotherapy and fatigue; failure of the pic to assure that the IFR (instrument) approach procedure was followed; and his failure to maintain the minimum descent altitude (MDA). Inadequate surveillance of the operation by company/operator/management personnel was a related factor.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 600) in Tallahassee: 1 killed

Date & Time: Oct 2, 1986 at 1845 LT
Registration:
N217HM
Flight Type:
Survivors:
No
Schedule:
Tampa – Tallahassee
MSN:
60-0236-098
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3500
Circumstances:
Witnesses stated seeing the aircraft enter a left downwind approach to runway 16, turn base to final normally then veer to the left of the runway in a nose high attitude and disappear behind a line of trees and crash approximately 500 feet east of runway 16. Post crash examination of the aircraft revealed the left engine was not producing power at the time of impact. Further examination revealed that the left engine fuel servo fuel mixture and idle speed settings were misadjusted. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: loss of engine power
Phase of operation: approach - vfr pattern - final approach
Findings
1. (f) fuel system, fuel control - other
----------
Occurrence #2: loss of control - in flight
Phase of operation: approach - vfr pattern - final approach
Findings
2. (f) in-flight planning/decision - poor - pilot in command
3. (c) directional control - not maintained - pilot in command
----------
Occurrence #3: in flight collision with object
Phase of operation: descent - uncontrolled
Findings
4. Object - tree(s)
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante in Jacksonville: 13 killed

Date & Time: Dec 6, 1984 at 1814 LT
Operator:
Registration:
N96PB
Flight Phase:
Survivors:
No
Schedule:
Jacksonville - Tampa
MSN:
110-365
YOM:
1981
Flight number:
PT1039
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
13
Captain / Total flying hours:
10000
Captain / Total hours on type:
400.00
Copilot / Total flying hours:
3000
Copilot / Total hours on type:
500
Aircraft flight hours:
5662
Aircraft flight cycles:
7858
Circumstances:
At 18:12, flight 1039 was cleared for takeoff from runway 31. At 18:13, while over the departure end of the runway and climbing through 600 feet, the crew acknowledged a frequency change. Thirty seconds later, the airplane was seen in a steep a descent near the extended centerline of the runway. The Bandeirante struck the ground 7,800 feet beyond the departure end of runway 31 and 85 feet to the right of the extended runway centerline in an inverted nose down attitude, after which it caught fire and burned. Before ground impact, the horizontal stabilizer, including bulkhead No. 36, had separated from the fuselage. Both elevators and elevator tips, the tail cone assembly, and the aft portion of the ventral fin also had separated in flight. All 13 occupants were killed.
Probable cause:
A malfunction of either the elevator control system or elevator trim system, which resulted in an airplane pitch control problem. The reaction of the flight crew to correct the pitch control problem overstressed the left elevator control rod, which resulted in asymmetrical elevator deflection and overstress failure of the horizontal stabilizer attachment structure. The Safety Board was not able to determine the precise problem with the pitch control system.
Final Report:

Crash of a Cessna 402C in Naples: 1 killed

Date & Time: Sep 7, 1984 at 2110 LT
Type of aircraft:
Operator:
Registration:
N89PB
Flight Phase:
Survivors:
Yes
Schedule:
Naples - Tampa
MSN:
402C-0650
YOM:
1982
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2639
Captain / Total hours on type:
412.00
Aircraft flight hours:
1495
Circumstances:
Shortly after takeoff, both engines lost power and a wheels up landing was made in an open field. The aircraft was destroyed by impact and fire. An investigation revealed that the aircraft had been refuel with Jet-A fuel rather than 100 low lead avgas. The lineman had inadvertently used the Jet-A fuel truck which was identical to the Avgas truck except for a decal, appx 4' by 16', which identified the type of fuel. The lineman stated that his training consisted of approximately 30 minutes of reading the company maintenance manual on how to refuel the different company aircraft, then was given on-the-job training for a brief time. When he went to refuel N89PB prior to the accident flight, he went to the parking space where the Avgas truck was normally parked, but on that occasion, the Jet-A fuel truck was there.
Probable cause:
Occurrence #1: loss of engine power (total) - nonmechanical
Phase of operation: climb - to cruise
Findings
1. (c) fluid, fuel grade - improper
2. (c) maintenance, service of aircraft/equipment - improper - ground personnel
3. (f) habit interference - ground personnel
4. (f) inadequate surveillance, inadequate procedure - company/operator mgmt
----------
Occurrence #2: forced landing
Phase of operation: landing - flare/touchdown
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: landing - flare/touchdown
Findings
5. Terrain condition - rough/uneven
6. Wheels up landing - performed - pilot in command
Final Report: