Crash of a BAe 125-403B in Luanda

Date & Time: Nov 21, 2003
Type of aircraft:
Operator:
Registration:
D2-EXR
Flight Type:
Survivors:
Yes
Schedule:
Luanda – Catumbela
MSN:
25215
YOM:
1970
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Few minutes after takeoff from Lunda-4 de Fevereiro Airport, en route to Catumbela, the crew informed ATC about hydraulic problems and was cleared for an emergency return to Luanda. Due to the failure of the primary hydraulic system, the crew was unable to lower the landing gear and decided to complete a belly landing on the grassy area located between both runways 23 and 25. The aircraft slid on its belly for few dozen metres before coming to rest. Both pilots were uninjured but the aircraft was damaged beyond repair.

Crash of a Cessna 550 Citation II in Mineral Wells

Date & Time: Nov 18, 2003 at 1410 LT
Type of aircraft:
Operator:
Registration:
N418MA
Flight Type:
Survivors:
Yes
Schedule:
Fort Worth – Mineral Wells
MSN:
550-0144
YOM:
1980
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16500
Captain / Total hours on type:
500.00
Circumstances:
A designated pilot examiner (DPE) was administering a type-rating check ride from the jump seat (located behind co-pilot's seat), and instructed the second-in-command (SIC) (required for the check ride and occupying the front right seat) to reduce the power on one engine to simulate a single engine approach. Approximately 23 seconds later, the airplane began to "drop rapidly." To arrest the descent, both pilots simultaneously applied full power on both engines, and the applicant (occupying the front left seat) increased the airplane's pitch attitude to 12 degrees. However, the airplane continued to descend and touched down short of the landing threshold for the runway. A post-impact fire consumed the airplane. According to the applicant, after takeoff, he demonstrated several maneuvers, and was then provided vectors for a VOR instrument approach. While executing the approach, it was "really bumpy", and they hit a gust of wind, which resulted in him having to correct the airplane's attitude back to straight and level flight. When the airplane was approximately one mile from the end of the runway, he looked outside and saw that he was high on the approach and extended the flaps to 40 degrees. Shortly after, the PIC reduced power on the left engine to simulate a single-engine approach. When the airplane was approximately 1/4 to 1/2-mile from the end of the runway, at 400 feet mean sea level (msl) (about 366 feet above ground level), Vref 110, the airplane began to sink rapidly, and it impacted the ground. The applicant said that he, "never experienced wind shear like that before...and in hindsight it would have been more helpful if they had a better understanding of the wind conditions before they tried to land." Under current FAA regulations, even though the pilot in the right seat (the applicant's flight instructor) acted as the SIC for the purpose of the check ride, the applicant was not type rated in the airplane, and technically, could not be designated as the pilot-in-command (PIC). The instructor was type rated in the airplane; and therefore, was the PIC.
Probable cause:
The pilot-in-command's failure to maintain control of the airplane while executing a simulated engine failure on final approach. A factor was the windshear.
Final Report:

Crash of a Swearingen SA226TC Metro II in Grand Junction

Date & Time: Nov 18, 2003 at 0721 LT
Type of aircraft:
Operator:
Registration:
N332BA
Flight Type:
Survivors:
Yes
Schedule:
Rifle – Grand Junction
MSN:
TC-222E
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2419
Captain / Total hours on type:
140.00
Aircraft flight hours:
23972
Circumstances:
According to the pilot, he was told to enter left base and was cleared to land. The pilot stated that, when he reduced the airspeed to lower the landing gear, he "heard the gear come down," and he verified "three green in the [landing] gear indicator." He landed the airplane on its "main [landing gear] wheels first" and slowly let the nose of the airplane drop. Although both main landing gear assemblies remained down and locked, the nose landing gear collapsed, allowing the nose of the airplane and both propellers to strike the runway. The airplane slid approximately 3,000 feet, coming to a stop on the right edge of the runway. Several fractured propeller pieces impacted the left and right sides of the fuselage substantially damaging two fuselage station bulkheads. The fuselage bulkhead, forward of the nose landing gear well, was also substantially damaged due to contact with the runway. The pilot said that, during the approach, from base to final, he did not hear a landing gear warning horn. An air traffic control specialist, stated that he told the pilot to enter a left base and that he was cleared to land. The specialist stated that he observed the airplane roll out on a 2-mile final "with the gear down." As the airplane was rolling down the runway the "nose wheel collapsed." An FAA inspector examined the airplane and noted that, according to the Fairchild SA226 Maintenance Manual, the nose landing gear's up-lock mechanism was not properly lubricated, a "critical clearance" measurement between the nose landing gear's bell crank roller and positioning cam was found to be out of tolerance, and when the throttles were retarded, the landing gear warning horn activated, but it was "barely audible." According to the Fairchild SA226 Maintenance Manual, the landing gear should be lubed every 200 hours. The FAA inspector stated that the approved maintenance inspection sheet for the operator, did not show the requirement for the main landing gear or nose landing gear to be lubed every 200 hours.
Probable cause:
The operator's improper maintenance and servicing of the airplane's nose landing gear assembly, resulting in the collapse of the nose landing gear during the landing roll. Contributing factors include the nose section of the airplane's subsequent contact with the runway, the impact of several fractured propeller pieces into the fuselage, and the operator's inadequate maintenance and servicing procedures.
Final Report:

Crash of an Antonov AN-12BP in Wau: 13 killed

Date & Time: Nov 17, 2003 at 1625 LT
Type of aircraft:
Operator:
Registration:
ST-SAA
Flight Type:
Survivors:
No
Schedule:
Khartoum – Wau
MSN:
5 3 429 05
YOM:
1965
Flight number:
SRW044
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
The aircraft was completing a cargo flight from Khartoum to Wau, carrying seven passengers, six crew members and a load consisting of foods and bank notes. On final approach to Wau Airport, the aircraft went out of control and crashed in an open field located 6 km short of runway, bursting into flames. All 13 occupants were killed, among them soldiers and members of the National Bank of Sudan.

Crash of a Learjet 24D in Saint Louis

Date & Time: Nov 12, 2003 at 0645 LT
Type of aircraft:
Operator:
Registration:
N77JL
Flight Phase:
Survivors:
Yes
Schedule:
Saint Louis – North Platte
MSN:
24-286
YOM:
1974
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9054
Captain / Total hours on type:
760.00
Copilot / Total flying hours:
3400
Copilot / Total hours on type:
150
Aircraft flight hours:
6653
Aircraft flight cycles:
6504
Circumstances:
The turbojet airplane was destroyed during a forced landing and post accident fire after a loss of power in both engines during takeoff climb. The pilot reported that both engines operated
normally during taxi and pre-takeoff checks. He reported that, "We rotated positive rate gear up, V2 plus 30 flaps up, and at that point we struck birds taking No. 2 engine out. Upon losing No. 2 engine I advanced thrust levers forward and realized that the No. 1 engine was only producing approximately 70% RPM with EGT over read line." He executed a forced landing to a field and the crew and passengers evacuated the burning airplane. The copilot reported, "At approximately 500 to 1,000 ft. above ground level, I observed a large flock of birds straight ahead of us, and then passing just off our nose to the left side. I immediately heard an engine flameout. As I started to go to the checklist for single engine operations, I quickly realized that we were loosing airspeed and unable to maintain altitude. The PIC said we were going down and heading for the best emergency-landing stop." The Cockpit Voice Recorder (CVR) recorded the pilot stating, "We hit a bird," and the copilot stating, "Yep," immediately following the CVR recording a "sound similar to decrease in engine RPM." The inspection of the airplane's fuel system, pneumatic system, engines, fuel controls and fuel pumps revealed no pre-impact anomaly. No physical evidence of bird ingestion was found in either engine. A CVR sound spectrum plot and a flight profile analysis revealed that one engine flamed out almost immediately after the sound of a "thump" on the CVR. The other engine's speed decreased and experienced stalls until the engine speed was reduced to flight idle. The original engine certification tests indicated that compressor stalls occurred when a 2-4 ounce starling was shot ingested into the engine, but physical damage from bird ingestion was very slight due to the all steel construction and geometry of the engine. Engine flameouts, however, were not recorded during the certification tests. A wildlife specialist conducted a bird count at the accident airport two days after the accident occurred, and he reported counting a flock of about 800 European Starlings.
Probable cause:
The total loss of power to the right engine and the partial loss of power to the left engine after the airplane encountered a flock of birds during initial climb out, resulting in impeded ram induction airflow.
Final Report:

Crash of a Short SC.7 Skyvan 3M Variant 100 in Georgetown: 2 killed

Date & Time: Nov 8, 2003 at 1100 LT
Type of aircraft:
Operator:
Registration:
8R-GMC
Flight Phase:
Survivors:
Yes
Schedule:
Georgetown – Ekereku
MSN:
1959
YOM:
1978
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
One minute after takeoff from Georgetown-Ogle Airport runway 24, the pilot declared an emergency after an engine failed. He elected to return for an emergency landing but eventually attempted to land in a sugarcane field when the aircraft crashed near the airport. Five people were seriously injured while two others were killed.
Probable cause:
Failure of the right engine during initial climb for unknown reasons.

Crash of an Antonov AN-12B in Geneina

Date & Time: Nov 3, 2003 at 0735 LT
Type of aircraft:
Operator:
Registration:
EK-11997
Flight Type:
Survivors:
Yes
Schedule:
Khartoum – Geneina
MSN:
6 3 444 07
YOM:
1966
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Geneina Airport, the crew failed to realize his altitude was too low when the aircraft struck the ground eight metres short of runway threshold. On impact, the undercarriage were torn off and the aircraft slid for about 800 metres before coming to rest. All five crew members escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Mitsubishi MU-2B-35 Marquise in Kralendijk

Date & Time: Nov 2, 2003 at 2331 LT
Type of aircraft:
Operator:
Registration:
N630HA
Flight Type:
Survivors:
Yes
Schedule:
Oranjestad – Kralendijk
MSN:
630
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On November 2, 2003, about 2331 Atlantic standard time, a Mitsubishi MU-2B-35, N630HA, registered to Hezemans Air, Inc., collided with terrain short of the runway at Flamingo Airport, Bonaire, Netherlands Antilles, while on a CFR Part 91 positioning flight from Aruba to Bonaire. Visual meteorological conditions prevailed at the time and an instrument flight rules flight plan was filed. The airplane received substantial damage and the airline transport-rated pilot received serious injuries. The flight originated from Aruba, the same day about 2250. The pilot stated that when on a 1- mile final approach for landing both engines lost power. The airplane descended and collided with terrain about 300 meters from the runway. Postaccident examination of the airplane by Civil Aviation Authorities showed the airplane did not contain any usable fuel and there was no evidence of fuel leakage from the airplane prior to the accident or after the accident.

Crash of a PZL-Mielec AN-28 in Kamina

Date & Time: Oct 30, 2003
Type of aircraft:
Operator:
Registration:
ER-AJG
Flight Type:
Survivors:
Yes
Schedule:
Kilembwe – Kamina
MSN:
1AJ004-09
YOM:
1987
Location:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft struck the ground 800 metres short of runway. Congolese Army' Soldiers guarded the site, so no UNO observers could get in. Illegal cargo flight with arms and war material on board is suspected.

Crash of a Piper PA-42-720 Cheyenne IIIA in Zurich

Date & Time: Oct 28, 2003 at 0742 LT
Type of aircraft:
Operator:
Registration:
D-IFSH
Flight Type:
Survivors:
Yes
Schedule:
Leipzig – Zurich
MSN:
42-8001101
YOM:
1982
Flight number:
RUS1050
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1000
Captain / Total hours on type:
900.00
Copilot / Total flying hours:
500
Copilot / Total hours on type:
34
Aircraft flight hours:
5276
Aircraft flight cycles:
4370
Circumstances:
The crew was completing a positioning flight (RUS1050) from Leipzig to Zurich on behalf of FSH Luftfahrtunternehmen but under contract of Cirrus Aviation. On final approach to Zurich-Kloten Airport, the crew encountered poor visibility due to foggy conditions. Despite the RVR for runway 14 was estimated to be 275 metres (below minimums of 400 metres for a CAT II approach if aircraft and crew are qualified), the crew decided to continue the approach, descended below the MDA until the aircraft struck the ground between both runways 14 and 16. The aircraft rolled for few dozen metres then lost its undercarriage and came to rest in a frosty field. Both pilots escaped with minor injuries and the aircraft was damaged beyond repair. At the time of the accident, the vertical visibility was 300 feet, the horizontal visibility was 200 metres with freezing fog, an OAT of -3° C and a dew point of -4° C.
Probable cause:
The accident is due to the fact that the crew continued the approach below the decision height during an ILS approach to runway 14 without sufficient visual references. As a result, the plane struck the ground and crashed. The following factors contributed to the development of the accident:
- The aircraft was neither equipped nor approved for approaches under the prevailing weather conditions.
- The crew was not trained for approaches in such weather conditions.
- The crew failed to comply with SOP's and did not assigned tasks.
- The crew was not familiar with the procedural requirements.
- The crew knowledge was insufficiently checked by the operator.
Final Report: