Country

Crash of an Airbus A300B4-230F in Recife

Date & Time: Oct 21, 2016 at 0630 LT
Type of aircraft:
Operator:
Registration:
PR-STN
Flight Type:
Survivors:
Yes
Schedule:
São Paulo – Recife
MSN:
236
YOM:
1983
Flight number:
STR9302
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11180
Captain / Total hours on type:
3000.00
Copilot / Total flying hours:
7300
Copilot / Total hours on type:
800
Circumstances:
Following an uneventful cargo service from São Paulo-Guarulhos Airport, the crew initiated the descent to Recife-Guararapes Airport. On final approach to runway 18, after the aircraft had been configured for landing, at an altitude of 500 feet, the crew was cleared to land. After touchdown, the thrust lever for the left engine was pushed to maximum takeoff power while the thrust lever for the right engine was simultaneously brang to the idle position then to reverse. This asymetric configuration caused the aircraft to veer to the right and control was lost. The airplane veered off runway to the right and, while contacting soft grounf, the nose gear collapsed. The airplane came to rest to the right of the runway and was damaged beyond repair. All four occupants evacuated safely.
Probable cause:
Contributing factors.
- Control skills - undetermined
Inadequate use of aircraft controls, particularly as regards the mode of operation of the Autothrottle in use and the non-reduction of the IDLE power levers at touch down, may have led to a conflict between pilots when performing the landing and the automation logic active during approach. In addition, the use of only one reverse (on the right engine) and placing the left throttle lever at maximum takeoff power resulted in an asymmetric thrust that contributed to the loss of control on the ground.
- Attitude - undetermined
The adoption of practices different from the aircraft manual denoted an attitude of noncompliance with the procedures provided, which contributed to put the equipment in an unexpected condition: non-automatic opening of ground spoilers and asymmetric thrust of the engines. These factors required additional pilot intervention (hand control), which may have made it difficult to manage the circumstances that followed the touch and led to the runway excursion.
- Crew Resource Management - a contributor
The involvement of the PM in commanding the aircraft during the events leading up to the runway excursion to the detriment of its primary responsibility, which would be to monitor systems and assist the PF in conducting the flight, characterized an inefficiency in harnessing the human resources available for the airplane operation. Thus, the improper management of the tasks assigned to each crewmember and the non-observance of the CRM principles delayed the identification of the root cause of the aircraft abnormal behavior.
- Organizational culture - a contributor
The reliance on the crew's technical capacity, based on their previous aviation experience, has fostered an informal organizational environment. This informality contributed to the adoption of practices that differed from the anticipated procedures regarding the management and operation of the aircraft. This not compliance with the procedures highlights a lack of safety culture, as lessons learnt from previous similar accidents (such as those in Irkutsk and Congonhas involving landing using only one reverse and pushing the thrust levers forward), have apparently not been taken into account at the airline level.
- Piloting judgment - undetermined
The habit of not reducing the throttle lever to the IDLE position when passing at 20ft diverged from the procedures contained in the aircraft-operating manual and prevented the automatic opening of ground spoilers. It is possible that the consequences of this adaptation of the procedure related to the operation of the airplane were not adequately evaluated, which made it difficult to understand and manage the condition experienced.
- Perception - a contributor
Failure to perceive the position of the left lever denoted a lowering of the crew's situational awareness, as it apparently only realized the real cause of the aircraft yaw when the runway excursion was already underway.
- Decision-making process - a contributor
An inaccurate assessment of the causes that would justify the behavior of the aircraft during the landing resulted in a delay in the application of the necessary power reduction procedure, that is, repositioning the left engine power lever.
Final Report:

Crash of an Airbus A300B4-203F in Afgooye

Date & Time: Oct 12, 2015 at 1930 LT
Type of aircraft:
Operator:
Registration:
SU-BMZ
Flight Type:
Survivors:
Yes
Schedule:
Oostend – Cairo – Mogadishu
MSN:
129
YOM:
1980
Flight number:
TSY810
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a cargo flight from Ostend to Mogadishu with an intermediate stop in Cairo with perishable goods on board on behalf of the AMISOM, the African Mission in Somalia. The final approach to Mogadishu-Aden Abdulle International Airport was performed by night. As the crew was unable to localize the runway, he abandoned the approach and initiated a go-around procedure. A second attempt was also interrupted and the crew initiated a new go-around then continued towards the north of the capital city. Eventually, the captain decided to attempt an emergency belly landing near Afgooye, about 25 km northwest of Mogadishu. Upon landing, the aircraft lost its both engines and came to rest in the bush. Two crew members were taken to hospital while four others were uninjured. The aircraft was damaged beyond repair. According to Somalian Authorities, the International Airport of Mogadishu is open to traffic from 0600LT till 1800LT. For undetermined reason, the crew started the descent while the airport was already closed to all traffic (sunset at 1747LT). Also, an emergency landing was unavoidable, probably due to a fuel exhaustion. It is unknown why the crew did not divert to the alternate airport.
Probable cause:
When the controller received the estimated time of arrival for TSY810 from the Flight Information Center (FIC) Nairobi he advised FIC Nairobi (Kenya) that Mogadishu Airport was closed at the estimated time of arrival and advised the crew should divert to their alternate aerodrome but received no feedback. At 14:45Z the tower received first communication from the crew advising they would be overhead the aerodrome at 15:02Z, the controller advised again that the aerodrome would already be closed by then, the crew insisted however that they would land. Tower provided the necessary landing information like weather and active runway. At 15:02Z there was no sight of the aircraft, tower queried with the crew who reported still being 54nm out and revised their estimated time of arrival. At 15:27Z the aircraft turned final for runway 05, tower advised the crew to land at own discretion as tower's "instructions were only advisory and not clearance". The controller added that the approach was aborted and all subsequent approaches were unsuccessful too. "At one point the pilot mistook street parallel to the runway lighted by flood lights with intention of landing but was alerted the runway was on his right and the approach was discontinued. The crew has been warned numerous times that Mogadishu Airport closed at 1800LT (1500Z) and there is no adequate runway lights as the airport is not prepared to receive flights during night time hours. Thus, the pilot has intentionally tried to land at the airport while the visibility was limited to few metres due to darkness.
Final Report:

Crash of an Airbus A300B4-203F in Bratislava

Date & Time: Nov 16, 2012 at 0525 LT
Type of aircraft:
Operator:
Registration:
EI-EAC
Flight Type:
Survivors:
Yes
Schedule:
Leipzig - Bratislava
MSN:
250
YOM:
1983
Flight number:
DHL6321
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew took off from Leipzig Airport at 0438LT bound for Bratislava Airport (Slovakia). The approximately forty-five minutes flight took place without incident and the crew was cleared for the ILS approach to runway 22. The Captain was PF. During the descent, the controller informed the crew that the wind was from  120° at  7  kt. The crew selected the slats and flaps at 25°. The antiskid and the autobrake were armed in MED mode. The ILS 22 approach was stable until the wheels touched down. The main landing gear touched the runway about 700 m from the threshold of runway  22. The crew deployed the thrust reversers. About six seconds after the nose gear touched, the crew felt strong vibrations that increased as the speed dropped. At 85 kt, the thrust reversers were retracted. The aeroplane veered towards the left. The PF explained that he applied energetic braking and tried in vain to counter the rocking by using the rudder pedals then the nose gear steering control. He  added that the sequence occurred so quickly that he did not think to use differential braking to try to keep the aeroplane on the runway. The aeroplane exited the runway to the left at a speed of about 45 kt. Its nose gear struck a concrete inspection pit and collapsed. The aeroplane skidded for a few dozen metres before coming to a stop. The crew evacuated the aeroplane. Between the start of the vibrations and the aeroplane stopping, it had rolled about 400 metres.
Probable cause:
Incorrect installation of one or more washers on the nose gear torque link centre hinge made it impossible to lock the hinge shaft nut effectively. The unscrewing and the detachment of the latter in service caused the loss of nose gear steering. Free on its axle, the nose gear bogie began to shimmy, which made the aeroplane veer to the left. The aeroplane exited the runway and the nose gear collapsed during the collision with a concrete inspection pit for access to the runway lighting electric cables.The runway excursion was due to the incorrect and undetected re-assembly of the nose gear torque links. Despite the presence of a detailed diagram, the absence of clear and detailed instructions in the text of the manufacturer’s AMM, allowing the operator to ensure that the assembly was correct, contributed to the incorrect assembly. The failure of the nose gear was due to the collision with an obstacle in the runway  strip. The absence of any regulation requiring that equipment in the immediate vicinity of a runway or of a runway overrun area be designed so as to limit as much as possible any damage to aeroplanes, in case of a runway excursion, contributed to the accident.
Final Report:

Crash of an Airbus A300B4-203F in Monterrey: 6 killed

Date & Time: Apr 13, 2010 at 2319 LT
Type of aircraft:
Operator:
Registration:
XA-TUE
Flight Type:
Survivors:
No
Schedule:
Mexico City - Monterrey - Los Angeles
MSN:
78
YOM:
1979
Flight number:
TNO302
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
16754
Captain / Total hours on type:
5446.00
Copilot / Total flying hours:
3114
Copilot / Total hours on type:
1994
Aircraft flight hours:
55170
Circumstances:
The aircraft departed Mexico City-Benito Juarez Airport on a cargo service to Los Angeles with an intermediate stop in Monterrey, carrying five crew members. On final approach to Monterrey-General Mariano Escobedo Airport by night, the crew encountered poor weather conditions with CB's and sky broken at 600 feet. On short final, while at a distance of 2 km from the runway threshold, the crew was cleared to land on runway 11. Shortly later, the aircraft rolled to the left then crashed on a motorway located 700 metres short of runway. The aircraft was totally destroyed and all five crew members were killed as well as one people in a car.
Probable cause:
The accident was the consequence of a loss of control following an unstable approach.
The following contributing factors were identified:
- Lack of crew coordination and crew resources management (CRM),
- Diminished situational awareness,
- Failure to follow proper operational procedures,
- Unstabilized non-precision approach,
- Unsuitable aircraft configuration,
- Adverse weather condition.
Final Report:

Crash of an Airbus A300B4-203F at Bagram AFB

Date & Time: Mar 1, 2010 at 1210 LT
Type of aircraft:
Operator:
Registration:
TC-ACB
Flight Type:
Survivors:
Yes
Schedule:
Bahrain - Bagram AFB
MSN:
121
YOM:
1980
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12923
Captain / Total hours on type:
8000.00
Aircraft flight hours:
25300
Aircraft flight cycles:
46516
Circumstances:
While approaching Bagram AFB, the crew did not obtain the three green lights when the undercarriage were lowered. The left main gear signal appears to remain red. The captain obtained the authorization to make two low passes over the airport then ATC confirmed that all three gears were down. The final approach was completed at low speed and after touchdown, while braking, the left main gear collapsed. The aircraft veered off runway to the left and came to rest some 2 km past the runway threshold. All five crewmen were unhurt while the aircraft was damaged beyond repair.
Probable cause:
Cracks as result of fatigue caused the fracture of the hinge arm of the left main gear strut. The cracking most likely occurred as result of corrosion that remained undetected during the last maintenance inspection. The origin of pitting could not be identified, the investigation however identified deficiencies in the maintenance task conducted during last overhaul of the gear strut. Incomplete maintenance documentation and tools available during overhaul contributed to the accident.
Final Report: