Crash of a Piper PA-31-350 Navajo Chieftain near Brevard: 1 killed

Date & Time: Nov 12, 1982 at 0514 LT
Registration:
N59771
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Columbus - Asheville
MSN:
31-7652401
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3300
Captain / Total hours on type:
900.00
Aircraft flight hours:
5131
Circumstances:
After a missed approach at Asheville the flight was cleared to the Greenville-Spartanburg Airport at Greer, SC. Enroute to Greer radar contact was lost. In response to a query from Atlanta artcc the pilot verified his position as being on the 235° radial of Spartanburg VOR and 11.9 miles southwest. He was then cleared to descend to 2,700 feet and execute an ILS approach. The aircraft impacted a mountain at the 3,200 feet level. The wreckage was found on the 235° radial of the Sugarloaf mountain vortac and at 24 miles. Review of the aircraft's logbook revealed that mechanical irregularities reported were not corrected for long periods of time. No corrective action was listed for an "outer marker inop aural and visual (needs to be fixed now, since ADF is also inoperative) and 'light in #2 VOR head out'. The marker beacon was described as inoperative on three dates beginning 22 August 1981 and the ADF was described as inoperative on seven dates beginning 8 May 1981. No corrective action was listed for any entry about the marker beacon or ADF. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: in flight collision with terrain/water
Phase of operation: descent - normal
Findings
1. (f) comm/nav equipment - inoperative
2. (f) maintenance - not performed - company maintenance personnel
3. (f) operation with known deficiencies in equipment - attempted - pilot in command
4. (f) company-induced pressure - company/operator management
5. (f) light condition - dark night
6. (f) weather condition - low ceiling
7. (f) missed approach - performed - pilot in command
8. (c) ifr procedure - improper - pilot in command
9. (c) flight/navigation instrument(s) - improper use of - pilot in command
10. (f) company-induced pressure - company/operator management
11. (f) excessive workload (task overload) - pilot in command
Final Report:

Crash of a Cessna 401A in Fort Pierce

Date & Time: Nov 9, 1980 at 1600 LT
Type of aircraft:
Registration:
N6233Q
Survivors:
Yes
Schedule:
Columbus - Fort Pierce
MSN:
401A-0033
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
988
Captain / Total hours on type:
66.00
Circumstances:
On final approach to Fort Pierce-St Lucie-County Airport, the pilot initiated an evasive maneuver to avoid collision with another aircraft turning in front of him. Due to insufficient speed, the twin engine airplane stalled and crashed. All three occupants were seriously injured.
Probable cause:
Stall during go-around after the pilot failed to maintain flying speed.
Final Report:

Crash of a Lockheed L-1049H Super Constellation in Columbus: 3 killed

Date & Time: Jun 22, 1980 at 1359 LT
Registration:
N74CA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Columbus - Seattle
MSN:
4850
YOM:
1959
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
17250
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
8000
Copilot / Total hours on type:
100
Aircraft flight hours:
20000
Circumstances:
The four engine airplane departed Columbus-Municipal (Bakalar) Airport on a cargo flight to Seattle, carrying a load of aircraft spare parts. After takeoff, during initial climb, the airplane encountered difficulties to gain height, struck power cables, stalled and crashed in flames in a soybean field. Both pilots and a passenger were killed while five other occupants were injured. The aircraft was totally destroyed by impact forces and a post crash fire.
Probable cause:
The flight crew's inadequate and uncoordinated response to the No 2 engine fire warning. The flight engineer failed to correct a gradual power decay on the other engines which occurred while he was retarding the No 2 engine throttle, and the power decay went uncorrected by the pilot and co-pilot. The lack of co-ordination and the lack of corrective action may have been caused by the lack of recent flight crew experience in the L-1049 aircraft. Contributing to the accident was the aircraft's over maximum take-off weight, the crew's use of less than full power for take-off, and the use of less than take-off cowl flaps which precluded adequate engine cooling.
Final Report:

Crash of a Convair CV-440-86 Metropolitan off Shippingport

Date & Time: May 12, 1978 at 1530 LT
Operator:
Registration:
N9302
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Columbus - Fort Lauderdale
MSN:
416
YOM:
1957
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15000
Circumstances:
En route from Columbus to Fort Lauderdale, the crew encountered technical problems with both engines. Tower asked the pilot if he wanted to return to the airport due to slow climb but there was no reply. The crew attempted to ditch the aircraft in the Ohio River. The airplane slid on water and came to rest off Shippingport. All three occupants were evacuated safely while the aircraft was written off.
Probable cause:
Double engine failure in flight due to master and connecting rods failure. The following contributing factors were reported:
- Improper in-flight decisions,
- Material failure,
- Failure of both engines,
- Inadequate preflight preparation,
- Aircraft came to rest in water,
- Forced landing off airport on water.
Final Report:

Crash of a Beechcraft D18S in Covington

Date & Time: Feb 14, 1977 at 2326 LT
Type of aircraft:
Registration:
N321D
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Covington - Columbus
MSN:
A-413
YOM:
1948
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14136
Captain / Total hours on type:
6233.00
Circumstances:
On a slush covered runway, the pilot completed a premature liftoff. After rotation, the airplane stalled during initial climb and crashed. The aircraft was destroyed and the pilot, sole on board, was seriously injured.
Probable cause:
Stall during initial climb after the pilot completed a premature liftoff and failed to maintain flying speed. The following contributing factors were reported:
- Inadequate preflight preparation,
- Physical impairment,
- Ice/slush on runway,
- Cargo net found underneath mail,
- Pilot no feeling well.
Final Report:

Crash of a Rockwell Shrike Commander 500S off South Portsmouth: 1 killed

Date & Time: Feb 21, 1975 at 1508 LT
Operator:
Registration:
N9179N
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Columbus - Huntington
MSN:
500-3126
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2089
Circumstances:
En route from Columbus to Huntington, the pilot informed ATC about an engine failure and attempted to divert to the nearest airport. Control was lost and the airplane crashed in the Ohio River off South Portsmouth, Kentucky. The aircraft was destroyed and the pilot's body was not recovered.
Probable cause:
Powerplant failure for undetermined reason. The pilot was observed to exit the aircraft and to swim toward shore. He disappeared and his body was never recovered.
Final Report:

Crash of a Beechcraft A90 King Air in Washington DC: 5 killed

Date & Time: Jan 25, 1975 at 1210 LT
Type of aircraft:
Operator:
Registration:
N57V
Survivors:
No
Site:
Schedule:
Columbus - Washington DC
MSN:
LJ-268
YOM:
1967
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
9745
Captain / Total hours on type:
50.00
Circumstances:
On a VOR/DME approach to Washington-National Airport, the crew encountered low clouds and failed to realize his altitude was insufficient. On final, the twin engine airplane struck a radio antenna. Upon impact, the left wing was torn off and the aircraft crashed in flames in the garden of the American University campus. The aircraft was destroyed by impact forces and a post crash fire and all five occupants were killed.
Probable cause:
The exact cause of the accident could not be determined. The following findings were reported:
- Low ceiling,
- High obstructions,
- Separation of the left wing in flight,
- Descended below minimum approach segment altitude during VOR/DME approach,
- Hit radio tower, causing the left wing to separate.
Final Report:

Crash of a Boeing 727-231 on Mt Weather: 92 killed

Date & Time: Dec 1, 1974 at 1110 LT
Type of aircraft:
Operator:
Registration:
N54328
Survivors:
No
Site:
Schedule:
Indianapolis - Columbus - Washington DC
MSN:
20306/791
YOM:
1970
Flight number:
TW514
Crew on board:
7
Crew fatalities:
Pax on board:
85
Pax fatalities:
Other fatalities:
Total fatalities:
92
Captain / Total flying hours:
3765
Captain / Total hours on type:
2899.00
Copilot / Total flying hours:
6205
Copilot / Total hours on type:
1160
Aircraft flight hours:
11997
Circumstances:
Trans World Airlines Flight TW514 was a regularly scheduled flight from Indianapolis, IN (IND), to Washington-National Airport, DC (DCA), with an intermediate stop at Columbus-Port Columbus International Airport, OH (CMH). Flight 514 departed Indianapolis at 08:53 EST and arrived in Columbus at 09:32. The Boeing 727 departed Columbus at 10:24, eleven minutes late. There were 85 passengers and 7 flight crew members aboard the aircraft when it departed Columbus. At 10:36, the Cleveland Air Route Traffic Control Center (ARTCC) informed the crew of Flight 514 that no landings were being made at Washington National Airport because of high crosswinds, and that flights destined for that airport were either being held or being diverted to Dulles International Airport (IAD). At 10:38, the captain of Flight 514 communicated with the dispatcher in New York and advised him of the information he had received. The dispatcher, with the captain's concurrence, subsequently amended Flight 514's release to allow the flight to proceed to Dulles. At 10:42, Cleveland ARTCC cleared Flight 514 to Dulles Airport via the Front Royal VOR, and to maintain FL290. One minute later, the controller cleared the flight to descend to FL230 and to cross a point 40 miles west of Front Royal at that altitude. Control of the flight was then transferred to the Washington ARTCC and communications were established with that facility at 10:48. In the meantime, the flightcrew discussed the instrument approach to runway 12, the navigational aids, and the runways at Dulles, and the captain turned the flight controls over to the first officer. When radio communications were established with Washington ARTCC, the controller affirmed that he knew the flight was proceeding to Dulles. Following this contact, the crew discussed the various routings they might receive to conduct a VOR/DME approach to runway 12 at Dulles. At 10:51, the Washington ARTCC controller requested the flight's heading. After being told that the flight was on a heading of 100 degrees, the controller cleared the crew to change to a heading of 090°, to intercept the 300° radial of the Armel VOR, to cross a point 25 miles northwest of Armel to maintain 8,000 feet, "...and the 300° radial will be for a VOR approach to runway 12 at Dulles." He gave the crew an altimeter setting of 29.74 for Dulles. The crew acknowledged this clearance. The pilots again discussed the VOR/DME approach At 10:55, the landing preliminary checklist was read by the flight engineer and the other crewmembers responded to the calls. A reference speed of 127 kts was calculated and set on the airspeed indicator reference pointers. The altimeters were set at 29.74. The crew then again discussed items on the instrument approach chart including the Round Hill intersection, the final approach fix, the visual approach slope indicator and runway lights, and the airport diagram. At 10:59, the captain commented that the flight was descending from 11,000 feet to 8,000 feet. He then asked the controller if there were any weather obstructions between the flight and the airport. The controller replied that he did not see any significant weather along the route. The captain replied that the crew also did not see any weather on the aircraft weather radar. At 11:01, the controller cleared the flight to descend to and maintain 7,000 feet and to contact Dulles approach control. Twenty-six seconds later, the captain initiated a conversation with Dulles approach control and reported that the aircraft was descending from 10,000 feet to maintain 7,000 feet. He also reported having received the information "Charlie" transmitted on the ATIS broadcast. The controller replied with a clearance to proceed inbound to Armel and to expect a VOR/DME approach to runway 12. The controller then informed the crew that ATIS information Delta was current and read the data to them. The crew determined that the difference between information Charlie and Delta was the altimeter setting which was given in Delta as 29.70. There was no information on the CVR to indicate that the pilots reset their altimeters from 29.74. At 11:04, the flight reported it was level at 7,000 feet. Five seconds after receiving that report, the controller said, "TWA 514, you're cleared for a VOR/DME approach to runway 12." This clearance was acknowledged by the captain. The CVR recorded the sound of the landing gear warning horn followed by a comment from the captain that "Eighteen hundred is the bottom." The first officer then said, "Start down." The flight engineer said, "We're out here quite a ways. I better turn the heat down." At 11:05:06, the captain reviewed the field elevation, the minimum descent altitude, and the final approach fix and discussed the reason that no time to the missed approach point was published. At 11:06:15, the first officer commented that, "I hate the altitude jumping around. Then he commented that the instrument panel was bouncing around. At 11:06:15, the captain said, "We have a discrepancy in our VOR's, a little but not much." He continued, "Fly yours, not mine." At 11:06:27, the captain discussed the last reported ceiling and minimum descent altitude. concluded, "...should break out." At 11:06:42, the first officer said, "Gives you a headache after a while, watching this jumping around like that." At 11:07:27, he said, "...you can feel that wind down here now." A few seconds later, the captain said, "You know, according to this dumb sheet it says thirtyfour hundred to Round Hill --- is our minimum altitude." The flight engineer then asked where the captain saw that and the captain replied, "Well, here. Round Hill is eleven and a half DME." The first officer said, "Well, but ---" and the captain replied, "When he clears you, that means you can go to your ---" An unidentified voice said, "Initial approach, and another unidentified voice said, "Yeah!" Then the captain said "Initial approach altitude." The flight engineer then said, "We're out a --- twenty-eight for eighteen." An unidentified voice said, "Right, and someone said, "One to go." At 11:08:14, the flight engineer said, "Dark in here," and the first officer stated, "And bumpy too." At 11:08:25, the sound of an altitude alert horn was recorded. The captain said, "I had ground contact a minute ago," and the first officer replied, "Yeah, I did too." At 11:08:29, the first officer said, "...power on this.... " The captain said "Yeah --- you got a high sink rate." "Yeah," the first officer replied. An unidentified voice said, "We're going uphill, " and the flight engineer replied, "We're right there, we're on course." Two voices responded, "Yeah!" The captain then said, "You ought to see ground outside in just a minute -- Hang in there boy." The flight engineer said, "We're getting seasick." At 1108:57, the altitude alert sounded. Then the first officer said, "Boy, it was --- wanted to go right down through there, man," to which an unidentified voice replied, "Yeah!" Then the first officer said, "Must have had a # of a downdraft." At 1109:14, the radio altimeter warning horn sounded and stopped. The first officer said, "Boy!" At 11:09:20, the captain said, "Get some power on." The radio altimeter warning horn sounded again and stopped. At 11:09:22, the sound of impact was recorded. After the aircraft left 7,000 feet, the descent was continuous with little rate variation until the indicated altitude was about 1,750 feet. increased about 150 feet over a 15-second period and then decreased about 200 feet during a 20-second period. The recorded altitude remained about 1,750 feet until the airplane impacted the west slope of Mount Weather, Virginia, about 25 nmi from Dulles, at an elevation of about 1,670 feet (509 m). The aircraft was totally destroyed by impact forces and a post crash fire and all 92 occupants were killed.
Probable cause:
The National Transportation Safety Board determines that the probable cause of the accident was the crew's decision to descend to 1,800 feet before the aircraft had reached the approach segment where that minimum altitude applied result of inadequacies and lack of clarity in the air traffic control procedures which led to a misunderstanding on the part of the pilots and of the controllers regarding each other's responsibilities during operations in terminal areas under instrument meteorological conditions. Nevertheless, the examination of the plan view of the approach chart should have disclosed to the captain that a minimum altitude of 1,800 feet was not a safe altitude.
The following contributing factors were reported:
- The failure of the FAA to take timely action to resolve the confusion and misinterpretation of air traffic terminology although the Agency had been aware of the problem for several years,
- The issuance of the approach clearance when the flight was 44 miles from the airport on an unpublished route without clearly defined minimum altitudes,
- Inadequate depiction of altitude restrictions on the profile view of the approach chart for the VOR/DME approach to runway 12 at Dulles International Airport.
Final Report:

Crash of a Cessna 411 in Lansing

Date & Time: Dec 14, 1973 at 1106 LT
Type of aircraft:
Operator:
Registration:
N1056R
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lansing - Columbus
MSN:
411-0245
YOM:
1967
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4000
Captain / Total hours on type:
800.00
Circumstances:
Just after liftoff, while in initial climb, the twin engine airplane stalled and crashed onto the runway and came to rest. Both occupants were uninjured while the aircraft was damaged beyond repair.
Probable cause:
Engine malfunction during initial climb caused the aircraft to stall and to crash. The following factors were reported:
- Improper operation or powerplant,
- Foreign material affecting normal operations,
- Fuel system: ram air assembly,
- The pilot attention diverted from operation of aircraft,
- Failed to obtain/maintain flying speed,
- Partial loss of power on both engines,
- Engine air intake openings restricted by snow,
- Pilot did not use alternate air,
- Pilot elected to land cartwheeled.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Pataskala: 1 killed

Date & Time: Jul 3, 1972 at 1132 LT
Operator:
Registration:
N5977M
Survivors:
No
Schedule:
Ann Arbor - Columbus
MSN:
421B-0220
YOM:
1972
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1563
Captain / Total hours on type:
500.00
Circumstances:
While approaching Columbus-John Glenn in marginal weather conditions, the pilot failed to realize his altitude was too low when the airplane struck power cables and trees, stalled and crashed in Pataskala, about 10,5 miles east of the airport. The aircraft was destroyed and the pilot, sole on board, was killed.
Probable cause:
The accident was caused by the incapacitation of the pilot. The following factors were reported:
- Low ceiling and fog,
- The pilot had moderate to severe arteriosclerosis.
Final Report: