Crash of a Nord 262A-27 in Reading: 3 killed

Date & Time: Apr 9, 1977 at 1356 LT
Type of aircraft:
Operator:
Registration:
N7886A
Flight Type:
Survivors:
No
Schedule:
Philadelphia - Reading
MSN:
47
YOM:
1968
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The crew was completing a ferry flight from Philadelphia to Reading. 54 seconds after being cleared for an approach to runway 31 at Reading-General Spaatz Airport, while flying at an altitude of 4,500 feet, the twin engine airplane collided with a Cessna 195 registered N4377N and owned by the Hagerstown Cash Register Company. His pilot was performing a private flight from Lincoln Park to York, Pennsylvania. Following the collision, both aircraft went out of control, entered a dive and crashed. All four occupants on both aircraft were killed.
Probable cause:
Inflight collision while descending to Reading Airport after the pilot-in-command failed to see and avoid other aircraft. The following contributing factors were reported:
- Pilot of other aircraft,
- Not under radar contact,
- No control area.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain off Grand View-On-Hudson: 3 killed

Date & Time: Dec 4, 1976 at 1205 LT
Operator:
Registration:
N59825
Flight Phase:
Survivors:
No
Schedule:
Philadelphia - White Plains
MSN:
31-7652076
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
3000
Circumstances:
En route from Philadelphia to White Plains with three people on board, the twin engine airplane collided with a Cessna 172 operated by Teterboro Flight Service, registered N75604 and carrying two people. Following the collision, both aircraft went out of control and crashed into the Hudson River near the Tappan Zee Bridge. Both aircraft were destroyed and all five occupants have been killed.
Probable cause:
In-flight collision after the pilot failed to see and avoid other aircraft. The following contributing factors were reported:
- Not under radar contact,
- No control zone,
- Fresh scuff marks on leading edge of deicing boot of vertical stabilizer.
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:

Crassh of an Howard 350 in Philadelphia

Date & Time: Oct 15, 1972 at 1127 LT
Operator:
Registration:
N361MC
Survivors:
Yes
Schedule:
Newark – Philadelphia
MSN:
5275
YOM:
1943
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3768
Captain / Total hours on type:
68.00
Circumstances:
After touchdown at Philadelphia-Intl Airport, the crew inadvertently retracted the gear. The twin engine airplane sank on its belly and slid for several yards before coming to rest in flames. All eight occupants escaped uninjured while the aircraft was partially destroyed by a post crash fire that was caused by the rupture of a fuel tank in the left wing.
Probable cause:
The pilot inadvertently retracted the gear after landing. Left wing tank ruptured.
Final Report:

Crash of a Mitsubishi MU-2-30 Marquise off Atlantic City: 3 killed

Date & Time: Apr 16, 1972 at 1419 LT
Type of aircraft:
Registration:
N132MA
Flight Phase:
Survivors:
No
Schedule:
Atlantic City - Philadelphia
MSN:
503
YOM:
1970
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8000
Captain / Total hours on type:
40.00
Circumstances:
Shortly after takeoff, while climbing, the twin engine airplane went out of control, nosed down and crashed into the Atlantic Ocean, few miles offshore. The aircraft was lost and all three occupants were killed. At the time of the accident, there were some fog banks along the shore.
Probable cause:
Loss of control and uncontrolled descent following a bird collision from climb to cruise. The following factors were reported:
- Evidence that geese hit windshield, possibly incapacitating one or both pilots,
- Fog bank along the shore.
Final Report:

Crash of an Howard Eldorado 700 in Philadelphia

Date & Time: Sep 11, 1971 at 0922 LT
Registration:
N25YC
Survivors:
Yes
Schedule:
Reading – Philadelphia
MSN:
5598
YOM:
1943
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19000
Captain / Total hours on type:
400.00
Circumstances:
On approach to Philadelphia International Airport, the crew encountered poor weather conditions with thunderstorm activity, heavy rain falls and turbulences. On short final, the captain decided to make a go-around when the airplane struck the ground and crashed few miles short of runway. All six occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Improper IFR operation on part of the crew who descended below MDA while encountering severe turbulences and heavy rain from a thunderstorm cell. The weather was slightly worse than forecast.
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:

Crash of a Mitsubishi MU-2B-20 Marquise in Salisbury

Date & Time: Jan 16, 1970 at 0115 LT
Type of aircraft:
Operator:
Registration:
N764Q
Survivors:
Yes
Schedule:
Miami – Norfolk – Philadelphia
MSN:
141
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9100
Captain / Total hours on type:
137.00
Circumstances:
The twin engine aircraft was completing a flight from Miami to Philadelphia with an intermediate stop in Norfolk, Virginia. On the second leg, the pilot encountered fuel problems and was forced to divert to Salisbury Regional Airport for an emergency landing. On final, both engines stopped simultaneously and the airplane stalled, struck trees and crashed in a wooded area. All five occupants were injured, two of them seriously. The aircraft was destroyed.
Probable cause:
Double engine failure caused by a fuel starvation. The following factors were considered as contributing:
- Mismanagement of fuel on part of the pilot,
- Miscalculation of fuel consumption on part of the pilot,
- Fuel starvation,
- Double engine failure,
- Fuel in tip tanks only as the others were empty,
- Undetermined amount of fuel lost due to broken O ring seal,
- Fuel level control valve.
Final Report:

Crash of a Douglas DC-7BF in Philadelphia

Date & Time: Jul 2, 1968 at 1811 LT
Type of aircraft:
Operator:
Registration:
N762Z
Flight Type:
Survivors:
Yes
Schedule:
Norfolk – Philadelphia
MSN:
44922
YOM:
1956
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19616
Captain / Total hours on type:
7095.00
Circumstances:
The crew was completing a cargo flight from Norfolk to Philadelphia on behalf of the US Air Force. After touchdown on wet runway 09/27 at Philadelphia-Intl Airport, the crew encountered difficulties to decelerate properly. The four engine aircraft suffered hydroplaning then went out of control and veered off runway to the right. While contacting soft ground, the undercarriage collapsed and the right wing was torn off. The airplane came to rest in flames and was destroyed by a post crash fire while all three crew members escaped uninjured.
Probable cause:
The accident was the consequence of the following factors:
- The crew failed to maintain directional control,
- Improper operation of powerplant,
- Asymmetrical thrust reversal,
- Wet runway,
- Hydroplaning,
- Overload failure,
- Asymmetrical power applied during reversing phase of landing due to n° 1 prop circuit breaker deactivated.
Final Report:

Crash of a Rockwell Aero Commander 680F in Reynoldsdale: 2 killed

Date & Time: Apr 15, 1967 at 0420 LT
Operator:
Registration:
N718MS
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Altoona - Philadelphia
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3991
Captain / Total hours on type:
1972.00
Circumstances:
The twin engine airplane departed Altoona Airport at 0328LT. Few minutes after takeoff, the pilot informed ATC he was starting the descent to Philadelphia Airport located 172 miles east of his position. About an hour later, apparently disoriented, the pilot lost control of the airplane that crashed in an open field located in Reynoldsdale. The pilot and a passenger were killed while the second passenger was seriously injured.
Probable cause:
The pilot became lost and disoriented due to physical impairment caused by excessive alcohol consumption.
Final Report: