Crash of a Cessna 208A Caravan 675 in Estancia Las Cruces: 1 killed

Date & Time: Apr 1, 2000 at 0800 LT
Type of aircraft:
Operator:
Registration:
LV-ZSR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Estancia Las Cruces - San Fernando
MSN:
208-0311
YOM:
1999
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
121
Circumstances:
After takeoff from Estancia Las Cruces Airport, while climbing in foggy conditions, the aircraft lost height and impacted ground in a wooded area located about 3 km from the airfield. The aircraft was destroyed and the pilot, sole on board, was killed.
Probable cause:
The aircraft impacted ground after takeoff while in instrument conditions. The pilot was not qualified nor trained for this type of flight.
Final Report:

Crash of an Antonov AN-26 in Anuradhapura: 40 killed

Date & Time: Mar 30, 2000
Type of aircraft:
Operator:
Registration:
UR-79170
Flight Type:
Survivors:
No
Schedule:
Palaly - Colombo
MSN:
47313410
YOM:
1980
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
36
Pax fatalities:
Other fatalities:
Total fatalities:
40
Circumstances:
The aircraft departed Jaffna-Palaly Airport on a flight to Colombo, carrying mostly Marines officers. While in cruising altitude, the pilot reported an engine fire and diverted to Anuradhapura Airport. On approach, the aircraft went out of control and crashed in a wooded area located 14,5 km from the airport. The aircraft was totally destroyed and all 40 occupants were killed.
Probable cause:
The aircraft was shot down by a Liberation Tigers of Tamil Eelam (LTTE) surface-to-air missile.

Crash of a Cessna 525 CitationJet CJ1 near Buda: 1 killed

Date & Time: Mar 26, 2000 at 0840 LT
Type of aircraft:
Registration:
N130MR
Flight Type:
Survivors:
No
Schedule:
Houston - Rutherford Ranch
MSN:
525-0097
YOM:
1995
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5887
Captain / Total hours on type:
154.00
Aircraft flight hours:
720
Circumstances:
The flight was approaching a private airport (elevation 983 feet msl), that did not have an instrument approach system, during instrument meteorological conditions. The pilot informed the air traffic controller that he had the airport in sight, and cancelled his instrument flight plan. The twin turbofan airplane impacted a tree approximately 4,000 feet northeast of the airport in an upright position. The airplane then impacted the ground in an inverted position approximately 200 yards from the initial impact with the tree. The weather observation facility located 16 miles northeast of the accident site was reporting an overcast ceiling at 400 feet agl, and visibility 4 statute miles in mist. The weather observation facility elevation was 541 feet msl. Local residents in the vicinity of the accident site stated that there was heavy fog and drizzle at the time of the accident. The pilot had filed an alternate airport (with a precision instrument approach); however, he elected not to divert to the alternate airport. Examination of the wreckage did not reveal any evidence of pre-impact anomalies that would have prevented operation of the airplane.
Probable cause:
The pilot's inadequate in-flight decision to continue a visual approach in instrument meteorological conditions which resulted in his failure to maintain terrain clearance. Contributing factors were the fog, drizzle, and low ceilings.
Final Report:

Crash of an Antonov AN-32B in Huambo: 3 killed

Date & Time: Mar 25, 2000
Type of aircraft:
Registration:
D2-MAJ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Huambo - Luanda
MSN:
3201
YOM:
1992
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
During the takeoff roll at Huambo-Albano Machado Airport, the pilot-in-command made a manoeuvre to avoid a hole in the runway when control was lost. The aircraft veered off runway, struck a ditch and came to rest, broken in two. Three passengers were killed.

Crash of an Antonov AN-12BP in Colombo: 9 killed

Date & Time: Mar 24, 2000 at 1804 LT
Type of aircraft:
Operator:
Registration:
RA-11302
Flight Type:
Survivors:
Yes
Schedule:
Bangkok - Colombo
MSN:
8 3 460 04
YOM:
1968
Flight number:
SCB702
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
9
Captain / Total flying hours:
6719
Captain / Total hours on type:
961.00
Copilot / Total flying hours:
10802
Copilot / Total hours on type:
1702
Aircraft flight hours:
7241
Aircraft flight cycles:
4651
Circumstances:
The Sky Cabs flight SCB701 originated in Colombo (Bandaranaike International Airport Colombo - hereinafter known as BIA Colombo), Sri Lanka at 1940 hours on 23rd March 2000. It landed in Bangkok, Thailand at 0120 hours on the following day after an uneventful flight. The alternate airport for Bangkok was Rayong/Ban U-Taphao (VTBU). The crew had recent experience in operating AN 12 flights between BIA Colombo and Bangkok International Airport, Thailand. The same flight crew made the return flight back to BIA Colombo after 4 hours and 20 minutes ground time in Bangkok. The crew had received the weather report from Aero Meteorological Division (AMD), prior to departure. An air traffic control flight plan was filed to BIA Colombo, the filed alternate airport was Male International (VRMM) in the Republic of Maldives. The aircraft was refueled adding 6681 kgs of fuel to the remaining 8300 kgs bringing the total fuel onboard to 14981 kg. Flight SCB702, cargo flight, departed Bangkok at 0540 hours on 24th March 2000 to BIA Colombo. The scheduled flight time for Bangkok – BIA Colombo was five hours and twenty minutes with a scheduled time of arrival of 1100 hours (17:00 hours Sri Lanka time). SCB702 made the first radio contact with Sri Lanka air traffic control at 1016 hours. The area controller passed SCB702 the latest weather report effective for BIA Colombo and later, a Sigmet valid at the time. When the control of the flight was handed to the approach radar controller (Director) by the area controller, at 1042 hours SCB 702 was asked to report his radial and DME from Colombo, (i.e. from “DVOR/DME KAT”). SCB702 reported as saying “074 radial and 55 DME ready for descent”, thus the two-way communication was established. Later, the flight SCB702 made two unsuccessful ILS approaches to runway 04. While on a radar heading to get established on the ILS to Runway 22 for a third attempt to land, the aircraft crashed 1.2 N.M. north-northwest of the threshold of Runway 22 (3.2 N.M. north-northeast of the DVOR/DME 'KAT') at BIA Colombo at 1204 hours (or 1804 hours in the evening, local time) on 24th March 2000. Six crew members and three people on the ground were killed.
Probable cause:
The aircraft accident occurred due to fuel starvation. Contributory factors to the accident are as follows:
i) Violation of Air Navigation Regulations on fuel planning;
ii) Failure of the flight crew to declare an emergency;
iii) Being unable to land due to adverse weather situation;
iv) Lack of communicability of the flight crew in English language;
v) Non-availability of established air traffic control procedures to assist an aircraft in distress;
vi) Failure of Sky Cabs (Pvt.) Ltd. to comply with the Air Navigation Regulations and the Conditions set-forth in Schedules issued with the Airline Lisence; and
vii) Absence of an effective Safety Oversight Program implemented by the Department of Civil Aviation, Sri Lanka.
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) in Randers

Date & Time: Mar 23, 2000 at 0838 LT
Operator:
Registration:
OY-PYY
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
61-0768-8063382
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll on runway 25 at Randers Airport, the right engine lost power then failed. The pilot continued the takeoff procedure and completed the rotation. Just after liftoff, while in initial climb, smoke spread from the right engine into the cockpit. The pilot attempted an emergency landing when the aircraft crash landed, collided with trees and came to rest about 500 metres past the runway end. The pilot escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Saab 340B in Killeen

Date & Time: Mar 21, 2000 at 1914 LT
Type of aircraft:
Operator:
Registration:
N353SB
Survivors:
Yes
Schedule:
Dallas - Killeen
MSN:
353
YOM:
1993
Flight number:
AA3789
Location:
Crew on board:
3
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12518
Captain / Total hours on type:
9251.00
Copilot / Total flying hours:
2105
Copilot / Total hours on type:
1040
Aircraft flight hours:
11976
Circumstances:
The captain was the flying pilot for the night landing on runway 01 in instrument meteorological conditions (IMC), with a right cross wind from 110 degrees at 14 gusting 18 knots, drizzle, and a wet runway. Prior to starting the approach, the flightcrew determined that the landing approach speed (Vref) and the approach speed (Vapp) were 122 and 128 knots, respectively. DFDR data showed the airplane flying on autopilot as it passed the middle marker at 200 feet AGL at 130 knots on the ILS approach. Approximately 3 seconds after the first officer called "runway in sight twelve o'clock," the captain disconnected the autopilot, while at a radio altitude of 132 feet and on a heading of approximately 18 degrees. Within approximately 11 seconds after the autopilot disconnect, the glideslope and localizer deviation increased. The first officer called "runway over there." Approximately 5 seconds before touchdown, the airplane rolled right, then left, then right. DFDR data-based performance calculations showed the airplane crossed the threshold at an altitude of 35 feet and 130 knots. The airplane touched down 2,802 feet from the approach end of the 5,495-foot runway (844- foot displaced threshold) at 125 knots on a heading of 10 degrees. The airplane overran the runway and struck a ditch 175 feet beyond the departure end of the runway. Landing roll calculations showed a ground roll of 2,693 feet after touchdown, consisting of 1,016 feet ground roll before braking was initiated and 1,677 feet ground roll after braking was initiated until the airplane exited the pavement. According to Saab, for a wet runway, the aircraft would have needed 1,989 feet from the time of braking initiation to come to a complete stop. The American Eagle Airlines, Inc., FAA approved aircraft operating manual (AOM), states in part: Stabilized approaches are essential when landing on contaminated runways. Landing under adverse weather conditions, the desired touch-down point is still 1,000 feet from the approach end of the runway. Touchdown at the planned point. Cross the threshold at Vapp, then bleed off speed to land approximately Vref -5. Use reverse, if needed. To achieve maximum braking effect on wet runway, apply maximum and steady brake pressure. In 1992, the City of Killeen submitted a proposal that included extending the north end of runway 01 by 194 feet. The FAA originally disapproved the proposal, in part, because the runway extension decreased the length of the runway safety area (RSA) which was already shorter than the recommended 1,000 feet for a 14 CFR Part 139 certificated airport. The proposal was subsequently approved and a drainage ditch was installed in the north RSA, perpendicular to the runway and approximately 175 feet north of the departure end of runway 01. In 1993, the airport received FAA Part 139 certification. The 1998 and 1999, FAA airport certification inspection reports noted the inadequate RSA; however, neither letter of correction, sent from the FAA to the City of Killeen following the inspections, mentioned the RSA. Following this accident, the ILS runway 01 was flight checked by the FAA and all components were found to be operating within prescribed tolerances. Examination of the airplane found no anomalies that would have prevented it from operating per design prior to departing the runway and encountering the ditch.
Probable cause:
The captain's failure to follow standard operating procedure for landing on a contaminated runway in that he touched down long, which combined with his delayed braking resulted in a runway overrun. Contributing factors were the captain's failure to maintain runway alignment following his disconnect of the autopilot, the gusty crosswind and the wet runway. In addition, the following were contributing factors:
(1) the airport operator's failure to fill in a ditch in the runway safety area,
(2) the FAA's granting of 14 CFR Part 139 approval to the airport when the runway safety area (RSA) did not meet the recommended length for a Part 139 airport, and
(3) the FAA's continued lack of acknowledgement to the airport of the inadequate RSA following their annual airport inspection checks.
Final Report:

Crash of a Beechcraft C90 King Air in Bursa: 1 killed

Date & Time: Mar 21, 2000
Type of aircraft:
Operator:
Registration:
TC-LMK
Survivors:
Yes
Schedule:
Ankara - Bursa
MSN:
LJ-1080
YOM:
1984
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On final approach to Bursa-Yenisehir Airport, the pilot encountered poor weather conditions. Due to low visibility, he was unable to establish a visual contact with the approach and runway lights and initiated a go-around procedure. While completing a circuit, the twin engine aircraft struck the top of a hill located near the airport and crashed. A passenger was killed while four other occupants were injured.

Crash of an Antonov AN-26B in Goma

Date & Time: Mar 19, 2000
Type of aircraft:
Operator:
Registration:
UR-26586
Flight Type:
Survivors:
Yes
MSN:
13805
YOM:
1984
Location:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was completing a humanitarian flight to Goma on behalf of the United Nations Organization. On final approach, at a distance of 1,000 metres from the runway threshold, the aircraft encountered windshear. The captain initiated a go-around procedure but the aircraft continued to descent until it struck the ground and crashed to the right of the runway. All 10 occupants were injured and the aircraft was destroyed.

Crash of an Embraer EMB-110P1A Bandeirante in Kaduna

Date & Time: Mar 17, 2000 at 1047 LT
Operator:
Registration:
5N-AXM
Survivors:
Yes
Schedule:
Abuja - Jos
MSN:
110-446
YOM:
1984
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8733
Captain / Total hours on type:
1008.00
Copilot / Total flying hours:
3100
Copilot / Total hours on type:
200
Aircraft flight hours:
10926
Circumstances:
On the day of the accident, the aircraft was engaged in a charter operation for the Central Bank of Nigeria. The first segment of the flight (Lagos - Abuja) was flown by the Commander. The aircraft departed Lagos about 0630 hours UTC and initially at cruise, the crew had a momentary problem setting power on the starboard engine after which the flight continued normally to Abuja. The aircraft which departed Abuja for Jos at 0900 hours UTC had 6 souls on board, 5 hours endurance with the first officer at the controls. At FL 90 and about 30NM from Abuja, the crew again had problems with the cruise power setting on the starboard engine. The torque remained at 1400. The crew retarded the right power lever to the minimum with the aim of achieving a cruise setting of 1300 but the gear warning came on. The Commander at this stage took over the controls from the first officer. At 0923 hours UTC, the aircraft contacted Kaduna Tower that it would be diverting to Kaduna as against its scheduled destination giving its flight level as 90 at a distance of 61 miles and estimating TMA at 24 miles, 'KC' at 41 miles, 6 souls on board and 5 hours endurance at departure. The tower then gave the aircraft an inbound clearance to 'KC' locator maintaining FL 90 and to expect no delay for a locator approach runway 05. Weather report at 0900 hours UTC was also passed to the aircraft as wind 090/05 knots, QNH 1014 and temperature 30°c. At 0928 hours UTC the airplane at about 42 miles, speed between 150-160 kts, requested descent and was cleared to 4,500H, QNH 1014. At about 0935 hours UTC, the pilots contacted tower that they would make a single engine approach because they were having problems controlling power on the starboard engine and it would be shut down. The tower in response, asked whether they would need fire coverage on landing to which the pilots affirmed. The commander then reviewed the single engine approach with the first officer estimating 4,500 ft at 8NM. Approaching 4,500 ft at 11 NM, the crew initiated right engine shut down after which the speed was decayed from 150 to 140 kts. At 0946 hours UTC, the pilot reported 6nm final and field in sight while the tower requested hire to report 4 miles final. Shortly, the controller reported having the aircraft in sight and subsequently cleared it to land on runway 05 giving wind as north easterly 06 knots. Descending at 500ft/min, the commander requested for 25% of flap when the first officer selected full flap. Shortly, the speed started decaying and bleeding faster. When the aircraft was at 2,700 ft high, the speed had already decayed to between 100 - 110 kts. The crew applied full power on the port engine to arrest the speed decay but to no avail . The pilot was trying to correct the descent rate, speed decay and the asymmetry when the stall warning came on. At this juncture, all effort by the controller to establish further contact with the airplane proved abortive. Suddenly, the controller observed a gust of dust in the atmosphere which gave him an indication that the aircraft had crashed. The aircraft crashed into the new VOR/DME site being constructed about 1175m from the threshold of runway 05. Time of accident was 0947 hours UTC.
Probable cause:
The probable cause of this accident was the poor handling by the crew of the one-engine inoperative approach.
The following findings were identified:
- The aircraft was properly registered and certified in accordance with the Civil Aviation Regulations of Nigeria.
- The commander of the aircraft was certified and qualified to take the flight while the first officer did not have a licence on board on the clay of the accident. The licence had expired and yet to he renewed.
- The proficiency check attended by the GWW was Without some critical manoeuvres such as simulated single engine approach and stalls.
- The aircraft on departure from Abuja was to land at Jos but diverted to Kaduna.
- The crew informed Kaduna Control Tower that they were doing to make a single engine (port) approach since they were having problems controlling power of the starboard engine.
- The pilots did not adhere to the laid down procedures for a one-engine inoperative approach.
- Crew coordination was practically lacking in this flight.
- The Control Tower lost contact with the aircraft at about 4NM to the airfield.
- The Landing Configuration of the aircraft was full flaps, gear up with power only on the poet engine.
- The starboard engine propeller was not feathered.
- The aircraft crashed into the new VOR/DME site being constructed about Urn from the threshold of runway 05.
- The final resting position of the aircraft was about 68m from the first point of impact and almost turning 180° from its initial direction (flight path).
- There was power on the port engine as there was severe flexural damage to the propeller blades (tips chip off).
Final Report: