Crash of a Beechcraft 200 Super King Air in Badiraguato

Date & Time: Mar 20, 2003
Operator:
Registration:
XC-ADP
Flight Type:
Survivors:
Yes
Schedule:
Hermosillo – Badiraguato
MSN:
BB-156
YOM:
1976
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Badiraguato Airport, the twin engine aircraft went out of control and veered off runway. It collided with rocks, lost its tail and came to rest. All five occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Beechcraft E90 King Air in Kremmling

Date & Time: Mar 19, 2003 at 1930 LT
Type of aircraft:
Operator:
Registration:
N711TZ
Flight Type:
Survivors:
Yes
Schedule:
Grand Junction – Kremmling
MSN:
LW-226
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10564
Captain / Total hours on type:
212.00
Aircraft flight hours:
8040
Circumstances:
The pilot reported that he maneuvered for a left hand downwind leg for landing from the east to west. The pilot set up his downwind leg at 8,400 feet mean sea level putting him at what would have been 1,000 feet above the airport elevation of 7,411 feet. The pilot reported it was very dark and he could see the airport, but could not see the terrain. The pilot reported that suddenly he saw the ground. The airplane impacted the terrain and came to rest. The pilot reported that the airplane was experiencing no malfunctions prior to the accident. The airplane accident site was on the snow-covered edge of a mountain ridge at an elevation of 8,489 feet. An examination of the airplane's systems revealed no anomalies. Published terminal procedures for the runway indicated high terrain of 8,739 feet south-southeast of the airport. The published airport diagram for the airport directs right traffic for the pattern to runway 27.
Probable cause:
The pilot's improper in-flight planning and his failure to maintain safe clearance from the high terrain. Factors contributing to the accident were the high terrain and the dark night.
Final Report:

Crash of a Grumman C-2A Greyhound at Cherry Point MCAS

Date & Time: Mar 12, 2003
Type of aircraft:
Operator:
Registration:
162153
Survivors:
Yes
MSN:
33
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Cherry Point MCAS, the aircraft went out of control, lost its undercarriage and both wings and came to rest, bursting into flames. There were no casualties.

Crash of a Fokker F27 Friendship 500RF in Kinston

Date & Time: Mar 8, 2003 at 1027 LT
Type of aircraft:
Operator:
Registration:
N712FE
Flight Type:
Survivors:
Yes
Schedule:
Greensboro - New Bern
MSN:
10613
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8130
Captain / Total hours on type:
1450.00
Copilot / Total flying hours:
2911
Copilot / Total hours on type:
955
Aircraft flight hours:
26665
Aircraft flight cycles:
28285
Circumstances:
According to the pilot, an unsafe right gear indication was received during the approach, and the control tower controller confirmed the right gear was not fully extended. On landing roll the right main landing gear collapsed and the airplane slid off of the runway. Examination of the right main landing gear revealed the drag brace was fractured. The fracture was located at the lower side of a transition from a smaller internal diameter on the upper piece to a larger internal diameter on the lower piece. The region of the fracture surface was flat and perpendicular to the tube longitudinal axis. The region had a smooth, curving boundary, also consistent with fatigue. The fatigue features emanated from multiple origins at the inner surface of the tube. The Federal Aviation Administration (FAA) issued an Airworthiness Directive (AD) requiring an inspections of main landing gear drag stay units. The AD was prompted by the fracture of a drag stay tube from fatigue cracking that initiated from an improperly machined transition radius at the inner surface of the tube. According to Fokker ,the Fokker F27 Mark 500 airplanes (such as the incident airplane) were not equipped with drag stay units having part number 200261001, 200485001, or 200684001. One tube, part number 200259300, had a change in internal diameter (stepped bore), and the other tube, part number 200485300, had a straight internal bore. AD 97-04-08 required an ultrasonic inspection to determine if the installed tube had a straight or stepped bore. A review of maintenance records revealed that the failed drag stay tube had accumulated 28, 285 total cycles.
Probable cause:
The fatigue failure of the main drag stay tube. A factor is no inspection procedure required.
Final Report:

Crash of a Piper PA-46-500TP Malibu Meridian in Albuquerque: 3 killed

Date & Time: Mar 7, 2003 at 1918 LT
Registration:
N522RF
Flight Type:
Survivors:
No
Schedule:
Scottsdale – Albuquerque
MSN:
46-97119
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1200
Aircraft flight hours:
365
Circumstances:
The pilot was performing a night, VFR traffic pattern, to a full stop at a non-towered airport in a turboprop aircraft. He entered the traffic pattern (6,800 feet; 1,000 feet AGL) on an extended downwind; radar data indicated that his ground-speed was 205 knots. Over the next 3 nautical miles on down wind, radar data indicated that he slowed to a ground-speed of 171 knots, lost approximately 500 feet of altitude, and reduced his parallel distance from the runway from 4,775 feet to 2,775 feet. Witnesses said that his radio transmissions on CTAF appeared normal. The two witnesses observed a bright blue flash, followed by a loss of contact with the airplane. Rescue personnel found a broken and downed static wire from a system of three sets of power transmission wires. The dark night precluded ground rescue personnel from locating the downed aircraft; a police helicopter found the airplane approximately 2 hours after the accident. The pilot had recently completed his factory approved annual flight training. His flight instructor said that the pilot was taught to fly a VFR traffic pattern at 1,500 feet AGL (or 500 feet above piston powered aircraft), enter the downwind leg from a 45 degree leg, and fly parallel to the downwind approximately 1 to 1.5 nautical miles separation from it. His speed on downwind should have been 145 to 150 knots indicated, with 90 to 95 knots on final for a stabilized approach. The flight instructor said that the base turn should be at a maximum bank angle of 30 degrees. Radar data indicates that the pilot was in a maximum descent, while turning base to final, of 1,800 to 1,900 feet per minute with an airspeed on final of 145 to 150 knots. His maximum bank angle during this turn was calculated to have been more than 70 degrees. The separated static wire was located 8,266.5 feet from the runway threshold, and was approximately 30 feet higher than the threshold. Post-accident examinations of the airplane and its engine revealed no anomalies which would have precluded normal operations prior to impact.
Probable cause:
The pilot's unstabilized approach and his failure to maintain obstacle clearance. Contributing factors were the dark night light condition, and the static wires.
Final Report:

Crash of a De Havilland DHC-2 Beaver off Whitsunday Island

Date & Time: Mar 6, 2003 at 1615 LT
Type of aircraft:
Operator:
Registration:
VH-AQV
Flight Type:
Survivors:
Yes
Schedule:
Hamilton Island - Whitsunday Island
MSN:
1257
YOM:
1958
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1757
Captain / Total hours on type:
50.00
Circumstances:
The pilot was conducting a charter positioning flight from Hamilton Island Marina to Whitehaven Beach, Whitsunday Island. At approximately 1615LT, pilot was landing the aircraft towards the south, about 600 metres off the beach, to avoid mechanical turbulence associated with terrain at the southern end of Whitehaven Beach. He reported that the approach and flare were normal, however, as the aircraft touched down on the right float, the aircraft swung sharply right and then sharply left. The left wing contacted the water, and the aircraft overturned. The pilot exited the upturned aircraft through the left rear passenger door and activated a 121.5 MHz distress beacon.
Probable cause:
The wind strength and sea state at the time of the occurrence were not ideal for floatplane operations, particularly given the pilot's relative lack of experience in open water operations. In comparison, it was unlikely the non-standard floats contributed significantly to the development of the accident. The loss of directional control suggests a lower than ideal pitch attitude at touchdown, a configuration which reduces a floatplane's directional stability. The pilot's use of a distress beacon for search and rescue purposes was appropriate, however the timeliness of his rescue from the upturned aircraft can be attributed to the effectiveness of the company's flight monitoring system and subsequent search and rescue actions.
Final Report:

Crash of a Cessna 208B Grand Caravan in Kotzebue

Date & Time: Mar 2, 2003 at 1504 LT
Type of aircraft:
Operator:
Registration:
N205BA
Flight Type:
Survivors:
Yes
Schedule:
Shungnak - Kotzebue
MSN:
208B-0890
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25600
Captain / Total hours on type:
4200.00
Aircraft flight hours:
2082
Circumstances:
Prior to departing on an air taxi flight, the airline transport certificated pilot obtained a weather briefing and filed a VFR flight plan for a trip from his home base, to several remote villages, and return. The area forecast contained an AIRMET for IFR conditions and mountain obscuration due to clouds and light snow. The terminal forecast contained expected conditions that included visibilities ranging from 3 to 3/4 mile in blowing snow, a vertical visibility of 500 feet, and wind speeds from 14 to 22 knots. During the filling of the flight plan, an FAA flight service station specialist advised that VFR flight was not recommended. The pilot acknowledged the weather information and departed. When the pilot took off on the return flight from an airport 128 miles east of his home base, the pilot reported that the visibility at his base was greater than 6 miles. As he neared his home base, the visibility had decreased and other pilots in the area were requesting special VFR clearances into the Class E surface area. The pilot requested a special VFR clearance at 1441, but had to hold outside the surface area for other VFR and IFR traffic. At 1453, a METAR at the airport included a wind 080 of 26 knots, and a visibility of 1 mile in blowing snow. While holding about 7 miles north of the airport, the pilot provided a pilot report that included deteriorating weather conditions east of the airport. Once the pilot was cleared to enter the surface area at 1458, he was provided with an airport advisory that included wind conditions of 25 knots, gusting to 33 knots. While the pilot was maneuvering for the approach, a special aviation weather observation at 1501 included a wind condition of 26 knots, and a visibility of 3/4 mile in blowing snow. The pilot said he established a GPS waypoint 4 miles from the runway and descended to 1,000 feet. He continued inbound and descended to 300 feet. At 1 mile from the airport, the pilot said he looked up from the instrument panel but could not see the airport. He also stated that he was in a whiteout condition. The airplane collided with the snow-covered sea ice, about 1 mile from the approach end of the runway threshold at 1504.
Probable cause:
The pilot's continued VFR flight into instrument meteorological conditions, and his failure to maintain altitude/clearance above the ground, resulting in a collision with snow and ice covered terrain during the final approach phase of a VFR landing. Factors in the accident were whiteout conditions and snow-covered terrain.
Final Report:

Crash of a Socata TBM-700 in Leesburg: 3 killed

Date & Time: Mar 1, 2003 at 1445 LT
Type of aircraft:
Registration:
N700PP
Survivors:
No
Schedule:
Greenville - Leesburg
MSN:
059
YOM:
1992
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
730
Copilot / Total flying hours:
8375
Aircraft flight hours:
1049
Circumstances:
The private pilot, who sat in the left seat, was executing the LOC RWY 17 instrument approach in actual instrument meteorological conditions, when the airplane decelerated, lost altitude, and began a left turn about 2 miles from the airport. Subsequently, the airplane collided with terrain and came to rest on residential property. The radar data also indicated that the airplane was never stabilized on the approach. A witness, a private pilot, said the airplane "appeared" out of the fog about 300-400 feet above the ground. It was in a left bank, with the nose pointed down, and was traveling fast. The airplane then "simultaneously and suddenly level[ed] out," pitched up, and the engine power increased. The witness thought that the pilot realized he was low and was trying to "get out of there." The airplane descended in a nose-high attitude, about 65 degrees, toward the trees. Radar data indicates that the airplane slowed to 80 knots about 3 miles from the airplane, and then to 68 knots 18 seconds later as the airplane began to turn to the left. Examination of the airplane and engine revealed no mechanical deficiencies. Weather reported at the airport 25 minutes before the accident included wind from 140 degrees at 5 knots, visibility 1 statute mile, and ceiling 500 foot overcast. Weather 5 minutes before the accident included wind from 140 degrees at 5 knots, visibility 1 statute miles, and ceiling 300 foot overcast.
Probable cause:
The pilot's failure to fly a stabilized, published instrument approach procedure, and his failure to maintain adequate airspeed which led to an aerodynamic stall.
Final Report:

Crash of a Cessna 402B off Marathon

Date & Time: Feb 20, 2003 at 1220 LT
Type of aircraft:
Registration:
N554AE
Flight Type:
Survivors:
Yes
Schedule:
Havana – Marathon – Miami
MSN:
402B-1308
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4000
Captain / Total hours on type:
817.00
Aircraft flight hours:
11303
Circumstances:
The fuel tanks were filled the day before the accident date, and on the day of the accident, the airplane was flown from that airport to the Miami International Airport, where the pilot picked up 2 passengers and flew uneventfully to Cuba. He performed a preflight inspection of the airplane in Cuba and noted both auxiliary fuel tanks were more than half full and both main tanks were half full. The flight departed, climbed to 8,000 feet; and was normal while in Cuban airspace. When the flight arrived at TADPO intersection, he smelled strong/fumes of fuel in the cabin. The engine instruments were OK at that time. The flight continued and when it was 10-12 miles from Marathon, he smelled something burning in the cabin like plastic material/paper; engine indications at that time were normal. He declared "PAN" three times with the controller, and shortly thereafter the right engine began missing and surging. He then observed fire on top of the right engine cowling near the louvers. He secured the right engine however the odor of fuel and fumes got worse to the point of irritating his eyes. He declared an emergency with the controller, began descending at blue line airspeed, and the fumes/odor got worse. Approximately 5 minutes after the right engine began missing and surging, the left engine began acting the same way. He secured the left engine but the propeller did not completely feather. At 400 feet he lowered full flaps and (contrary to the Pilot's Operating Handbook and FAA Approved Airplane Flight Manual) the landing gear in preparation for ditching. He intentionally stalled the airplane when it was 5-7 feet above the water, evacuated the airplane with a life vest, donned then inflated it. The airplane sank within seconds and he was rescued approximately 20 minutes later. The pilot first reported 4 months and 19 days after the accident that his passport which was in the airplane at the time of the accident had burned pages. He was repeatedly asked for a signed, dated statement that explained where it was specifically located in the airplane, and that it was not burned before the accident flight; he did not provide a statement. Examination of the airplane by FAA and NTSB revealed no evidence of an in-flight fire to any portion of the airplane, including the right engine or engine compartment area, or upper right engine cowling. Examination of the left engine revealed no evidence of preimpact failure or malfunction. The left magneto operated satisfactorily on a test bench, while the right magneto had a broken distributor block; and the electrode tang which fits in a hole of the distributor gear; no determination was made as to when the distributor block fractured or the electrode tang became bent. The left propeller blades were in the feathered position. Examination of the right engine revealed no evidence or preimpact failure or malfunction. The right hand stack assembly was fractured due to overload; no fatigue or through wall thickness erosion was noted. Both magnetos operated satisfactorily on a test bench. The right propeller was in the feathered position. An aluminum fuel line that was located in the cockpit that had been replaced the day before the accident was examined with no evidence or failure or malfunction; no fuel leakage was noted.
Probable cause:
The loss of engine power to both engines for undetermined reasons.
Final Report:

Crash of a Fokker F27 Friendship 200 near Kohat: 17 killed

Date & Time: Feb 20, 2003 at 0915 LT
Type of aircraft:
Operator:
Registration:
10254
Flight Type:
Survivors:
No
Site:
Schedule:
Islamabad - Kohat
MSN:
10254
YOM:
1964
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
The aircraft departed Islamabad on a flight to Kohat, carrying nine passengers and eight crew members. While descending to Kohat, the crew encountered poor visibility when, at an altitude of 3,000 feet, the aircraft struck the slope of a mountain located 27 km from the airport. The aircraft disintegrated on impact and all 17 occupants were killed, among them Mushaf Ali Mir, Chief of Staff of the Pakistan Air Force and his wife. He was flying to Kohat with a delegation to perform the annual inspection of the airbase.
Probable cause:
Controlled flight into terrain after the crew initiated the descent prematurely, causing the aircraft to descend below the minimum safe altitude until it impacted ground. Poor weather conditions were considered as a contributing factor.