Crash of a Douglas DC-3-455 in Las Gaviotas

Date & Time: Jun 21, 2004 at 1700 LT
Type of aircraft:
Operator:
Registration:
HK-1212
Flight Phase:
Survivors:
Yes
Schedule:
Las Gaviotas – Puerto Carreño
MSN:
4987
YOM:
1942
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
50159
Circumstances:
Following technical problems, a DC-3 operated by Viarco diverted to Las Gaviotas Airport and was grounded. The operator send a second aircraft to Las Gaviotas to pick up the passengers. Shortly after takeoff from runway 24, while in initial climb, the right engine failed and caught fire. The aircraft stalled and crashed in a wooded area, bursting into flames. All 20 occupants were injured, six seriously. The aircraft was destroyed.
Probable cause:
Rupture of a crank and subsequent total loss of power and fire in the right engine during rotation of the plane, which reduced the performance of the aircraft, causing the pilot to lose control of the aircraft, resulting in the immediate collision with the ground.

Crash of a PZL-Mielec AN-2R in Bozoy: 1 killed

Date & Time: May 19, 2004 at 1040 LT
Type of aircraft:
Operator:
Registration:
UN-70276
Flight Phase:
Survivors:
Yes
Schedule:
Kyzylorda – Bozoy – Vozrozhdeniya Island
MSN:
1G139-35
YOM:
1972
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The single engine aircraft departed Kyzylorda on a charter flight to the island of Vozrozhdeniya with an intermediate stop in Bozoy, carrying 10 doctors and two pilots. They were taking part to a plague control program. After takeoff from Bozoy, while climbing to a height of about 50 metres, the aircraft stalled and crashed in an open field. All 12 occupants were rescued, among them three passengers were seriously injured. Few hours later, one of them died from his injuries.
Probable cause:
Stall and loss of control after the cargo shifted during initial climb. It was determined that the cargo was not properly secured in the cabin and moved to the rear during initial climb. The distance between the aircraft and the ground was insufficient to expect recovery. It was also reported that the aircraft has been refueled with AI-96 motor gasoline instead of aviation fuel.

Crash of a De Havilland DHC-2 Beaver in Fawcett Lake: 4 killed

Date & Time: May 18, 2004 at 1800 LT
Type of aircraft:
Registration:
C-GQHT
Survivors:
No
Schedule:
Pickeral Arm Camp - Fawcett Lake
MSN:
682
YOM:
1954
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1688
Captain / Total hours on type:
344.00
Circumstances:
Pickerel Arm Camps is located about 22 km south of Sioux Lookout, Ontario. It operates a main campsite at its water base and several remote fishing lodges. The company operates two float equipped de Havilland DHC-2 Beaver aircraft to fly guests and supplies to their remote sites. Seven guests of the company arrived at the water base on 18 May 2004, the day before their scheduled four-day fishing trip at Fawcett Lake, one of the remote lodges. Because the remote lodge was available, a decision was made to fly in that afternoon. The group was divided in two, and a group of three guests and all the supplies for the seven guests were to go in the first aircraft. The second group of four, with their personal baggage, was to follow in the company’s other Beaver. The occurrence aircraft, a de Havilland DHC-2 Beaver (C-GQHT, serial number 682) with one pilot and three camp guests on board, departed the company water base at approximately 1700 eastern daylight time on a day visual flight rules flight to Fawcett Lake. At approximately 1930, the pilot and the other four guests arrived in the second aircraft to discover that the first group had not arrived. The guests later found the accident aircraft overturned in the lake. Ontario Provincial Police divers recovered the bodies of the pilot and the three passengers. The aircraft sustained substantial damage. There was no fire.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The pilot flew a high-drag approach configuration for which his proficiency was not established.
2. The pilot most likely allowed the airspeed to decrease to the point that the aircraft stalled on approach at an altitude at which recovery was unlikely.
3. The impact was non-survivable because of the high impact forces.
Findings as to Risk:
1. The emergency locator transmitter (ELT) airframe antenna was broken off above the fuselage; however, the flight was within the 30-day period allowed by regulation for flight with an unserviceable ELT.
2. The pilot did not secure the cargo prior to flight, which allowed the cargo to shift forward on impact.
3. The weight and centre of gravity (C of G) were not indicated in the operational flight plan and load record, and the aircraft’s weight and C of G could only be estimated.
Final Report:

Crash of a Beechcraft A100 King Air in Chibougamau

Date & Time: Apr 19, 2004 at 1018 LT
Type of aircraft:
Operator:
Registration:
C-FMAI
Survivors:
Yes
Schedule:
Quebec - Chibougamau
MSN:
B-145
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11338
Captain / Total hours on type:
2600.00
Copilot / Total flying hours:
1176
Copilot / Total hours on type:
400
Circumstances:
The Beechcraft A100, registration C-FMAI, operated by Myrand Aviation Inc., was on a chartered instrument flight rules flight from QuÈbec/Jean Lesage International Airport, Quebec, to Chibougamau/Chapais Airport, Quebec, with two pilots and three passengers on board. The copilot was at the controls and was flying a non-precision approach for Runway 05. The pilot-in-command took the controls less than one mile from the runway threshold and saw the runway when they were over the threshold. At approximately 1018 eastern daylight time, the wheels touched down approximately 1500 feet from the end of Runway 05. The pilot-in-command realized that the remaining landing distance was insufficient. He told the co-pilot to retract the flaps and applied full power, but did not reveal his intentions. The co-pilot cut power, selected reverse pitch and applied full braking. The aircraft continued rolling through the runway end, sank into the gravel and snow, and stopped abruptly about 500 feet past the runway end. The aircraft was severely damaged. None of the occupants were injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was positioned over the runway threshold at an altitude that did not allow a landing at the beginning of the runway, and this, combined with a tailwind component and the wet runway surface, resulted in a runway excursion.
2. Failure to follow standard operating procedures and a lack of crew coordination contributed to confusion on landing, which prevented the crew from aborting the landing and executing a missed approach.
3. The pilot-in-command held several management positions within the company and controlled the pilot hiring and dismissal policies. This situation, combined with the level of experience of the co-pilot compared with that of the pilot-in-command, had an impact on crew cohesiveness.
Findings as to Risk:
1. The pilot-in-command of C-FMAI decided to execute an approach for Runway 05 without first ensuring that there would be no possible risk of collision with the other aircraft.
2. The regulatory requirement to conform to or avoid the traffic pattern formed by other aircraft is not explicit as to how the traffic pattern should be avoided, in terms of either altitude or distance, which can result in risks of collision.
3. The regulations do not indicate whether the missed approach segment should be considered part of the traffic pattern; this situation can lead pilots operating in uncontrolled airspace to believe that they are avoiding another aircraft executing an instrument approach when in reality a risk of collision exists.
Final Report:

Crash of a Cessna 414 Chancellor in Linz

Date & Time: Feb 13, 2004 at 0615 LT
Type of aircraft:
Operator:
Registration:
OE-FRW
Flight Phase:
Survivors:
Yes
Schedule:
Linz - Stuttgart
MSN:
414-0825
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2527
Captain / Total hours on type:
830.00
Copilot / Total flying hours:
522
Copilot / Total hours on type:
250
Aircraft flight hours:
4463
Circumstances:
The twin engine aircraft departed Linz-Hörsching Airport on a taxi flight to Stuttgart with five passengers and two pilots on board. During the takeoff roll on runway 27, at a speed of 105 knots, the crew started the rotation. Immediately after liftoff, the aircraft adopted a high nose attitude with an excessive angle of attack. It rolled to the left, causing the left gear door and the left propeller to struck the runway surface, followed shortly later by the right propeller. After the speed dropped, the aircraft stalled and crash landed on the runway. It slid for few dozen metres and came to rest 2,752 metres past the runway threshold. All seven occupants were evacuated, one passenger suffered serious injuries. The aircraft was damaged beyond repair.
Probable cause:
The loss of control immediately after liftoff was the consequence of an aircraft contaminated with ice, resulting in an excessive weight, a loss of lift and a consequent stall. The following factors were identified:
- Poor flight preparation,
- The crew failed to follow the SOP procedures prior to takeoff,
- The aircraft has not been deiced prior to takeoff, increasing the total weight of the aircraft by 231 kilos, 8% above the MTOW,
- This situation caused the CofG to be out of the permissible limits,
- Poor judgment on part of the crew when the undercarriage were lowered.

Crash of a Beechcraft 1900D in Ghardaïa: 1 killed

Date & Time: Jan 28, 2004 at 2101 LT
Type of aircraft:
Operator:
Registration:
7T-VIN
Survivors:
Yes
Schedule:
Hassi R’Mel – Ghardaïa
MSN:
UE-365
YOM:
1999
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
1742
Circumstances:
The aircraft departed Hassi R'Mel-Tilrhempt Airport at 2030LT on a 15-minutes charter flight to Ghardaïa, carrying three crew members and two employees of the Sonatrach (Société Nationale pour le Transport et la Commercialisation d’Hydrocarbures). At 2044LT, the crew was cleared for a right hand circuit in preparation for an approach to runway 30. At that moment a Boeing 727 inbound from Djanet was on long finals. The copilot stated that he intended to carry out an NDB/ILS approach to runway 30. The captain however preferred a visual approach. The copilot carried out the captain's course and descent instructions with hesitation. At 2057LT, the EGPWS alarm sounded. Power was added and a climb was initiated from a lowest altitude of 240 feet above ground level. The captain then took over control and assumed the role of Pilot Flying. The airplane manoeuvred south of the airport until 2101LT when the copilot saw the runway. The captain rolled left to -57° and pitched down to -18.9° in order to steer the airplane towards the runway. Again the EGPWS sounded but the descent continued until the airplane impacted the ground and broke up. All five occupants were injured and the aircraft was destroyed. A day later, the copilot died from his injuries.
Probable cause:
The Commission believes that the accident can be explained by a series of several causes which, taken separately, would not lead to an accident.
The causes are related to:
1 - the lack of rigor in the approach and landing phase evidenced by a failure to follow standard operating procedures, including the arrival checklist.
2 - the failure to strictly comply with the holding, approach and landing procedures in force for the aerodrome of Ghardaïa.
3 - the fact that the captain seemed occupied by the visual search maneuvers that put him temporarily out of the control loop. He was so focused on the visual search for the runway and abandoned the monitoring of parameters that are critical for the safety of the flight. This concentration completely disoriented him.
4 - the fact that the crew did not respond appropriately to different alarms that occurred, indicating a lack of control in the operation of the aircraft in that kind of situation. Lack of control was apparently due to his lack of training on this aircraft type.
5 - The activities in the southern part of Algeria may cause a certain routine that can promote the tendency to conduct visual approaches. It seems, indeed, that the crew is more experienced in visual flights.
6 - A lack of coordination and communication between the crew members flying together for the first time.

Crash of an Ilyushin II-18D in Luena

Date & Time: Jan 27, 2004 at 1440 LT
Type of aircraft:
Operator:
Registration:
ER-ICJ
Flight Phase:
Survivors:
Yes
Schedule:
Luena – Luanda
MSN:
186 0091 02
YOM:
1966
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll on runway 29, the aircraft did not accelerate as expected. The captain decided to abort the takeoff procedure but the aircraft could not be stopped within the remaining distance. It overran and collided with trees located 100 meters further. A crew member was injured and the aircraft was damaged beyond repair.

Crash of a Boeing 737-3Q8 off Sharm el-Sheikh: 148 killed

Date & Time: Jan 3, 2004 at 0445 LT
Type of aircraft:
Operator:
Registration:
SU-ZCF
Flight Phase:
Survivors:
No
Schedule:
Sharm el-Sheikh - Cairo - Paris
MSN:
26283
YOM:
1992
Flight number:
FSH604
Country:
Region:
Crew on board:
13
Crew fatalities:
Pax on board:
135
Pax fatalities:
Other fatalities:
Total fatalities:
148
Captain / Total flying hours:
7443
Captain / Total hours on type:
474.00
Copilot / Total flying hours:
788
Copilot / Total hours on type:
242
Aircraft flight hours:
25603
Aircraft flight cycles:
17976
Circumstances:
Following a night takeoff from runway 22R at Sharm el Sheikh-Ophira Airport, the plane climbed and maneuvered for a procedural left turn to intercept the 306 radial from the Sharm el Sheikh VOR station. When the autopilot was engaged the captain made an exclamation and the autopilot was immediately switched off again. The captain then requested Heading Select to be engaged. The plane then began to bank to the right. The copilot then warned the captain a few times about the fact that the bank angle was increasing. At a bank angle of 40° to the right the captain stated "OK come out". The ailerons returned briefly to neutral before additional aileron movements commanded an increase in the right bank. The aircraft had reached a maximum altitude of 5,460 feet with a 50° bank when the copilot stated 'overbank'. Repeating himself as the bank angle kept increasing. The maximum bank angle recorded was 111° right. Pitch attitude at that time was 43° nose down and altitude was 3,470 feet. The observer on the flight deck, a trainee copilot, called 'retard power, retard power, retard power'. Both throttles were moved to idle and the airplane gently seemed to recover from the nose-down, right bank attitude. Speed however increased, causing an overspeed warning. At 04:45 the airplane struck the surface of the water in a 24° right bank, 24° nose-down, at a speed of 416 kts and with a 3,9 G load. The aircraft disintegrated on impact and debris sank by a depth of 900 metres. All 148 occupants were killed, among them 133 French citizens, one Moroccan, one Japanese and 13 Egyptian (all crew members, among them six who should disembark at Cairo). Weather at the time of accident was good with excellent visibility, outside temperature of 17° C and light wind. On January 17, the FDR was found at a depth of 1,020 metres and the CVR was found a day later at a depth of 1,050 metres.
Probable cause:
No conclusive evidence could be found from the findings gathered through this investigation to determine the probable cause. However, based on the work done, it could be concluded that any combination of these findings could have caused or contributed to the accident. Although the crew at the last stage of this accident attempted to correctly recover, the gravity upset condition with regards to attitude, altitude and speed made this attempt insufficient to achieve a successful recovery.
Possible causes:
- Trim/Feel Unit Fault (Aileron Trim Runaway),
- Temporarily, Spoiler wing cable jam (Spoiler offset of the neutral position),
- Temporarily, F/O wheel jam (Spoilers offset of the neutral position),
- Autopilot Actuator Hardover Fault.
Possible contributing factors:
- A distraction developing to Spatial Disorientation (SD) until the time the F/O announced 'A/C turning right' with acknowledgment of the captain,
- Technical log copies were kept on board with no copy left at departure station,
- Operator write up of defects was not accurately performed and resulting in unclear knowledge of actual technical status,
- There are conflicting signals which make unclear whether the captain remained in SD or was the crew unable to perceive the cause that was creating an upset condition until the time when the F/O announced that there was no A/P in action,
- After the time then the F/O announced 'no A/P commander' the crew behavior suggests the recovery attempt was consistent with expected crew reaction, evidences show that the corrective action was initiated in full, however the gravity of the upset condition with regards to attitude, altitude and speed made this attempt insufficient to achieve a successful recovery.
Additional findings:
- The ECAA authorization for RAM B737 simulator was issued at a date later than the date of training for the accident crew although the inspection and acceptance test were carried out at an earlier date.
- Several recorded FDR parameters were unreliable and could not be used for the investigation.
Final Report:

Crash of a De Havilland DHC-3 Otter in Jellicoe: 2 killed

Date & Time: Dec 16, 2003 at 1200 LT
Type of aircraft:
Operator:
Registration:
C-GOFF
Flight Phase:
Survivors:
Yes
MSN:
65
YOM:
1954
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5016
Captain / Total hours on type:
540.00
Circumstances:
At approximately 0900 eastern standard time (EST), the pilot arrived at the airstrip and prepared the ski-equipped de Havilland DHC–3 (Otter) aircraft (registration C–GOFF, serial number 65) for the morning flight. This Otter was equipped with a turbine engine. Two passengers, with enough supplies for an extended period of time, including a snowmobile and camping gear, were to be flown to a remote location. The pilot loaded the aircraft and waited for the weather to improve. At approximately 1200 EST, the pilot and passengers boarded the aircraft and took off in an easterly direction. The aircraft got airborne near the departure end of the airstrip, and, shortly after take-off, the right wing struck a number of small bushes and the top of a birch tree. The aircraft descended and struck the frozen lake surface, approximately 70 feet below the airfield elevation in a steep, nose-down, right-wing-low attitude. When it came to rest, the aircraft was inverted and partially submerged, with only the aft section of the fuselage remaining above the ice. All of the occupants were wearing lap belts. The pilot and front seat passenger received fatal injuries. The rear seat passenger survived the impact and evacuated the aircraft with some difficulty due to leg injuries. The following morning, about 22 hours after the accident, a local air operator searching for the missing aircraft located and rescued the surviving passenger.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The pilot attempted to take off from an airstrip that was covered with approximately 18 inches of snow, and the aircraft did not accelerate to take-off speed because of the drag; the aircraft was forced into the air and was unable to climb out of ground effect and clear the obstacles.
2. The pilot did not abort the take-off when it became apparent that the aircraft was not accelerating normally and before the aircraft became airborne.
Findings as to Risk:
1. Unidirectional G switches, which are found on many types of ELTs, do not always activate the unit when impact forces are not aligned with the usual direction of flight.
Other Findings:
1. The validity of the aircraft’s certificate of airworthiness was affected while it flew more flights than allowed by the ferry permit issued by Transport Canada.
2. The rear passenger seat was found to be installed incorrectly, contrary to de Havilland Alert Service Bulletin A3/49, dated 19 July 1991.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Viekoda Bay

Date & Time: Nov 29, 2003 at 0935 LT
Type of aircraft:
Operator:
Registration:
N13VF
Survivors:
Yes
Site:
Schedule:
Kodiak – Viekoda Bay
MSN:
1613
YOM:
1965
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7103
Captain / Total hours on type:
3100.00
Aircraft flight hours:
14953
Circumstances:
During an on-demand air taxi flight, the airline transport certificated pilot was preparing to land an amphibious float-equipped airplane near a cabin that was located on the shore of a coastal bay. A 10 to 15 knot wind was blowing from the bay toward the land, and the pilot decided to approach over land. As the airplane descended over a small creek bed, adjacent to a hill, the airplane encountered a downdraft, and descended rapidly. The left wing collided with alder trees which spun the airplane 180 degrees. The right wing and float assembly were torn off the airplane. The closest official weather observation station, located 30 miles away, was reporting calm wind.
Probable cause:
The pilot's inadequate evaluation of the weather conditions, and his failure to maintain adequate altitude/clearance, which resulted in a collision with terrain during the final landing approach. A factor contributing to the accident was the presence of a downdraft.
Final Report: