Crash of a PZL-Mielec AN-2R in Orenburg

Date & Time: Feb 29, 2008
Type of aircraft:
Operator:
Registration:
RA-43990
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
1G211-09
YOM:
1985
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Orenburg-Tsentralny Airport, while climbing with a tailwind component, the skis collided with a concrete perimeter wall. The aircraft lost height and crashed 20 metres further. All 4 crew escaped unhurt while the aircraft was damaged beyond repair.

Crash of a Cessna 207 Skywagon in Aniak

Date & Time: Jan 16, 2008 at 1215 LT
Operator:
Registration:
N1701U
Flight Type:
Survivors:
Yes
Schedule:
Crooked Creek - Aniak
MSN:
207-0301
YOM:
1975
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9455
Captain / Total hours on type:
1914.00
Aircraft flight hours:
18448
Circumstances:
The commercial certificated pilot was returning from a remote village after a round robin flight of about 130 miles over a frozen and snow-covered river. He was in cruise flight about 500 feet agl, but then circled while holding between 6 or 7 miles east of his destination airport, awaiting a special VFR (SVFR) clearance. The weather condition in that area was about 1 mile visibility, with a ceiling of about 1,000 feet agl. After receiving his SVFR clearance, the pilot flew toward the airport, but the engine fuel pressure began fluctuating. The engine rpm began decreasing, along with the airplane's altitude. The pilot switched fuel tanks, selected full flaps, and prepared for a forced landing. He said the weather was near white-out conditions, but he could see the bank of the river. After switching fuel tanks from the left to the right tank, the engine power suddenly returned to full power. He applied forward flight control pressure to prevent the airplane from climbing too fast, but the airplane collided with the surface of the river. The airplane sustained structural damage to the wings and fuselage. At the time of the accident, the ceiling at the airport was 600 feet obscured, with a visibility of 1/2 mile in snow. Neither the fuel status of the accident airplane, nor the mechanical condition of the engine, were verified by either the NTSB or FAA.
Probable cause:
A partial loss of engine power for an undetermined reason. Contributing to the accident were the pilot's inadvertent encounter with IMC conditions, and a whiteout during his attempted go around from an emergency landing approach.
Final Report:

Crash of a Beechcraft A100 King Air in Chibougamau: 2 killed

Date & Time: Oct 25, 2007 at 0859 LT
Type of aircraft:
Operator:
Registration:
C-FNIF
Flight Type:
Survivors:
No
Schedule:
Val d’Or – Chibougamau
MSN:
B-178
YOM:
1973
Flight number:
CRQ501
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1800
Captain / Total hours on type:
122.00
Copilot / Total flying hours:
1022
Copilot / Total hours on type:
71
Circumstances:
The Beechcraft A100 (registration C-FNIF, serial number B-178), operated by Air Creebec Inc. on flight CRQ 501, was on a flight following instrument flight rules between Val-d’Or, Quebec, and Chibougamau/Chapais, Quebec, with two pilots on board. The aircraft flew a non-precision approach on Runway 05 of the Chibougamau/Chapais Airport, followed by a go-around. On the second approach, the aircraft descended below the cloud cover to the left of the runway centreline. A right turn was made to direct the aircraft towards the runway, followed by a steep left turn to line up with the runway centreline. Following this last turn, the aircraft struck the runway at about 500 feet from the threshold. A fire broke out when the impact occurred and the aircraft continued for almost 400 feet before stopping about 50 feet north of the runway. The first responders tried to control the fire using portable fire extinguishers but were not successful. The Chibougamau and Chapais fire departments arrived on the scene at about 0926 eastern daylight time, which was about 26 minutes after the crash. The aircraft was destroyed by the fire. The two pilots suffered fatal injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was configured late for the approach, resulting in an unstable approach condition.
2. The pilot flying carried out a steep turn at a low altitude, thereby increasing the load factor. Consequently, the aircraft stalled at an altitude that was too low to allow the pilot to carry out a stall recovery procedure.
Findings as to Risk:
1. The time spent programming the global positioning system reduced the time available to manage the flight. Consequently, the crew did not make the required radio communications on the mandatory frequency, did not activate the aircraft radio control of aerodrome lighting (ARCAL), did not make the verbal calls specified in the standard operating procedures (SOPs), and configured the aircraft for the approach and landing too late.
2. During the second approach, the aircraft did a race-track pattern and descended below the safe obstacle clearance altitude, thereby increasing the risk of a controlled flight into terrain. The crew’s limited instrument flight rules (IFR) experience could have contributed to poor interpretation of the IFR procedures.
3. Non-compliance with communications procedures in a mandatory frequency area created a situation in which the pilots of both aircraft had poor knowledge of their respective positions, thereby increasing the risk of collision.
4. The pilot-in-command monitored approach (PICMA) procedure requires calls by the pilot not flying when the aircraft deviates from pre-established acceptable tolerances. However, no call is required to warn the pilot flying of an approaching steep bank.
5. The transfer of controls was not carried out as required by the PICMA procedure described in the SOPs. The transfer of controls at the co-pilot’s request could have taken the pilot-in-command by surprise, leaving little time to choose the best option.
6. Despite their limited amount of IFR experience in a multiple crew working environment, the two pilots were paired. Nothing prohibited this. Although the crew had received crew resource management (CRM) training, it still had little multiple crew experience and consequently little experience in applying the basic principles of CRM.
Other Findings:
1. The emergency locator transmitter (ELT) had activated after the impact but due to circuit board damage its transmission power was severely limited. This situation could have had serious consequences had there been any survivors.
2. The Chibougamau/Chapais airport does not have an aircraft rescue and firefighting service. Because the fire station is 23 kilometres from the airport, the firefighters arrived at the scene 26 minutes after the accident.
3. Although this accident does not meet the criteria of a controlled flight into terrain (CFIT), it nonetheless remains that a stabilized constant descent angle (SCDA) non-precision approach (NPA) would have provided an added defence tool to supplement the SOPs.
4. After the late call within the mandatory frequency (MF) area, the specialist at the Québec flight information centre asked the crew about its familiarity with the MF area while the aircraft was in a critical phase of the first approach, which was approaching the minimum descent altitude (MDA). This situation could have distracted the flight crew while they completed important tasks.
5. The standard checklist used by the flight crew made no reference to the enhanced ground proximity warning system (EGPWS). Therefore, the crew was not prompted to check it to ensure that it was properly activated before departure.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante in Curitiba: 2 killed

Date & Time: Aug 22, 2007 at 0035 LT
Operator:
Registration:
PT-SDB
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Curitiba – Jundiaí
MSN:
110-323
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
18400
Captain / Total hours on type:
8200.00
Copilot / Total flying hours:
5600
Copilot / Total hours on type:
1600
Circumstances:
After passengers were dropped at Curitiba-Afonso Pena Airport, the crew was returning to his base in Jundiaí. Shortly after takeoff from runway 11 by night and marginal weather conditions, the airplane entered clouds at an altitude of 300 feet and continued to climb. Following a left turn, the aircraft climbed to an altitude of 700 feet then entered a right turn and an uncontrolled descent until it crashed in a field located near the Guatupê Police Academy located 3 km northeast of the airport. The accident occurred two minutes after takeoff. The aircraft was totally destroyed and both pilots were killed. At the time of the accident, the visibility was poor due to the night and a cloud base at 300 feet.
Probable cause:
Loss of control during initial climb in IMC conditions after the crew suffered a spatial disorientation. The following factors were identified:
- Weather conditions were not suitable for the completion of the flight,
- The crew failed to prepare the flight according to published procedures,
- The crew failed to follow the pre-takeoff checklist,
- The copilot did not have adequate training for this type of operation,
- The captain had emotional conditions that compromised flight operations,
- The relationship between both pilots was incompatible,
- The main attitude indicator was out of service since a week and the crew referred to the emergency attitude indicator,
- Because of poor flight preparation and non observation of the pre-takeoff checklist, the captain forgot to switch on the emergency attitude indicator prior to takeoff,
- At the time of the accident, the captain had accumulated 15 hours and 22 minutes of work without rest, which is against the law,
- The captain showed overconfidence and inflexibility which weakened his performances,
- Both pilots disagreed on operations,
- The visibility was poor due to the night and the ceiling at 300 feet above ground,
- The state of complacency of the organization was characterized by a culture adaptable to internal processes, without the adoption of formal rules for the operations division and the acceptance of operating conditions incompatible with security rules and protocols, which allowed the newly hired crew to feel free to act in disagreement with the standards and regulations in force at the time of the accident,
- Performing a sharp turn to the right in IMC conditions associated with a long working day and a lack of rest,
- The level of stress of the captain due to intense fatigue generated by a high workload and an insufficient rest period,
- Poor crew discipline,
- Poor judgment of the situation,
- Poor flight planning,
- Failures in the operator's organizational processes and lack of supervision of flight operations.
Final Report:

Crash of a Beechcraft B200 Super King Air in Garissa

Date & Time: Aug 6, 2007
Operator:
Registration:
5Y-HHM
Flight Type:
Survivors:
Yes
Schedule:
Nairobi - Garissa
MSN:
BB-1152
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a positioning flight from Nairobi to Garissa. On final approach to Garissa, a donkey entered the runway. The crew initiated a go-around procedure but the aircraft stalled and landed very hard. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 208B Grand Caravan in Arekuna Camp

Date & Time: Jul 21, 2007 at 1655 LT
Type of aircraft:
Operator:
Registration:
YV1182
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
208B-0729
YOM:
1998
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Arekuna Camp Airstrip, while climbing to a height of about 200 feet, the engine lost power. The crew attempted an emergency landing when the aircraft collided with trees and came to rest upside down. Both pilots were injured and the aircraft was destroyed.
Probable cause:
Engine failure for unknown reasons.

Crash of a Learjet 25 in Saint Augustine

Date & Time: Jul 21, 2007 at 1410 LT
Type of aircraft:
Operator:
Registration:
N70SK
Flight Type:
Survivors:
Yes
Schedule:
Gainesville - Saint Augustine
MSN:
25-49
YOM:
1970
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4620
Captain / Total hours on type:
250.00
Copilot / Total flying hours:
2453
Copilot / Total hours on type:
368
Aircraft flight hours:
15812
Circumstances:
About 5 miles from the destination airport, the flight was cleared by air traffic control to descend from its cruise altitude of 5,000 feet for a visual approach. As the first officer reduced engine power, both engines "quit." The captain attempted to restart both engines without success. He then took control of the airplane, and instructed the first officer to contact air traffic control and advise them that the airplane had experienced a "dual flameout." The captain configured the airplane by extending the landing gear and flaps and subsequently landed the airplane on the runway "hard," resulting in substantial damage to the airframe. Both engines were test run following the accident at full and idle power with no anomalies noted. Examination of the airplane revealed that it was equipped with an aftermarket throttle
quadrant, and that the power lever locking mechanism pins as well as the throttle quadrant idle stops for both engines were worn. The power lever locking mechanism internal springs for both the left and right power levers were worn and broken. Additionally, it was possible to repeatedly move the left engine's power lever directly into cutoff without first releasing its power lever locking mechanism; however, the right engine's power lever could not be moved to the cut off position without first releasing its associated locking mechanism. The right throttle thrust reverser solenoid installed on the airplane was found to be non-functional, but it is not believed that this component contributed to the accident. No explicit inspection or repair instructions were available for the throttle quadrant assembly. Other than the throttle quadrant issues, no other issues were identified with either the engines or airframe that could be contributed to both engines losing power simultaneously.
Probable cause:
A loss of power on both engines for an undetermined reason.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Orlando

Date & Time: Jul 11, 2007 at 1215 LT
Operator:
Registration:
N105GC
Flight Type:
Survivors:
Yes
Schedule:
Melbourne - Orlando
MSN:
31-7652130
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13000
Captain / Total hours on type:
200.00
Circumstances:
The airplane had undergone routine maintenance, and was returned to service on the day prior to the incident flight. The mechanics who performed the maintenance did not secure the right engine cowling using the procedure outlined in the airplane's maintenance manual. The mechanic who had been working on the outboard side of the right engine could not remember if he had fastened the three primary outboard cowl fasteners before returning the airplane to service. During the first flight following the maintenance, the right engine's top cowling departed the airplane. The pilot secured the right engine, but the airplane was unable to maintain altitude, so he then identified a forced landing site. The airplane did not have a sufficient glidepath to clear a tree line and buildings, so he landed the airplane in a clear area about 1,500 yards short of the intended landing area. The airplane came to rest in a field of scrub brush, and about 5 minutes after the pilot deplaned, the grass under the left engine ignited. The subsequent brush fire consumed the airplane. Examination of the right engine cowling revealed that the outboard latching fasteners were set to the "open" position. When asked about the security of the cowling during the preflight inspection, the pilot stated that he "just missed it."
Probable cause:
The mechanic's failure to secure the right engine cowling fasteners. Contributing to the incident was the pilot's inadequate preflight inspection.
Final Report:

Crash of a Britten-Norman BN-2A Islander in Nassau

Date & Time: Jun 27, 2007 at 1721 LT
Type of aircraft:
Operator:
Registration:
N133RS
Flight Type:
Survivors:
Yes
Schedule:
Little White Cay - Nassau
MSN:
606
YOM:
1970
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
9010
Circumstances:
On June 27, 2007 about 1721 eastern daylight time (2121Z) a Pilatus Britten Norman Islander, N133RS registered to and owned by FYP LTP, and operated by Golden Wings Charter, Windsor Field, Nassau, Bahamas, had crashed short of runway 14. Just prior to crashing, approximately 1718 eastern daylight time (2118Z), the pilot of aircraft N133RS reported the left engine had failed. At approximately 1721 eastern daylight time (2121Z), the pilot reported he was unable to make runway 14 and crashed approximately ½ mile short of Runway 14. The State of Manufacture and State of Design along with the State of Registry were notified of the accident on June 28, 2007. They were invited to participate in the investigation in accordance with Annex 13 and CASR 2001 Schedule 18. Visual Meteorological Conditions prevailed at the time of the accident. The flight originated from Lynden Pindling International Airport, Nassau [MYNN] to Little Whale Cay, Berry Island [MYBX] and returned to Nassau [MYNN], the incident leg. The airplane sustained substantial damage. The Pilot was the only person aboard the aircraft. The Pilot in Command holds a current United States Commercial Pilot Rating. No serious injuries or fatalities were reported.
Probable cause:
The Flight Standards Inspectorate determined that the probable cause of this accident was Propulsion System Malfunction due to fuel exhaustion of the left engine, followed by inappropriate crew response (fuel mismanagement).
Contributing Factors:
- Pilot’s unfamiliarity with aircraft fuel system.
- Pilot’s limited command experience. (He was a new hire, low time pilot)
- Pilot’s failure to conduct a proper preflight inspection of his aircraft. (did not visually check fuel tanks despite knowing that the gauges were faulty)
- Pilot’s complacency with documentation of defects. (Pilot never advised maintenance or management that the gauges were faulty)
- Pilot’s reliance on indications that he admitted were erroneous.
- Pilot’s lack of situational awareness.
- Pilot’s failure to recognize that his problem was fuel exhaustion and not engine failure and neglected to use cross-feed procedure.
Final Report:

Ground accident of a Saab 340A in Kuwait City

Date & Time: Mar 12, 2007
Type of aircraft:
Operator:
Registration:
OD-IST
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Kuwait City - Beirut
MSN:
13
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While taxiing at Kuwait City Airport, preparing for a flight to Beirut, the twin engine aircraft collided with a vehicle, causing serious damages to the right wing. Both pilots escaped uninjured while the aircraft was damaged beyond repair.