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 Let L-410UVP in Kimry-Borki: 11 killed

Date & Time: Mar 1, 2003 at 1425 LT
Type of aircraft:
Operator:
Registration:
FLARF-01032
Flight Phase:
Survivors:
Yes
Schedule:
Kimry-Borki - Kimry-Borki
MSN:
83 11 09
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
23
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
The twin engine aircraft departed Kimry-Borki Airport on a local skydiving flight, carrying 23 skydivers and two pilots. At an altitude of 3,800 metres, 11 skydivers prepared to jump and moved through the rear of the cabin. While four of them jumped out, the aircraft stalled from the tail and nosed up then entered an uncontrolled descent. At an altitude of about 2,000 metres, the aircraft suffered a structural failure and broke up. Several skydivers were thrown out then the aircraft crashed in a snow covered forest located two km from the airfield. Nine skydivers and both pilots were killed while all other occupants were found alive. The aircraft was totally destroyed.
Probable cause:
It was determined that the aircraft was operated in illegal conditions at the time of the accident. On board were 23 skydivers while the aircraft was certified for 12 skydivers maximum. At the time of the accident, the total weight of the aircraft was 618 kilos above MTOW and the CofG was well beyond the rear limit (around 35%), especially when the 11 skydivers moved through the rear of the cabin. Some of the skydivers were seating on the floor and one was in the toilets.

Ground accident of a Fokker F27 Friendship 500 in Blenheim

Date & Time: Feb 27, 2003 at 1950 LT
Type of aircraft:
Operator:
Registration:
ZK-NAN
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Blenheim - Blenheim
MSN:
10365
YOM:
1968
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Airwork F-27 was on a training flight, during which the crew carried out an exercise that simulated a gear problem. They extended the gear using the emergency system. However, after landing they did not select the main gear handle down and in addition did not install the gear locking pins. The crew were then distracted by other events and during this the co-pilot selected the emergency gear handle up to reset the system. The main gear then partially collapsed.

Ground accident of a Dornier DO228-201 in Karachi

Date & Time: Feb 19, 2003
Type of aircraft:
Operator:
Registration:
AP-BGF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Karachi - Karachi
MSN:
8016
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful training flight at Karachi-Quaid-e-Azam Airport, the crew was taxiing to his parking place when control was lost. The aircraft rolled across the apron and eventually collided with a concrete wall. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 421A Golden Eagle I in Somerset: 3 killed

Date & Time: Feb 16, 2003 at 2002 LT
Type of aircraft:
Registration:
N421TJ
Survivors:
Yes
Schedule:
Griffith - Somerset
MSN:
421A-0051
YOM:
1968
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
11732
Captain / Total hours on type:
518.00
Aircraft flight hours:
4129
Circumstances:
The airplane joined the inbound course for the GPS instrument approach between the intermediate approach fix and the final approach fix, and maintained an altitude about 200 feet below the sector minimum. The last radar return revealed the airplane to be about 3/4 nautical miles beyond the final approach fix, approximately 1,000 feet left of course centerline. An initial tree strike was found about 1 nautical mile before the missed approach point, about 700 feet left of course centerline, at an elevation about 480 feet below the minimum descent altitude. Witnesses reported seeing the airplane flying at a "very low altitude" just prior to its impact with hilly terrain, and also described the sound of the airplane's engines as "really loud" and "a constant roar." Night instrument meteorological conditions prevailed at the time of the accident. There was no evidence of mechanical malfunction.
Probable cause:
The pilot's failure to follow the instrument approach procedure, which resulted in an early descent into trees and terrain. Factors included the low ceiling and the night lighting conditions.
Final Report:

Crash of a Britten-Norman BN-2A-21 Defender at Braasschaat AFB

Date & Time: Feb 14, 2003
Type of aircraft:
Operator:
Registration:
B-03
Flight Type:
Survivors:
Yes
Schedule:
Braasschaat - Braasschaat
MSN:
476
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training flight at Braasschaat AFB. For unknown reasons, the twin engine aircraft landed hard and bounced several times before coming to rest on the runway. Both pilots escaped with minor injuries and the aircraft was damaged beyond repair.

Crash of a PZL-Mielec AN-28PD in Tallinn: 2 killed

Date & Time: Feb 10, 2003 at 1942 LT
Type of aircraft:
Operator:
Registration:
ES-NOY
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Tallinn - Helsinki
MSN:
1AJ006-04
YOM:
1989
Flight number:
ENI827
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
10856
Captain / Total hours on type:
510.00
Copilot / Total flying hours:
2827
Copilot / Total hours on type:
475
Aircraft flight hours:
1428
Aircraft flight cycles:
2141
Circumstances:
The twin engine aircraft departed Tallinn-Ülemiste Airport on a mail flight to Helsinki, carrying three crew members (two pilots and one mechanic) and a load consisting of 514 kilos of mail. Four seconds after lift off from runway 08, while climbing to a height of 12 metres and at a speed of 170 km/h, the left engine suffered vibrations. The power lever for the left engine was brought back to idle then in a full forward position. Nevertheless, the aircraft lost height, nosed down and crashed in a wooded area located one km past the runway end. Both pilots were killed and the mechanic was seriously injured.
Probable cause:
It was determined that the right engine failed during initial climb following the rupture of a turbine ball bearing due to poor lubrication.
Final Report:

Crash of an Ilyushin II-76TD in Baucau: 6 killed

Date & Time: Jan 31, 2003 at 1521 LT
Type of aircraft:
Registration:
RDPL-34141
Flight Type:
Survivors:
No
Schedule:
Macau - Baucau
MSN:
00534 65941
YOM:
1985
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
14500
Copilot / Total flying hours:
6800
Aircraft flight hours:
2349
Aircraft flight cycles:
1400
Circumstances:
Carrying 31 tons of telecommunications equipments for a Portuguese telephone company, the aircraft departed Macau to Baucau with two passengers and four crew members. On approach, the aircraft impacted terrain near Caicido village during a landing approach, about 1 NM (1.87 km) to the northwest of Cakung Airport, Baucau, Timor-Leste. The pilot in command was the handling pilot during the descent and approaches at Baucau. The aircraft was destroyed by impact forces and a severe post-impact fire, and the six occupants were fatally injured. The occupants included the flight crew, which comprised the pilot in command, the copilot, the flight navigator and the flight engineer, and two loadmasters who did not form part of the flight crew. At the time of the occurrence, there was low cloud near the aerodrome.2 Witnesses at the aerodrome estimated the cloud base to be about 1,000 ft (305 m) above ground level, and visibility to be about 1,500 m (0.8 NM). Before the aircraft’s departure from Macau, the flight crew was provided with notices to airmen (NOTAMs) and weather forecast information for the planned flight. The weather information provided to the flight crew did not include a terminal aerodrome forecast (TAF), or an aviation routine weather report (METAR) for Baucau. Those weather forecasts were not produced for Baucau.
Probable cause:
The following findings were identified:
Air Traffic Services:
1. ATS was not available at Baucau at the time of the occurrence.
2. There was no procedure in place to provide flight crews of aircraft engaged in non-UN operations with an altimeter subscale setting for Baucau at the time of the occurrence.
Organisational factors:
1. Neither the Lao-based company, nor the Cambodian-based company, sought the consent for the proposed sublease, dated 18 November 2002, and accordingly the inferred sublease had not been finalised.
2. The Cambodian-based company was not the operator of the aircraft for the occurrence flight.
3. The Lao PDR was the State of Registry and State of the Operator.
4. The Lao DCA was responsible for the continued surveillance of the operator to ensure that the required standards of operation were maintained.
5. The operator provided flight crews with inflight CFIT avoidance procedures in its operations manual.
CFIT risk exposure:
1. The planned flight from Macau to Baucau was exposed to moderate risk of a CFIT event, based on historical CFIT data and the Transport Canada simple method of risk analysis.
2. The destination risk factors, type of operation, area of operation, weather conditions, and flight crew non-compliance with published procedures increased the CFIT risk exposure of the planned flight to an above-average level.
3. The consequences of the accident were catastrophic and resulted in loss of human life and damage to property and the environment.
4. Those catastrophic consequences resulted from the flight crew’s disregard of established procedures; that disregard bypassed all the safety criteria and inbuilt risk treatments in the design of those procedures and steadily increased the CFIT risk exposure to an extreme level during the latter stages of the flight.
Significant factors:
1. The flight crew did not comply the published non-precision instrument approach and/or missed approach procedures at Baucau during flight in instrument meteorological conditions.
2. The flight crew conducted user-defined non-precision instrument approaches to runway 14 at Baucau during flight in instrument meteorological conditions.
3. The pilot in command permitted the aircraft to descend below the MDA(H) published on both the Jeppesen and CAD runway 14 instrument approach charts during flight in instrument meteorological conditions.
4. The flight crew did not recognise the increased likelihood and therefore risk of CFIT.
5. The flight crew did not recognise or treat that risk in a timely manner.
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) in Scottsdale: 2 killed

Date & Time: Jan 26, 2003 at 2023 LT
Registration:
N3636Q
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Scottsdale – Santa Fe
MSN:
61-0785-8063398
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1450
Captain / Total hours on type:
160.00
Aircraft flight hours:
2574
Circumstances:
The airplane collided with mountainous terrain 5 miles from the departure airport during a dark night takeoff. Review of recorded radar data found a secondary beacon code 7267 (the code assigned to the airplane's earlier inbound arrival ) on the runway at 2021:08, with a mode C report consistent with the airport elevation. Two more secondary beacon returns were noted on/over the runway at 2021:12 and 2021:19, reporting mode C altitudes of 1,600 and 1,700 feet, respectively. Between 2021:08 and 2021:38, the secondary beacon target (still on code 7267) proceeded on a northeasterly heading of 035 degrees (runway heading) as the mode C reported altitude climbed to 2,000 feet and the computed ground speed increased to 120 knots. Between 2021:38 and 2021:52, the heading changed from an average 035 to 055 degrees as the mode C reports continued to climb at a mathematically derived 1,300 feet per minute and the ground speed increased to average of 170 knots. At 2022:23, the code 7267 target disappeared and was replaced by a 1200 code target. The mode C reports continued to climb at a mathematically derived rate of 1,200 feet per minute as the ground speed increased to the 180- knot average range. The computed average heading of 055 degrees was maintained until the last target return at 2022:53, which showed a mode C reported altitude of 3,500 feet. The accident site elevation was 3,710 feet and was 0.1 miles from the last target return. The direct point to point magnetic course between Scottsdale and Santa Fe was found to be 055 degrees. Numerous ground witnesses living at the base of the mountain where the accident occurred reported hearing the airplane and observing the aircraft's lights. The witnesses reported observations consistent with the airplane beginning a right turn when a large fireball erupted coincident with the airplane's collision with the mountain. No preimpact mechanical malfunctions or failures were found during an examination of the wreckage. The radar data establishes that the pilot changed the transponder code from his arrival IFR assignment to the VFR code 30 seconds before impact and this may have been a distraction.
Probable cause:
The pilot's failure to maintain an adequate altitude clearance from mountainous terrain. Contributing factors were dark night conditions, mountainous terrain, and the pilot's diverted attention.
Final Report: