Operator Image

Crash of a Nord 262A-36 in Clarksburg: 2 killed

Date & Time: Feb 12, 1979 at 1300 LT
Type of aircraft:
Operator:
Registration:
N29824
Flight Phase:
Survivors:
Yes
Schedule:
Clarksburg – Washington DC
MSN:
48
YOM:
1968
Flight number:
AL561
Crew on board:
3
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4028
Captain / Total hours on type:
528.00
Copilot / Total flying hours:
7474
Copilot / Total hours on type:
474
Aircraft flight hours:
9140
Circumstances:
On February 12, 1979, Allegheny Airlines Flight 561 (N29824) had originally departed Benedum Airport, Clarksburg, West Virginia, for Morgantown, West Virginia, at 1116, but the pilot decided not to make an approach at Morgantown because the instrument landing system's (ILS) glide slope was out of service, and the visibility was 1/2 mi. Thereafter the flight returned to Benedum Airport and landed at 1146. The aircraft was on the ground for about 1 hr 14 min at Benedum Airport. During that time the aircraft was refueled to 3,000 lbs of Jet-A fuel (1,500 lbs in each wing tank), and all surfaces were deiced with a mixture of unheated ethylene glycol and water. Although the Safety Board could not determine the precise time of deicing, the persons involved stated that it was performed between 1220 and 1235. The persons involved stated that it was performed between 1220 and 1235. The persons who deiced the plane stated that there was no snow or ice on the aircraft when they finished decing it. Flight 561 was rescheduled as a passenger flight from Benedum Airport to National Airport, Washington, D.C. There were 22 passengers and a crew of 3 on board. Before the captain started the engines for taxiing, the station agent asked him if he wanted the aircraft deiced again, since it was still snowing. The captain declined the offer and about 1257 he taxied the aircraft from the parking ramp. According to the station agent, the aircraft had about 1/4 in. of wet snow on all its horizontal surfaces when it left the parking ramp. He said that some of the snow blew off as the aircraft moved toward the departure runway, but some of the snow appeared to stick to the aircraft's horizontal surfaces. Twelve of the passengers recalled that shortly after liftoff, the aircraft rolled to the right, back to the left, and back to the right. After the last roll, the right wingtip struck the ground and impact followed shortly thereafter. The aircraft crashed in an inverted position off the right side of the departure end of runway 21. According to other witnesses, the ground roll appeared normal. The Clarksburg Tower local controller said that he saw Flight 561 taxi to runway 21, and he cleared the flight for takeoff. He saw the aircraft during takeoff until it reached taxiway D, which is about 1,000 ft from the tower, but he did not see the aircraft after that point. He had spoken with the captain by telephone before the takeoff and had given him the 1215 special observation weather. He also radioed the same weather to Flight 561 when it was taxiing for takeoff. He stated that he saw no snow on the aircraft but that moderate snow was falling at the time. The Clarksburg approach controller said that he saw Flight 561 as it turned to line up for takeoff on runway 21. He watched the aircraft through binoculars and saw nothing abnormal as the takeoff roll began. He thought the aircraft was rotated about 1,900 ft down the runway and the liftoff appeared to him to be normal. He lost sight of the aircraft at 50 ft of altitude because of the poor visibility. He recalled that during Flight 561's takeoff, the runway lights were set at their highest intensity. He also stated that he saw no snow blow off the aircraft during its takeoff roll. Shortly after the aircraft disappeared from his view, he heard the sound of an emergency locator transmitter on 121.5 MHz. He asked the Cleveland Center controller if Flight 561 had established contact with him. Since his reply was negative, the approach controller closed the airport and activated the airport emergency plan. The control tower chief observed Flight 561 during takeoff. He lost sight of the aircraft when it was at an altitude of about 20 ft above the runway. At that time the aircraft's attitude appeared to be normal. A pilot in the terminal restaurant said that when the aircraft left the parking ramp, he saw about 1/2 to 1 in. of snow on the wing and tail surfaces of the aircraft. He said that the takeoff appeared normal; but, just before the aircraft disappeared into the overcast, it appeared to pitch up sharply. Another witness who had experience as a pilot was located on taxiway C about 75 ft from the runway. He thought the aircraft lifted off about 200 to 300 ft past taxiway C. Shortly after liftoff, he saw the right wing of the aircraft dip about 45°, then the left wing dipped about the same amount, and the right wing dipped again before the aircraft disappeared from his view about 100 ft above the runway. Shortly thereafter, he heard two separate and distinct sounds of impact. The witness heard no unusual engine noises from the aircraft. The aircraft crashed during daylight hours at an elevation of 1,203 ft ms1. A passenger and a crew member were killed while 23 other occupants were injured, some of them seriously.
Probable cause:
The National Transportation Safety Board determines that the probable cause of the accident was the captain's decision to take off with snow on the aircraft's wing and empennage surfaces which resulted in a loss of lateral control and a loss of lift as the aircraft ascended out of ground effect. The following findings were reported:
- The aircraft had been deiced 20 to 30 min before takeoff; however, about 1/4 in. of wet snow had accumulated on the top of the wings and horizontal stabilizer before the captain taxied the aircraft for takeoff,
- The captain of Flight 561 did not insure that the aircraft's wings, stabilizing surfaces, and control surfaces were clean and free of snow before he began the takeoff roll,
- Shortly after liftoff, the aircraft became laterally unstable; it rolled to the right, then to the left, back to the right, and its right wing struck the runway,
- The snow adhering to the outboard sections of the wing probably caused those sections to stall prematurely,
- The stalling of the outboard sections of the wings caused a loss of lift and significantly reduced the effectiveness of the ailerons, which resulted in lateral control problems and lateral instability,
- The lateral oscillation of the aircraft further decreased lift and caused the aircraft to lose altitude and crash,
- One passenger was fatally injured because her seatbelt was not fastened,
- The accident was marginally survivable for the flight crew because the cockpit structure was crushed inward, which reduced the occupiable space, particularly for the first officer.
Final Report:

Crash of a BAc 111-203AE in Rochester

Date & Time: Jul 9, 1978 at 1730 LT
Type of aircraft:
Operator:
Registration:
N1550
Survivors:
Yes
Schedule:
Boston - Rochester - Montreal
MSN:
44
YOM:
1965
Flight number:
AL453
Crew on board:
4
Crew fatalities:
Pax on board:
73
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13461
Captain / Total hours on type:
7008.00
Copilot / Total flying hours:
8746
Copilot / Total hours on type:
4687
Aircraft flight hours:
33693
Aircraft flight cycles:
48215
Circumstances:
The pilot-in-command adopted a wrong approach configuration and passed over the runway 28 threshold at an excessive speed of 184 knots (61 knots above the Vref) in a nose down attitude. The nose gear landed first at a speed of 163 knots (40-45 knots above normal touchdown speed) 2,540 feet past the runway threshold (runway 28 is 5,500 feet long). Unable to stop within the remaining distance, the airplane overran, struck a drainage ditch, lost its undercarriage and came to rest 728 past the runway end. All 77 occupants were evacuated safely, one of them was slightly injured.
Probable cause:
The captain's lack of awareness of airspeed, vertical speed, and aircraft performance throughout an ILS approach and landing in visual meteorological conditions which resulted in his landing the aircraft at an excessively high speed and with insufficient runway remaining for stopping the aircraft, but with sufficient aircraft performance capability to reject the landing well after touchdown. Contributing to the accident was the first officer's failure to provide required callouts which might have alerted the captain to the airspeed and sink rate deviations. The Safety Board was unable to determine the reasons for the captain's lack of awareness or the first officer's failure to provide required callouts.
Final Report:

Crash of a Douglas DC-9-31 in Philadelphia

Date & Time: Jun 23, 1976 at 1712 LT
Type of aircraft:
Operator:
Registration:
N994VJ
Survivors:
Yes
Schedule:
Providence – Windsor Locks – Philadelphia – Nashville – Memphis
MSN:
47333/481
YOM:
1969
Flight number:
AL121
Crew on board:
4
Crew fatalities:
Pax on board:
102
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Captain / Total hours on type:
6000.00
Copilot / Total flying hours:
11000
Copilot / Total hours on type:
6000
Aircraft flight hours:
21320
Circumstances:
Allegheny Airlines Flight 121, a Douglas DC-9-31, suffered a landing accident on the Philadelphia International Airport, Pennsylvania. Of the 106 persons onboard, 86 persons were injured; there were no fatalities. The captain of Flight 121 had conducted an instrument approach to runway 27R in visual conditions as a thunderstorm passed over the airport in a north-northeasterly direction. When near the threshold the captain initiated a go-around from a low altitude and entered rain of increasing intensity. Shortly thereafter the aircraft was seen descending in a nose-up attitude with the landing gear retracted. After striking tail first on a taxiway about 4,000 feet beyond the threshold of runway 27, the aircraft slid about 2,000 feet and stopped. The wreckage came to rest about 6,000 feet beyond the threshold and about 350 feet to the right of the centerline of runway 27R.
Probable cause:
The aircraft's encounter with severe horizontal and vertical wind shears near the ground as a result of the captain's continued approach into a clearly marginal severe weather condition. The aircraft's ability to cope under these conditions was borderline when flown according to standard operating procedures; however, if the aircraft's full aerodynamic and power capability had been used, the wind shear could probably have been flown through successfully. Contributing to the accident was the tower controller's failure to provide timely below-minimum RVR information.
Final Report:

Crash of a Convair CV-580 in Pittsburgh

Date & Time: Aug 20, 1971 at 2040 LT
Type of aircraft:
Operator:
Registration:
N5844
Survivors:
Yes
Schedule:
Pittsburgh – Parkersburg – Cincinnati
MSN:
43
YOM:
1952
Crew on board:
3
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8300
Captain / Total hours on type:
4100.00
Circumstances:
The aircraft was performing a flight from Pittsburgh to Cincinnati with an intermediate stop in Parkersburg. Upon landing at Parkersburg Airport, West Virginia, the crew encountered technical problems with the right main gear. The captain increased engine power and decided to return to Pittsburgh-Greater Pittsburgh Airport for a safe landing. Upon touchdown on runway 28R, as the wheels were missing on the right main gear, the airplane deviated from the centerline to the right when the left main gear collapsed as well. The airplane came to rest and was damaged beyond repair while all 53 occupants escaped uninjured.
Probable cause:
The right main gear lower assembly separated at Parkersburg Airport after a worn lock pin in the upper bearing sheared. The crew diverted to Pittsburgh. Failure of the landing gear, main gear-shock absorbing, assy, struts, attachments, etc.
Final Report:

Crash of a Convair CV-580 in New Haven: 28 killed

Date & Time: Jun 7, 1971 at 0949 LT
Type of aircraft:
Operator:
Registration:
N5832
Survivors:
Yes
Schedule:
Washington DC – Groton – New London – New Haven – Philadelphie – Newport News
MSN:
384
YOM:
1967
Flight number:
AL485
Crew on board:
3
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
28
Captain / Total flying hours:
12107
Captain / Total hours on type:
3600.00
Copilot / Total flying hours:
4150
Copilot / Total hours on type:
2400
Aircraft flight hours:
33058
Circumstances:
During a non precision approach to New Haven-Tweed Airport, the crew encountered poor weather conditions with rain falls. On final, the pilot-in-command passed below the glide slope and continued the approach until the airplane struck cottages and crashed in flames 4,890 feet short of runway 02. Three occupants survived while 28 others were killed.
Probable cause:
The captain's intentional descent below the prescribed minimum descent altitude under adverse weather conditions without adequate forward visibility or the crew's sighting of the runway environment. The captain disregarded advisories from his first officer that minimum descent altitude had been reached and that the airplane was continuing to descend at a normal descent rate and airspeed. The Board was unable to determine what motivated the captain to disregard prescribed operating procedures and altitude restrictions and finds it difficult to reconcile the actions he exhibited during the conduct of this flight.
Final Report:

Crash of a Douglas DC-9-31 in Fairland: 82 killed

Date & Time: Sep 9, 1969 at 1529 LT
Type of aircraft:
Operator:
Registration:
N988VJ
Survivors:
No
Schedule:
Boston - Baltimore - Cincinnati - Indianapolis - Saint-Louis
MSN:
47211
YOM:
1968
Flight number:
AL853
Crew on board:
4
Crew fatalities:
Pax on board:
78
Pax fatalities:
Other fatalities:
Total fatalities:
82
Captain / Total flying hours:
23813
Captain / Total hours on type:
900.00
Copilot / Total flying hours:
2980
Copilot / Total hours on type:
651
Aircraft flight hours:
3170
Circumstances:
An Allegheny Airlines DC-9 and a Forth Corporation Piper PA-28-140 Cherokee registered N7374J collided in flight approximately 4 miles northwest of Fairland, Indiana, at approximately 1529 e.d.t., September 9, 1969. All 83 occupants, 78 passengers and four crew members, aboard the DC-9 and the pilot of the PA-28 were fatally injured. Both aircraft were destroyed by the collision and ground impact. Allegheny flight AL853 was wider positive radar control of the Federal Aviation Administration's Indianapolis Approach Control, descending from 6,000 feet to an assigned altitude of 2,530 feet at the time of the collision. N7374J has being flown by a student pilot on a solo cross-country flight in accordance with a Visual Flight Rules (VFR) flight plan. The collision occurred at an altitude of approximately 3,550 feet. The visibility in the area was at least 15 miles, but there was an intervening cloud condition wbich precluded the crew of either aircraft from sighting the other until a few seconds prior to collision.
Probable cause:
The deficiencies in the collision avoidance capability of the Air Traffic Control (ATC) system of the Federal Aviation Administration in a terminal area wherein there was mixed Instrument Flight Rules (IFR) and Visual Flight Rules (VFR) traffic. The deficiencies included the inadequacy of the see-and-avoid concept under the circumstances of this case; the technical limitations of radar in detecting all aircraft; and the absence of Federal Aviation Regulations which would provide a system of adequate separation of mixed VFR and IFR traffic in terminal areas.
Final Report:

Crash of a Convair CV-580 in Bradford: 11 killed

Date & Time: Jan 6, 1969 at 2035 LT
Type of aircraft:
Operator:
Registration:
N5825
Survivors:
Yes
Schedule:
Washington DC – Harrisburg – Bradford – Erie – Detroit
MSN:
386
YOM:
1956
Flight number:
AL737
Crew on board:
3
Crew fatalities:
Pax on board:
25
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
5761
Captain / Total hours on type:
499.00
Copilot / Total flying hours:
8220
Copilot / Total hours on type:
738
Aircraft flight hours:
27285
Circumstances:
Allegheny Airlines Flight 737 was a scheduled passenger flight from Washington, DC, to Detroit, MI, with en route stops at Harrisburg, Bradford, and Erie, PA. The flight was uneventful until it arrived in the Bradford area, about 20:22. About 20:23, Erie Approach Control asked flight 737 to report their distance to the airport: "Allegheny seven thirty seven, what are you showing DME from Bradford?". Upon which the crew replied, "Fifteen". Erie Approach Control then instructed, "... descend and cruise four thousand via Victor thirty three and cleared for the VOR thirty two (runway 32) approach to the Bradford Airport, report leaving six and Bradford's current weather sky partially obscured, measured ceiling eight hundred overcast, visibility one and one half and light snow showers, wind one seventy degrees at ten (knots) Bradford altimeter twenty nine point four nine." At ten miles from the airport Flight 737 asked for clearance to make its instrument approach to runway 14 instead of runway 32. The Bradford FSS Specialist obtained approval for this change from Erie Approach Control and so advised the flight. At 20:31 the flight reported completing the procedure turn inbound. The Convair clipped treetops 4,7nm short of the airport and cut a swath through trees bordering a fairway of the Pine Acres Golf Course. The aircraft came to rest inverted. Both pilots and 9 passengers were killed while 17 other occupants were injured. The aircraft was destroyed.
Probable cause:
Investigations were unable to determine precisely the probable cause of this accident. Of some 13 potential causes examined by the Board, three remain after final analysis. They are:
- Misreading of the altimeter by the captain,
- A malfunction of the captain's altimeter after completion of the instrument approach procedure turn, and
- A misreading of the instrument approach chart. Of these three, no single one can be accepted or rejected to the exclusion of another based on the available evidence.
Final Report:

Crash of a Convair CV-580 in Bradford: 20 killed

Date & Time: Dec 24, 1968 at 2012 LT
Type of aircraft:
Operator:
Registration:
N5802
Survivors:
Yes
Schedule:
Detroit – Erie – Bradford – Harrisburg – Washington DC
MSN:
410
YOM:
1957
Flight number:
AL736
Crew on board:
6
Crew fatalities:
Pax on board:
41
Pax fatalities:
Other fatalities:
Total fatalities:
20
Captain / Total flying hours:
6701
Captain / Total hours on type:
1477.00
Copilot / Total flying hours:
4330
Copilot / Total hours on type:
928
Aircraft flight hours:
29173
Circumstances:
Allegheny Airlines Flight 736 departed Detroit, MI for a flight to Washington, DC with intermediate stops at Erie, Bradford and Harrisburg, PA. The Convair CV-580 took off from Erie at 19:46. At 20:06 Flight 736 reported over the VOR outbound at the beginning of the instrument approach procedure. Erie Approach Control then told the crew to contact the Bradford Flight Service Station (FSS). At 20:08:47 the flight reported that they were doing the procedure turn inbound for runway 32 and Bradford FSS told them wind was 290 degrees at 15 knots. The Convair descended in light snow showers until the aircraft contacted trees along terrain which had an average upslope of 1.5deg some 2,5 NM short of the runway. The airplane cut a swath through the trees and impacted the ground at a point 800 feet from the initial tree contact. The fuselage came to rest inverted.
Probable cause:
The continuation of the descent from the final approach fix through the Minimum Descent Altitude and into obstructing terrain at a time when both flight crewmembers were looking outside the aircraft in an attempt to establish visual reference to the ground. Contributing factors were the minimal visual references available at night on the approaches to the Bradford Regional Airport; a small but critical navigational error during the later stages of the approach; and a rapid change in visibility conditions that was not known to the crew.
Final Report:

Crash of a Convair CV-440 Metropolitan in Harrisburg

Date & Time: Nov 29, 1966 at 1728 LT
Operator:
Registration:
N3414
Flight Phase:
Survivors:
Yes
Schedule:
Harrisburg – Pittsburgh
MSN:
45
YOM:
1953
Flight number:
AL305
Crew on board:
4
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17718
Captain / Total hours on type:
2500.00
Circumstances:
During the takeoff roll on runway 26, the electrical system failed. The crew aborted the takeoff maneuver, started an emergency braking procedure and triggered the reverse thrust system. The reverse thrust system failed to work so the aircraft was unable to stop within the remaining distance and overran. Past the runway end, the nose gear collapsed and the airplane came to rest against a metallic tower supporting the approach light system. All 16 occupants were evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Failure of the electrical system due to an improperly installed heater on part of the ground technicians. Improper emergency procedures on part of the pilot-in-command.
Final Report:

Crash of a Convair CV-440 Metropolitan in Williamsport

Date & Time: Jul 23, 1965 at 1506 LT
Operator:
Registration:
N8415H
Flight Phase:
Survivors:
Yes
Schedule:
Pittsburgh-Du Bois-Phillipsburg-Williamsport-Wilkes-Barre-Newark
MSN:
125
YOM:
1953
Flight number:
AL604
Crew on board:
4
Crew fatalities:
Pax on board:
36
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10071
Captain / Total hours on type:
1296.00
Copilot / Total flying hours:
5061
Copilot / Total hours on type:
1410
Aircraft flight hours:
26266
Circumstances:
Allegheny Airlines, Inc., Flight 604, a Convair 340/440, N8415H, crashed 5 miles east-northeast of the Williamsport-Lycoming County Airport, Montoursville, Pennsylvania, on July 23, 1965. The 36 passengers, 3 crew members, and 1 jumpseat rider survived but received varying degrees of injuries. The flight, regularly scheduled from Pittsburgh, Pennsylvania to Newark, New Jersey, with intermediate stops at Dubois, Phillipsburg, Williamsport and Wilkes-Barre, Pennsylvania, departed Runway 09 at 1503. e.d.t. Shortly after takeoff smoke and fire were observed coming from the right engine and at approximately 1505:30 the captain advised "Six oh four is coming back in, we've got the right engine feathered.” The crash occurred moments later on the crest of a ridge approximately 600 feet above the airport elevation. The aircraft was destroyed by fire. The failure of the right engine is attributed to the failure of the front row master rod and all the associated link rods. Damage to the rod ends precluded any determination of the cause of the master rod failure.
Probable cause:
The Board determines that the probable cause of this accident was the failure of the crew to implement proper procedures for an engine failure on takeoff.
Final Report: