Crash of a Beechcraft B100 King Air in Aurora

Date & Time: Oct 6, 2009 at 1450 LT
Type of aircraft:
Registration:
N2TX
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Oklahoma City - Fort Worth
MSN:
BE-103
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4120
Captain / Total hours on type:
103.00
Aircraft flight hours:
1063
Circumstances:
The pilot added fuel to the multi-engine airplane prior to departure. While en route to the destination airport, the pilot noted that the fuel gauges indicated that the right main-tank appeared to be almost empty and the left tank appeared half full. The pilot initiated the crossfeed procedure in an effort to supply fuel to both engines from the left main tank. Shortly after beginning the crossfeed procedure, both engines experienced a total loss of power. The pilot notified air traffic control (ATC) and selected a field to perform a forced landing. Prior to touchdown, the right engine produced a surge of power and, in response, the airplane rolled to the left. The surge abruptly ended and the pilot continued the forced landing by lowering landing gear and extending the flaps. The airplane impacted the ground, coming to rest in an open field. A postimpact examination did not reveal any anomalies with the airframe or engine that would have precluded normal operation. Although both fuel tanks were ruptured, the accident scene did not contain a large amount of residual fuel. A small fuel slick was found on the surface of a nearby pond; however, the grass area underneath both wings did not contain dead grass; this would have been expected if there was more than a negligible amount of fuel in the tanks at time of impact.
Probable cause:
The loss of engine power due to fuel exhaustion as a result of the pilot's inadequate fuel management.
Final Report:

Crash of a Beechcraft 100 King Air near Valera: 6 killed

Date & Time: Mar 1, 2009 at 1153 LT
Type of aircraft:
Registration:
YV2129
Survivors:
No
Site:
Schedule:
Charallave – Valera
MSN:
B-83
YOM:
1971
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The twin engine aircraft departed Charallave-Óscar Machado Zuloaga Airport on a charter flight to Valera, carrying four passengers and two pilots. While descending to Valera-Carvajal Airport in IMC conditions, at an altitude of 9,650 feet, the aircraft impacted the slope of Mt Piedra Gorda located 35 km from the airport. The wreckage was found the following day at the end of the afternoon. The aircraft disintegrated on impact and all 6 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew started the descent prematurely. The lack of visibility was considered as a contributing factor.

Crash of a Beechcraft 100 King Air in Island Lake

Date & Time: Jan 16, 2009 at 2110 LT
Type of aircraft:
Operator:
Registration:
C-GNAA
Flight Type:
Survivors:
Yes
Schedule:
Thompson - Island Lake
MSN:
B-24
YOM:
1969
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3200
Captain / Total hours on type:
500.00
Copilot / Total flying hours:
1200
Copilot / Total hours on type:
620
Circumstances:
The crew was on a re-positioning flight from Thompson to Island Lake, Manitoba. On arrival in the Island Lake area, the crew commenced an instrument approach to Runway 12. On the final approach segment, the aircraft descended below the minimum descent altitude and the crew initiated a missed approach. During the missed approach, the aircraft struck trees. The crew was able to return for a landing on Runway 12 at Island Lake without further incident. The two crew members were not injured; the aircraft sustained damage to its right wing and landing gear doors. The accident occurred during hours of darkness at approximately 2110 Central Standard Time.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew conducted an Area Navigation (RNAV) approach for which they were not trained, with an aircraft that was not properly equipped nor approved for such purpose.
2. The aircraft descended 300 feet below the minimum descent altitude (MDA) as a result of a number of lapses, errors and adaptations which, when combined, resulted in the mismanaged approach.
3. The aural warning on the aircraft’s altitude alerter had been silenced prior to the approach, which precluded it from alerting the crew when the aircraft descended below minimum descent altitude.
4. The SkyNorth standard operating procedures for conducting a non-precision approach were not followed, which resulted in the aircraft descending below the minimum descent altitude. During the ensuing missed approach, the aircraft struck trees.
Findings as to Risk:
1. The lack of a more-structured training environment and the type of supervisory flying provided increased the risk that deviations from standard operating procedures (SOPs) would not be identified.
2. There are several instrument approach procedures in Canada that contain step-down fixes that are not displayed on global positioning system (GPS) units. This may increase the risk of collision with obstacles during step-downs on approaches.
Final Report:

Crash of a Beechcraft A100 King Air in Gods Lake Narrows

Date & Time: Nov 22, 2008 at 2140 LT
Type of aircraft:
Operator:
Registration:
C-FSNA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Gods Lake Narrows – Thompson
MSN:
B-227
YOM:
1976
Flight number:
SNA683
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3200
Captain / Total hours on type:
1850.00
Copilot / Total flying hours:
1000
Copilot / Total hours on type:
500
Circumstances:
The Sky North Air Ltd. Beechcraft A100 (registration C-FSNA, serial number B-227) operating as SN683 departed Runway 32 at Gods Lake Narrows, Manitoba, for Thompson, Manitoba with two pilots, a flight nurse, and two patients on board. Shortly after takeoff, while in a climbing left turn, smoke and then fire emanated from the pedestal area in the cockpit. The crew continued the turn, intending to return to Runway 14 at Gods Lake Narrows. The aircraft contacted trees and came to rest in a wooded area about one-half nautical mile northwest of the airport. The accident occurred at 2140 central standard time. All five persons onboard evacuated the aircraft; two received minor injuries. At approximately 0250, the accident site was located and the occupants were evacuated. The aircraft was destroyed by impact forces and a post-crash fire. The emergency locator transmitter was consumed by the fire and whether or not it transmitted a signal is unknown.
Probable cause:
Findings as to Causes and Contributing Factors:
1. An electrical short circuit in the cockpit pedestal area produced flames and smoke, which induced the crew to take emergency action.
2. The detrimental effects of aging on the wires involved may have been a factor in this electrical arc event.
3. The crew elected to return to the airport at low level in an environment with inadequate visual references. As a result, control of the aircraft was lost at an altitude from which a recovery was not possible.
Findings as to Risk:
1. The actions specified in the standard operating procedures (SOP) do not include procedures for an electrical fire encountered at low altitude at night, which could lead to a loss of control.
2. Visual inspection procedures in accordance with normal phase inspection requirements may be inadequate to detect defects progressing within wiring bundles, increasing the risk of electrical fires.
3. In the event of an in-flight cockpit pedestal fire, the first officer does not have ready access to available fire extinguishers, reducing the likelihood of successfully fighting a fire of this nature.
4. Sealed in plastic containers and stored behind each pilot seat, the oxygen masks and goggles are time consuming to access and cumbersome to apply and activate. This could increase the probability of injury or incapacitation through extended exposure to smoke or fumes, or could deter crews from using them, especially during periods of high cockpit workload.
Other Finding:
1. A failure of the hot-mic recording function of the cockpit voice recorder (CVR) had gone undetected and information that would have been helpful to the investigation was not available.
Final Report:

Crash of a Beechcraft 100 King Air in Stony Rapids

Date & Time: Nov 11, 2008 at 1817 LT
Type of aircraft:
Registration:
C-GWWQ
Flight Type:
Survivors:
Yes
Schedule:
Uranium City – Stony Rapids
MSN:
B-76
YOM:
1971
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reasons, the aircraft made a wheels up landing and skidded on runway at Stony Rapids Airport before coming to rest. Both pilots were uninjured while the aircraft was damaged beyond repair.
Probable cause:
Gear up landing for undetermined reason.

Crash of a Beechcraft 100 King Air in Bauru: 1 killed

Date & Time: Oct 12, 2008
Type of aircraft:
Registration:
N525ZS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bauru – Sorocaba
MSN:
B-66
YOM:
1971
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from Bauru Airport, the twin engine aircraft encountered difficulties to maintain a positive rate of climb. It then descended until it impacted ground about 5 km from the airport. The pilot, sole on board, was killed. He was supposed to deliver the aircraft at Sorocaba Airport.

Crash of a Beechcraft A100 King Air in Moab: 10 killed

Date & Time: Aug 22, 2008 at 1750 LT
Type of aircraft:
Registration:
N601PC
Flight Phase:
Survivors:
No
Schedule:
Moab - Cedar City
MSN:
B-225
YOM:
1975
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
1818
Captain / Total hours on type:
698.00
Aircraft flight hours:
9263
Circumstances:
The twin engine aircraft, owned by the Red Canyon Aesthetics & Medical Spa, a dermatology clinic headquartered in Cedar City, was returning to its base when shortly after take off, the pilot elected to make an emergency landing due to technical problem. The aircraft hit the ground, skidded for 300 meters and came to rest in flames in the desert, near the Arches National Park. All 10 occupants, among them some cancer specialist who had traveled to Moab early that day to provide cancer screening, cancer treatment, and other medical services to citizens in Moab, were killed.
Probable cause:
The pilot’s failure to maintain terrain clearance during takeoff for undetermined reasons.
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 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 Beechcraft A100 King Air in Chibougamau: 2 killed

Date & Time: Oct 25, 2007 at 0859 LT
Type of aircraft:
Operator:
Registration:
C-FNIF
Flight Type:
Survivors:
No
Schedule:
Val d’Or – Chibougamau
MSN:
B-178
YOM:
1973
Flight number:
CRQ501
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1800
Captain / Total hours on type:
122.00
Copilot / Total flying hours:
1022
Copilot / Total hours on type:
71
Circumstances:
The Beechcraft A100 (registration C-FNIF, serial number B-178), operated by Air Creebec Inc. on flight CRQ 501, was on a flight following instrument flight rules between Val-d’Or, Quebec, and Chibougamau/Chapais, Quebec, with two pilots on board. The aircraft flew a non-precision approach on Runway 05 of the Chibougamau/Chapais Airport, followed by a go-around. On the second approach, the aircraft descended below the cloud cover to the left of the runway centreline. A right turn was made to direct the aircraft towards the runway, followed by a steep left turn to line up with the runway centreline. Following this last turn, the aircraft struck the runway at about 500 feet from the threshold. A fire broke out when the impact occurred and the aircraft continued for almost 400 feet before stopping about 50 feet north of the runway. The first responders tried to control the fire using portable fire extinguishers but were not successful. The Chibougamau and Chapais fire departments arrived on the scene at about 0926 eastern daylight time, which was about 26 minutes after the crash. The aircraft was destroyed by the fire. The two pilots suffered fatal injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was configured late for the approach, resulting in an unstable approach condition.
2. The pilot flying carried out a steep turn at a low altitude, thereby increasing the load factor. Consequently, the aircraft stalled at an altitude that was too low to allow the pilot to carry out a stall recovery procedure.
Findings as to Risk:
1. The time spent programming the global positioning system reduced the time available to manage the flight. Consequently, the crew did not make the required radio communications on the mandatory frequency, did not activate the aircraft radio control of aerodrome lighting (ARCAL), did not make the verbal calls specified in the standard operating procedures (SOPs), and configured the aircraft for the approach and landing too late.
2. During the second approach, the aircraft did a race-track pattern and descended below the safe obstacle clearance altitude, thereby increasing the risk of a controlled flight into terrain. The crew’s limited instrument flight rules (IFR) experience could have contributed to poor interpretation of the IFR procedures.
3. Non-compliance with communications procedures in a mandatory frequency area created a situation in which the pilots of both aircraft had poor knowledge of their respective positions, thereby increasing the risk of collision.
4. The pilot-in-command monitored approach (PICMA) procedure requires calls by the pilot not flying when the aircraft deviates from pre-established acceptable tolerances. However, no call is required to warn the pilot flying of an approaching steep bank.
5. The transfer of controls was not carried out as required by the PICMA procedure described in the SOPs. The transfer of controls at the co-pilot’s request could have taken the pilot-in-command by surprise, leaving little time to choose the best option.
6. Despite their limited amount of IFR experience in a multiple crew working environment, the two pilots were paired. Nothing prohibited this. Although the crew had received crew resource management (CRM) training, it still had little multiple crew experience and consequently little experience in applying the basic principles of CRM.
Other Findings:
1. The emergency locator transmitter (ELT) had activated after the impact but due to circuit board damage its transmission power was severely limited. This situation could have had serious consequences had there been any survivors.
2. The Chibougamau/Chapais airport does not have an aircraft rescue and firefighting service. Because the fire station is 23 kilometres from the airport, the firefighters arrived at the scene 26 minutes after the accident.
3. Although this accident does not meet the criteria of a controlled flight into terrain (CFIT), it nonetheless remains that a stabilized constant descent angle (SCDA) non-precision approach (NPA) would have provided an added defence tool to supplement the SOPs.
4. After the late call within the mandatory frequency (MF) area, the specialist at the Québec flight information centre asked the crew about its familiarity with the MF area while the aircraft was in a critical phase of the first approach, which was approaching the minimum descent altitude (MDA). This situation could have distracted the flight crew while they completed important tasks.
5. The standard checklist used by the flight crew made no reference to the enhanced ground proximity warning system (EGPWS). Therefore, the crew was not prompted to check it to ensure that it was properly activated before departure.
Final Report: