Crash of an Embraer EMB-120ER Brasília in Rio Branco: 23 killed

Date & Time: Aug 30, 2002 at 1800 LT
Type of aircraft:
Operator:
Registration:
PT-WRQ
Survivors:
Yes
Schedule:
Cruzeiro do Sul – Tarauacá – Rio Branco
MSN:
120-043
YOM:
1987
Flight number:
RLE4823
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
23
Captain / Total flying hours:
9315
Captain / Total hours on type:
4560.00
Copilot / Total flying hours:
4242
Copilot / Total hours on type:
3585
Circumstances:
Following an uneventful flight from Tarauacá, the crew started the descent to Rio Branco-Presidente Médici Airport in limited visibility due to the night and rain falls. On final, the aircraft descended below the MDA and, at a speed of 130 knots, struck the ground and crashed in a field located 4 km short of runway 06. The aircraft was totally destroyed. Eight passengers were rescued while 23 other occupants were killed, among them the Brazilian politician Ildefonço Cardeiro.
Probable cause:
The exact cause of the accident could not be determined with certainty. However, it is believed that the accident was the consequence of a controlled flight into terrain after the crew continued the approach in poor weather conditions and descended below the MDA until the aircraft, in a flaps and gear down configuration, impacted ground. The following contributing factors were identified:
- A difference of 70 feet in the settings was noted between both pilot's altimeters,
- Poor crew coordination,
- Complacency on part of the flying crew caused several deviations from procedures during the approach,
- Lack of crew resources management,
- The crew failed to check the altitude during the final stage of the approach,
- Poor weather conditions.
Final Report:

Crash of a Learjet 25C in Lexington: 1 killed

Date & Time: Aug 30, 2002 at 1307 LT
Type of aircraft:
Registration:
N45CP
Flight Type:
Survivors:
Yes
Schedule:
Marco Island - Lexington
MSN:
25-073
YOM:
1972
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2681
Captain / Total hours on type:
436.00
Copilot / Total flying hours:
1363
Copilot / Total hours on type:
60
Aircraft flight hours:
7514
Circumstances:
Shortly before landing, the crew confirmed that the hydraulic and emergency air pressures were "good", and that the circuit breakers on the "right and left" were in. In addition, the first officer reported "arming one and two." The airplane landed 1,000 - 1,500 feet from the landing threshold of runway 04, which was 7,003 feet in length. The captain utilized aerodynamic braking during part of the landing roll. About 3 seconds after touchdown, the first officer stated, "they're not deployed, they're armed only." About 6 seconds after touchdown, there was an increase in engine rpm. Shortly after that, there was an expletive from the captain. One and a half seconds later, there was another expletive. Slightly less than 2 seconds later, the captain told the first officer to "brake me," and 2.7 seconds after that, stated "emergency brake." About 4 seconds later, there was a "clunk", followed by a decrease in engine rpm 1 second later. Immediately after that, the captain stated, "we're going off the end." The airplane subsequently dropped off an embankment at the end of the runway, impacted and descended through a localizer tower, then impacted the ground and slid across a highway. The airplane had been fitted with a conversion that included thrust reversers. An examination of the wreckage revealed that the thrust reversers were out of the stowed position, but not deployed. The drag chute was also not deployed. Brake calipers were tested with compressed air, and operated normally. Brake disc pads were measured, and found to be within limits. According to an excerpt from the conversion maintenance manual, reverser deployment was hydraulically actuated and electrically controlled. There was also an accumulator which allowed deploy/stow cycling in the event of hydraulic system failure. Interlocks were provided so that the reverser doors could not be deployed until the control panel ARM switch was on, the main throttle levers were in idle position, and the airplane was on the ground with the squat switches engaged. The previous crew reported no mechanical anomalies. Runway elevation rose by approximately 35 feet during the first 2/3 of its length, then decreased until it was 8 feet lower at its departure end. Winds were reported as being from 050 degrees true at 7 knots. At the airplane's projected landing weight, without the use of thrust reversers, the estimated landing distance was about 2,850 feet with the anti-skid operative, and 3,400 feet with the anti-skid inoperative.
Probable cause:
The captain's addition of forward thrust during the landing rollout, which resulted in a lack of braking effectiveness and a subsequent runway overrun. A factor was the captain's inability to deploy the thrust reversers for undetermined reasons.
Final Report:

Crash of a Fokker 100 in Campinas

Date & Time: Aug 30, 2002 at 1205 LT
Type of aircraft:
Operator:
Registration:
PT-MRL
Survivors:
Yes
Schedule:
Salvador – São Paulo
MSN:
11441
YOM:
1993
Flight number:
JJ3499
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Captain / Total hours on type:
3600.00
Copilot / Total flying hours:
4300
Copilot / Total hours on type:
145
Circumstances:
The aircraft departed Salvador-Deputado Luís Eduardo Magalhães Airport at 0846LT on a schedule service JJ3499 to São Paulo-Guarulhos Airport, carrying 33 passengers and five crew members. En route, while cruising at an altitude of 35,000 feet, the crew encountered technical problems with the primary hydraulic system. He contacted ATC and was cleared to divert to Campinas-Viracopos Airport for an emergency landing. On approach, the crew was unable to lower the undercarriage that remained blocked in their wheel well. The crew elected to lower the gear manually and several troubleshootings were unsuccessful. The decision was taken to complete a belly landing on runway 33. After touchdown, the aircraft slid for few dozen metres and eventually came to rest. All 38 occupants evacuated safely and the aircraft was damaged beyond repair. It was later transferred to the TAM Museum.
Probable cause:
A loss of hydraulic fluids occurred on a hose separating a fitting from a pump on the right engine, causing the malfunction of the primary hydraulic system and resulting in the degradation of the mechanical system of the landing gear control command.
Final Report:

Crash of a PZL-Mielec AN-28 in Ayan: 16 killed

Date & Time: Aug 29, 2002 at 1856 LT
Type of aircraft:
Operator:
Registration:
RA-28932
Survivors:
No
Schedule:
Khabarovsk – Poliny Osipenko – Ayan
MSN:
1AJ008-19
YOM:
1990
Flight number:
VTK359
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
16
Circumstances:
The aircraft was completing a flight from Khabarovsk to Ayan with an intermediate stop in Poliny Osipenko, carrying 14 passengers and two pilots. Before takeoff from Poliny Osipenko, the crew was informed about weather conditions at Ayan with a visibility up to 5 km. But while approaching the destination, the crew realized that weather conditions deteriorated rapidly with poor visibility due to low stratus and fog. The crew initiated the descent prematurely and after the first turn, the aircraft was already at an insufficient altitude of 800 metres instead of the required 950 metres. At a speed of 283 km/h, the aircraft descended too low and deviated to the right of the approach pattern by 2,3 km when it entered an area of low stratus at an altitude of 320 metres. In a visibility reduced to 50 metres, the crew lost visual contact with the ground but the captain decided to continue the approach. At a height of 188 metres, the aircraft impacted a hill (226 metres high) located near the shore of the Okhotsk Sea. The aircraft was destroyed by impact forces and a post crash fire and all 16 occupants were killed.
Probable cause:
Controlled flight into terrain following after the crew initiated the descent prematurely and failed to follow the published procedures. The following contributing factors were identified:
- The approach was continued in below minima weather conditions,
- Failure of the crew to get a current weather report for Ayan and the alternate airport,
- The decision of the captain to continue the approach at decision height without any visual contact with the ground and his failure to initiate a go-around procedure,
- Failure of the crew to follow the established approach pattern,
- Failure of the meteorological observer to issue updated weather bulletin,
- Absence of radio navigational aids at Ayan Airport,
- Lack of interaction between ATC and meteorological observer at Ayan Airport when aircraft are approaching in adverse weather conditions.

Crash of an Airbus A320-231 in Phoenix

Date & Time: Aug 28, 2002 at 1843 LT
Type of aircraft:
Operator:
Registration:
N635AW
Survivors:
Yes
Schedule:
Houston - Phoenix
MSN:
092
YOM:
1990
Flight number:
AWE794
Crew on board:
5
Crew fatalities:
Pax on board:
154
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19500
Captain / Total hours on type:
7000.00
Copilot / Total flying hours:
11000
Copilot / Total hours on type:
800
Aircraft flight hours:
40084
Aircraft flight cycles:
18530
Circumstances:
After an asymmetrical deployment of the thrust reversers during landing rollout deceleration, the captain failed to maintain directional control of the airplane and it veered off the runway, collapsing the nose gear and damaging the forward fuselage. Several days before the flight the #1 thrust reverser had been rendered inoperative and mechanically locked in the stowed position by maintenance personnel. In accordance with approved minimum equipment list (MEL) procedures, the airplane was allowed to continue in service with a conspicuous placard noting the inoperative status of the #1 reverser placed next to the engine's thrust lever. When this crew picked up the airplane at the departure airport, the inbound crew briefed the captain on the status of the #1 thrust reverser. The captain was the flying pilot for this leg of the flight and the airplane touched down on the centerline of the runway about 1,200 feet beyond its threshold. The captain moved both thrust levers into the reverse position and the airplane began yawing right. In an effort at maintaining directional control, the captain then moved the #1 thrust lever out of reverse and inadvertently moved it to the Take-Off/Go-Around (TOGA) position, while leaving the #2 thrust lever in the full reverse position. The thrust asymmetry created by the left engine at TOGA power with the right engine in full reverse greatly increased the right yaw forces, and they were not adequately compensated for by the crew's application of rudder and brake inputs. Upon veering off the side of the runway onto the dirt infield, the nose gear strut collapsed. The airplane slid to a stop in a nose down pitch attitude, about 7,650 feet from the threshold. There was no fire. Company procedures required the flying pilot (the captain) to give an approach and landing briefing to the non flying pilot (first officer). The captain did not brief the first officer regarding the thrust reverser's MEL'd status, nor was he specifically required to do so by the company operations manual. Also, the first officer did not remind the captain of its status, nor was there a specific requirement to do so. The operations manual did state that the approach briefing should include, among other things, "the landing flap setting...target airspeed...autobrake level (if desired) consistent with runway length, desired stopping distance, and any special problems." The airline's crew resource management procedures tasked the non flying pilot to be supportive of the flying pilot and backup his performance if pertinent items were omitted from the approach briefing. The maintenance, repair history, and functionality of various components associated with the airplane's directional control systems were evaluated, including the brake system, the nose landing gear strut and wheels, the brakes, the antiskid system, the thrust levers and reversers, and the throttle control unit. No discrepancies were found regarding these components.
Probable cause:
The captain's failure to maintain directional control and his inadvertent application of asymmetrical engine thrust while attempting to move the #1 thrust lever out of reverse. A factor in the accident was the crew's inadequate coordination and crew resource management.
Final Report:

Crash of a Douglas C-54E-15-DO Skymaster in Diavik

Date & Time: Aug 28, 2002 at 1650 LT
Type of aircraft:
Operator:
Registration:
C-GQIC
Flight Type:
Survivors:
Yes
Schedule:
Yellowknife – Diavik
MSN:
27343
YOM:
1944
Flight number:
BFL928
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Diavik Airport, the four engine aircraft was too low. This caused the undercarriage to struck the ground about one metre short of runway 10 threshold. On impact, the undercarriage were torn off and the aircraft slid on the runway for almost 300 metres then lost its right wing and rotated to the right before coming to rest, bursting into flames. Both pilots escaped with minor injuries and the aircraft was destroyed.

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

Date & Time: Aug 26, 2002
Type of aircraft:
Operator:
Registration:
RA-33501
Flight Phase:
Survivors:
Yes
MSN:
1G228-53
YOM:
1988
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was forced to make an emergency landing at Kashtak Airfield near Chita. There were no casualties but the aircraft was damaged beyond repair.

Crash of a Shaanxi Y-8B in Colombo: 5 killed

Date & Time: Aug 15, 2002 at 1235 LT
Type of aircraft:
Operator:
Registration:
CR-873
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Colombo - Colombo
MSN:
07 08 02
YOM:
1993
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The crew departed Colombo-Ratmalana Airport for a local post maintenance test flight as one of the engine has been changed. During climbout, an engine caught fire. The crew was cleared to return for an emergency landing when the engine exploded and separated from the aircraft. Out of control, the airplane crashed in an open field, bursting into flames. All five crew members were killed. It was reported that the engine that caught fire was not the one that has been changed.
Probable cause:
Engine fire and explosion for unknown reasons.

Ground accident of an Embraer EMB-120RT Brasília in Manaus

Date & Time: Aug 13, 2002 at 1225 LT
Type of aircraft:
Operator:
Registration:
PT-WGE
Flight Phase:
Survivors:
Yes
Schedule:
Humaitá – Manaus
MSN:
120-004
YOM:
1986
Flight number:
RLE4847
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13474
Captain / Total hours on type:
518.00
Copilot / Total flying hours:
4110
Copilot / Total hours on type:
3660
Aircraft flight hours:
26756
Circumstances:
Following an uneventful flight from Humaitá, the crew completed the landing at Manaus-Eduardo Gomes Airport. After taxi, the crew was approaching the apron when he feathered the propellers and applied the brakes as they wanted to stop the aircraft. There was no deceleration despite both crew applied brakes. The copilot suggested to use reverse thrust but this was not possible as the propellers were already feathered. Out of control, the aircraft struck a brick building, damaging the left engine, and the right landing gear fell into a drainage ditch, approximately one meter deep. All 25 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The following factors were identified:
- The crew did not have sufficient training to enable the desired assertiveness for the correct use of aircraft resources, which would probably have prevented the accident, since, instead of applying the emergency brake, they applied reverse with the feathered props, contrary to the procedure provided for in the Aircraft Manual.
- The maintenance services were not efficient, as they did not comply with the Aircraft Maintenance Manual in relation to the dimensional adjustment of the Hub Cap Drive Clips' drive clips, and the Service Bulletin incorporated stickers to the outer doors of the main landing gear, as a reminder to the mechanic to check the clearances.
- The copilot failed to apply the reverse pitch on the propellers as they were feathered, and at that moment the emergency brake should be commanded to brake the aircraft.
- The company failed to adequately check the execution of the actions provided for in the Aircraft Maintenance Manual regarding the 'Antiskid' system and to verify the application of all service bulletins issued by the manufacturer.
Final Report:

Crash of a Cessna 550 Citation S/II in Big Bear Lake

Date & Time: Aug 13, 2002 at 1120 LT
Type of aircraft:
Registration:
N50BK
Survivors:
Yes
Schedule:
Las Vegas – Big Bear Lake
MSN:
550-0031
YOM:
1985
Flight number:
CFI850
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3900
Captain / Total hours on type:
800.00
Copilot / Total flying hours:
2800
Aircraft flight hours:
5776
Circumstances:
On a final approach to runway 26 the flight crew was advised by a flight instructor in the traffic pattern that a wind shear condition existed about one-quarter of the way down the approach end of the runway, which the flight crew acknowledged. On a three mile final approach the flight crew was advised by the instructor that the automated weather observation system (AWOS) was reporting the winds were 060 degrees at 8 knots, and that he was changing runways to runway 08. The flight crew did not acknowledge this transmission. The captain said that after landing smoothly in the touchdown zone on Runway 26, he applied normal braking without any response. He maintained brake pedal pressure and activated the engine thrust reversers without any response. The copilot said he considered the approach normal and that the captain did all he could to stop the airplane, first applying the brakes and then pulling up on the thrust reversers twice, with no sensation of slowing at all. Considering the double malfunction and the mountainous terrain surrounding the airport, the captain elected not to go around. The aircraft subsequently overran the end of the 5,860 foot runway (5,260 feet usable due to the 600 displaced threshold), went through the airport boundary fence, across the perimeter road, and came to rest upright in a dry lakebed approximately 400 feet from the departure end of the runway. With the aircraft on fire, the five passengers and two crew members safely egressed the aircraft without injuries before it was consumed. Witnesses to the landing reported the aircraft touched down at midfield, was too fast, porpoised, and was bouncing trying to get the gear on the runway. Passengers recalled a very hard landing, being thrown about the cabin, and that the speed was excessive. One passenger stated there was a hard bang and a series of smaller bangs during the landing. Federal Aviation Regulations allowed 3,150 feet of runway for a full stop landing. Under the weather conditions reported just after the mishap, and using the anticipated landing weight from the load manifest (12,172.5 pounds), the FAA approved Cessna Flight Manual does not provide landing distance information. Post-accident examination and testing of various wheel brake and antiskid/power brake components revealed no anomalies which would have precluded normal operations.
Probable cause:
The pilot's failure to obtain the proper touchdown point which resulted in an overrun. Contributing factors were the pilot's improper in-flight planning, improper use of performance data, the tailwind condition, failure to perform a go-around, and the pilot-induced porpoising condition.
Final Report: