Crash of an Antonov AN-24RV in Yuzhno-Sakhalinsk

Date & Time: Nov 2, 2005
Type of aircraft:
Operator:
Registration:
RA-46618
Survivors:
Yes
MSN:
3 73 087 05
YOM:
1973
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing at Yuzhno-Sakhalinsk Airport, the nose gear collapsed and punctured the ground floor just behind the cockpit. The aircraft came to rest on the main runway following a course of few dozen metres. All occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Boeing 727-22F in Kindu

Date & Time: Oct 31, 2005 at 1300 LT
Type of aircraft:
Registration:
9Q-CPJ
Flight Type:
Survivors:
Yes
MSN:
19088
YOM:
1967
Location:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was completing a cargo flight with various equipments on behalf of the Conader, the Commission Nationale de Désarmement et de Réinsertion. Following an uneventful flight, the crew started the approach in heavy rain falls. After landing on a wet runway, the aircraft was unable to stop within the remaining distance and overran. It lost its undercarriage and came to rest in marshy field. All three occupants escaped uninjured while the aircraft was damaged beyond repair. Aquaplaning suspected.

Crash of a Learjet 25D in Sacramento

Date & Time: Oct 26, 2005 at 1825 LT
Type of aircraft:
Operator:
Registration:
N888DV
Flight Type:
Survivors:
Yes
Schedule:
Sacramento - Sacramento
MSN:
25-370
YOM:
1984
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17500
Captain / Total hours on type:
1100.00
Copilot / Total flying hours:
20000
Copilot / Total hours on type:
70
Circumstances:
The crew landed with the landing gear in the retracted position. While the airplane was on the base leg of the traffic pattern, the pilot heard a helicopter pilot make a transmission over the common radio frequency. As he completed the before landing checklist the pilot searched for the helicopter that he heard over the radio. During the landing flare he realized something was amiss and looked down at the instrument panel. He noticed that the landing gear lights were illuminated red. Just prior to contacting the runway surface he reached for the landing gear handle and manipulated it in the down position. The airplane made a smooth touchdown with the landing gear in the retracted position. The pilot stated that he did not make the proper check for the gear extension due to the timing of the helicopter distraction. The pilot reported no preimpact mechanical malfunctions or failures with the airplane or engine, stating that the accident was the result of pilot error.
Probable cause:
The pilot's failure to extend the landing gear and to verify they were in the down and locked position prior to touchdown. A related factor was his diverted attention.
Final Report:

Crash of a Cessna 411 in East Hampton: 1 killed

Date & Time: Oct 23, 2005 at 1345 LT
Type of aircraft:
Registration:
N7345U
Flight Type:
Survivors:
No
Site:
Schedule:
Jefferson - Nantucket
MSN:
411-0045
YOM:
1965
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
452
Captain / Total hours on type:
0.00
Aircraft flight hours:
2808
Circumstances:
The pilot purchased the multiengine airplane about 18 months prior to the accident, and was conducting his first flight in the airplane, as he flew it from Georgia to Massachusetts. While en route, the airplane experienced a failure of the left engine. The airplane began maneuvering near an airport, as its groundspeed decreased from 173 miles per hour (mph) to 90 mph, 13 mph below the minimum single engine control speed. A witness reported that the airplane appeared to be attempting to land, when it banked to the left, and descended to the ground. The airplane impacted on a road, about 3 miles east-southeast of the airport. A 3-inch, by 2.5- inch hole was observed on the top of the left engine crankcase, and streaks of oil were present on the left gear door, left flap, and the left side of the fuselage. The number two connecting rod was fractured and heat distressed. The number 2 piston assembly was seized in the cylinder barrel. The airplane had been operated about 30 hours, during the 6 years prior to the accident, and it had not been flown since its most recent annual inspection, which was performed about 16 months prior to the accident. In addition, both engines were being operated beyond the manufacturer's recommended time between overhaul limits. The pilot did not possess a multiengine airplane rating. He attended an airplane type specific training course about 20 months prior to the accident. At that time, he reported 452 hours of total flight experience, with 0 hours of multiengine flight experience.
Probable cause:
The pilot's failure to maintain airspeed, while maneuvering with the left engine inoperative. Contributing to the accident were the failure of the left engine, and the pilot's lack of multiengine certification.
Final Report:

Crash of a Boeing 737-4Q8 in Mumbai

Date & Time: Oct 9, 2005 at 1920 LT
Type of aircraft:
Operator:
Registration:
VT-SID
Survivors:
Yes
Schedule:
Calcutta - Mumbai
MSN:
24705
YOM:
1990
Flight number:
RSH117
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
111
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Calcutta, the aircraft landed at Mumbai-Chhatrapati Shivaji Airport runway 27. Unable to stop within the remaining distance, the aircraft overran and came to rest few dozen metres further. All 117 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Casa 212 Aviocar 100 in Gerona

Date & Time: Oct 9, 2005
Type of aircraft:
Operator:
Registration:
T.12B-29
Flight Type:
Survivors:
Yes
MSN:
51
YOM:
1976
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Empuriabrava Airfield, the aircraft was too low, causing the undercarriage to collide with the perimeter fence. Decision was taken to divert to Gerona-Costa Brava Airport. The aircraft landed on a foamed runway and came to rest. There were no casualties but the aircraft was damaged beyond repair.

Crash of an Antonov AN-12 in Aru: 2 killed

Date & Time: Oct 4, 2005
Type of aircraft:
Operator:
Registration:
9Q-CWC
Survivors:
Yes
Schedule:
Kisangani – Bunia
MSN:
2 40 09 01
YOM:
1962
Location:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
96
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The aircraft departed Kisangani on a flight to Bunia, carrying 96 soldiers and four crew members on behalf of the Congolese Army Forces. Upon landing at Aru Airstrip, the right main gear collapsed and the aircraft veered to the left and came to rest on the left side of the runway. Two soldiers were killed while walking into the still running propellers. Eleven people were injured.

Crash of a Cessna 421C Golden Eagle III in Northrepps

Date & Time: Sep 30, 2005 at 1817 LT
Registration:
N421CA
Flight Type:
Survivors:
Yes
MSN:
421C-0153
YOM:
1976
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2475
Captain / Total hours on type:
255.00
Circumstances:
Northrepps Airfield has a single grass runway, orientated 18/36, and 1617 ft (493 m) long, with a down slope of 1.8% on Runway 18. On the day of the accident, the short grass was wet and an aftercast indicated that the wind at Northrepps was from approximately 210º at 10 to 13 kt. The pilot first flew an approach to Runway 18 and touched down close to the threshold; he subsequently reported that, looking at the slope of the runway ahead of him, he decided to go around and re‑position for a landing on Runway 36, to take advantage of the up-slope on that runway. The pilot stated that, during the approach to Runway 18, he had assessed that the braking effect of the wind would be insignificant in comparison to the braking effect that would be afforded by the uphill slope when landing on Runway 36. The pilot recalled seeing a “shortened” and “non‑standard” windsock mounted on a caravan adjacent to the Runway 18 threshold, but he did not believe that it could be relied upon for an accurate wind strength determination. He did not recall having seen the airfield’s other, larger, windsock. The approach for a short field landing on Runway 36 was normal and the pilot closed the throttles just before the threshold. The aircraft touched down close to the threshold, and the pilot immediately retracted the flaps. The pilot reported that he had lost two thirds of his touchdown speed by about the mid-point of the runway, and that the braking was within his expectations. He subsequently stated that he “seemed to get to a point… when I realised that I was effectively getting no braking at all from the wheels and the uphill slope had petered away”; he then experienced a sensation which he described as being similar to aquaplaning, with all braking authority seemingly lost. The aircraft continued along the runway, crossed the grassed overshoot area, ran over an earth bank beyond the end of the runway and came to rest on a public road just north of this bank. The pilot shut the aircraft down and all three occupants vacated the aircraft without difficulty.
Probable cause:
Prior to the flight, the pilot did not use the aircraft flight manual to calculate his landing performance. Given the wind and the surface conditions at Northrepps at the time of the intended operation, performance calculations showed that a landing could only be made safely if both the precise landing parameters and adequate braking were achieved. There was no evidence regarding the point of touchdown or the associated speed; it is therefore not possible to say with any certainty whether the failure to stop was the result of an imperfectly executed landing or the lack of braking effect on the short, wet grass.
Final Report:

Crash of a Mitsubishi MU-2B-36 Marquise in West Memphis: 1 killed

Date & Time: Sep 22, 2005 at 1958 LT
Type of aircraft:
Operator:
Registration:
N103RC
Flight Type:
Survivors:
No
Schedule:
West Memphis - Gainesville
MSN:
673
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
12600
Captain / Total hours on type:
1900.00
Aircraft flight hours:
10892
Circumstances:
The twin-engine airplane was destroyed when it impacted an earthmoving scraper and terrain in a field about 2.5 miles north of the departure airport in night visual meteorological conditions. Witnesses reported that the pilot had aborted an earlier flight when he returned to the airport and told the mechanic that he had a right engine fire warning light. The discrepancy could not be duplicated during maintenance, and the airplane departed. About 23 minutes after departure, the pilot reported to air traffic control that he needed to return to the airport to have something checked out. The pilot did not report to anyone why he decided to return to the departure airport, and he flew over four airports when he returned to the departure airport. Radar track data indicated that the airplane flew over the departure end of runway 35 at an altitude of about 1,600 feet agl, and made a descending left turn. The airplane's altitude was about 800 feet agl when it crossed the final approach course for runway 35. The airplane continued the descending left turn, but instead of landing on runway 35, the airplane flew a course that paralleled the runway, about 0.8 nm to the right of runway 35. The airplane continued to fly a northerly heading and continued to descend. The radar track data indicated that the airplane's airspeed was decreasing from about 130 kts to about 110 kts during the last one minute and fifty seconds of flight. The last reinforced beacon return indicated that the airplane's altitude was about 200 feet agl, and the airspeed was about 107 kts. The airplane impacted terrain about 0.75 nm from the last radar contact on a 338-degree magnetic heading. A witness reported that the airplane was going slow and was "extremely low." He reported that the airplane disappeared, and then there was an explosion and a fireball that went up about 1,000 feet. Inspection of the airplane revealed that it impacted the earthmover in about a wings level attitude. The landing gear handle was found to be in the landing gear UP position. The inspection of the left engine and propeller revealed damage indicative of engine operation at the time of impact. Inspection of the right engine revealed damage indicative of the engine not operating at the time of impact, consistent with an engine shutdown and a feathered propeller. No pre-existing conditions were found in either engine that would have interfered with normal operation. The inspection of the right engine fire detection loop revealed that the connector had surface contamination. When tested, an intermittent signal was produced which could give a fire alarm indication to the pilot. After the surface contamination was removed, the fire warning detection loop operated normally.
Probable cause:
The pilot's improper in-flight decision not to land at the departure runway or other available airports during the emergency descent, and his failure to maintain clearance from a vehicle and terrain. Contributing factors were a false engine fire warning light, inadequate maintenance by company personnel, a contaminated fire warning detection loop, and night conditions.
Final Report:

Crash of a Learjet 25B in Cedar Rapids

Date & Time: Sep 13, 2005 at 1330 LT
Type of aircraft:
Registration:
N252BK
Flight Type:
Survivors:
Yes
Schedule:
Cedar Rapids – McAllen
MSN:
25-107
YOM:
1973
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6225
Captain / Total hours on type:
350.00
Copilot / Total flying hours:
1107
Copilot / Total hours on type:
5
Aircraft flight hours:
11970
Circumstances:
The airplane collided with a berm following a loss of directional control while landing. The airplane was on a 14 CFR Part 91 positioning flight at the time of the accident. The pilots reported that they encountered what they thought were rough spots on the runway during the takeoff roll. The captain reported that after takeoff, he called for the co-pilot to raise the gear and engage the yaw damper. The crew then noticed an unsafe gear indication for the nose gear. The captain stated they leveled off at 5,000 feet and decreased the airspeed so they could recycled the landing gear. Cycling the landing gear did not resolve the problem. The crew then requested to return to the departure airport for landing. The landing gear was extended and a gear down and locked indication for all three landing gear was observed. The captain stated that on touchdown, the co-pilot extended the spoilers and armed the thrust reversers. He stated that after the nose wheel touched down the airplane made a sharp left turn and traveled off the side of the runway through the grass. The airplane contacted a four-foot high berm prior to coming to a stop on another runway. The captain stated he attempted to taxi the airplane only to discover that they did not have any nose wheel steering. Post accident inspection revealed the seal on the nose gear strut had failed which prevented the nose gear from centering.
Probable cause:
The pilot was not able to maintain directional control of the airplane due to the failure of the nose gear strut seal which prevented the nose wheel from centering. A factor associated with the accident was the berm that the airplane contacted.
Final Report: