Crash of a Beechcraft C90B King Air in Kiev: 5 killed

Date & Time: Dec 9, 2007 at 1759 LT
Type of aircraft:
Operator:
Registration:
D-IBDH
Survivors:
No
Schedule:
Hradec Králové – Kiev
MSN:
LJ-1307
YOM:
1992
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
18200
Captain / Total hours on type:
900.00
Aircraft flight hours:
3257
Aircraft flight cycles:
3639
Circumstances:
The twin engine aircraft departed Hradec Králové on an exec flight to Kiev with four passengers and one pilot on board. On final approach to Kiev-Zhuliany Airport, the pilot encountered poor visibility (below minimums) and descended too fast and too low. On short final, at a speed of 220 knots, the aircraft impacted ground and crashed in a wasteland located 2,590 metres short of runway 08 and 48 metres to the right of its extended centerline. The aircraft was destroyed upon impact and all five occupants were killed, among them the CEO of the Czech company Minib that bought the aircraft last 28 November. According to Czech Authorities, the aircraft was to be transferred to the Czech Republic Registry within January 2008. At the time of the accident, the horizontal visibility was 900 metres and the vertical visibility was 100 feet due to low clouds.
Probable cause:
It was determined that the aircraft impacted ground after the pilot continued the approach in below minima weather conditions.
The following findings were identified:
- The pilot continued the descent below MDA until the aircraft impacted ground,
- Few seconds prior to the accident, ATC instructed twice the pilot to initiate a go-around procedure, but this was too late,
- The pilot was approaching the airport at an excessive speed and below the glide,
- Poor visibility due to low clouds (below minimums).
Final Report:

Crash of a McDonnell Douglas MD-83 in Isparta: 57 killed

Date & Time: Nov 30, 2007 at 0136 LT
Type of aircraft:
Operator:
Registration:
TC-AKM
Survivors:
No
Site:
Schedule:
Istanbul - Isparta
MSN:
53185/2090
YOM:
1994
Flight number:
KK4203
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
57
Circumstances:
The aircraft departed Istanbul-Atatürk Airport at 0051LT on a schedule service to Isparta, carrying 50 passengers and 7 crew members. After being cleared to proceed to a VOR/DME approach to Isparta Airport runway 05, the crew was supposed to fly over IPT VOR then to follow a 223° heading. But the crew failed to input the arrival procedures in the FMS and started the approach by night over rising terrain. As the EGPWS failed to activate, the crew did not realize his altitude was insufficient when the aircraft collided with trees and crashed in a mountainous area located near Çukurören, about 12 km west of Isparta Airport. The aircraft was destroyed and all 57 occupants were killed.
Probable cause:
The following findings were identified:
- The crew failed to follow the published procedures,
- The crew failed to adhere to SOP's,
- The EGPWS system failed to activate and to warn the crew about the insufficient altitude,
- The EGPWS failed 86 times during the last 235 flights and was removed from another aircraft to be installed on TC-AKM 10 days prior to the accident,
- Lack of visibility due to the night,
- The CVR system was unserviceable,
- The DFDR system was partially unserviceable and recorded the last 15 minutes of flight only,
- Lack of crew training,
- The captain followed only 20 of the requested 32 hours training,
- The copilot followed a 32-hours training program in Sofia but this was not documented,
- A probable lack of situational awareness on part of the crew.

Crash of a Bombardier BD-700-1A11 Global Express 5000 in Fox Harbour

Date & Time: Nov 11, 2007 at 1434 LT
Operator:
Registration:
C-GXPR
Survivors:
Yes
Schedule:
Hamilton – Fox Harbour
MSN:
9211
YOM:
2006
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9188
Captain / Total hours on type:
64.00
Copilot / Total flying hours:
6426
Copilot / Total hours on type:
9
Aircraft flight hours:
92
Aircraft flight cycles:
26
Circumstances:
The aircraft, operated by Jetport Inc., departed Hamilton, Ontario, for Fox Harbour, Nova Scotia, with two crew members and eight passengers on board. At approximately 1434 Atlantic standard time, the aircraft touched down seven feet short of Runway 33 at the Fox Harbour aerodrome. The main landing gear was damaged when it struck the edge of the runway, and directional control was lost when the right main landing gear collapsed. The aircraft departed the right side of the runway and came to a stop 1000 feet from the initial touchdown point. All occupants evacuated the aircraft. One crew member and one passenger suffered serious injuries; the other eight occupants suffered minor injuries. The aircraft sustained major structural damage.
Probable cause:
Findings as to Risk:
1. Because aircraft EWH information is not readily available to pilots, crews may continue to conduct approaches with an aircraft mismatched to the visual glide slope indicator (VGSI) system, increasing the risk of a reduced TCH safety margin.
2. Due to limited knowledge of the various VGSI systems in operation and their limitations, flight crews will continue to follow visual guidance that might not provide for safe TCH.
3. Jetport did not develop an accurate company risk profile. This precluded identification of systemic safety deficiencies and development of appropriate mitigation strategies.
4. If adequate safety oversight of POC operators is not maintained by the regulator, or the delegated organization, especially during SMS implementation, there is an increased risk that safety deficiencies will not be identified.
5. The fact that the Canadian Business Aviation Association (CBAA) did not insist that milestones for SMS implementation and development be followed may result in some POC operators never reaching full SMS compliance.
6. If Transport Canada does not ensure that the CBAA fulfills its responsibilities for adequate oversight of the Canadian Aviation Regulations (CARs) subpart 604 community, safety deficiencies will not be identified and addressed.
7. The audit of Jetport’s SMS, conducted by the CBAA–accredited auditor, did not identify the deficiencies in the program or make any suggestions for improvement. Without a comprehensive audit of an operator’s SMS, deficiencies could exist resulting in the operator’s inability to implement an effective mitigation strategy.
8. Contrary to the recommendations made in the Transport Canada/CBAA feasibility studies, the CBAA did not have a quality assurance program for its audit process. As a result, there is a risk that the CBAA will fail to identify weaknesses in the POC audit program.
9. At the time of the accident, no one at Fox Harbour (CFH4) had been assigned responsibility for regular maintenance of the APAPI, therefore preventing timely identification of APAPI equipment misalignment.
10. Jetport’s risk analysis before the introduction of the Global 5000 did not identify the incompatibility between the EWH of the aircraft and the APAPI at CFH4.
11. Not wearing shoulder harnesses during landings and take-offs increases the potential risk of passenger injuries.
12. Passengers not wearing footwear could impede evacuation, increase the risk of injury, and reduce post-crash mobility and (potentially) survival.
Other Findings:
1. A SMS integrates sound risk management policies, practices, and procedures into day-to-day operations and, properly implemented, offers great potential to reduce accidents.
2. Contrary to its own assessment protocol, Transport Canada did not document its decision to close off the CBAA assessment even though the CBAA had not submitted an acceptable corrective action plan.
3. Depiction of the different types of VGSIs differs, depending on the publication.
Final Report:

Crash of an Airbus A340-642 in Quito

Date & Time: Nov 9, 2007 at 1706 LT
Type of aircraft:
Operator:
Registration:
EC-JOH
Survivors:
Yes
Schedule:
Madrid - Quito
MSN:
731
YOM:
2006
Flight number:
IB6463
Country:
Crew on board:
14
Crew fatalities:
Pax on board:
345
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14024
Captain / Total hours on type:
2375.00
Copilot / Total flying hours:
10095
Copilot / Total hours on type:
1742
Aircraft flight hours:
8704
Aircraft flight cycles:
965
Circumstances:
Following an uneventful flight from Madrid, the crew contacted Quito Approach at 1650LT and received descent instructions in preparation for an instrument approach no. 4 (VOR QIT DME/ILS) for runway 35. During the descent the crew were notified that preceding flights had reported braking action medium to poor. The flight crew selected auto braking to 'High'. At 17:05, the crew reported the runway in sight, after which the controller stated that the wind was 170° at 4 knots, the runway was wet and reported braking action was poor. The flight was cleared to land. The pilot in command, following the procedures established by Iberia, decided to leave the ILS glide path and captured the path of the PAPI lights. The aircraft touched down 200 metres past the threshold at a 3.09g side load. The spoilers deployed automatically and main gear tyres 3 and 8 blew. The flap lever was moved involuntarily by the copilot, from the full position to position 2. The crew applied full manual braking and select reverse thrust. The Auto Brake function failed, after which the crew disconnected the antiskid braking system and continued to apply manual braking. The aircraft passed the end of runway 35, with a ground speed of 90 knots, hit the ILS localizer and stopped 232 meters further. Passengers and crew were evacuated using the slide at door 2R, thirty minutes after the aircraft stopped. All occupants escaped uninjured while the aircraft was considered as damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the crew who decided to continue the approach to Quito Airport, knowing the poor runway conditions, poor weather conditions and the aircraft weight, and his failure to initiate a go-around procedure while forcing the aircraft to intercept the PAPI, causing the aircraft to be unstabilized.
Contributing factors:
- On the date of the incident, the crew did not have specific regulations and operating procedures (the briefing of the operator for the airport in Quito was inappropriate to the existent conditions).
- The fact that the crew still being experienced similar airports in Quito and had not experienced similar weather situations, circumstances that would have allowed a strategy of approximation consistent with the terms of this operation, in particular as regards:
- Calculations in flight for landing runway length,
- Minimum altitude to start the maneuver of changing the path of ILS to PAPI,
- Carrying out a very detailed briefing that allowed unwanted deviations on approach,
- The weather conditions existing at the time of landing (visibility, tail wind and moderate rain).

Crash of an Antonov AN-12TB in Khartoum: 2 killed

Date & Time: Nov 8, 2007 at 0807 LT
Type of aircraft:
Operator:
Registration:
ST-JUA
Flight Type:
Survivors:
Yes
Schedule:
Khartoum - Juba
MSN:
3 3 411 10
YOM:
1963
Flight number:
JUC700
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Aircraft flight hours:
11787
Aircraft flight cycles:
7220
Circumstances:
The four engine aircraft departed Khartoum-Haj Yusuf Airport at 0759LT on a cargo flight to Juba, carrying four crew members and a load of 11 tons of various goods. After takeoff, while climbing, the crew reported the failure of the engine n°3 and was cleared to return for an emergency landing. After touchdown, the aircraft went out of control, veered off runway and came to rest in the military area of the airport, bursting into flames. All four crew members were injured while two people on the ground were killed. The aircraft was destroyed by a post crash fire.
Probable cause:
Failure of the engine n°3 during initial climb following a bird strike.

Crash of a Cessna 340 in Garberville: 3 killed

Date & Time: Nov 6, 2007 at 0855 LT
Type of aircraft:
Operator:
Registration:
N5049Q
Survivors:
No
Schedule:
Redding – Garberville
MSN:
340-0016
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
18500
Aircraft flight hours:
7691
Circumstances:
The pilot arrived in the vicinity of his destination airport, which was located in a narrow river valley. The airport was located within a large area of Visual Flight Rules (VFR) conditions with clear skies and almost unlimited visibility, but the pilot discovered that the airport was covered by a localized dense layer of fog about 200 to 250 feet thick. There were no instrument approaches to the non-controlled airport. Witnesses reported that the pilot flew at low-level up the valley, and eventually entered the fog as the flight approached the airport. About one mile prior to reaching the airport, the pilot attempted to climb out of the valley, but the airplane began impacting trees on the rising terrain. The airplane eventually sustained sufficient damage from impacting the trees that it descended into the terrain. Post-accident inspection of the airframe and engines found no evidence of a mechanical failure or malfunction.
Probable cause:
The pilot's intentional visual flight rules (VFR) flight into instrument meteorological conditions (IMC), and his failure to maintain clearance from the trees and terrain during climb. Contributing to the accident were the weather conditions of fog and a low ceiling, and the mountainous/hilly terrain.
Final Report:

Crash of a Beechcraft A100 King Air near Santa Elena: 2 killed

Date & Time: Nov 4, 2007
Type of aircraft:
Operator:
Registration:
XB-JVV
Flight Type:
Survivors:
No
MSN:
B-170
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The crew was performing an illegal flight from Colombia to Mexico with one ton of cocaine on board. While flying over the State of El Petén in Guatemala, the pilot informed ATC about technical problem and was cleared to divert to Santa Elena-Munda Maya Airport. On approach, the twin engine aircraft crashed in an open field located 30 km from the airport. The aircraft was destroyed and both occupants were killed. Guatemaltecan Authorities confirmed that at the time of the accident, the aircraft was registered YV-1568 which was a false registration; the real one was XB-JVV.

Crash of a Boeing 737-230 in Malang

Date & Time: Nov 1, 2007 at 1324 LT
Type of aircraft:
Operator:
Registration:
PK-RIL
Survivors:
Yes
Schedule:
Jakarta – Malang
MSN:
22137/788
YOM:
1981
Flight number:
RI260
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
89
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19357
Captain / Total hours on type:
10667.00
Copilot / Total flying hours:
2300
Copilot / Total hours on type:
1528
Aircraft flight hours:
57823
Circumstances:
On 1 November 2007, a Boeing Company B737-200 aircraft, registered PK-RIL, operated by PT. Mandala Airlines as flight number MDL 260, was on a scheduled passenger flight from Jakarta Soekarno-Hatta International Airport, Jakarta, to Abdurrachman Saleh Airport, Malang, East Java. The pilot in command (PIC) was the handling pilot, and the copilot was the support/monitoring pilot. There were 94 persons on board the aircraft, consisting of two pilots, three cabin crew, and 89 passengers. The aircraft landed at Malang at 1324 Western Indonesian Standard Time (06:24 Coordinated Universal Time (UTC). It was reported to have been raining heavily when the aircraft landed on runway 35 at Malang. The aircraft bounced twice after the initial severe hard landing, and the lower drag strut of the nose landing gear fractured, resulting in the rearwards collapse of the nose landing gear and separation of the lower nose landing gear shock strut and wheel assembly. The aircraft’s nose then contacted the runway, and the aircraft came to rest 290 metres before the departure end of runway 17. The crew subsequently reported that during the visual segment of the landing approach, they realized that the aircraft was too high with reference to the precision approach path indicator (PAPI) for runway 35. The PIC increased the aircraft’s rate of descent (ROD) to capture the PAPI. The high ROD was not arrested, and as a consequence, the severe hard landing occurred which substantially damaged the aircraft. No one of the passengers or crew was injured.
Probable cause:
The flight crew did not appear to have an awareness that the aircraft was above the desired approach path to runway 35 at Malang until they sighted the visual approach slope indication lighting system. The pilot in command continued the approach in reduced visibility and heavy rain; marginal visual meteorological conditions. Non-adherence by the flight crew to stabilized approach procedures, which resulted in the initial severe hard landing at Malang, together with the omission of a high bounced landing recovery, resulted in substantial damage to the aircraft. The following findings were identified:
- The PIC allowed the approach at Malang to become unstabilized and did not correct that condition.
- The PIC continued the approach in reduced visibility and heavy rain; marginal visual meteorological conditions.
- Neither pilot responded appropriately to the ground proximity warning system voice aural ‘SINK RATE’ or ‘PULL UP’ warnings that sounded during the final approach to Malang.
- The PIC did not initiate action to recover from the high bounced landing following the initial severe hard landing impact.
- The PIC did not ensure that effective crew coordination was maintained during the landing approach.
Final Report:

Crash of an Ilyushin II-76TD in Bamako

Date & Time: Oct 31, 2007
Type of aircraft:
Operator:
Registration:
5A-DNQ
Flight Type:
Survivors:
Yes
MSN:
00434 54641
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 Bamako-Senou Airport, the nose gear collapsed. The aircraft was damaged beyond repair and all six crew members evacuated safely. The exact date of the mishap remains unknown, somewhere in October 2007.

Crash of a Cessna 650 Citation III in Atlantic City

Date & Time: Oct 27, 2007 at 1110 LT
Type of aircraft:
Operator:
Registration:
N697MC
Flight Type:
Survivors:
Yes
Schedule:
Farmingdale – Atlantic City
MSN:
650-0097
YOM:
1985
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9472
Captain / Total hours on type:
199.00
Copilot / Total flying hours:
2535
Copilot / Total hours on type:
120
Aircraft flight hours:
7052
Circumstances:
The first officer was flying the Area Navigation, Global Positioning System, approach to runway 22. During the approach, the airplane was initially fast as the first officer had increased engine power to compensate for wind conditions. Descending below the minimum descent altitude (MDA), the first officer momentarily deployed the speed brakes, but stowed them about 200 feet above ground level (agl), and reduced the engine power to flight idle. The airplane became low and slow, and developed an excessive sink rate. The airplane subsequently landed hard on runway 22, which drove the right main landing gear into the right wing, resulting in substantial damage to the right wing spar. The first officer reported intermittent airspeed fluctuations between his airspeed indicator and the captain's airspeed indicator; however, a subsequent check of the pitot-static system did not reveal any anomalies that would have precluded normal operation of the airspeed indicators. About the time of the accident, the recorded wind was from 190 degrees at 11 knots, gusting to 24 knots; and the captain believed that the airplane had encountered windshear near the MDA, with the flaps fully extended. Review of air traffic control data revealed that no windshear advisories were contained in the automated terminal information system broadcasts. Although the local controller provided windshear advisories to prior landing aircraft, he did not provide one to the accident aircraft. Review of the airplane flight manual (AFM) revealed that deploying the speed brakes below 500 feet agl, with the flaps in any position other than the retracted position, was prohibited.
Probable cause:
The first officer's failure to maintain airspeed during approach, and the captain's inadequate remedial action. Contributing to the accident was the first officer's failure to comply with procedures, windshear, and the lack of windshear warning from air traffic control.
Final Report: