Crash of a Canadair RegionalJet CRJ-100ER in Yerevan

Date & Time: Feb 14, 2008 at 0415 LT
Operator:
Registration:
EW-101PJ
Flight Phase:
Survivors:
Yes
Schedule:
Yerevan - Minsk
MSN:
7316
YOM:
1999
Flight number:
BRU1834
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
15563
Aircraft flight cycles:
14352
Circumstances:
A Canadair CRJ100ER passenger jet, operated by Belavia, was destroyed when crashed and burned on takeoff from Yerevan-Zvartnots Airport (EVN), Armenia. All three crew members and eighteen passengers survived the accident. The airplane arrived as flight BRU1833 from Minsk-2 International Airport (MSQ), Belarus at 02:05. Refueling was carried out in preparation for the return flight and the crew conducted the flight planning. After refueling the pilot carried out a tactile and visual inspection of all critical surfaces of the wing and visual inspection of the tail assembly. All the planes were clean and dry. The weather reported for the 04:00 was: wind 110 degrees at the ground 1 m/sec, visibility 3500 meters, haze, small clouds, vertical visibility of 800 meters, scattered clouds at 3000 m, a temperature of minus 3° C, dew point minus 4° C, pressure 1019 hPa. At 04:08 both engines were started. The engine air intake heating (cowl anti-ice) was switched on but the wing anti-icing system was not switched on. The crew taxied to runway 27 and were cleared for departure. During takeoff the airplane progressively banked left until the left wing tip contacted runway. The airplane went off the side with the airplane rolling the right. The right hand wing broke off and spilled fuel caught fire. The airplane came to rest upside down.
Probable cause:
The accident involving aircraft CRJ-100LR registration number EW-101PJ was the result of an asymmetric loss of lift of the wing during take-off, which led to the toppling of the aircraft immediately after liftoff from the runway, the left wing tip contacting the ground, the subsequent destruction and fire. The reason for the loss of lift of the wing at the actual weather conditions, was the formation of frost, which "pollutes" the surface of the wing. The cause of formation of frost, most likely, was the fuel icing, while the aircraft was parked at the airport and during taxiing for the return flight, resulting in a difference in temperature of the surrounding air and cold fuel in the tanks after the flight. The situation could be aggravated when exceeding the values recommended by the operations manual of the angular velocity when lifting the nose wheel during takeoff with "contaminated" wings when it is impossible to monitor this parameter instrumentally. Existing procedural methods of control of the aerodynamic surfaces of the aircraft before departure, along with the inefficiency, during takeoff, the existing system of protection from stalling due to increased sensitivity of the wing, even to a slight contamination of the leading edge, can not fully guarantee the prevention of similar accidents in future. An Airworthiness Directive on the need to include anti-icing systems on the wing in the final stage of taxiing at the actual weather conditions was issued by Transport Canada after the accident. This probably could have prevented the accident.

Crash of an Ilyushin II-76TD in Kandahar

Date & Time: Feb 14, 2008
Type of aircraft:
Registration:
UN-76020
Flight Type:
Survivors:
Yes
MSN:
00434 50493
YOM:
1984
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing at Kandahar Airport, the engine n°1 exploded and caught fire. The crew was able to stop the aircraft and to evacuate the cabin. The left wing and wing root suffered fire damage.

Crash of a BAe 3103 Jetstream 31 in Los Roques

Date & Time: Feb 13, 2008 at 0920 LT
Type of aircraft:
Operator:
Registration:
YV186T
Survivors:
Yes
Schedule:
Porlamar - Los Roques
MSN:
616
YOM:
1983
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing at Los Roques Airport, the left main gear collapsed. The aircraft veered off runway to the left and came to rest on the edge of a lagoon. All 16 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the left main gear upon landing for unknown reasons.

Ground accident of a DC-9-31 in Caracas

Date & Time: Feb 12, 2008
Type of aircraft:
Operator:
Registration:
YV298T
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
48147/1048
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was on a post maintenance delivery mission. A crew of two engineers was positioning the aircraft from a technical hangar at Caracas-Maiquetía-Simón Bolívar Airport to the main terminal. While taxiing on the ramp, the crew lost control of the aircraft that rolled to a grassy area and eventually collided with a drainage ditch. The left main gear collapse and the left wing was severely damaged. Both crew were uninjured while the aircraft was damaged beyond repair.
Probable cause:
Loss of control for undetermined reasons.

Ground collision with a Fokker F27 in Edinburgh

Date & Time: Feb 2, 2008 at 2115 LT
Type of aircraft:
Operator:
Registration:
TC-MBG
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Edinburgh - Coventry
MSN:
10459
YOM:
1971
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4080
Captain / Total hours on type:
2745.00
Circumstances:
The aircraft was scheduled to operate a night cargo flight from Edinburgh to Coventry. The weather conditions at Edinburgh Airport were wintry with snowfall, which required the aircraft to be de-iced. Shortly after both engines had been started, the commander signalled to the marshaller to remove the Ground Power Unit (GPU) from the aircraft, which was facing nose out from its stand, down a slight slope. As the marshaller went to assist his colleague to remove the GPU to a safe distance prior to the aircraft taxiing off the stand, the aircraft started to move forward slowly, forcing them to run to safety. The flight crew, who were looking into the cockpit, were unaware that the aircraft was moving. It continued to move forward until its right propeller struck the GPU, causing substantial damage to the GPU, the propeller and the engine. The ground crew were uninjured. No cause as to why the aircraft moved could be positively identified.
Probable cause:
The aircraft moved forward inadvertently after engine start, causing its right propeller to strike a GPU. Possible explanations include that the parking brake was not set, the chocks had slipped from the nosewheel, or the chocks were removed prematurely. There was insufficient evidence to determine which of these scenarios was the most likely. Contributory factors were: the aircraft was facing down a slight downslope, the ramp was slippery due to the weather conditions and the flight crew increased engine speed to top up the pneumatic system pressure. The airport operator’s instructions contained in MDD 04/07 required aircraft facing nose-out on North Cargo Apron stands to be towed onto the taxiway centreline, prior to starting engines. Had these instructions been complied with, the accident would probably have been avoided.
Final Report:

Crash of a Britten-Norman BN-2A-26 Islander in Anguilla

Date & Time: Feb 2, 2008 at 1420 LT
Type of aircraft:
Operator:
Registration:
VP-AAG
Flight Type:
Survivors:
Yes
Schedule:
Anguilla - Sint Maarten
MSN:
88
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4217
Captain / Total hours on type:
693.00
Circumstances:
The commander intended to fly the BN-2 Islander aircraft from Anguilla Wallblake International Airport (AXA) to the neighbouring island of St Maarten (SXM) to await cargo inbound on another flight. The cabin of the aircraft was configured for cargo operations with no passenger seats fitted, as the only other planned occupant was the operator’s Chief Engineer, who would be sitting beside the commander in the right hand seat. However, the commander asked the operator if he could take a family member with him to SXM. The operator agreed and an extra seat was fitted. Witnesses stated that the commander appeared "rushed" prior to departure. The commander stated that he partially carried out the normal pre-flight inspection. He then started the engines. Before taxiing he realised that the nose landing gear chocks were still in place so he shut down the left hand engine, removed and stowed the chocks and then restarted the left engine. The aircraft took off from runway 10 at 14:15 hrs. At between 100 ft and 150 ft the commander initiated a left turn but after some initial movement the ailerons jammed. When he discovered that he was unable to straighten the ailerons he attempted to return to land on runway 10. The other flight controls did not appear to be restricted. With the ailerons jammed, the aircraft continued to turn to the left, losing altitude as it flew over a settlement to the north of the aerodrome, until pointed directly at the Air Traffic Control tower, causing the Air Traffic Control Officer (ATCO) to abandon the tower. The commander judged that the aircraft was too fast and high to attempt a landing and therefore initiated a go-around, applying full power. He continued the left turn, losing height and speed to position the aircraft for another approach but, as the aircraft descended over the northern edge of the runway, its left wing struck the perimeter fence. On impact the aircraft spun about its vertical axis with its wings level and continued sliding sideways on its right side for approximately 80 ft before coming to rest facing north-west.
Probable cause:
The commander was probably distracted from his normal duties whilst arranging additional seating to accommodate the second passenger. He did not complete the requisite pre-flight check or the subsequent check of full and free movement of the flight controls, either of which would have revealed an obstruction to proper operation of the ailerons.
Final Report:

Serious incident with a Boeing 747-2D7B in Lomé

Date & Time: Feb 2, 2008
Type of aircraft:
Operator:
Registration:
N527MC
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lomé - Amsterdam
MSN:
22471/504
YOM:
1981
Flight number:
GTI014
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after take off from Lomé international Airport, while on a cargo flight to Amsterdam, the crew declared an emergency and was cleared for an immediate return. The approach and landing were considered as normal and the aircraft returned safely to the apron. While all three crew members were uninjured, the aircraft was damaged beyond repair due to bulkhead destruction.
Probable cause:
It appears that the cargo shifted shortly after rotation and destroyed the bulkhead and several others structural parts inside the airplane.

Crash of a Cessna 525A CitationJet CJ1 in West Gardiner: 2 killed

Date & Time: Feb 1, 2008 at 1748 LT
Type of aircraft:
Registration:
N102PT
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Augusta - Lincoln
MSN:
525-0433
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3522
Aircraft flight hours:
1650
Aircraft flight cycles:
1700
Circumstances:
The instrument-rated private pilot departed on an instrument flight rules (IFR) cross-country flight plan in near-zero visibility with mist, light freezing rain, and moderate mixed and clear icing. After departure, and as the airplane entered a climbing right turn to a track of about 260 degrees, the pilot reported to air traffic control that she was at 1,000 feet, climbing to 10,000 feet. The flight remained on a track of about 260 degrees and continued to accelerate and climb for 38 seconds. The pilot then declared an emergency, stating that she had an attitude indicator failure. At that moment, radar data depicted the airplane at 3,500 feet and 267 knots. Thirteen seconds later, the pilot radioed she wasn't sure which way she was turning. The transmission ended abruptly. Radar data indicated that at the time the transmission ended the airplane was in a steep, rapidly descending left turn. The fragmented airplane wreckage, due to impact and subsequent explosive forces, was located in a wooded area about 6 miles south-southwest of the departure airport. Examination of the accident site revealed a near vertical high-speed impact consistent with an in-flight loss of control. The on-site examination of the airframe remnants did not show evidence of preimpact malfunction. Examination of recovered engine remnants revealed evidence that both engines were producing power at the time of impact and no preimpact malfunctions with the engines were noted. The failure, single or dual, of the attitude indicator is listed as an abnormal event in the manufacturer's Pilot's Abbreviated Emergency/Abnormal Procedures. The airplane was equipped with three different sources of attitude information: one incorporated in the primary flight display unit on the pilot's side, another single instrument on the copilot's side, and the standby attitude indicator. In the event of a dual failure, on both the pilot and copilot sides, aircraft control could be maintained by referencing to the standby attitude indicator, which is in plain view of the pilot. The indicators are powered by separate sources and, during the course of the investigation, no evidence was identified that indicated any systems, including those needed to maintain aircraft control, failed. The pilot called for a weather briefing while en route to the airport 30 minutes prior to departure and acknowledged the deteriorating weather during the briefing. Additionally, the pilot was eager to depart, as indicated by comments that she made before her departure that she was glad to be leaving and that she had to go. Witnesses indicated that as she was departing the airport she failed to activate taxi and runway lights, taxied on grass areas off taxiways, and announced incorrect taxi instructions and runways. Additionally, no Federal Aviation Administration authorization for the pilot to operate an aircraft between 29,000 feet and 41,000 feet could be found; the IFR flight plan was filed with an en route altitude of 38,000 feet. The fact that the airplane was operating at night in instrument meteorological conditions and the departure was an accelerating climbing turn, along with the pilot's demonstrated complacency, created an environment conducive to spatial disorientation. Given the altitude and speed of the airplane, the pilot would have only had seconds to identify, overcome, and respond to the effects of spatial disorientation.
Probable cause:
The pilot's spatial disorientation and subsequent failure to maintain airplane control.
Final Report:

Ground accident of a Rockwell Sabreliner 80 in Fort Lauderdale

Date & Time: Feb 1, 2008 at 1542 LT
Type of aircraft:
Operator:
Registration:
N3RP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Fort Lauderdale - Brooksville
MSN:
380-42
YOM:
1976
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8500
Captain / Total hours on type:
350.00
Copilot / Total flying hours:
14400
Copilot / Total hours on type:
360
Aircraft flight hours:
5825
Circumstances:
The Rockwell International Sabreliner had just been released from the repair station following several months of maintenance, primarily for structural corrosion control and repair. According to the pilots, they began to taxi away from the repair station. Initially, the brakes and steering were satisfactory, but then failed. The airplane then contacted several other airplanes and a tug with an airplane in tow, before coming to a stop. The airplane incurred substantial damage as a result of the multiple collisions. Neither crewmember heard or saw any annunciations to alert them to a hydraulic system problem. Postaccident examination revealed that there was no pressure in the normal hydraulic system, as expected, and that the auxiliary system pressure was adequate to facilitate emergency braking. Additional examination and testing revealed that the aural warning for low hydraulic system pressure was inoperative, but all other hydraulic, steering, and braking systems functioned properly. Both the pilot and copilot were type-rated in the Sabreliner, and each had approximately 350 hours of flight time in type. Neither crewmember had any time in Sabreliners in the 90 days prior to the accident. Operation of the emergency braking system in the airplane required switching the system on, waiting for system pressure to decrease to 1,700 pounds per square inch (psi), pulling the "T" handle, and then pumping the brake pedals 3 to 5 times. In addition, the system will not function if both the pilot's and copilot's brake pedals are depressed simultaneously. The investigation did not uncover any evidence to suggest the crew turned on the auxiliary hydraulic system, or waited for the system pressure to decrease to 1,700 psi in their attempt to use the emergency braking system.
Probable cause:
The depletion of pressure in the normal hydraulic system for an undetermined reason, and the pilots' failure to properly operate the emergency braking system. Contributing to the accident was an inoperative hydraulic system aural warning.
Final Report:

Crash of a Beechcraft C90A King Air in Mount Airy: 6 killed

Date & Time: Feb 1, 2008 at 1128 LT
Type of aircraft:
Registration:
N57WR
Flight Type:
Survivors:
No
Schedule:
Cedartown - Mount Airy
MSN:
LJ-1678
YOM:
2003
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
780
Aircraft flight hours:
800
Circumstances:
While flying a non precision approach, the pilot deliberately descended below the minimum descent altitude (MDA) and attempted to execute a circle to land below the published circling minimums instead of executing the published missed approach procedure. During the circle to land, visual contact with the airport environment was lost and engine power was never increased after the airplane had leveled off. The airplane decelerated and entered an aerodynamic stall, followed by an uncontrolled descent which continued until ground impact. Weather at the time consisted of rain, with ceilings ranging from 300 to 600 feet, and visibility remaining relatively constant at 2.5 miles in fog. Review of the cockpit voice recorder (CVR) audio revealed that the pilot had displayed some non professional behavior prior to initiating the approach. Also contained on the CVR were comments by the pilot indicating he planned to descend below the MDA prior to acquiring the airport visually, and would have to execute a circling approach. Moments after stating a circling approach would be needed, the pilot received a sink rate aural warning from the enhanced ground proximity warning system (EGPWS). After several seconds, a series of stall warnings was recorded prior to the airplane impacting terrain. EGPWS data revealed, the airplane had decelerated approximately 75 knots in the last 20 seconds of the flight. Examination of the wreckage did not reveal any preimpact failures or malfunctions with the airplane or any of its systems. Toxicology testing detected sertraline in the pilot’s kidney and liver. Sertraline is a prescription antidepressant medication used for anxiety, obsessive-compulsive disorder, panic disorder, posttraumatic stress disorder, and social phobia. The pilot’s personal medical records indicated that he had been treated previously with two other antidepressant medications for “anxiety and depression” and a history of “impatience” and “compulsiveness.” The records also documented a diagnosis of diabetes without any indication of medications for the condition, and further noted three episodes of kidney stones, most recently experiencing “severe and profound discomfort” from a kidney stone while flying in 2005. None of these conditions or medications had been noted by the pilot on prior applications for an airman medical certificate. It is not clear whether any of the pilot’s medical conditions could account for his behavior or may have contributed to the accident.
Probable cause:
The pilot's failure to maintain control of the airplane in instrument meteorological conditions. Contributing to the accident were the pilot's improper decision to descend below the minimum descent altitude, and failure to follow the published missed approach procedure.
Final Report: