Crash of a Let L-410UVP-E9D in Kanpur

Date & Time: May 18, 1996 at 0738 LT
Type of aircraft:
Operator:
Registration:
VT-ETB
Survivors:
Yes
Schedule:
New Delhi - Kanpur
MSN:
92 27 02
YOM:
1992
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8237
Circumstances:
Archana Airways L-410 aircraft VT-ETB was operating a scheduled flight from Delhi to Kanpur civil aerodrome on 18.05.96. The flight from Delhi to Kanpur was uneventful. The aircraft took-off from Delhi with 19 persons including three flight crew. During landing, the aircraft touched down late and could not be stopped within the available runway length and went beyond the runway. The aircraft hit the boundary wall of the airport and came to halt. The aircraft sustained major damages. There was no fire and no injury to persons on board the aircraft.
Probable cause:
The accident was caused due to late touchdown at higher aircraft touchdown speed as a result of which the aircraft overshot the runway and suffered damage by impact with boundary wall.
The following contributing factors were reported:
- Wrong selection of runway,
- Overloading of aircraft,
- Non-deployment of spoilers,
- Lower visibility conditions than the required,
- Disregard of procedures, regulations and instructions on part of the pilot.
Final Report:

Crash of a Douglas DC-9-15 in Tampico

Date & Time: May 14, 1996
Type of aircraft:
Operator:
Registration:
XA-SNR
Survivors:
Yes
Schedule:
Orlando – Cancún
MSN:
45699
YOM:
1965
Flight number:
LL401
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
43
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Orlando to Cancún, the crew got lost and was unable to follow the prescribed route, causing the aircraft to deviate from the flight plan to the west. Eventually, the crew was vectored to the Tampico-General Francisco Javier Mina Airport located about 1,144 km northwest of the destination airport. On final approach, both engines failed simultaneously due to fuel exhaustion. The aircraft lost speed, stalled and collided with ILS equipment located about 300 metres short of runway 31. Upon impact, the undercarriage were sheared off and the aircraft crash landed on the runway and came to rest 220 metres further. All 47 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Douglas DC-9-32 in the Everglades National Park: 110 killed

Date & Time: May 11, 1996 at 1413 LT
Type of aircraft:
Operator:
Registration:
N904VJ
Flight Phase:
Survivors:
No
Schedule:
Miami - Atlanta
MSN:
47377
YOM:
1969
Flight number:
VJA592
Crew on board:
5
Crew fatalities:
Pax on board:
105
Pax fatalities:
Other fatalities:
Total fatalities:
110
Captain / Total flying hours:
8928
Captain / Total hours on type:
2116.00
Copilot / Total flying hours:
6448
Copilot / Total hours on type:
2148
Aircraft flight hours:
68395
Aircraft flight cycles:
80663
Circumstances:
ValuJet Flight 592 was a scheduled flight from Miami (MIA) to Atlanta (ATL). The inbound flight had been delayed and arrived at Miami at 13:10. Flight 592 had been scheduled to depart at 13:00. The cruising altitude was to be flight level 350 with an estimated time en route of 1 hour 32 minutes. The DC-9 was loaded with 4,109 pounds of cargo (baggage, mail, and company-owned material (COMAT)). The COMAT consisted of two main tires and wheels, a nose tire and wheel, and five boxes that were described as "Oxy Cannisters -‘Empty.’" This cargo was loaded in the forward cargo compartment. Flight 592 was pushed back from the gate shortly before 13:40. The DC-9 then taxied to runway 09L. At 14:03:24, ATC cleared the flight for takeoff and the flightcrew acknowledged the clearance. At 14:04:24, the flightcrew was instructed by ATC to contact the north departure controller. At 1404:32, the first officer made initial radio contact with the departure controller, advising that the airplane was climbing to 5,000 feet. Four seconds later, the departure controller advised flight 592 to climb and maintain 7,000 feet. The first officer acknowledged the transmission. At 14:07:22, the departure controller instructed flight 592 to "turn left heading three zero zero join the WINCO transition climb and maintain one six thousand," which was acknowledged. At 14:10:03, the flight crew heard a sound, after which the captain remarked, "What was that?" At that moment, the airplane was at 10,634 feet msl, 260 knots indicated airspeed (KIAS), and both engine pressure ratios (EPRs) were 1.84. At 14:10:15, the captain stated, "We got some electrical problem," followed 5 seconds later with, "We’re losing everything." At 14:10:21, the departure controller advised flight 592 to contact Miami on frequency 132.45 mHz. At 14:10:22, the captain stated, "We need, we need to go back to Miami," followed 3 seconds later by shouts in the background of "fire, fire, fire, fire." At 14:10:27, the CVR recorded a male voice saying, "We’re on fire, we’re on fire." At 14:10:28, the controller again instructed flight 592 to contact Miami Center. At 14:10:31, the first officer radioed that the flight needed an immediate return to Miami. The controller replied, "Critter five ninety two uh roger turn left heading two seven zero descend and maintain seven thousand." The first officer acknowledged the heading and altitude. The peak altitude reached was 10,879 feet msl at 14:10:31, and about 10 seconds a wings-level descent started. Shouting in the cabin subsided. The controller then queried flight 592 about the nature of the problem. The captain stated "fire" and the first officer replied, "uh smoke in the cockp... smoke in the cabin." The controller responded, "roger" and instructed flight 592, when able, to turn left to a heading of two five zero and to descend and maintain 5,000 feet. At 14:11:12, a flight attendant was heard shouting, "completely on fire." The DC-9 began to change heading to a southerly direction and at 14:11:26, the north departure controller advised the controller at Miami Center that flight 592 was returning to Miami with an emergency. At 14:11:37, the first officer transmitted that they needed the closest available airport. At 1411:41, the controller replied, "Critter five ninety two they’re gonna be standing (unintelligible) standing by for you, you can plan runway one two when able direct to Dolphin [a navaid] now." At 14:11:46, the first officer responded that the flight needed radar vectors. At 14:11:49, the controller instructed flight 592 to turn left heading one four zero. The first officer acknowledged the transmission. At 14:12:45, the controller transmitted, "Critter five ninety two keep the turn around heading uh one two zero." There was no response from the flightcrew. The last recorded FDR data showed the airplane at 7,200 feet msl, at a speed of 260 KIAS, and on a heading of 218 degrees. At 14:12:48, the FDR stopped recording data. The airplane’s radar transponder continued to function; thus, airplane position and altitude data were recorded by ATC after the FDR stopped. At 14:13:18, the departure controller instructed, "Critter five ninety two you can uh turn left heading one zero zero and join the runway one two localizer at Miami." Again there was no response. At 14:13:27, the controller instructed flight 592 to descend and maintain 3,000 feet. At 1413:37, an unintelligible transmission was intermingled with a transmission from another airplane. No further radio transmissions were received from flight 592. At 14:13:43, the departure controller advised flight 592, "Opa Locka airport’s about 12 o’clock at 15 miles." The accident occurred at 14:13:42. Ground scars and wreckage scatter indicated that the airplane crashed into the Everglades in a right wing down, nose down attitude.
Probable cause:
The National Transportation Safety Board determines that the probable causes of the accident, resulting in a fire in the Class D cargo compartment from the actuation of one or more oxygen generators improperly carried as cargo, were: (1) the failure of SabreTech to properly prepare, package, identify, and track unexpended chemical oxygen generators before presenting them to ValuJet for carriage; (2) the failure of ValuJet to properly oversee its contract maintenance program to ensure compliance with maintenance, maintenance training, and hazardous materials requirements and practices; and (3) the failure of Federal Aviation Administration (FAA) to require smoke detection and fire suppression systems in Class D cargo compartments. Contributing to the accident was the failure of the FAA to adequately monitor ValuJet's heavy maintenance program and responsibilities, including ValuJet's oversight of its contractors, and Sabre Tech's repair station certificate; the failure of the FAA to adequately respond to prior chemical oxygen generator fires with programs to address the potential hazards; and the failure of ValuJet to ensure that both ValuJet and contract maintenance employees were aware of the carrier's no-carry hazardous materials policy and had received appropriate hazardous materials training." (NTSB/AAR-97/06)
Final Report:

Crash of a Britten-Norman BN-2A-20 Islander in Oumba: 1 killed

Date & Time: May 11, 1996 at 1315 LT
Type of aircraft:
Operator:
Registration:
P2-ISD
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Menyamya – Marawaka
MSN:
582
YOM:
1977
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
En route from Menyamya to Marawaka, weather conditions deteriorated while the pilot was flying in a deep valley. He elected to find a hole in the clouds to leave the area when, at a speed of 80 knots, the aircraft stalled, collided with trees and crashed on hilly terrain. A passenger was killed while nine other occupants were injured.
Probable cause:
The pilot failed to monitor his speed indicator and failed to realize the speed dropped while trying to get out of a deep valley.

Crash of a De Havilland DHC-6 Twin Otter 200 in Santa Maria de Otaez: 17 killed

Date & Time: May 10, 1996
Operator:
Registration:
XA-SWJ
Survivors:
Yes
Schedule:
Durango - Santa Maria de Otaez
MSN:
126
YOM:
1968
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
On approach to Santa Maria de Otaez Airstrip, the crew encountered strong winds and turbulences when the aircraft went out of control and crashed on a hill located few km from the airfield. Three passengers were seriously injured while 16 other occupants were killed. About two weeks later, one of the survivor died from his injuries.

Crash of a Swearingen SA227AC Metro III in Saint George

Date & Time: May 3, 1996 at 1630 LT
Type of aircraft:
Operator:
Registration:
N670PA
Survivors:
Yes
Schedule:
Saint Paul - Saint George
MSN:
AC-613
YOM:
1985
Flight number:
KS661
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19100
Captain / Total hours on type:
5500.00
Aircraft flight hours:
17167
Circumstances:
According to passenger's accounts, the airplane was flying low and approached the runway at an angle. The airplane made a right turn and dragged the right wing on the runway's surface. The airplane landed hard and sheared off the right main landing gear and the nose gear. The weather reported by AWOS was 300 foot overcast with a visibility of 2.5 miles with fog. The Captain stated the airplane drifted to the left side of the runway due to the crosswind, and he executed a right turn to realign with the runway. The cockpit voice recorder indicated that the stall warning horn sounded as the First Officer called for the application of power.
Probable cause:
Failure of the captain to maintain proper altitude and wingtip clearance, while aligning the airplane with the runway before landing. His delay in aligning the aircraft with the runway was a related factor.
Final Report:

Crash of an Avro 748-352-2B in Meghauli

Date & Time: Apr 25, 1996 at 1158 LT
Type of aircraft:
Operator:
Registration:
9N-ABR
Survivors:
Yes
Schedule:
Kathmandu - Meghauli
MSN:
1771
YOM:
1979
Flight number:
RA155
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Kathmandu, the crew started the descent to Meghauli Airfield. On final, the aircraft was too high and landed too far down the runway, about 1,148 feet past the runway threshold (Meghauli Airstrip is 3,500 feet). Unable to stop on a wet grassy runway, the aircraft overran and came to rest in a ravine. All 31 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the crew who landed the aircraft too far down the runway, reducing the landing distance available. Also, it was reported that the braking action was poor as the grassy runway was wet.

Crash of an Antonov AN-2TP off Anadyr

Date & Time: Apr 20, 1996
Type of aircraft:
Registration:
RA-33631
Flight Phase:
Survivors:
Yes
MSN:
1G233-15
YOM:
1989
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances in the sea (Anadyrsky Liman) off Anadyr. There were no casualties.

Crash of a De Havilland DHC-6 Vista Liner 300 in Virgin Gorda

Date & Time: Apr 7, 1996 at 0600 LT
Registration:
N143SA
Flight Phase:
Survivors:
Yes
Schedule:
Virgin Gorda - Christiansted
MSN:
591
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On April 7, 1996, about 0600 Atlantic standard time, N143SA, a De Havilland DH6, operated by Dolphin Express Airlines crashed on takeoff roll at Virgin Gorda Airport, British Virgin Islands. The flight was a 14 CFR Part 135 scheduled international passenger commuter flight. Visual meteorological conditions prevailed at the time and a VFR flight plan was filed. The airplane was substantially damaged and the captain, first officer, and eight passengers reported no injuries. One passenger received minor injuries. The flight was originating at the time of the accident. The captain stated the while on takeoff roll the airplane veered sharply to the left and she could not exercise directional control. The airplane then departed the runway and crashed through a fence, ripping one wing off the airplane. The airplane was equipped with a CVR that is being removed for further readout.

Crash of a Dornier DO228-212 off Matsu Nangan

Date & Time: Apr 5, 1996 at 1625 LT
Type of aircraft:
Operator:
Registration:
B-12257
Survivors:
Yes
Schedule:
Taipei - Matsu Nangan
MSN:
8223
YOM:
1993
Flight number:
VY7613
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
On approach to Matsu Nangan Airport, the crew encountered poor weather conditions with reduced visibility due to fog. The descent was completed under VFR mode in IMC conditions. On final, the copilot who was the pilot-in-command continued the approach despite he did not establish any visual contact with the runway, and failed to monitor the instruments. Eventually, the crew attempted to make a go-around but this decision was taken too late. The aircraft struck the water surface and crashed in the sea about 1,600 metres offshore. Six passengers were killed while 11 other occupants were injured.
Probable cause:
Wrong approach configuration on part of the crew who continued the descent under VFR mode in IMC conditions, below the MDA until the aircraft struck the water surface. Poor supervision on part of the captain. Poor crew coordination and poor approach and landing planning.