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 Rockwell Aero Commander 500B near Armstrong

Date & Time: Nov 30, 2007 at 0917 LT
Operator:
Registration:
C-GETK
Flight Phase:
Survivors:
Yes
Schedule:
Dryden – Geraldton
MSN:
500-1093-56
YOM:
1961
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed from Dryden, Ontario, en route to Geraldton, Ontario. The flight was conducted under visual flight rules at 5500 feet above sea level with ambient temperatures aloft of -33°C. Approximately 40 minutes into the flight, the crew observed an abnormal right engine fuel flow indication. While troubleshooting the right engine, the engine rpm and fuel flow began to decrease and the crew diverted toward Armstrong, Ontario. A short time later, the left engine rpm and fuel flow began to decrease and the crew could no longer maintain level flight. At 0917 central standard time, the crew made a forced landing 20 nautical miles southwest of Armstrong, into a marshy wooded area. The captain sustained serious injuries and the co-pilot and passenger sustained minor injuries. The aircraft was substantially damaged. The crew and passenger were stabilized and transported to Thunder Bay, Ontario, for medical assistance.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Suspended water in the fuel system precipitated out of solution and froze in the fuel distributor valve. This blocked the fuel supply to the fuel nozzles and led to the loss of engine power.
2. The aircraft was being operated without a fuel additive icing inhibiter. Use of such an additive would have inhibited ice formation in the aircraft’s fuel system and would likely have prevented the fuel system blockage.
Findings as to Risk:
1. The fuel distributor valve on the Aero Commander 500B is exposed directly to the cooling blast of the outside air, which under extremely cold conditions, can lead to the freezing of super-cooled water droplets present in the fuel stream.
2. The operator did not have procedures to describe how fuel additive icing inhibiter should be used during winter operations.
Final Report:

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 a Beechcraft A100 King Air in Chino: 2 killed

Date & Time: Nov 6, 2007 at 0918 LT
Type of aircraft:
Operator:
Registration:
N30GC
Flight Phase:
Survivors:
No
Schedule:
Chino - Visalia
MSN:
B-177
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3136
Aircraft flight hours:
11849
Circumstances:
The reported weather at the time of the accident was calm winds, a 1/4-mile visibility in fog and a vertical visibility of 100 feet. Shortly after takeoff for the instrument-flight-rules flight, the airplane made a slight turn to the left and impacted the tops of 25-foot trees about a 1/2 mile from the runway. An enhanced ground proximity warning system was installed on the airplane and data extraction from the system indicated that the airplane achieved an initial positive climb profile with a slight turn to the left and then a descent. A witness reported hearing the crash and observed the right wing impact the ground and burst into flames. The airplane then cartwheeled for several hundred feet before coming to rest inverted. The airframe, engines, and propeller assemblies were inspected with no mechanical anomalies noted that would have precluded normal flight.
Probable cause:
The pilot's failure to maintain a positive climb rate during an instrument takeoff. Contributing to the accident was the low visibility.
Final Report:

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 Learjet 35A in Goodland

Date & Time: Oct 17, 2007 at 1010 LT
Type of aircraft:
Operator:
Registration:
N31MC
Survivors:
Yes
Schedule:
Fort Worth - Goodland
MSN:
35A-270
YOM:
1979
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20000
Captain / Total hours on type:
7000.00
Copilot / Total flying hours:
9500
Copilot / Total hours on type:
700
Aircraft flight hours:
5565
Circumstances:
According to the flight crew, they exited the clouds approximately 250 feet above ground level, slightly left of the runway centerline. The pilot not flying took control of the airplane and adjusted the course to the right. The airplane rolled hard to the right and when the pilot corrected to the left, the airplane rolled hard to the left. The airplane impacted the ground in a right wing low attitude, resulting in substantial damage. Further examination and testing revealed anomalies with the yaw damper and spoileron computer. According to the manufacturer, these anomalies would not have prevented control of the airplane. Greater control wheel displacement and force to achieve a desired roll rate when compared with an operative spoileron system would be required. The result would be a slightly higher workload for the pilot, particularly in turbulence or crosswind conditions. An examination of the remaining systems revealed no anomalies.
Probable cause:
The pilot's failure to maintain aircraft control during the landing.
Final Report:

Crash of a Beechcraft 60 Duke in Silvânia: 2 killed

Date & Time: Sep 17, 2007 at 1340 LT
Type of aircraft:
Operator:
Registration:
PT-OOH
Flight Phase:
Survivors:
No
Schedule:
Montes Claros – Goiânia
MSN:
P-27
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1000
Captain / Total hours on type:
85.00
Circumstances:
The twin engine aircraft departed Montes Claros Airport at 1200LT on a flight to Goiânia, carrying one passenger and one pilot. As he started the descent to Goiânia Airport, the pilot reported the failure of the left engine and requested the permission to proceed with a direct approach to runway 32 despite the runway 14 was in use. Few seconds later, the right engine failed as well. The pilote reduced his altitude and attempted an emergency landing when the aircraft crashed in an open field located near Silvânia, about 50 km east of Goiânia Airport. On impact, the fixing points of the seat belts broke away, causing both occupants to impact the instrument panel. The aircraft was severely damaged and both occupants were killed.
Probable cause:
Failure of both engines in flight due to fuel exhaustion. The following contributing factors were identified:
- Poor judgment on the part of the pilot who considered that the quantity of fuel present in the tanks before departure was sufficient, which was not the case,
- Poor flight planning on part of the pilot who miscalculated the fuel consumption,
- The pilot failed to follow the procedures related to fuel policy.
Final Report:

Crash of an IAI 1125 Astra APX in Atlanta

Date & Time: Sep 14, 2007 at 1719 LT
Type of aircraft:
Operator:
Registration:
N100G
Survivors:
Yes
Schedule:
Coatesville - Atlanta
MSN:
092
YOM:
1998
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10800
Captain / Total hours on type:
2200.00
Copilot / Total flying hours:
16042
Copilot / Total hours on type:
1500
Aircraft flight hours:
4194
Circumstances:
The pilot-in-command (PIC) of the of the airplane was the flight department's chief pilot, who was in the right seat and monitoring the approach as the non-flying pilot. The second-in-command (SIC) was a captain for the flight department, who was in the left seat and the flying pilot. On arrival at their destination, they were vectored for an instrument-landing-system (ILS) approach to a 6,001-foot-long runway. Visibility was 1-1/4 miles in rain. The autopilot was on and a coupled approach was planned. After the autopilot captured the ILS, the airplane descended on the glideslope. The PIC announced that the approach lights were in sight and the SIC stated that he also saw the lights and disengaged the autopilot. The SIC turned on the windshield wipers and then lost visual contact with the runway. He announced that he lost visual contact, but the PIC stated that he still saw the runway. The SIC considered a missed approach, but continued because the PIC still had visual contact. The PIC stated, "I have the lights" and began to direct the SIC. He then "took over the controls." The airplane touched down, the speed brakes extended and, approximately 1,000 feet later, the airplane overran the runway. The PIC stated that he was confused as to who was the PIC, and that he and the SIC were "co-captains." When asked about standard operating procedures (SOPs), the PIC advised that they did not have any. They had started out with one pilot and one airplane, and they now had five pilots and two airplanes. The PIC later stated that they probably should have gone around when the flying pilot could not see out the window. The PIC added that the windshields had no coating and did not shed water. One year prior, while flying in rain, his vision through the windshield was blurred but he did not report it to their maintenance provider. Manufacturer's data revealed that the windshield was coated to enhance vision during rain conditions. The manufacturer advised that the coating might not last the life of the windshield and provided guidance to determine both acceptable and unacceptable rain repellent performance.
Probable cause:
The pilot's failure to initiate a missed approach and his failure to obtain the proper touchdown point while landing in the rain. Contributing to the accident were the operator's lack of standard operating procedures and the inadequate maintenance of the windshield.
Final Report:

Crash of a Partenavia P.68C Victor in Bangalore: 4 killed

Date & Time: Sep 8, 2007 at 1520 LT
Type of aircraft:
Operator:
Registration:
VT-JOY
Flight Phase:
Survivors:
No
Schedule:
Bangalore – Cochin
MSN:
436
YOM:
2004
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3140
Circumstances:
The aircraft departed Bangalore-Hindustan Airport runway 27 at 1514LT on a flight to Cochin with 3 passengers and one pilot on board. Six minutes after takeoff, the pilot reported technical problems and elected to return for an emergency landing. However, the aircraft entered an uncontrolled descent and crashed in the lakebed of the Gawdanapalya Lake located about 9 km southwest of the airport. The aircraft was destroyed and all four occupants were killed.
Probable cause:
Engine power loss during initial climb after the aircraft had been refueled with Jet fuel instead of Avgas 100LL.
The following contributing factors were identified:
- The low experience of the pilot on type,
- The non-compliance of correct refueling procedure and its supervision by IOC personnel and pilot or operator's representative.
Final Report:

Crash of a Rockwell Shrike Commander 500S in Clonbinane: 2 killed

Date & Time: Jul 31, 2007 at 2000 LT
Operator:
Registration:
VH-YJB
Flight Phase:
Survivors:
No
Site:
Schedule:
Melbourne – Shepparton
MSN:
500-3299
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2342
Captain / Total hours on type:
970.00
Aircraft flight hours:
4558
Circumstances:
At 1946 Eastern Standard Time on 31 July 2007, a Rockwell International Aero Commander 500S, registered VH-YJB (YJB), departed Essendon Airport, Vic. on a business flight to Shepparton that was conducted at night under the instrument flight rules (IFR). On board were the pilot and one passenger. At 1958, while in the cruise at 7,000 ft above mean sea level (AMSL) in Class C controlled airspace, radar and radio contact with the aircraft was lost simultaneously by air traffic control when it was about 25 NM (46 km) north-north-east of Essendon. The air traffic controller declared a distress phase after a number of unsuccessful attempts to contact the pilot. At 2003, the Operations Director at Melbourne Centre declared the aircraft as probably lost and advised AusSAR. A search was commenced using a helicopter and an aeroplane in addition to ground search parties. No emergency locator transmitter signal was reported. At 2147, aircraft wreckage was located by a searching aircraft in timbered ranges near Clonbinane, approximately 50 km north of Melbourne. At about 2200, a ground search party confirmed that the wreckage was that of YJB and that there were no survivors. The flight was arranged to take the company owner, who was also a licensed aircraft maintenance engineer (LAME), to Shepparton to replace an unserviceable starter motor in another of the operator‟s aircraft. The pilot, who had landed at Essendon at 1915 from a previous flight in another of the operator‟s aircraft, was tasked to fly the owner to Shepparton. The pilot transferred to YJB, which had previously been prepared for flight by another company pilot. At 1938, while taxiing for takeoff, the pilot advised the aerodrome controller of the intention to conduct the IFR flight, adding, „…and request a big favour for a submission of a flight plan, with an urgent departure Essendon [to] Shepparton [and] return‟. The aerodrome controller did not have the facilities for processing flight notifications and sought the assistance of a controller in the Melbourne air traffic control centre. There were no eyewitnesses to the accident. Residents living in the vicinity of the accident site were inside their homes and reported difficulty hearing anything above the noise made by the wind and the foliage being blown about. One of the residents reported hearing a brief, loud engine noise. Another resident thought the noise was that of a noisy vehicle on the road. The noise was described as being constant, „…not spluttering or misfiring‟ and lasted for only a few seconds. Some of those residents near the accident site reported hearing and feeling an impact only moments after the engine noise ceased. The aircraft was seriously damaged by excessive in-flight aerodynamic forces and impact with the terrain. The vegetation in the immediate vicinity of the main aircraft wreckage was slightly damaged as the aircraft descended, nearly vertically, through the trees. The pilot and passenger were fatally injured.
Probable cause:
Structural failure and damage:
From the detailed examination and study of the aircraft wreckage undertaken by ATSB investigation staff, it was evident that all principal structural failures had occurred under gross overstress conditions i.e. stresses significantly in excess of the physical strength of the respective structures. The examination found no evidence of pre-existing cracking, damage or material degradation that could have appreciably reduced the strength of the failed sections, nor was there any indication that the original manufacture, maintenance or repair processes carried out on the aircraft were in any way contributory to the failures sustained.

Breakup sequence:
From the localised deformation associated with the spar failures, it was evident that the aircraft had sustained a large negative (downward) loading on the wing structure. That downward load resulted in the localised bending failure of the wing around the station 145 position (145” outboard of the aircraft centreline). The symmetry of both wing failures and the absence of axial twisting within the fuselage section suggested that the load encountered was sudden and well in excess of the ultimate strength of the wing structure. Based upon the witness marks on both wing under-surfaces and the crushing and paint transfer along the leading edges of the horizontal stabilisers, it was concluded that after separating from the inboard structure, both wings had moved aft in an axial twisting and rotating fashion; simultaneously impacting the leading edges of both horizontal tailplanes. Forces imparted into the empennage structure from that impact subsequently produced the rearward separation of the complete empennage from the fuselage. The loss of the left engine nacelle fairing was likely brought about through an impact with a section of wing leading edge as it rotated under and to the rear. The damage sustained by all of the aircraft‟s control surfaces was consistent with failure and separation from their respective primary structure under overstress conditions associated with the breakup of the aircraft. There was no evidence of cyclic or oscillatory movement of the surfaces before separation that might have suggested the contribution of an aerodynamic flutter effects.

Findings
The following statements are a summary of the verified findings made during the progress of the aircraft wreckage structural examination and analysis:
- All principal failures within the aircraft wings, tailplanes and empennage had occurred as a result of exposure to gross overstress conditions.
- The damage sustained by the aircraft wreckage was consistent with the aircraft having sustained multiple in-flight structural failures.
- The damage sustained by the aircraft wreckage was consistent with the structural failure sequence being initiated by the symmetric, downward bending failure of both wing sections, outboard of the engine nacelles.
- Breakup and separation of the empennage was consistent with having been initiated by impact of the separated outboard wings with the leading edges of the horizontal stabilisers.
- There was no evidence of material or manufacturing abnormalities within the aircraft structure that could be implicated in the failures and breakup sustained.
- There was no evidence of service-related degradation mechanisms (such as corrosion, fatigue cracking or environmental cracking) having affected the aircraft structure in the areas of failure.
Final Report: