Crash of a Cessna 425 Conquest I in Harbor Springs

Date & Time: Jan 12, 2007 at 1830 LT
Type of aircraft:
Registration:
N425TN
Flight Type:
Survivors:
Yes
Schedule:
Toledo - Harbor Springs
MSN:
425-0196
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1991
Captain / Total hours on type:
60.00
Aircraft flight hours:
2345
Circumstances:
The pilot reported that during cruise descent the airplane accumulated about 1/2-to 3/4-inch of rime ice between 8,000 and 6,000 feet. During the approach, the pilot noted that a majority of the ice had dissipated off the leading edge of both wings, although there was still trace ice on the aft-portion of the wing deice boots. The pilot maintained an additional 20 knots during final approach due to gusting winds from the north-northwest. He anticipated there would be turbulence caused by the surrounding topography and the buildings on the north side of the airport. While on short final for runway 28, the pilot maintained approximately 121 knots indicated airspeed (KIAS) and selected flaps 30-degrees. He used differential engine power to assist staying on the extended centerline until the airplane crossed the runway threshold. After crossing the threshold, the pilot began a landing flare and the airspeed slowed toward red line (92 KIAS). Shortly before touchdown, the airplane "abruptly pitched up and was pushed over to the left" and flight control inputs were "only marginally effective" in keeping the wings level. The airplane drifted off the left side of the runway and began a "violent shuddering." According to the pilot, flight control inputs "produced no change in aircraft heading, or altitude." The pilot advanced the engine throttles for a go-around as the left wing impacted the terrain. The airplane cartwheeled and subsequently caught fire. No pre-impact anomalies were noted with the airplane's flight control systems and deice control valves during a postaccident examination. No ice shapes were located on the ground leading up to the main wreckage. The reported surface wind was approximately 4 knots from the north-northwest.
Probable cause:
The pilot's failure to maintain aircraft control and adequate airspeed during landing flare. Contributing to the accident was the aerodynamic stall/mush encountered at a low altitude.
Final Report:

Crash of a Learjet 35A in Columbus

Date & Time: Jan 10, 2007 at 0330 LT
Type of aircraft:
Operator:
Registration:
N40AN
Flight Type:
Survivors:
Yes
Schedule:
Jacksonville - Columbus
MSN:
35-271
YOM:
1979
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6400
Captain / Total hours on type:
1700.00
Copilot / Total flying hours:
3500
Copilot / Total hours on type:
600
Aircraft flight hours:
20332
Circumstances:
The airplane was substantially damaged during an in-flight recovery after the captain attempted an intentional aileron roll maneuver during cruise flight and lost control. The cargo flight was being operated at night under the provisions of 14 CFR Part 135 at the time of the accident. The captain reported the airplane was "functioning normally" prior to the intentional aileron roll maneuver. The captain stated that the "intentional roll maneuver got out of control" while descending through flight level 200. The captain reported that the airplane "over sped" and experienced "excessive G-loads" during the subsequent recovery. The copilot
reported that the roll maneuver initiated by the captain resulted in a "nose-down unusual attitude" and a "high speed dive." Inspection of the airplane showed substantial damage to the left wing and elevator assembly.
Probable cause:
The pilot's failure to maintain aircraft control during an inflight maneuver which resulted in the design stress limits of the airplane being exceeded. A factor was the excessive airspeed
encountered during recovery.
Final Report:

Crash of a Learjet 24F near Guadalajara: 2 killed

Date & Time: Jan 9, 2007 at 2323 LT
Type of aircraft:
Operator:
Registration:
N444TW
Flight Type:
Survivors:
No
Site:
Schedule:
Laredo – Guadalajara
MSN:
24-348
YOM:
1977
Flight number:
AJI878
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On January 9, 2007, at 2323 central standard time, a Gates Learjet model 24F airplane, N444TW, serial number 348, was destroyed upon impact with terrain, about 18.8 nautical miles east of Guadalajara, State of Jalisco, in the Republic of Mexico. The airline transport-rated pilot and the commercial pilot functioning as first officer were fatally injured. The airplane was registered to the Sierra American Corporation of Wilmington, Delaware, and was being operated by Ameristar Jet Charter, Inc., of Addison, Texas, as Ameristar flight 878, a Title 14 Code of Federal Regulations Part 135 on-demand cargo flight. Night visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed for the flight from Laredo, Texas. The cargo flight had originated in Laredo, Texas, at about 2210, with the Don Miguel Hidalgo International Airport (MMGL) near Guadalajara, Mexico, as its intended destination. Mexican Air Traffic Control personnel reported that the flight had approached MMGL from the north. At 2313, Guadalajara Approach Control cleared the flight to descend to 12,000 feet, provided an altimeter setting of 30.28, and told the flight to expect radar vectors for the ILS runway 28 approach to MMGL. After being provided a vector of 190 to intercept the localizer for the ILS runway 28 approach, there were communications between the flight and the controller to clarify which runway was active, and at 2318:00, the flight was given a right turn to a heading of 200 degrees. At 2318:56 the flight was cleared to descend to 10,000 feet, and at 2320:38, the flight was cleared to descend to 9,000 feet. The airplane was last observed on radar descending through 9,200 feet, while crossing the GDL VOR 085 degree radial.
Probable cause:
Controlled flight into terrain.

Crash of a BAe 3112 Jetstream 31 in Fort Saint John

Date & Time: Jan 9, 2007 at 1133 LT
Type of aircraft:
Operator:
Registration:
C-FBIP
Survivors:
Yes
Schedule:
Grande Prairie – Fort Saint John
MSN:
820
YOM:
1988
Flight number:
PEA905
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13000
Captain / Total hours on type:
300.00
Copilot / Total flying hours:
275
Copilot / Total hours on type:
20
Circumstances:
The aircraft was conducting an instrument approach to Runway 29 at Fort St. John, British Columbia, on a scheduled instrument flight rules flight from Grande Prairie, Alberta. At 1133 mountain standard time, the aircraft touched down 320 feet short of the runway, striking approach and runway threshold lights. The right main and nose landing gear collapsed and the aircraft came to rest on the right side of the runway, 380 feet from the threshold. There were no injuries to the 2 pilots and 10 passengers. At the time of the occurrence, runway visual range was fluctuating between 1800 and 2800 feet in snow and blowing snow, with winds gusting to 40 knots.
Probable cause:
Findings as to Causes and Contributing Factors:
1. A late full flap selection at 300 feet above ground level (agl) likely destabilized the aircraft’s pitch attitude, descent rate and speed in the critical final stage of the precision approach, resulting in an increased descent rate before reaching the runway threshold.
2. After the approach lights were sighted at low altitude, both pilots discontinued monitoring of instruments including the glide slope indicator. A significant deviation below the optimum glide slope in low visibility went unnoticed by the crew until the aircraft descended into the approach lights.
Finding as to Risk:
1. The crew rounded the decision height (DH) figure for the instrument landing system (ILS) approach downward, and did not apply a cold temperature correction factor. The combined error could have resulted in a descent of 74 feet below the DH on an ILS approach to minimums, with a risk of undershoot.
Other Finding:
1. The cockpit voice recorder (CVR) was returned to service following an intelligibility test that indicated that the first officer’s hot boom microphone intercom channel did not record. Although the first officer voice was recorded by other means, a potential existed for loss of information, which was key to the investigation.
Final Report:

Crash of an Antonov AN-26B-100 in Balad: 34 killed

Date & Time: Jan 9, 2007 at 0702 LT
Type of aircraft:
Operator:
Registration:
ER-26068
Survivors:
Yes
Schedule:
Adana – Balad
MSN:
113 08
YOM:
1981
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
30
Pax fatalities:
Other fatalities:
Total fatalities:
34
Circumstances:
The aircraft was performing a charter flight from Adana, Turkey, to Balad AFB (located 70 km north of Baghdad), carrying 30 workers coming from Moldova, Russia, Turkey and Ukraine, on behalf of the Turkish Company Kulak specialized in reconstruction projects. The aircraft departed Adana Airport at 0600LT for a 90 minutes flight. On approach, the crew encountered poor visibility due to foggy conditions. Unable to locate the runway, the captain decided to initiate a go-around procedure. Few minutes later, while attempting a second approach, the aircraft descended too low and crashed 2,5 km short of runway, bursting into flames. A passenger was seriously injured while 34 other occupants were killed.
Probable cause:
The cause of the accident and the exact position of the aircraft during the last segment could not be determined with certainty as the FDR was not in the aircraft at the time of the accident.

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 Piper PA-31-310 Navajo in Matambwe: 1 killed

Date & Time: Jan 5, 2007 at 0902 LT
Type of aircraft:
Registration:
5H-MUX
Survivors:
Yes
Schedule:
Dar es Salaam – Matambwe
MSN:
31-627
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1700
Circumstances:
The aircraft was carrying tourists, including the organizer of the trip to Matambwe. These passengers included five adults, a boy of sixteen, three girls of eleven, five and four years. There was also an infant of 11 months. This trip was arranged by a company called Tent with a View Safaris, which owns a camp at Matambwe in the Selous Game Reserve. According to the company, initially two aircraft were organized to transport the passengers to Matambwe. The booking was made through a telephone call to an operator called Wings of Zanzibar, who advised them to go to Terminal I of Julius Nyerere International Airport in Dar es Salaam. However, when the passengers arrived at the Wings of Zanzibar office at the airport, they found it closed. When Wings of Zanzibar was contacted on the telephone, a pilot employed by another company, DJB Ltd, was alerted to meet them. The pilot initially took them to the offices of DJB for payment. He also recommended that one aircraft would suffice for the trip. According to the pilot, he believed that the three children were small enough to sit on their parents’ laps. The passengers had little baggage. The aircraft, a Piper PA31-310 Navajo, took off from Dar es Salaam at 0825 hours and cruised at FL 65. The flight to Matambwe was uneventful and the aircraft was overhead the airstrip at 0902 hours. The pilot over flew the airstrip to alert the camp staff and check for wind and animals, a common procedure for landing in the Game Reserve airstrips. He also made another low run over the runway to ascertain its condition. Eye witnesses and passengers confirmed that the pilot made an overshoot, having flown very low attempting to land. The pilot was not sure of the runway condition because he had not flown into this airfield for a long time. In addition, before embarking on this trip, he had requested information on the runway condition from another pilot who had recently flown into the airstrip. He was told that the runway was usable. Finally, the pilot decided to land. He chose to land on runway 28 with full flaps. He touched down about two hundred and fifty meters beyond the beginning of the usable part of the runway and braked normally. After rolling for some time, he realized that the aircraft would not be able to stop before the end of the remaining length of the runway. With about another two hundred and fifty meters ahead, the pilot initiated a go round believing he had sufficient runway length remaining to gather enough speed for takeoff and climb out. He immediately increased power and initiated the go around. It is at this moment that the aircraft became airborne with no speed increase. The aircraft flew straight and level at full power without gaining height. It subsequently started chopping small tree tops for about two hundred meters beyond the end of the runway and then started to lose height. As it did so, the starboard wing collided with a large tree and the aircraft rotated through 180 degrees before coming to rest. The main wreckage settled below the impact tree and the passengers evacuated immediately. The wreckage caught fire immediately after the last passenger was evacuated. It burned completely, leaving only the tail fin and parts of the engine nacelle. When staff members from Tent with a View Camp located at Matambwe arrived, the aircraft was burning fiercely. They assisted in moving the occupants to a safer location, far from the burning wreckage and in administering first aid. The aircraft occupants were later treated at a local dispensary before being transported to a hospital in Dar es Salaam. One passenger died in the hospital four hours after the accident. Two passengers were treated for serious injuries. The injuries to the rest of the occupants were minor.
Probable cause:
The accident was caused by the aircraft colliding with trees just beyond the end of the runway. The failure to select the correct flap position for the take off, the lack of proficiency training, insufficient flight preparation and lack of real time information on the runway at Matambwe were contributory factors.
Final Report:

Crash of a Rockwell Sabreliner 40R in Culiacán Rosales: 2 killed

Date & Time: Dec 30, 2006 at 1730 LT
Type of aircraft:
Operator:
Registration:
XA-TNP
Flight Type:
Survivors:
No
Site:
Schedule:
La Paz – Culiacán Rosales
MSN:
265-62
YOM:
1962
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Following an uneventful cargo flight from La Paz (Mexico), the crew was approaching Culiacán Rosales-Federal de Bachigualato Airport. On final, the aircraft crashed onto several houses located less than one km from runway the threshold. Both pilots were killed while there were no casualties on the ground despite several houses were destroyed by fire. For unknown reasons, the crew was completing the approach at an unsafe altitude.

Crash of a Beechcraft 99 in Rapid City

Date & Time: Dec 29, 2006 at 0200 LT
Type of aircraft:
Operator:
Registration:
N99TH
Flight Type:
Survivors:
Yes
Schedule:
Pierre - Rapid City
MSN:
U-155
YOM:
1974
Flight number:
AIP408
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3652
Captain / Total hours on type:
3069.00
Aircraft flight hours:
39795
Circumstances:
The airplane was on an instrument flight rules flight in night instrument meteorological conditions when the accident occurred. The airplane had been cleared for an ILS approach and the pilot elected to use a non-published procedure to intercept the final approach. After becoming established on the final approach, the airplane impacted the ground about 7 miles from the destination airport at an elevation approximately the same as the airport elevation. Flight inspections of the instrument approach performed prior to and subsequent to the accident revealed satisfactory performance of both the localizer and glideslope functions. The number one altimeter setting did not match the altimeter setting that was current at the time of the accident. Post accident examination of the altimeters revealed that the number one altimeter read 360 feet high. No determination was made as to whether the discrepancy existed prior to impact. However, the pilot did not report any pre-flight discrepancies with regard to the airplane's altimeters. No other anomalies were found or reported with regard to the airplane's structure or systems.
Probable cause:
The pilot's failure to follow the published instrument approach procedure which contributed to his failure to maintain altitude and clearance from terrain during the instrument approach. A factor was the night light condition.
Final Report:

Crash of a Cessna 414 Chancellor in Johnstown: 2 killed

Date & Time: Dec 26, 2006 at 1555 LT
Type of aircraft:
Operator:
Registration:
N400CS
Flight Type:
Survivors:
No
Schedule:
Morgantown - Teterboro
MSN:
414-0613
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3547
Aircraft flight hours:
5904
Circumstances:
The airplane encountered in-flight icing, and the pilot diverted to an airport to attempt to knock the ice off at a lower altitude. During the instrument approach, the pilot advised the tower controller of the ice, and that it depended on whether or not the ice came off the airplane if she would land. As the airplane broke out of the clouds, it appeared to tower personnel to be executing a missed approach; however, it suddenly "dove" for the runway. The tower supervisor noticed that the landing gear were not down, and at 75 to 100 feet above the runway, advised the pilot to go around. The airplane continued to descend, and by the time it impacted the runway, the landing gear were only partially extended, and the propellers and airframe impacted the pavement. The pilot then attempted to abort the landing. The damaged airplane became airborne, climbed to the right, stalled, and nosed straight down into the ground.
Probable cause:
The pilot's improper decision to abort the landing with a damaged airplane. Contributing to the accident were the damage from the airplane's impact with the runway, the pilot's failure to lower the landing gear prior to the landing attempt, and the in-flight icing conditions.
Final Report: