Crash of a De Havilland DHC-2 Beaver near Sitka

Date & Time: May 30, 2003 at 1430 LT
Type of aircraft:
Operator:
Registration:
N60TF
Flight Type:
Survivors:
Yes
Schedule:
Sitka - Salmon Lake
MSN:
1205
YOM:
1958
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3720
Captain / Total hours on type:
500.00
Aircraft flight hours:
6060
Circumstances:
The airline transport certificated pilot departed from a paved runway for a short flight to a remote lake in an amphibious float-equipped airplane to deliver supplies to a client. The pilot reported that he was transporting several loads of equipment to the lake, and failed to visually check the gear position while looking for a new unloading area. He also indicated that he was distracted when he had to reset the flaps, and by a minor malfunction with the airplane's GPS receiver. He said he forgot to raise the landing gear wheels, and landed on the lake with the wheels extended. During the landing touchdown on the lake, the airplane nosed over and received damage to the left wing and fuselage. The airplane is equipped with floats that have landing gear position lights installed on the instrument panel. The airplane also has a mirror enabling the pilot to visually observe the landing gear position.
Probable cause:
The pilot's failure to retract the landing gear wheels of an amphibious float equipped airplane after departure from a paved runway, which resulted in a nose over when the airplane was landed on a nearby lake with the wheels extended. A contributing factor in the accident was the pilot's diverted attention during the short flight from the airport to the lake.
Final Report:

Crash of an Antonov AN-12BP in Goma

Date & Time: May 27, 2003
Type of aircraft:
Operator:
Registration:
9L-LCR
Flight Type:
Survivors:
Yes
Schedule:
Entebbe – Kisangani – Goma
MSN:
4 3 418 01
YOM:
1964
Location:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon touchdown at Goma Airport, the four engine aircraft bounced. Unable to stop within the remaining distance, the aircraft overran the 2'050 metres long runway, turned to the left and came to rest in a solidified lava area. All four crew members escaped uninjured while the aircraft was damaged beyond repair. It was reported that the landing was performed with a tailwind component following an approach in stormy weather.

Crash of a Yakovlev Yak-42D near Trabzon: 75 killed

Date & Time: May 26, 2003 at 0445 LT
Type of aircraft:
Operator:
Registration:
UR-42352
Survivors:
No
Site:
Schedule:
Bishkek - Trabzon - Zaragoza
MSN:
18 11 395
YOM:
1988
Flight number:
UKM4230
Country:
Region:
Crew on board:
13
Crew fatalities:
Pax on board:
62
Pax fatalities:
Other fatalities:
Total fatalities:
75
Aircraft flight hours:
18739
Aircraft flight cycles:
9700
Circumstances:
Chartered by the Spanish Government, the aircraft was completing a charter flight from Bishkek to Zaragoza with an intermediate stop in Trabzon, carrying 62 Spanish peacekeepers and 13 crew members. The 62 passengers were respectively 41 members of the Land Forces and 21 members of the Air Force who were returning to Spain following a peacekeeping mission in Afghanistan. While descending to Trabzon Airport by night, the crew encountered poor visibility due to foggy conditions. Unable to establish a visual contact with the approach lights and the runway 29, the crew initiated a go-around procedure. Few minutes later, while completing a second approach, the crew failed to realize he was not following the correct pattern for an approach to runway 29 when the aircraft impacted a mountain at an altitude of 4,600 feet. The aircraft disintegrated on impact and all 75 occupants were killed. The wreckage was found 3,5 km east of the village of Maçka, about 23 km southwest of the airport.
Probable cause:
The accident was the consequence of a controlled flight into terrain due to the combination of the following factors:
- Loss of situational awareness on part of the flying crew,
- The crew failed to comply with the Standard Operational Procedures published by the operator,
- The crew failed to follow the published approach charts,
- Implementation of a non-precision approach,
- Incorrect use of the automated flight systems,
- Inadequate training (LOFT),
- The crew descended below the MDA in limited visibility.

Crash of a Learjet U-36A at Iwakuni AFB: 4 killed

Date & Time: May 21, 2003 at 1125 LT
Type of aircraft:
Operator:
Registration:
9202
Flight Type:
Survivors:
No
Schedule:
Iwakuni - Iwakuni
MSN:
36-056
YOM:
1988
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The crew departed Iwakuni AFB at 0900LT on a training mission over the Sea of Japan. At 1045LT, the aircraft returned to Iwakuni and the crew completed several touch-and-go manoeuvres on runway 02. During one of these procedures, the aircraft went out of control upon touchdown and crashed beside the runway, bursting into flames. All four crew members were killed.

Crash of a Beechcraft B350 Super King Air in West Houston

Date & Time: May 18, 2003 at 0935 LT
Operator:
Registration:
N2SM
Flight Type:
Survivors:
Yes
Schedule:
Houston-William P. Hobby – West Houston – Las Vegas
MSN:
FL-24
YOM:
1990
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5200
Circumstances:
The aircraft overran the departure end of the runway while landing on Runway 33. The 5,200-hour pilot reported that while on the base leg, the annunciator light for the "low pitch stop" propeller system on the right side illuminated. The pilot pulled the circuit breaker and left it out, as per the pilot operating handbook (POH). During the landing-roll, the pilot encountered a severe yaw to the right. The pilot added power to the right engine and realigned the airplane down the centerline. He then applied brakes and reverse thrust. The pilot stated that " it felt like I had no braking action and then felt the right side grab and brake, but not the left." The combination of right side braking and the right low pitch system malfunction caused considerable adverse yaw, jerking the plane to the right. The pilot applied power again and straightened the nose of the airplane. He then made the decision to go around, but at this point did not have adequate airspeed or runway length to safely accomplish a go around. He applied the brakes again, and the airplane immediately yawed to the right again, at which time the pilot was unable to compensate before the airplane caught the edge of the runway. The airplane went into the grass, where the pilot attempted to control the direction of the airplane and bring it to a complete stop. Examination of the hydraulic brake hoses from the left and right main landing gears revealed that both hoses appeared to have been damaged with a hand tool.
Probable cause:
The severed hydraulic brake hoses induced a loss of braking action, which resulted in the pilot's failure to control the aircraft.
Final Report:

Crash of a Beechcraft B200C Super King Air in Coffs Harbour

Date & Time: May 15, 2003 at 0833 LT
Operator:
Registration:
VH-AMR
Flight Type:
Survivors:
Yes
Schedule:
Sydney – Coffs Harbour
MSN:
BL-126
YOM:
1985
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18638
Captain / Total hours on type:
460.00
Circumstances:
The aircraft impacted the sea or a reef about 6 km north-east of Coffs Harbour airport. The impact occurred immediately after the pilot initiated a go-around during an instrument approach to runway 21 in Instrument Meteorological Conditions (IMC) that included heavy rain and restricted visibility. Although the aircraft sustained structural damage and the left main gear detached, the aircraft remained airborne. During the initial go-around climb, the aircraft narrowly missed a breakwater and adjacent restaurant at the Coffs Harbour boat harbour. Shortly after, the pilot noticed that the primary attitude indicator had failed, requiring him to refer to the standby instrument to recover from an inadvertent turn. The pilot positioned the aircraft over the sea and held for about 30 minutes before returning to Coffs Harbour and landing the damaged aircraft on runway 21. There were no injuries or any other damage to property and/or the environment because of the accident. The aircraft was on a routine aeromedical flight from Sydney to Coffs Harbour with the pilot, two flight nurses, and a stretcher patient on board. The flight was conducted under instrument flight rules (IFR) in predominantly instrument meteorological conditions (IMC). During the descent, the enroute air traffic controller advised the pilot to expect the runway 21 Global Positioning System (GPS) non-precision approach (NPA). The pilot reported that he reviewed the approach diagram and planned a 3-degree descent profile. He noted the appropriate altitudes, including the correct minimum descent altitude (MDA) of 580 ft, on a reference card. A copy of the approach diagram used by the pilot is at Appendix A. The aerodrome controller advised the pilot of the possibility of a holding pattern due to a preceding IFR aircraft being sequenced for an instrument approach to runway 21. The controller subsequently advised that holding would not be required if the initial approach fix (SCHNC)2 was reached not before 0825. At about 0818, the aerodrome controller advised the pilot of the preceding aircraft that the weather conditions in the area of the final approach were a visibility of 5000 m and an approximate cloud base of 1,000 ft. At 0825 the aerodrome controller cleared the pilot of the King Air to track the aircraft from the initial approach fix to the intermediate fix (SCHNI) and to descend to not below 3,500 ft. The published minimum crossing altitude was 3,600 ft. About one minute later the pilot reported that he was leaving 5,500 ft and was established inbound on the approach. At 0828 the pilot reported approaching the intermediate fix and 3,500 ft. The controller advised that further descent was not available until the preceding aircraft was visible from the tower. At 0829 the controller, having sighted the preceding aircraft, cleared the pilot of the King Air to continue descent to 2,500 ft. The pilot advised the controller that he was 2.2 NM from the final approach fix (SCHNF). At that point an aircraft on a 3-degree approach slope to the threshold would be at about 2,500 ft. The controller then cleared the pilot for the runway 21 GPS approach, effectively a clearance to descend as required. The pilot subsequently explained that he was high on his planned 3-degree descent profile because separation with the preceding aircraft resulted in a late descent clearance. He had hand flown the approach, and although he recalled setting the altitude alerter to the 3,500 ft and 2,500 ft clearance limits, he could not recall setting the 580 ft MDA. He stated that he had not intended to descend below the MDA until he was visual, and that he had started to scan outside the cockpit at about 800 ft altitude in expectation of becoming visual. The pilot recalled levelling the aircraft, but a short time later experienced a 'sinking feeling'. That prompted him to go-around by advancing the propeller and engine power levers, and establishing the aircraft in a nose-up attitude. The passenger in the right front seat reported experiencing a similar 'falling sensation' and observed the pilot's altimeter moving rapidly 'down through 200 ft' before it stopped at about 50 ft. She saw what looked like a beach and exclaimed 'land' about the same time as the pilot applied power. The pilot felt a 'thump' just after he had initiated the go-around. The passenger recalled feeling a 'jolt' as the aircraft began to climb. Witnesses on the northern breakwater of the Coffs Harbour boat harbour observed an aircraft appear out of the heavy rain and mist from the north-east. They reported that it seemed to strike the breakwater wall and then passed over an adjacent restaurant at a very low altitude before it was lost from sight. Wheels from the left landing gear were seen to ricochet into the air and one of the two wheels was seen to fall into the water. The other wheel was found lodged among the rocks of the breakwater.During the go-around the pilot unsuccessfully attempted to raise the landing gear, so he reselected the landing gear selector to the 'down' position. He was unable to retract the wing flaps. It was then that he experienced a strong g-force and realised that he was in a turn. He saw that the primary attitude indicator had 'toppled' and referred to the standby attitude indicator, which showed that the aircraft was in a 70-degree right bank. He rapidly regained control of the aircraft and turned it onto an easterly heading, away from land. The inverter fail light illuminated but the pilot did not recall any associated master warning annunciator. He then selected the number-2 inverter to restore power to the primary attitude indicator, and it commenced to operate normally. The pilot observed that the left main landing gear had separated from the aircraft. He continued to manoeuvre over water while awaiting an improvement in weather conditions that would permit a visual approach. About 4 minutes after the King Air commenced the go-around, the aerodrome controller received a telephone call advising that a person at the Coffs Harbour boat harbour had witnessed an aircraft flying low over the harbour, and that the aircraft had '…hit something and the wheel came off'. The controller contacted the pilot, who confirmed that the aircraft was damaged. The controller declared a distress phase and activated the emergency response services to position for the aircraft's landing. Witnesses reported that the landing was smooth. As the aircraft came to rest on the runway, foam was applied around the aircraft to minimise the likelihood of fire. The occupants exited the aircraft through the main cabin door.
Probable cause:
This occurrence is a CFIT accident resulting from inadvertent descent below the MDA on the final segment of a non-precision approach, fortunately without the catastrophic consequences normally associated with such events. The investigation was unable to conclusively determine why the aircraft descended below the MDA while in IMC, or why the descent continued until CFIT could no longer be avoided. However, the investigation identified a number of factors that influenced, or had the potential to influence, the development of the occurrence.
Final Report:

Crash of an Antonov AN-12B in Asmara

Date & Time: May 11, 2003
Type of aircraft:
Operator:
Registration:
ER-AXD
Flight Type:
Survivors:
Yes
Schedule:
Dubai - Asmara
MSN:
9 3 466 02
YOM:
1969
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown at Asmara Airport runway 25, the crew encountered brakes problems. Unable to stop within the remaining distance, the aircraft overran, collided with approach lights and came to rest. All seven occupants escaped uninjured while the aircraft was damaged beyond repair. Wind was from 170 at 10 knots at the time of the accident.

Crash of a Basler BT-67 in Ocaña

Date & Time: Apr 30, 2003
Type of aircraft:
Operator:
Registration:
PNC-212
Survivors:
Yes
MSN:
13110
YOM:
1944
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Ocaña-Aguas Claras Airstrip, the aircraft was unable to stop within the remaining distance. It overran and came to rest in a ditch. There were no casualties.

Crash of a Beechcraft 1900C-1 in Kinshasa

Date & Time: Apr 29, 2003 at 1930 LT
Type of aircraft:
Operator:
Registration:
TR-LFQ
Survivors:
Yes
Schedule:
Brazzaville - Kinshasa
MSN:
UC-80
YOM:
1989
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Brazzaville on a charter flight to Kinshasa, carrying 13 passengers (all Air France crew members) and two pilots. On approach to Kinshasa, the crew encountered poor weather conditions with thunderstorm activity, heavy rain falls and strong crosswinds. After touchdown, the aircraft became unstable, deviated to the left and veered off runway. While contacting soft ground, the aircraft lost its undercarriage and slid for few dozen metres before coming to rest beside the runway. All 15 occupants escaped uninjured but the aircraft was damaged beyond repair.
Probable cause:
It is believed that the aircraft became unstable at touchdown due to strong crosswinds. A inappropriate reaction on part of the pilot-in-command, an overcorrection or a wrong configuration may have been a contributing factor.

Crash of a De Havilland DHC-6 Twin Otter 300 in Mulia

Date & Time: Apr 28, 2003 at 0730 LT
Operator:
Registration:
PK-WAR
Survivors:
Yes
Schedule:
Wamena - Mulia
MSN:
313
YOM:
1971
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Mulia Airport, the twin engine aircraft struck the ground and crashed few km short o runway. All four occupants were injured and the aircraft was damaged beyond repair.