Crash of a Beechcraft C99 Airliner in Butte: 2 killed

Date & Time: Mar 18, 2006 at 1455 LT
Type of aircraft:
Operator:
Registration:
N54RP
Flight Type:
Survivors:
No
Schedule:
Helena - Butte
MSN:
U-218
YOM:
1983
Flight number:
AMF2591
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5219
Captain / Total hours on type:
2616.00
Aircraft flight hours:
22169
Aircraft flight cycles:
35539
Circumstances:
The cargo flight collided with mountainous terrain in controlled flight while executing an instrument approach procedure. Two pilots were aboard; the company's training and check captain/pilot-in-command in the right seat, and a newly hired commercial pilot in left seat, who was in training for captain The flight had been cleared for the VOR or GPS-B approach via the 7 DME arc. According to the approach plate, the transition to the approach is via a DME arc at 9,000 feet with no procedure turn. The flight is to track inbound on the 127 degree radial, descending down to, but no lower than, 7,700 feet to the initial approach fix (IAF). After crossing the IAF, the flight is to turn to 097 degrees for 10 nautical miles and descend to 6,900 feet. The remainder of the 1.5 nautical miles to the runway is to be flown under visual conditions. Documentation of the accident site indicated that the aircraft collided with trees and subsequently the mountainous terrain on a heading of approximately 127 degrees and about 6,900 feet mean sea level. The initial impact point was located approximately nine nautical miles on a magnetic bearing of 130 degrees from the IAF. Documentation of the horizontal situation indicator (HSI) on the left side instrument panel indicated that the course arrow was positioned to approximately 127 degrees, the inbound heading to the IAF. The copilot (right side) course arrow was positioned to 115 degrees. The location of the wreckage and the 127 degree heading on the HSI indicate that the pilots failed to follow the approach procedure and turn to a heading of 097 degrees after crossing the IAF. Instrument meteorological conditions were reported in the area consisting of icing conditions, heavy snow fall, with poor visibility and mountain obscuration. No pre-impact mechanical malfunctions or failures were identified.
Probable cause:
The second pilot's failure to follow the published instrument approach procedure and the captain/PIC's inadequate supervision. Snow and mountain obscuration were factors.
Final Report:

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

Date & Time: Mar 8, 2006 at 1639 LT
Operator:
Registration:
C-GNAY
Flight Type:
Survivors:
Yes
Schedule:
Vancouver – Powell River
MSN:
31-8052095
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1200
Copilot / Total flying hours:
500
Circumstances:
The aircraft departed from its home base at Vancouver, British Columbia, with two crew members on board. The aircraft was being repositioned to Powell River (a 30-minute flight) to commence a freight collection route. On arriving at Powell River, the crew joined the circuit straight-in to a right downwind for a visual approach to Runway 09. A weather system was passing through the area at the same time and the actual local winds were shifting from light southwesterly to gusty conditions (11 to 37 knots) from the northwest. The aircraft was lower and faster than normal during final approach, and it was not aligned with the runway. The crew completed an overshoot and set up for a second approach to the same runway. On the second approach, at about 1639 Pacific standard time, the aircraft touched down at least halfway down the wet runway and began to hydroplane. At some point after the touchdown, engine power was added in an unsuccessful attempt to abort the landing and carry out an overshoot. The aircraft overran the end of the runway and crashed into an unprepared area within the airport property. The pilot-in-command suffered serious injuries and the first officer was fatally injured. A local resident called 911 and reported the accident shortly after it occurred. The pilot-in-command was attended by paramedics and eventually removed from the wreckage with the assistance of local firefighters. The aircraft was destroyed, but there was no fire. The ELT (emergency locator transmitter) was automatically activated, but the signal was weak and was not detected by the search and rescue satellite.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The downwind condition on approach contributed to the aircraft landing long and with a high ground speed. This, in combination with hydroplaning, prevented the crew from stopping the aircraft in the runway length remaining.
2. When the decision to abort the landing was made, there was insufficient distance remaining for the aircraft to accelerate to a sufficient airspeed to lift off.
3. The overrun area for Runway 09 complied with regulatory standards, but the obstacles and terrain contour beyond the overrun area contributed to the fatality, the severity of injuries, and damage to the aircraft.
Finding as to Risk:
1. Alert Service Bulletin A25-1124A (dated 01 June 2000), which recommended replacing the inertia reel aluminum shaft with a steel shaft, was not completed, thus resulting in the risk of failure increasing over time.
Other Findings:
1. The weather station at the Powell River Airport does not have any air–ground communication capability with which to pass the flight crew timely wind updates.
2. The decision to make a second approach was consistent with normal industry practice, in that the crew could continue with the intent to land while maintaining the option to break off the approach if they assessed that the conditions were becoming unsafe.
Final Report:

Crash of an Antonov AN-2 in Lubanimanga

Date & Time: Mar 2, 2006
Type of aircraft:
Operator:
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Tshikapa – Kamonya
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft departed Tshikapa on a flight to Kamonya with five passengers, one pilot and a load of various goods on board. Few minutes after takeoff, the pilot encountered technical difficulties and elected to return. The aircraft crashed near Lubanimanga, about 35 km from Tshikapa. All six occupants were seriously injured and the aircraft was destroyed by a post crash fire.

Crash of a Swearingen SA226TC Metro II in Paris: 1 killed

Date & Time: Feb 8, 2006 at 1210 LT
Type of aircraft:
Operator:
Registration:
N629EK
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Dayton - Harlingen
MSN:
TC-396
YOM:
1980
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5237
Captain / Total hours on type:
164.00
Aircraft flight hours:
15883
Circumstances:
While in cruise flight at 16,000 feet, the pilot requested from ATC and was cleared to make a 360-degree turn to the left. Shortly after this, the pilot requested a 360-degree turn to the right. The pilot then requested radar vectors to the closest airport and was given this. ATC asked the pilot if he had an emergency and the pilot reported he had an asymmetric fuel condition. The pilot then asked for a lower altitude and was cleared by ATC to 4,000 feet. About a minute later the pilot transmitted "Mayday" six times and shortly after this radar and radio contact with the flight was lost. Recorded radar data showed that at 1803:13 the accident airplane was proceeding on a southerly heading at 16,100 feet mean sea level (MSL). At 1803:53 the airplane turned left to a southeasterly heading. At 1804:13 the airplane turned right returning to its original southerly heading. At 1805:14 the accident airplane turned to the right on a southwesterly heading, and maintained that heading until 1809:04 at which time the airplane turned due west and was at an altitude of 15,400 feet. The last radar contact was at 1810:06 at an altitude of 13,800 feet. The airplane wreckage was located due north from this last recorded radar contact. Witnesses observed the airplane descend in a near vertical attitude, collide with the ground, and then explode. Components from all areas of the aircraft structure and flight control surfaces were located at the crash site along with components from both engines and propellers. Impact and post crash fire damage precluded the examination of the airplanes fuel system and components.
Probable cause:
The pilot's inflight loss of control following a reported fuel asymmetry condition for undetermined reasons.
Final Report:

Ground fire of a Douglas DC-8-71F in Philadelphia

Date & Time: Feb 8, 2006 at 0001 LT
Type of aircraft:
Operator:
Registration:
N748UP
Flight Type:
Survivors:
Yes
Schedule:
Atlanta - Philadelphia
MSN:
45948
YOM:
1967
Flight number:
UPS1307
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Captain / Total hours on type:
16000.00
Copilot / Total flying hours:
7500
Copilot / Total hours on type:
2100
Aircraft flight hours:
67676
Circumstances:
On February 7, 2006, about 2359 eastern standard time, United Parcel Service Company flight 1307, a McDonnell Douglas DC-8-71F, N748UP, landed at its destination airport, Philadelphia International Airport, Philadelphia, Pennsylvania, after a cargo smoke indication in the cockpit. The captain, first officer, and flight engineer evacuated the airplane after landing. The flight crewmembers sustained minor injuries, and the airplane and most of the cargo were destroyed by fire after landing. The scheduled cargo flight was operating under the provisions of 14 Code of Federal Regulations Part 121 on an instrument flight rules flight plan. Night visual conditions prevailed at the time of the accident.
Probable cause:
An in-flight cargo fire that initiated from an unknown source, which was most likely located within cargo container 12, 13, or 14. Contributing to the loss of the
aircraft were the inadequate certification test requirements for smoke and fire detection systems and the lack of an on-board fire suppression system.
Final Report:

Crash of an Antonov AN-12A in Mbuji-Mayi

Date & Time: Jan 24, 2006 at 1150 LT
Type of aircraft:
Operator:
Registration:
9Q-CER
Flight Type:
Survivors:
Yes
Schedule:
Goma – Mbuji-Mayi
MSN:
2 34 08 05
YOM:
1962
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was performing a cargo flight from Goma to Mbuji-Mayi with a crew of 4 and a cargo consisting of fuel drums. The aircraft landed hard, causing both wings to break down. The undercarriage partially collapsed then the aircraft skidded for about 500 metres before coming to rest on the left side of the runway. A fire erupted in the rear of the cabin and the aircraft was destroyed.

Crash of a Douglas C-54G-15-DO Skymaster in Norman Wells

Date & Time: Jan 5, 2006 at 1704 LT
Type of aircraft:
Operator:
Registration:
C-GXKN
Flight Type:
Survivors:
Yes
Schedule:
Norman Wells – Yellowknife
MSN:
36090
YOM:
1946
Flight number:
BFL1405
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Buffalo Airways Limited Douglas C-54G-DC (DC-4), registration C-GXKN, serial number 36090, departed from Norman Wells, Northwest Territories, at 1749 mountain standard time for a visual flight rules flight to Yellowknife, Northwest Territories, with a crew of four and 2000 pounds of cargo. While climbing through an altitude of approximately 3500 feet above sea level, the crew experienced a failure of the number 2 engine and a nacelle fire. The crew carried out the Engine Fire Checklist, which included discharging the fire bottles and feathering the number 2 propeller. The fire continued unabated. During this period, an uncommanded feathering of the number 1 propeller and an uncommanded extension of the main landing gear occurred. The crew planned for an emergency off-field landing, but during the descent to the landing area, the fuel selector was turned off as part of the Engine Securing Checklist, and the fire self-extinguished. A decision was made to return to the Norman Wells Airport where a successful two-engine landing was completed at 1804 mountain standard time. The aircraft sustained substantial fire damage, but there were no injuries to the four crew members on board.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Airworthiness Directive AD 48-12-01 mandates the replacement of the potentially hazardous fuel line, but the line had not been replaced on this aircraft.
2. A fuel leak from the main fuel inlet line in the engine compartment of this cargo DC-4 caused an in-flight fire that spread into the nacelle and wing.
3. The fuel-fed fire burned for an extended period of time because turning the fuel selector off is not required as part of the primary Engine Fire Checklist.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Portland

Date & Time: Dec 24, 2005 at 0743 LT
Type of aircraft:
Operator:
Registration:
N753FE
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Portland - Medford
MSN:
208B-0248
YOM:
1991
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4625
Captain / Total hours on type:
2450.00
Aircraft flight hours:
7375
Circumstances:
The pilot stated that during takeoff, "after becoming airborne, the airplane quit accelerating and a positive climb rate was not established." He pushed the power lever all the way forward, but did not feel a response from the airplane. Witnesses reported that the airplane became airborne, but failed to gain altitude and struck an antenna array and a fence off the departure end of the runway. The airplane continued across a slough, struck an embankment and came to rest about 900 feet from the departure end of the runway on a golf course located adjacent to the airport. Examination of the airplane revealed no pre-mishap airframe anomalies. Examination of the engine revealed that the compressor and power turbines displayed moderate circular rubbing damage to the blades suggesting engine operation at impact, likely in the low to mid power range. Examination of the airframe and engine revealed no anomalies that would have prevented the engine from producing power prior to impact. The reason for the partial loss of engine power was not determined.
Probable cause:
A partial loss of engine power for an undetermined reason during the initial takeoff climb resulting in an in-flight collision with objects.
Final Report:

Crash of a Mitsubishi MU-2B-36 Marquise in Terrace: 2 killed

Date & Time: Dec 20, 2005 at 1834 LT
Type of aircraft:
Operator:
Registration:
C-FTWO
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Terrace – Vancouver
MSN:
672
YOM:
1975
Flight number:
FCV831
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2111
Captain / Total hours on type:
655.00
Copilot / Total flying hours:
2000
Copilot / Total hours on type:
500
Circumstances:
At 1834 Pacific standard time, the Nav Air Charter Inc. Mitsubishi MU-2B-36 aircraft (registration C-FTWO, serial number 672) took off from Runway 15 at the Terrace Airport for a courier flight to Vancouver, British Columbia. The left engine lost power shortly after take-off. The aircraft descended, with a slight left bank, into trees and crashed about 1600 feet east of the departure end of Runway 15 on a heading of 072° magnetic. The aircraft was destroyed by the impact and a post-crash fire, and the two pilots were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. During the take-off, the left engine combustion chamber plenum split open due to a fatigue crack. The rupture was so extensive that the engine flamed out.
2. The crew did not feather the left engine or retract the flaps, and the aircraft entered a moderate left-hand turn after take-off; the resulting drag caused the aircraft to descend until it contacted trees.
3. The first officer’s flying skills may have been challenged during the handling of the engine failure, and the checklist was conducted out of sequence, suggesting that there may have been uncertainty in the cockpit. A contributing factor may have been the captain’s unfamiliarity with handling an emergency from the right seat.
4. The use of flap 20 for take-off, although in accordance with company policy, contributed to the difficulty in handling the aircraft during the emergency.
Findings as to Risk:
1. The TPE331 series engine plenum is prone to developing cracks at bosses, particularly in areas where two bosses are in close proximity and a reinforcing weld has been made. Cracks that develop in this area cannot necessarily be detected by visual inspections or even by fluorescent dye-penetrant inspections (FPIs).
2. Because the wing was wet and the air temperature was at 0°C, it is possible that ice may have formed on top of the wing during the take-off, degrading the wing’s ability to generate lift.
3. Being required to conduct only flap 20 take-offs increases the risk of an accident in the event of an engine problem immediately after take-off.
Other Finding:
1. The plenum manufactured with a single machined casting, incorporating the P3 and bleed air bosses, is an improvement over the non-single casting boss plenum; however, cracks may still develop at bosses elsewhere on the plenum.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante in Orangeburg

Date & Time: Dec 9, 2005 at 2240 LT
Operator:
Registration:
N790RA
Flight Type:
Survivors:
Yes
Schedule:
Savannah - Columbia
MSN:
110-278
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2250
Captain / Total hours on type:
195.00
Aircraft flight hours:
14837
Circumstances:
The pilot had flown the airplane the day before the accident and after landing on the morning of the accident; she ordered fuel for the airplane. While exiting the airplane another pilot informed her that he had heard a "popping noise" coming from one of the engines. The pilot of the accident airplane elected to taxi to a run up area to conduct an engine run up. The fuel truck arrived at the run up area and the pilot elected not to refuel the airplane at that time and continued the run up. No anomalies were noted during the run up and the airplane was taxied back to the ramp and parked. The pilot arrived back at the airport later on the day of the accident and did not re-order fuel for the airplane nor did she recall checking the fuel tanks during the preflight inspection of the airplane. The pilot departed and was in cruise flight when she noticed the fuel light on the annunciator panel flickering. The pilot checked the fuel gauges and observed less than 100 pounds of fuel per-side indicated. The pilot declared low fuel with Columbia Approach Control controllers and requested to divert to the nearest airport, Orangeburg Municipal. The controller cleared the pilot for a visual approach to the airport and as she turned the airplane for final, the left engine lost power followed by the right engine. The pilot made a forced landing into the trees about 1/4 mile from the approach end of runway 36. The pilot exited the airplane and telephoned 911 emergency operators on her cell phone. The pilot stated she did not experience any mechanical problems with the airplane before the accident. Examination of the airplane by an FAA inspector revealed the fuel tanks were not ruptured and no fuel was present in the fuel tanks.
Probable cause:
The pilot's inadequate preflight inspection and her failure to refuel the airplane which resulted in total loss of engine power due to fuel exhaustion, and subsequent in-flight collision with trees.
Final Report: