Crash of a Cessna 550 Citation II off Milwaukee: 6 killed

Date & Time: Jun 4, 2007 at 1600 LT
Type of aircraft:
Operator:
Registration:
N550BP
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Milwaukee - Detroit
MSN:
550-0246
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
14000
Aircraft flight hours:
4402
Circumstances:
On June 4, 2007, about 1600 central daylight time, a Cessna Citation 550, N550BP, impacted Lake Michigan shortly after departure from General Mitchell International Airport, Milwaukee, Wisconsin (MKE). The two pilots and four passengers were killed, and the airplane was destroyed. The airplane was being operated by Marlin Air under the provisions of 14 Code of Federal Regulations Part 135 and departed MKE about 1557 with an intended destination of Willow Run Airport, near Ypsilanti, Michigan. At the time of the accident flight, marginal visual meteorological conditions prevailed at the surface, and instrument meteorological conditions prevailed aloft; the flight operated on an instrument flight rules flight plan.
Probable cause:
The pilots’ mismanagement of an abnormal flight control situation through improper actions, including failing to control airspeed and to prioritize control of the airplane, and lack of crew coordination. Contributing to the accident were Marlin Air’s operational safety deficiencies, including the inadequate checkrides administered by Marlin Air’s chief pilot/check airman, and the Federal Aviation Administration’s failure to detect and correct those deficiencies, which placed a pilot who inadequately emphasized safety in the position of company chief pilot and designated check airman and placed an ill-prepared pilot in the first officer’s seat.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Grand Lac Germain: 1 killed

Date & Time: Apr 1, 2007 at 0700 LT
Operator:
Registration:
C-FTIW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Seven Islands - Wabush
MSN:
31-7752123
YOM:
1977
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5475
Captain / Total hours on type:
790.00
Circumstances:
The aircraft, operated by Aéropro, was on a visual flight rules (VFR) flight from Sept-Îles, Quebec, to Wabush, Newfoundland and Labrador. The pilot, who was the sole occupant, took off around 0630 eastern daylight time. Shortly before 0700, the aircraft turned off its route and proceeded to Grand lac Germain to fly over the cottage of friends. Around 0700, the aircraft overflew the southeast bay of Grand lac Germain. The pilot then overflew a second time. The aircraft proceeded northeast and disappeared behind the trees. A few seconds later, the twin-engine aircraft crashed on the frozen surface of the lake. The pilot was fatally injured; the aircraft was destroyed by impact forces.
Probable cause:
Finding as to Causes and Contributing Factors:
1. The aircraft stalled at an altitude that was too low for the pilot to recover.
Findings as to Risk:
1. The aircraft was flying at an altitude that could lead to a collision with an obstacle and that did not allow time for recovery.
2. The steep right bank of the aircraft considerably increased the aircraft’s stall speed.
3. The form used to record the pilot’s flight time, flight duty time, and rest periods had not been updated for over a month; this did not allow the company manager to monitor the pilot’s hours.
4. At the time of the occurrence, the Aéropro company operations manual did not make provision for the restrictions on daytime VFR flights prescribed in Section 703.27 of the Canadian Aviation Regulations.
Other Findings:
1. The fact that the aircraft was not equipped with a flight data recorder (FDR) or a cockpit voice recorder (CVR) limited the information available for the investigation and limited the scope of the investigation.
2. Since the aircraft was on a medical evacuation (MEDEVAC) flight, the company mistakenly advised the search and rescue centre that there were two pilots on board the aircraft when it was reported missing.
Final Report:

Crash of a Beechcraft 200 Super King Air in Bozeman: 3 killed

Date & Time: Feb 6, 2007 at 2104 LT
Operator:
Registration:
N45MF
Flight Type:
Survivors:
No
Schedule:
Great Falls - Bozeman
MSN:
BB-234
YOM:
1977
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
17608
Captain / Total hours on type:
1318.00
Aircraft flight hours:
5992
Circumstances:
The cross-country flight was on an instrument flight rules (IFR) flight plan, approximately 42 nautical miles from the tower-controlled destination airport, when the pilot was cleared for the visual approach. Dark night visual meteorological conditions prevailed, and there was an overcast layer of clouds at 11,000 feet. After the en route radar service was terminated, the pilot contacted the local control tower and made a garbled and partially unintelligible transmission. Shortly after the time of the transmission, local law enforcement personnel received reports of a downed aircraft. The wreckage was located later that evening approximately 80 feet below the peak of a ridge that rose to an elevation of approximately 5,700 feet. From the initial point of contact with terrain, the debris path was scattered over the crest of the ridge and continued down the opposing side, in a south-southeast direction, toward the airport. The ridge was the highest obstruction between the accident location and the destination airport. The airport is located in a large valley and is surrounded by rising mountainous terrain. At night, clouds and terrain are difficult for pilots to see, and a gradual loss of visual cues can occur as flight is continued toward darker terrain. Additionally, the horizon is less visible and less distinct at night than during the day. Because the pilot was descending the airplane over rural, mountainous terrain that provided few visual ground reference cues, and because the overcast cloud layer would have prevented moonlight from illuminating the terrain, it is likely that the pilot did not see the rising terrain as the airplane continued toward it. The airplane was equipped with an Enhanced Ground Proximity Warning System; however, impact damage to the unit precluded post accident testing. It is not known how the unit was configured during the flight or what type of alerts the pilot received prior to impact. Post accident examination of the wreckage, to include both engines, did not disclose evidence of a mechanical malfunction prior to impact. Additionally, no evidence was found to suggest an in-flight structural failure.
Probable cause:
The pilot's failure to maintain an adequate altitude and descent rate during a night visual approach. Dark night conditions and mountainous terrain are factors in the accident.
Final Report:

Crash of a Cessna 550 Citation II in Butler

Date & Time: Jan 24, 2007 at 0905 LT
Type of aircraft:
Operator:
Registration:
N492AT
Flight Type:
Survivors:
Yes
Schedule:
Winchester - Butler
MSN:
550-0472
YOM:
1983
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
22700
Captain / Total hours on type:
1200.00
Copilot / Total flying hours:
1758
Copilot / Total hours on type:
85
Aircraft flight hours:
10735
Circumstances:
The Citation 550 was being repositioned for an air ambulance transportation flight, and was on approach to land on a 4,801-foot-long, grooved, asphalt runway. The airplane was being flown manually by the copilot, who reported that the landing approach speed (Vref) was 106 knots. The pilot-in-command (PIC) estimated that the airplane "broke out" of the clouds about two miles from the runway. Both pilots stated that the airplane continued to descend toward the runway, while on the glide slope and localizer. Neither pilot could recall the airplane's touchdown point on the runway, or the speed at touchdown. Witnesses observed the airplane, "high and fast" as it crossed over the runway threshold. The airplane touched down about halfway down the runway, and continued off the departure end. It then struck a wooden localizer antenna platform, and the airport perimeter fence, before crossing a road, and coming to rest about 400 feet from the end of the runway. Data downloaded from the airplane's Enhanced Ground Proximity Warning System (EGPWS) revealed that the airplane's groundspeed at touchdown was about 140 knots. Review of the cockpit voice recorder suggested that the PIC failed to activate the airplane's speed brake upon touchdown. Braking action was estimated to be "fair" at the time of the accident, with about 1/4 to 1/2 inches of loose, "fluffy" snow on the runway. The PIC reported that he thought the runway might be covered with an inch or two of snow, which did not concern him. The copilot reported encountering light snow during the approach. Both pilots stated that they were not aware of any mechanical failures, or system malfunctions during the accident; nor were any discovered during post accident examinations. According to the airplane flight manual, the conditions applicable to the accident flight prescribed a Vref of 110 knots, with a required landing distance on an uncontaminated runway of approximately 2,740 feet. The prescribed landing distance on a runway contaminated with 1-inch of snow, at a Vref of 110 knots was approximately 5,800 feet. At Vref + 10 knots, the required landing distance increased to about 7,750 feet.
Probable cause:
The copilot's failure to maintain the proper airspeed, and failure to obtain the proper touchdown point, and the pilot-in-command's inadequate supervision, which resulted in an overrun. Contributing to the accident was the PIC's failure to activate the speed brake upon touchdown and the snow contaminated runway.
Final Report:

Crash of a Beechcraft A100 King Air in Sandy Bay: 1 killed

Date & Time: Jan 7, 2007 at 2002 LT
Type of aircraft:
Operator:
Registration:
C-GFFN
Flight Type:
Survivors:
Yes
Schedule:
La Ronge – Sandy Bay
MSN:
B-190
YOM:
1974
Flight number:
TW350
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
8814
Captain / Total hours on type:
449.00
Copilot / Total flying hours:
672
Copilot / Total hours on type:
439
Aircraft flight hours:
17066
Circumstances:
The aircraft departed La Ronge, Saskatchewan, at 1930 central standard time under instrument flight rules to Sandy Bay, with two flight crew members and two emergency medical technicians aboard. TW350 was operating under Part VII, Subpart 3, Air Taxi Operations, of the Canadian Aviation Regulations. At 1948, air traffic control cleared TW350 out of controlled airspace via the Sandy Bay Runway 05 non-directional beacon approach. The crew flew the approach straight-in to Runway 05 and initiated a go-around from the landing flare. The aircraft did not maintain a positive rate of climb during the go-around and collided with trees just beyond the departure end of the runway. All four occupants survived the impact and evacuated the aircraft. The captain died of his injuries before rescuers arrived. Both emergency medical technicians were seriously injured, and the first officer received minor injuries. The aircraft sustained substantial damage from impact forces and was subsequently destroyed by a post-impact fire. The accident occurred at 2002 during the hours of darkness.
Probable cause:
Findings as to Risk:
1. Some Canadian Air Regulations (CARs) subpart 703 air taxi and subpart 704 commuter operators are unlikely to provide initial or recurrent CRM training to pilots in the absence of a regulatory requirement to do so. Consequently, these commercial pilots may be unprepared to avoid, trap, or mitigate crew errors encountered during flight.
2. Transport Canada (TC) Prairie and Northern Region (PNR) management practices regarding the June 2006 replacement of the regional combined audit program, in order to manage safety management system (SMS) workload, did not conform to TC’s risk management decision-making policies. Reallocation of resources without assessment of risk could result in undetected regulatory non-compliance.
3. Although TC safety oversight processes identified the existence of supervisory deficiencies within TWA, the extent of the deficiencies was not fully appreciated by the PNR managers because of the limitations of the oversight system in place at that time.
4. It is likely that the National Aviation Company Information System (NACIS) records for other audits include inaccurate information resulting from data entry errors and wide use of the problematic audit tracking form, reducing the effectiveness of the NACIS as a management tracking system.
5. Self-dispatch systems rely on correct assessment of operational hazards by pilots, particularly in the case of unscheduled commercial service into uncertified aerodromes. Unless pilots are provided with adequate decision support tools, flights may be dispatched with defences that are less than adequate.
6. TWA King Air crews did not use any standard practice in applying cold temperature altitude corrections. Inconsistent application of temperature corrections by flight crews can result in reduction of obstacle clearance to less than the minimum required and reduced safety margins.
7. The practice of not visually verifying wind/runway conditions at aerodromes where this information is otherwise unavailable increases the risk of post-touchdown problems.
8. The company dispatched flights to Sandy Bay without a standard means for crews to deal with non-current altimeter settings. Use of non-current or inappropriate altimeter settings can reduce minimum obstacle clearance and safety margins.
9. The crew was likely unaware of their ¼ nautical mile (nm) error in the aircraft position in relation to the runway threshold resulting from use of the global positioning system (GPS). Unauthorized and informal use of the GPS by untrained crews during instrument flight rules (IFR) approaches can introduce rather than mitigate risk.
10. Widespread adaptations by the King Air pilots resulted in significant deviations from the company’s SOPs, notwithstanding the company’s disciplinary policy.
11. In a SMS environment, inappropriate use of punitive actions can result in a decrease in the number of hazards and occurrences reported, thereby reducing effectiveness of the SMS.
12. Pilot workload is increased and decision making becomes more complicated where limited visual cues are available for assessing aircraft orientation relative to runway and surrounding terrain.
13. Aerodromes with limited visual cues and navigational aids are not explicitly identified in flight information publications as hazardous for night/IFR approaches. Passengers and crews will continue to be exposed to this hazard unless aircraft and aerodrome operators carry out risk assessments to identify them and take mitigating action.
14. To properly assess applicants for pilot positions, operators need access to information on experience and performance that is factual, objective, and (preferably) standardized. Because some employers are unprepared to provide this information—fearing legal action—this may lead to the appointment of pilots to positions for which they are unsuited, thereby compromising safety.
Other Findings:
1. TWA’s safety management system was not yet capable or expected to be capable of detecting, analyzing, and mitigating the risks presented by the hazards underlying this occurrence.
2. The first officer and captain met competency standards on the completion of their initial flight training before they began employment as line pilots.
3. It is very likely that the captain became the pilot flying for the remaining 20 seconds of the flight. The scenario that neither pilot was controlling the aircraft at that time is considered very unlikely.
Final Report:

Crash of a Beechcraft C90B King Air in Besançon: 4 killed

Date & Time: Oct 19, 2006 at 0042 LT
Type of aircraft:
Operator:
Registration:
F-GVPD
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Besançon – Amiens
MSN:
LJ-1321
YOM:
1992
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3500
Captain / Total hours on type:
450.00
Copilot / Total flying hours:
4000
Aircraft flight hours:
3501
Circumstances:
The twin engine aircraft was engaged in an ambulance flight from Besançon to Amiens with 2 surgeons, one pilot and one operator agent. Following a course of 950 metres on runway 23 at Besançon-La Vèze Airport by night, the aircraft lifted off. With a low climb gradient, the aircraft collided with trees and crashed in a wooded area located 250 metres past the runway end, bursting into flames. The aircraft was totally destroyed and all four occupants were killed. Both surgeons were en route to Amiens in order to a lever harvesting.
Probable cause:
The lack of flight recorders made it impossible to trace the chain of events on board the aircraft. As a result, the causes of the accident could not be determined with precision. However, at least two scenarios could simultaneously explain the length of the takeoff roll and the low height after rotation: a lack of control of the airplane by the pilot, either by poor adjustment of the elevator trim or because his attention would have been focused inside the cockpit by any event, without reaction from the pilot passenger seated on the right. This scenario is consistent with his relative inexperience with the type of aircraft. The second scenario could be based on an inappropriate decision to seek significant speed after take-off or improvised instruction, neither pilot being aware of the obstacle constraints of the airfield. The significant obscurity, the operating specificities in medical transport and the presence of a second pilot with a status and role not provided for in the operations manual, without there being therefore any crew or distribution of tasks within the company's crew, are likely contributing factors. The 48-year-old pilot had a total of 3,500 flight hours, including 450 on type. The company agent who was seating on the right was a professional pilot who did not have a license on this type of aircraft and took advantage of the flight, in agreement with the corporate management, to acquire experience in a view to his future qualification on this type of airplane. He had a total of more than 4,000 flight hours.
Final Report:

Crash of an IAI-1124 Westwind in Moss Town

Date & Time: May 24, 2006 at 0055 LT
Type of aircraft:
Operator:
Registration:
N475AT
Flight Type:
Survivors:
Yes
Schedule:
San Juan – Norfolk
MSN:
270
YOM:
1979
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
At 0444Z On May 24 2006, Miami Centre (George Town Sector) informed Nassau ATC That Lifeguard Flight N475AT, a Westwind Jet (WW-1124), en-route from San Juan, Puerto Rico to Norfolk, Virginia reported that it had developed generator problems and the aircraft was looking to land at the nearest airport to its position. Miami Air Traffic Center vectored the aircraft to Exuma International Airport at Great Exuma, Bahamas, as that was the nearest airport. Attempts were made by Nassau ATC to contact the authorities at Exuma International Airport to have the runway lights turned on. At 0454Z, Miami ATC reported loss of contact with the aircraft; therefore, N475AT proceeded with an emergency landing, before Miami ATC could give further instructions. The uncontrolled aircraft came to rest approximately 800 feet beyond the end of runway 30 and approximately 300 feet right of the extended centre line of the runway. The aircraft landing gears were sheered off when the aircraft exited the runway, hence traveling into the clearing and then eventually into the bushes on the right side of the runway. The right wing of the aircraft collided with a mound of dirt, causing it to spin uncontrollably, resulting in it coming to rest on an easterly heading at an approximate 30 degree incline. The occupants were evacuated from the wreckage and received minor injuries while making their way thru the thick brush and shrubbery while being led to safety. All Crew members were ATP rated and both proficiency checks found to be were valid and current neither of the pilots was available for an interview at the time of the field investigation at Exuma International Airport.
Probable cause:
Findings and Probable Cause could not be determined as the aircraft was stripped of its components, instrumentations, manuals and CVR by the owners of the aircraft, without permission or authorization from the Accident Investigation Personnel (Department of Civil Aviation). Documents and manuals requested of the owners were never obtained. The help of the NTSB as well as the FAA were enlisted in an effort to retrieve documents from the owners. All attempts were fruitless.
Final Report:

Crash of a Cessna 414A Chancellor in Kahului: 3 killed

Date & Time: Mar 8, 2006 at 1913 LT
Type of aircraft:
Operator:
Registration:
N5601C
Flight Type:
Survivors:
No
Schedule:
Honolulu - Kahului
MSN:
414A-0113
YOM:
1978
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
3141
Aircraft flight hours:
8734
Circumstances:
The twin-engine medical transport airplane was on a positioning flight when the pilot reported a loss of power affecting one engine before impacting terrain 0.6 miles west of the approach end of the runway. The airplane was at 2,600 feet and in a shallow descent approximately 8 miles northwest of the airport when the pilot checked in with the tower and requested landing. Three and a half minutes later, the pilot reported that he had lost an engine and was in a righthand turn. Radar data indicated that the airplane was 2 miles southwest of the airport at 1,200 feet msl. The radar track continued to depict the airplane in a descent and in a right-hand turn, approximately 1.9 miles west of the approach end of the runway. The altitude fluctuated between 400 and 600 feet, the track turned right again, and stabilized on an approximate 100- degree magnetic heading, which put the airplane on a left base for the runway. The track entered a third right-hand turn at 500 feet. The pilot's last transmission indicated that one engine was not producing power. The last radar return was 6 seconds later at 200 feet, in the direct vicinity of where the wreckage was located. Using the radar track data, the average ground speed calculations showed a steady decrease from 134 knots at the time of the pilot's initial report of a problem, to 76 knots immediately before the airplane impacted terrain. The documented minimum controllable airspeed (VMC) for this airplane is 68 knots. The zero bank angle stall speed varied from 78 knots at a cruise configuration to 70 knots with the gear and flaps down. A sound spectrum study using recorded air traffic control communications concluded that one engine was operating at 2,630 rpm, and one engine was operating at 1,320 rpm. Propeller damage was consistent with the right engine operating at much higher power than the left engine at the time of impact, and both propellers were at or near the low pitch stops (not feathered). Examination and teardown of both engines did not reveal any evidence of mechanical malfunction. Investigators found that the landing gear was down and the flaps were fully deployed at impact. In this configuration, performance calculations showed that level flight was not possible with one engine inoperative, and that once the airspeed had decreased below minimum controllable airspeed (VMC), the airplane could stall, roll in the direction of the inoperative engine, and enter an uncontrolled descent. The pilot had been trained and had demonstrated a satisfactory ability to operate the airplane in slow flight and single engine landings. However, flight at minimum controllable airspeed with one engine inoperative was not practiced during training. The operator's training manual stated that during single engine training an objective was to ensure the pilot reduced drag; however, there was no procedure to accomplish this objective, and the ground training syllabus did not specifically address engine out airplane configuration performance as a dedicated topic of instruction. The operator's emergency procedures checklist and manufacturer's information manual clearly addressed the performance penalties of configuring the airplane with an inoperative engine, propeller unfeathered, the landing gear down, and/or the flaps deployed. The engine failure during flight procedure checklist and the engine inoperative go-around checklist, if followed, configure the airplane for level single engine flight by feathering the propeller, raising the flaps, and retracting the landing gear.
Probable cause:
The failure of the pilot to execute the published emergency procedures pertaining to configuring the airplane for single engine flight, which would have allowed him to maintain minimum controllable airspeed (VMC) and level flight. The pilot's failure to maintain minimum controllable airspeed (VMC) led to a stall and subsequent VMC roll at a low altitude. Contributing to the accident was the operator's inadequate pilot training in the single engine flight regime, and the loss of power from the left engine for undetermined reasons.
Final Report:

Crash of a Beechcraft A100 King Air in Sault Sainte Marie

Date & Time: Jan 2, 2006 at 0200 LT
Type of aircraft:
Operator:
Registration:
N700NC
Flight Type:
Survivors:
Yes
Schedule:
Traverse City – Sault Sainte Marie
MSN:
B-138
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7620
Captain / Total hours on type:
70.00
Aircraft flight hours:
13033
Circumstances:
The airplane, operated as an emergency medical flight, received substantial damage when it veered off the edge of runway 32 (5,235 feet long by 100 foot wide asphalt, slush and snow covered) and impacted a snow bank during landing roll at a non 14 CFR Part 139 airport. Night instrument meteorological conditions prevailed at the time of the accident. The pilot stated that during a non precision approach while two miles from the runway, he observed it to be completely covered in snow and slush. He continued the approach and upon touchdown the airplane decelerated in deep slush and veered to the left after a rollout of 1,200 feet. The pilot reported that prior to accepting the emergency medical flight, he obtained a weather briefing from a flight service station during which time no notices to airman (NOTAMs) existed that pertained to the destination airport. The pilot reported that he knew the airport was getting rain and was expecting the runway to be clear. He was surprised that the runway was covered with heavy slush. The airport manager stated that the runway was covered with wet, slushy snow as there had been periods of wet snow and rain that occurred late the previous day and evening of the accident. The airport weather observation recorded the presence of light snow in a period of approximately 24 hours before the accident. The pilot "wondered" why no NOTAM was issued relating to the runway condition. The Airport Facility Directory and the FAA's web site provides a list of 14 CFR Part 139 airports which are inherently required to issue NOTAMs. However, Advisory Circular 150/5200-28C states, the management of a public use airport is expected to make known, as soon as practical, any condition on or in the vicinity of an airport, existing or anticipated, that will prevent, restrict, or present a hazard during the arrival or departure of aircraft. Airport management is responsible for observing and reporting the condition of airport movement areas. Public notification is usually accomplished through the NOTAM system. The Aeronautical Information Manual, states that NOTAM information is information that could affect a pilot's decision to make a flight. It includes information such as airport or primary runway closures, changes in the status of navigational aids, ILS's, radar service availability, and other information essential to planned en route, terminal, or landing operations.
Probable cause:
The inadequate in-flight decision to continue the approach to land, directional control not maintained, and the contaminated runway. Contributing factors were flight to destination alternate not performed, a notice to airman not issued by airport personnel relating to snow/slush contamination of the runway, and the snow bank that the airplane impacted during the landing.
Final Report:

Crash of a Beechcraft A100 King Air in La Ronge

Date & Time: Dec 30, 2005 at 1500 LT
Type of aircraft:
Operator:
Registration:
C-GAPK
Flight Type:
Survivors:
Yes
Schedule:
Pinehouse Lake – La Ronge
MSN:
B-198
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
A Beechcraft A100 King Air, C-GAPK was inbound to La Ronge Airport, SK (YVC), from Pinehouse Lake on a medevac flight. On descent into La Ronge the crew noticed ice building on the wing leading edges. At approximately 6 miles back on final the crew operated the wing de-ice boots, however a substantial amount of residual ice remained after application of the boots. It was reported that in the landing flare at about 100 knots, the aircraft experienced an ice-induced stall from an altitude of about 20 feet followed by a hard landing. The right wing and nacelle buckled forward and downward from the landing impact forces to the extent that the right propeller struck the runway surface while the aircraft was taxiing off the runway.