Crash of a Boeing 737-2A8 in Madras

Date & Time: Apr 26, 1979 at 1159 LT
Type of aircraft:
Operator:
Registration:
VT-ECR
Survivors:
Yes
Schedule:
Trivandrum - Madras
MSN:
20962/380
YOM:
1974
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
61
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14769
Circumstances:
The flight for 35 minutes after takeoff from Trivandrum Airport was normal and uneventful. After receiving clearance from Madras, the aircraft commenced descent from a cruising altitude of 27,000 feet. Soon thereafter, a loud explosion was heard from the forward lavatory area. The cockpit and front portion of cabin were filled with smoke and cabin lights went off. There was completed instrument and electrical failure. The aircraft with undercarriage down made a flapless approach and touched down at a distance of 2,500 feet beyond threshold of runway 25 at Madras Airport. The aircraft overshot the runway, ploughing through kutcha grassy field and nullah. After the accident came to a halt, the passengers evacuated through forward and rear doors. The aircraft was destroyed due to inflight explosion and subsequent post crash overrun. The fire started on starboard side after the aircraft came to a halt and damaged the starboard wing. 14 occupants were injured.
Probable cause:
The accident was caused by the denotation of an explosive device in the forward lavatory of the aircraft. The aircraft overshot the runway due to high speed of touchdown, non-availability of reverse thrust and antiskid system, due to systems failure consequent on explosion.

Crash of a Boeing 737-2A8 in Hyderabad: 4 killed

Date & Time: Dec 17, 1978 at 1042 LT
Type of aircraft:
Operator:
Registration:
VT-EAL
Flight Phase:
Survivors:
Yes
Schedule:
Hyderabad - New Delhi
MSN:
20485/277
YOM:
1971
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
126
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
After liftoff from runway 09 at Hyderabad-Begumpet Airport, during initial climb, the captain noticed severe vibrations as the leading edges were not properly deployed. After the undercarriage were raised, the captain decided to land back. The airplane belly landed, slid for about 940 meters, overran, struck a perimeter fence and came to rest in flames in a grassy area. The aircraft was totally destroyed by a post crash fire. 31 passengers were injured while 100 other occupants escaped unhurt. A passenger as well as three people cutting grass near the boundary fence were killed.
Probable cause:
Severe vibrations and decision to attempt an emergency landing following incorrect deployment of the leading edges for undetermined reasons.

Crash of a Boeing 737-229C in Charleroi

Date & Time: Apr 4, 1978 at 1807 LT
Type of aircraft:
Operator:
Registration:
OO-SDH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Charleroi - Charleroi
MSN:
20914/396
YOM:
1975
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
6983
Aircraft flight cycles:
7424
Circumstances:
The aircraft was engaged in a local training flight at Charleroi-Gosselies Airport and was carrying a crew of three (one instructor and two student pilots) who just landed from Brussels. Both students were going to practice ILS approaches to runway 25 at Charleroi-Gosselies Airport (CRL) followed by a touch-and-go. The initial six approaches were uneventful. The students then changed seats. The second student's first approach and touch-and-go were uneventful. During the second touch-and-go a flock of birds (ring doves) were observed crossing the runway. Several birds were ingested as the airplane was rotating. The instructor took over control and attempted to continue takeoff. The airplane failed to respond to his control inputs and seemed to decelerate. He then decided to abort the takeoff. There was insufficient runway length available so the Boeing overran, struck localiser antennas and skidded. It lost its undercarriage and came to rest in flames on a road located about 320 meters past the runway end. All three occupants evacuated safely while the aircraft was destroyed by fire.
Probable cause:
The probable cause of the accident was the interruption of the takeoff maneuver at the time of the impact of birds, followed by a stop for undetermined reasons. The deceleration due to braking prevented the aircraft to respond to the action of the pilot-instructor using the ailerons. The takeoff was interrupted while the remaining runway length was insufficient to stop the aircraft.

Crash of a Boeing 737-2A1 in São Paulo

Date & Time: Apr 2, 1978 at 2120 LT
Type of aircraft:
Operator:
Registration:
PP-SMX
Survivors:
Yes
Schedule:
Rio de Janeiro - São Paulo
MSN:
20969
YOM:
1974
Flight number:
VP005
Country:
Crew on board:
7
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The airplane departed Rio de Janeiro-Galeão Airport at 2015LT on flight VP005 to São Paulo. Following an uneventful flight, the crew was unable to lower the undercarriage and decided to complete a belly landing. Upon touchdown, the airplane slid for few hundred meters before coming to rest in flames onto the runway. All 44 occupants were evacuated safely while the aircraft was damaged beyond repair.

Crash of a Boeing 737-275 in Cranbrook: 42 killed

Date & Time: Feb 11, 1978 at 1255 LT
Type of aircraft:
Operator:
Registration:
C-FPWC
Survivors:
Yes
Schedule:
Fort McMurray – Edmonton – Calgary – Cranbrook – Castlegar
MSN:
20142/253
YOM:
1970
Flight number:
PW314
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
42
Captain / Total flying hours:
5173
Captain / Total hours on type:
2780.00
Copilot / Total flying hours:
1316
Copilot / Total hours on type:
81
Circumstances:
Pacific Western Airlines flight 314 was a scheduled Boeing 737 service from Fort McMurray, Aberta, to Castlegar with stops at Edmonton, Calgary and Cranbrook, B. C. The flight departed Calgary at 1932Z 11 February 1978, for Cranbrook with a Company estimated time enroute of 23 minutes. This estimate was passed to the Company Agent in Cranbrook. Flight 314 was cleared by Calgary Air Traffic Control to Cranbrook via high level airway 505, and reached the assigned altitude of 20,000 feet at 1938Z. Air Traffic Control in Calgary transmitted an ETA (estimated time of arrival) of 2005Z to Cranbrook Aeradio, via the land line. Cranbrook is an "uncontrolled" airport without a control tower, but within controlled airspace, with an "Aeradio" station providing communications, weather, and advisory service. At Cranbrook it was snowing with the visibility reported as 314 of a mile, and a radio equipped snow removal vehicle was sweeping the runway. The Aeradio operator at Cranbrook alerted the vehicle operator about the incoming aircraft at 1935Z and gave him the ETA of 2005Z; they both expected the flight would report by the "Skookum Beacon" on a straight-in approach to runway 16, thus giving the vehicle operator about seven minutes to get off the runway. At 1942Z Flight 314 called Calgary and requested and received descent clearance; it was also given clearance for the approach to Cranbrook. At 1944Z, the flight called out of 18000 feet in the descent, and Calgary ATC advised the flight to contact Aeradio. At 1945Z, Flight 314 made initial contact with Cranbrook Aeradio and at 1946Z Cranbrook passed the latest weather, altimeter and runway information. At 1947Z Cranbrook Aeradio advised the flight that snow removal was in progress and gave the latest visibility; Flight 314 acknowledged. No further transmissions were received from the flight by Aeradio or ATC. Evidence indicates the aircraft passed the Skookum beacon inbound on a straight-in instrument approach, and flew the ILS for runway 16 to touchdown.' According to witnesses and estimates partially derived from flight data recorder information, the aircraft touched down at 1955Z approximately 800 feet from the threshold and reverse thrust was selected. Reverse thrust was cancelled immediately after touchdown and a go-around was initiated. The aircraft became airborne prior to the 2000 foot mark, and flew down the runway at a height of 50 to 70 feet, flying over a snow removal vehicle which was still on the runway, 2050 feet from the threshold and 20 feet from the right edge. About this time the left engine thrust reverser doors deployed. A few seconds later, the flap was selected up from 40° to 15°. The landing gear remained down and locked. Six seconds before impact and just over 4,000 feet from the runway threshold, the flight recorder data indicates that a large amount of left rudder was momentarily applied. The aircraft climbed to 300 to 400 feet above the airfield, banked steeply to the left, lost height and side-slipped into the ground to the left of the runway. Fire broke out on impact. Four crew members and 38 passengers were killed while seven other occupants were killed.
Probable cause:
The following findings were reported:
- The estimated time of arrival of the aircraft at Cranbrook, calculated by Calgary ATC, and used by Aeradio for advisory purposes was considerably in error and resulted in a traffic conflict between the arriving aircraft and a vehicle working on the runway,
- The flight crew did not report by the Skookum beacon on final approach, as was the normal practice at Cranbrook, thereby allowing the incorrect ETA to remain undetected,
- Regulatory provisions concerning mandatory pilot position reporting during instrument approaches were inadequate,
- The interfaces between the organizations providing Air Traffic Services, Telecommunications (Aeradio) and Airports Services were not well enough developed to provide a reliable fail-safe flight information service,
- The pilots lost control of the aircraft consequent upon the left engine thrust reverser deploying in flight when the aircraft was at low speed, and in a high drag configuration,
- The FAA design standards under which the Boeing 737 was constructed did not adequately provide for the possibility of an aborted landing after touchdown and thrust reverser initiation,
- The lack of a suitable national system of incident reporting, investigation, and follow-up corrective action allowed operational problems to remain uncorrected,
- Rescue efforts at the accident scene were hampered due to lack of a fire fighting vehicle capable of negotiating deep snow and shortage of trained rescue personnel.
Final Report:

Crash of a Boeing 737-2H6 near Jalan Tanjung Kupang: 100 killed

Date & Time: Dec 4, 1977 at 2036 LT
Type of aircraft:
Operator:
Registration:
9M-MBD
Flight Phase:
Survivors:
No
Schedule:
Penang - Kuala Lumpur
MSN:
20585/306
YOM:
1972
Flight number:
MH653
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
93
Pax fatalities:
Other fatalities:
Total fatalities:
100
Circumstances:
The airplane departed Penang Airport at 1921LT on scheduled service MH653 to Kuala Lumpur. During the descent, while at an altitude of 4,000 feet, a hijacker entered the cockpit and forced the crew to divert to Singapore. The aircraft then climbed to FL210 and proceeded to Singapore when the hijacker shot both pilots and then himself. Few minutes later, the airplane entered a dive and crashed in a wooded area located in the region of Jalan Tanjung Kupang. The aircraft was totally destroyed and all 100 occupants were killed. The cockpit voice recordings indicate noises suggestive of the cockpit door being broken in, along with a reasonable amount of screaming and cursing. No noises are heard from within the cockpit to indicate any of the three occupants were conscious. The autopilot was then disconnected, possibly due to a pitch input by someone entering the cockpit and trying to control the aircraft. An investigator speculated that someone pulled back on the column, causing a pitch up, followed by an oscillation. This rapidly developed into a high amplitude phugoid oscillation that resulted in a rapid dive.
Probable cause:
The aircraft was hijacked in-flight and both pilots were shot.

Crash of a Boeing 737-247 in Casper

Date & Time: Mar 31, 1975 at 0743 LT
Type of aircraft:
Operator:
Registration:
N4527W
Survivors:
Yes
Schedule:
Denver - Casper - Minneapolis
MSN:
20131/165
YOM:
1969
Flight number:
WA470
Crew on board:
6
Crew fatalities:
Pax on board:
93
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6698
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
8900
Copilot / Total hours on type:
2000
Aircraft flight hours:
14076
Circumstances:
Western Air Lines flight 470 to Casper and Minneapolis departed Denver at 07:03 in the morning. The airplane, on an IFR flight plan, climbed to its cruising altitude of FL220. At 07:36, following a descent to 12,000 feet, the flight crew contacted Casper approach control and advised that the flight was about 12 miles south of the Evansville Intersection. At that time, the controller cleared the flight to use the localizer back course approach for runway 25, to circle to runway 3, or to land straight in. The weather reported to the crew indicated poor visibility with light snow falling and wind 040° at 9 knots. One minute later, the approach controller advised that "runway 7/25 has been plowed. There's about a 1/4-inch of powder snow on it. Braking action reported, Convair 580, as poor. Runway 3/21 is being plowed at this time." At 07:51, Flight 470 reported at the Henning Intersection and was cleared to contact the Casper Tower. The tower controller cleared the flight to land on runway 25 and gave the wind as 030° at 8 knots. The flight was also advised by the controller that a disabled snow blower was "just west of the intersection runway 21, left side runway 25, on the edge ...." At 07:41:42, the first officer called out "thousand to go to the field." At 07:42:09, the first officer called "approaching minimums," and 12 seconds later, he called "just about at minimums." The aircraft then flew level for a few moments a t the minimum descent altitude (MDA). At 07:42:25, the first officer called the runway in sight directly below the aircraft. At that time airspeed was 150 knots and the flaps were at 25°. The first office then set the flaps at 30° as the captain initiated the final descent. The aircraft crossed the threshold at reference speed +15 knots. The aircraft touched down 2,375 feet from the departure end of the runway, about 6,306 feet from the approach end of the runway. The aircraft went off the departure end of the runway to the right of the centerline. After striking several metal stanchions in the first row of terminal bar lights, which were located 200 feet off the end of the runway, the aircraft struck a shallow irrigation ditch 280 feet off the runway end. The aircraft veered farther to the right and stopped about 800 feet beyond the departure end of the runway.
Probable cause:
The failure of the pilot-in-command to exercise good judgment when he failed to execute a missed approach and continued a non-precision approach to a landing without adequately assessing the aircraft's position relative to the runway threshold. Contributing to the accident were the excessive height and speed at which he crossed the approach end of the runway and the failure of other flight crew members to provide him with required callouts.
Final Report:

Crash of a Boeing 737-2A8 in New Delhi: 48 killed

Date & Time: May 31, 1973 at 2158 LT
Type of aircraft:
Operator:
Registration:
VT-EAM
Survivors:
Yes
Schedule:
Madras - New Delhi
MSN:
20486/279
YOM:
1971
Flight number:
IC440
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
58
Pax fatalities:
Other fatalities:
Total fatalities:
48
Circumstances:
On final approach to New Delhi-Palam Airport by night, the crew encountered poor weather conditions. In below-minimum visibility, despite he was unable to locate the runway, the captain decided to continue the approach and passed below the glide. With the flaps down to 40°, the airplane struck power cables and crashed in flames near the district of Vasant Vihar, about 3 km east of the airport. Five crew members and 43 passengers were killed while 17 other occupants were injured.
Probable cause:
Wrong approach configuration and poor flight planing on part of the flight crew.

Crash of a Boeing 737-222 in Chicago: 45 killed

Date & Time: Dec 8, 1972 at 1428 LT
Type of aircraft:
Operator:
Registration:
N9031U
Survivors:
Yes
Site:
Schedule:
Washington DC - Chicago - Omaha
MSN:
19069/75
YOM:
1968
Flight number:
UA553
Crew on board:
6
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
45
Captain / Total flying hours:
18000
Captain / Total hours on type:
2435.00
Copilot / Total flying hours:
10638
Copilot / Total hours on type:
1676
Aircraft flight hours:
7247
Circumstances:
Flight UA553 departed Washington-National Airport at 1250LT for Omaha with an intermediate stop at Chicago-Midway Airport. Chicago ARTCC cleared the crew to descend to 4000 feet and the flight was given vectors for a Midway Airport runway 31L localizer course. At 14:19 the flight was transferred to Chicago Approach Control which later requested UA553 to slow down to 180 knots and later down to 160 knots. After issuing a descent clearance down to 2000 feet at 14:23 the controller requested the flight to slow down to approach speed because of separation between UA553 and a preceding Aero Commander. At 14:24 the Aero Commander passed the Outer Marker and was cleared to land on runway 31L. Two minutes later UA553 passed the Outer Marker inbound. Then, at 14:27:04 the air traffic controller decided to issue a missed approach clearance: "United 553 execute a missed approach make a left turn to a heading of 180 climb to 2000". At the same time, having just reached 1000 feet, the stick shaker suddenly activated. Full power was applied and the gear was retracted in an attempt to execute a missed approach. The Boeing continued to descend however, attaining a high nose up attitude (of at least 30deg, according to some survivors). The aircraft then clipped a tree and impacted trees, houses, utility pole cables and garages before coming to rest. Post crash fire destroyed part of the fuselage.
Probable cause:
The captain's failure to exercise positive flight management during the execution of a non-precision approach, which culminated in a critical deterioration of airspeed into the stall regime where level flight could no longer be maintained.
Final Report:

Crash of a Boeing 737-222 in Philadelphia

Date & Time: Jul 19, 1970 at 1907 LT
Type of aircraft:
Operator:
Registration:
N9005U
Flight Phase:
Survivors:
Yes
Schedule:
Philadelphia - Rochester
MSN:
19043/18
YOM:
1968
Flight number:
UA611
Crew on board:
6
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11236
Captain / Total hours on type:
517.00
Copilot / Total flying hours:
2319
Copilot / Total hours on type:
736
Aircraft flight hours:
3956
Circumstances:
At 18:50 Boeing 737 "City of Bristol" taxied to runway 09 for departure. At 19:05 the first officer, who was pilot flying, initiated the takeoff roll. Shortly after rotation, at a speed above V2, a loud bang was heard and the aircraft veered to the right. The captain moved both throttles forward but there seemed to be no response. The captain then made the instantaneous decision to set the aircraft back on the runway. The aircraft touched down 1075 feet short of the runway end. The 737 continued of the end of the runway and across the blast pad. It crossed a field, passed through a 6-foot high aluminum chain link fence into an area covered with high grass, weeds and brush. The aircraft came to rest 1634 feet past the end of the runway.
Probable cause:
The termination of the take-off, after the No.1 engine failed, at a speed above V2 at a height of approximately 50 feet, with insufficient runway remaining to effect a safe landing. The captain's decision and his action to terminate the take-off were based on the erroneous judgment that both engines had failed.
Final Report: