Crash of an Airbus A320-233 in Tegucigalpa: 5 killed

Date & Time: May 30, 2008 at 0940 LT
Type of aircraft:
Operator:
Registration:
EI-TAF
Survivors:
Yes
Schedule:
San Salvador – Tegucigalpa – Miami
MSN:
1374
YOM:
2000
Flight number:
TA390
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
118
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
11899
Captain / Total hours on type:
8514.00
Copilot / Total flying hours:
1607
Copilot / Total hours on type:
250
Aircraft flight hours:
21957
Aircraft flight cycles:
9992
Circumstances:
A TACA Airlines Airbus A320, flight TA390, with Irish Registry EI-TAF, with 135 passengers and crew on board, overran at the end of the runway during landing at Tegucigalpa caused the deaths of three people on board and two on the ground. The government of Honduras delegated the conduct of investigation to the Salvadoran Civil Aviation Authorities, as provided for in Annex 13 to the Chicago Convention. In accordance with international agreements, France sent two investigators from the BEA (Bureau d'Enquêtes et d'Analyses), accompanied by five technical advisors from Airbus; United States sent two investigators from the NTSB (National Transportation Safety Board), accompanied by one advisor from FAA (Federal Aviation Administration) and one technical Advisor from IAE (International Aero Engine); and Ireland sent one investigator. Both flight recorders (CVR and DFDR) were recovered and taken to the NTSB in order to perform the read out. The following data result from the analysis done by the BEA and Airbus of the accident recorders, which have been processed within the NTSB facilities under the leadership of the in-charge Authorities. It is confirmed that the aircraft was dispatched without any deferred MEL item. Prior to landing, the wind information given by the ATC to the crew was 190°/10kt and ATC also confirmed that the runway was wet. The Captain was the Pilot Flying (PF). Landing configuration was established with Slats/Flaps fully extended, gear down, ground spoilers armed, autobrake selected to MED. The aircraft landing weight was 63.5t (max landing weight 64.5t), Vapp 137kt. The aircraft was cleared to land on runway 02 and landed with Autopilot and Flight Directors OFF, and autothrust engaged in managed speed mode. At time of touch down, IAS was 139kt and Ground Speed (GS) was 159kt (estimated tailwind was 12kt from DFDR data analysis). The aircraft landed on runway 02 (Runway 02 is 3297 feet high and has a displaced threshold of 213m). The Landing Distance Available (LDA) for runway 02 is of 1649m. The touch down occurred at approximately 400m from the runway 02 displaced threshold. Immediately after touchdown, the crew selected MAX REV, and both engine reversers and the Ground Spoilers (G/S) deployed normally. The nosewheel touch down occurred 7s after the Main Landing Gear (MLG) following PF inputs. The crew applied manual braking 4s after MLG touch down and commanded maximum pedal braking in 10s (14s after MLG touch down). At 70 knots Indicated Airspeed Speed (IAS), upon Pilot Non Flying (PNF) call-out, the PF selected IDLE REV. The remaining distance to the runway end was approximately 190m. The aircraft overran the runway at 54kt and dropped down the 20 m embankment sustaining severe damage on impact with the ground. The landing performance analysis confirms that the landing performances are consistent with runway condition and crew actions.
Probable cause:
Contributing factors:
- Wrong approach configuration,
- Excessive speed upon landing,
- The aircraft landed too far down the runway with a tailwind component,
- On approach, the crew failed to recalculate the aircraft weight for landing and the landing distance,
- The non precision approach was completed in poor weather conditions, which increased the cockpit crew workload,
- The absence of a stopping zone at the end of runway 02 contributed to the severity of the occurrence,
- The runway surface was wet and not equipped with a water drainage system, which reduced the braking coefficient.
Final Report:

Crash of an Antonov AN-32B in Goma

Date & Time: May 26, 2008 at 1500 LT
Type of aircraft:
Registration:
9Q-CMG
Flight Type:
Survivors:
Yes
Schedule:
Goma – Kalima
MSN:
32 01
YOM:
1993
Location:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Few minutes after takeoff from Goma Airport, en route to Kalima, the crew reported engine problems and was cleared to return for an emergency landing. After touchdown, control was lost. The aircraft veered off runway to the right and collided with lava blocs. The aircraft was destroyed and all five occupants were injured.

Crash of a Boeing 747-209F in Brussels

Date & Time: May 25, 2008 at 1331 LT
Type of aircraft:
Operator:
Registration:
N704CK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
New York – Brussels – Bahrain
MSN:
22299/462
YOM:
1980
Flight number:
CKS207
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15000
Captain / Total hours on type:
3000.00
Copilot / Total flying hours:
7000
Copilot / Total hours on type:
200
Aircraft flight hours:
108560
Aircraft flight cycles:
20599
Circumstances:
The flight crew arrived at Brussels the day before the accident, with a flight from Bahrain. The crew rested until the Sunday morning. The aircraft arrived at Brussels on Sunday with another crew; the two crews exchanged some information regarding the airplane. There were no mechanical problems reported. Runway 20 was in service for take-offs, while Runway 25L was mostly used for landings. The pilot performed the pre-flight inspection; he found only minor discrepancies (left inner tire check and E&E door latch down). The pre-flight briefing covered the standard departure call-outs, the runway incursion information, a discussion on the Runway 20 length, etc.. The crew also briefed about the engine failure procedures for an engine failure prior to V1, and they also briefed about an abort takeoff after V1 if there was a dangerous situation that would not allow the airplane to fly. After completing the flight documents, the crew requested an early departure, which they received. For the computation of the take-off parameters, the crew used the Kalitta Air On-board Performance System (OPS computer). The crew determined they needed the full length of the runway for take-off. The airplane taxied towards the B1 intersection for the Runway 20. After a few minutes, waiting for another airplane to land on Runway 25, they lined up on Runway 20, making a tight turn, in order to gain a few meters with respect to the usual departure position. The airplane was cleared for take-off at 11:29. The pilot pushed the throttles forward and checked the engines were stable. The Flight Engineers then set the engine power for take-off (setting “normal”, also known as “reduced thrust”). The aircraft started to accelerate. The standard call-out were made when the speed reached the determined value.
- “airspeed”
- 80 knots
- V1
A few seconds after reaching V1, the engine N°3 ingested a bird. Approximately 5 seconds after V1, the engine N°3 stalled and caused a loud “bang”, and a vibration felt in the cockpit. The pilot stated he had the feeling that the aircraft was no longer accelerating, and decided to abort the take-off. Two seconds after having heard the detonation, the thrust levers were brought back to idle, and braking action was initiated. The thrust reversers were not deployed. The FO called the tower, and notified the aircraft was going to the overrun. The pilot turned the aircraft a few degrees to the right, in order to avoid the approach lights at the end of the runway. The aircraft left the runway at a speed of approximately 72 Knots. The aircraft reached a first embankment, dropping from a height of 4 m, and broke in three parts. The aircraft came to a stop just above the top of the railroad embankment. The crew exited the airplane through the service door since the L1 door normally used was blocked due to deformation of the structure.
Probable cause:
The accident was caused by the decision to reject the takeoff 12 knots after passing V1 speed. The following factors contributed to the accident:
- Engine Nr 3 experienced a bird strike, causing it to stall. This phenomenon was accompanied by a loud bang, noticed by the crew.
- The aircraft line up at the B1 intersection although the take-off parameters were computed with the full length of the runway.
- The situational awareness of the crew,
- Less than maximum use of deceleration devices.
- Although the RESA conforms to the minimum ICAO requirement, it does not conform to the ICAO recommendation for length.
Final Report:

Crash of a Beechcraft 1900C in Billings: 1 killed

Date & Time: May 23, 2008 at 0124 LT
Type of aircraft:
Operator:
Registration:
N195GA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Billings - Great Falls
MSN:
UB-65
YOM:
1986
Flight number:
AIP5008
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4770
Captain / Total hours on type:
362.00
Aircraft flight hours:
34651
Circumstances:
About one minute after takeoff on a night Instrument Flight Rules (IFR) contract cargo flight, the tower controller advised the pilot that he was squawking the wrong transponder code. Although the pilot reset the transponder to the correct code, he was advised that he was still squawking the wrong code. He then realized that he had selected the wrong transponder, and then switched to the correct one. During the time the pilot was dealing with this issue, the airplane drifted about 30 degrees right of the assigned heading, but the pilot returned to the correct heading as he was contacting the departure controller. The departure controller cleared him to continue his climb and instructed him to turn left about 120 degrees, which he did. About 40 seconds after initiating his left turn of about 120 degrees, while climbing straight ahead through an altitude about 4,700 feet above ground level (AGL), the pilot was instructed to turn 20 degrees further left. Almost immediately thereafter, the airplane began turning to the right, and then suddenly entered a rapidly descending right turn. The airplane ultimately impacted the terrain in a nearly wings-level nose-down attitude of greater than 45 degrees. At the moment of impact the airplane was on a heading about 220 degrees to the right of the its last stabilized course. The investigation did not find any indication of an airframe, control system, or engine mechanical failure or malfunction that would have precluded normal flight, and no autopsy or toxicological information could be acquired due to the high amount of energy that was released when the airplane impacted the terrain. The determination of the initiating event that led to the uncontrolled descent into the terrain was not able to be determined.
Probable cause:
The pilot's failure to maintain aircraft control during the initial climb for undetermined reasons.
Final Report:

Crash of Beechcraft T-1A Jayhawk in Lubbock

Date & Time: May 21, 2008 at 2144 LT
Type of aircraft:
Operator:
Registration:
93-0633
Flight Type:
Survivors:
Yes
Schedule:
Lubbock - Lubbock
MSN:
TT-90
YOM:
1993
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a night training flight on behalf of the U.S. Air Force 86th Flying Training Squadron, 47th Flying Training Wing, Laughlin Air Force Base, Texas. After several manoeuvres in the vicinity of the Lubbock-Preston Smith Airport, the crew started an non precision approach to runway 17R. At that time, weather conditions were not so good with rain showers and winds up to 40 knots. On final approach, the aircraft seems to sink and pitched down. The captain increased both engines power but the aircraft hit the ground 1,1 mile short of runway 17R threshold. On impact, the nose gear was sheared off and the aircraft came to rest in a field. Both pilots were slightly injured while the aircraft was damaged beyond repair.
Probable cause:
Conjunction of poor weather conditions and crew errors. The aircraft encountered windshear with downburst on descent and the crew ignored warnings. The combination of the following human factors placed the aircraft in a dangerous weather environment: poor mission planning, inattention, complacency, lack of procedural knowledge and restricted vision.

Crash of a Cessna 208B Super Cargomaster in Ada

Date & Time: May 9, 2008 at 2045 LT
Type of aircraft:
Operator:
Registration:
N893FE
Flight Type:
Survivors:
Yes
Schedule:
Traverse City - Grand Rapids
MSN:
208B-0223
YOM:
1990
Flight number:
FDX7343
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5600
Captain / Total hours on type:
3450.00
Aircraft flight hours:
8625
Circumstances:
The airplane was on a visual approach to an airport when the engine stopped producing power. The pilot subsequently landed the airplane in a field, but struck trees at the edge of the field during the forced landing. Examination of the engine, engine fuel controls, and Power Analyzer and Recorder (PAR), provided evidence that the engine shut down during the flight. Further examination of engine and fuel system components from the accident airplane failed to reveal a definitive reason for the uncommanded engine shut-down.
Probable cause:
A loss of engine power for undetermined reasons.
Final Report:

Crash of A Piper PA-31-350 in Winterveld

Date & Time: May 7, 2008
Registration:
ZS-KKR
Flight Type:
Survivors:
Yes
MSN:
31-8052183
YOM:
1980
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing in Winterveld, the aircraft (a Panther III version) hit a rock on the ground. On impact, the right main gear was torn off. The aircraft veered to the right and came to rest with its right wing severely damaged. Nobody was injured but the aircraft was damaged beyond repair.
Probable cause:
Hit a rock on the ground after landing.

Crash of a Cessna 208B Grand Caravan in Doro

Date & Time: Apr 28, 2008 at 1240 LT
Type of aircraft:
Operator:
Registration:
5Y-SPK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Doro - Nairobi
MSN:
208B-0243
YOM:
1990
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single aircraft was on a return flight from Doro to Nairobi, carrying four mission personnel who took part to a humanitarian mission in the region of Doro. The takeoff was performed from a muddy airstrip and the aircraft was unable to gain sufficient height after liftoff. As a result, the left wing impacted a tree trunk and the airplane crashed in a ditch, coming to rest upside down. All five occupants escaped uninjured.

Crash of a Piper PA-31T Cheyenne II in Foremost

Date & Time: Apr 25, 2008 at 1430 LT
Type of aircraft:
Operator:
Registration:
C-FRJE
Flight Type:
Survivors:
Yes
MSN:
31-7820002
YOM:
1978
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft made a wheels-up landing at Foremost Airport. The pilot, sole on board, was uninjured while the aircraft was damaged beyond repair. For unknown reasons, the landing gear had not been extended on approach.

Crash of a Cessna 421A Golden Eagle I in Saltillo

Date & Time: Apr 25, 2008 at 1200 LT
Type of aircraft:
Registration:
XB-WUF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Saltillo – Aguascalientes
MSN:
421A-0124
YOM:
1968
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Saltillo-Plan de Guadalupe Airport, while in initial climb, one of the engine caught fire. The pilot attempted an emergency landing when the aircraft crash landed in a field past the runway end, bursting into flames. All six occupants escaped with minor injuries and the aircraft was destroyed.
Probable cause:
Engine fire for unknown reasons.