Crash of a Lockheed L-049 Constellation on Peak Genoa: 85 killed

Date & Time: Mar 1, 1964 at 1129 LT
Operator:
Registration:
N86504
Survivors:
No
Site:
Schedule:
Oakland – San José – Salinas – South Lake Tahoe
MSN:
2025
YOM:
1946
Flight number:
PD901A
Crew on board:
4
Crew fatalities:
Pax on board:
81
Pax fatalities:
Other fatalities:
Total fatalities:
85
Captain / Total flying hours:
15391
Captain / Total hours on type:
3266.00
Copilot / Total flying hours:
3553
Copilot / Total hours on type:
1353
Aircraft flight hours:
45629
Circumstances:
The Paradise Airlines Lockheed Constellation operated Flight 901A from Oakland (OAK) to Tahoe-Valley Airport (TVL) via Salinas (SNS) and San Jose (SJC). The aircraft departed Oakland at 08:43 and was ferried to Salinas, arriving at 09:11. The flight departed at 09:27 with 18 passengers and arrived at San Jose at 09:46. The Constellation departed was airborne again at 10:40 on a VFR flight plan. After becoming airborne, the crew requested and received an IFR clearance via airways Victor 6 South to Sacramento, Victor 6 to the Lake Tahoe VOR, to maintain 11,000 feet. The company prepared flight plan then called for a VFR flight to the Tahoe Valley Airport because there was no approved IFR approach procedure for the destination. At 10:57 Flight 901A was in radio communication with Paradise Flight 802 which was outbound from the Tahoe Valley Airport. The captain of Flight 802 advised the crew of Flight 901 that he had encountered "...icing at 12,000 (feet) ... there were snow showers over the lake and clouds topping mountains in the vicinity ...". Flight 901A then climbed to a cruising altitude of 15000 feet. The crew of Flight 901A contacted the Paradise Airlines passenger agent at the Tahoe Valley Airport at 11:27. At this time he gave them the 11:00 Tahoe Valley weather which was: Estimated ceiling 2,000 feet overcast; 3 miles visibility; snow showers; temperature 32°; dewpoint 32°; wind from 210°; 10 knots, gusts to 15 knots; altimeter 29.97. He also asked the crew to call the company if they decided to land at Reno, Nevada rather than Tahoe Valley. The crew acknowledged this transmission with "will do." The crew apparently decided to abandon the approach. They took up a heading which took them towards the high terrain east of the lake. It is very likely that from their position over the Tahoe VOR they were able to observe the VFR conditions that existed east of Lake Tahoe on the leeward side of the mountains. Additionally, investigators assumed that the first officer was aware of the existence of Daggett Pass and considered it an access to VFR conditions beyond the pass. An altitude of 9,000 feet would provide about 1,500 feet terrain clearance through the center of the pass. Then, either because they believed they had sufficient altitude to clear the terrain or because they were unable to climb higher due to structural ice, the aircraft leveled off. At that time the aircraft struck several trees on the west slope of a ridge of Genoa Peak at approximately 8,675 ft, slightly right-wing-low in a nearly level flight attitude. The airplane broke up, killing all aboard.
Probable cause:
The Board determines that the probable cause of this accident was the pilot's deviation from prescribed VFR flight procedures in attempting a visual landing approach in adverse weather conditions. This resulted in an abandoned approach and geographical disorientation while flying below the minimum altitude prescribed or operations in mountainous areas.
Final Report:

Crash of a Douglas R4D-5 at Fallon NAS: 6 killed

Date & Time: Apr 18, 1961
Operator:
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Grosse Ile – Fallon – Alameda
Crew on board:
4
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
Shortly after takeoff from Fallon NAS, while climbing to a height of 10 feet, the airplane stalled and crashed in flames. Six occupants were killed and 12 others were injured.

Crash of a Douglas DC-7 near Las Vegas: 47 killed

Date & Time: Apr 21, 1958 at 0830 LT
Type of aircraft:
Operator:
Registration:
N6328C
Flight Phase:
Survivors:
No
Site:
Schedule:
Los Angeles – Denver – New York
MSN:
45142
YOM:
1956
Flight number:
UA736
Crew on board:
5
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
47
Circumstances:
United Airlines Flight 736 departed Los Angeles International Airport at 0737 hours Pacific standard time with 42 passengers and 5 crew aboard. It was a scheduled passenger flight to New York, which was proceeding normally in accordance with an IFR flight plan along Victor Airway 16 to Ontario, California, and Victor Airway 8 to Denver. The aircraft was cleared to a cruising altitude of 21 000 ft msl and advised to climb in VFR weather conditions. At 0735 the flight reported to Aeronautical Radio that it was over Ontario at 12 000 ft and was climbing in VFR conditions. Then at 081 1 it reported over Daggett at its cruising altitude of 21 000 ft and estimated that it would reach Las Vegas (omni range station) at 0831, This was the last position report made by the flight. At approximately 0745 hours that morning F-100F, 56-3755, took off from Nellis Air Force Base, Las Vegas, Nevada on an instrument training flight carrying an instructor and a trainee pilot. The flight was in accordance with a VFR local flight plan filed with Nellis Operations and the local traffic control tower. At approximately 0823, 755 called Nellis VFR Control and reported that it was "inbound on KRAM" ( a local commercial radio broadcast station). The flight requested an altitude assignment from which it would conduct a simulated ADF instrument jet penetration utilizing KRAM. The VFR controller assigned 755, 28 000 ft and advised it to report over the radio station. At approximately 0828, the flight reported that it was over KRAM requesting a penetration. The VFR controller cleared it for an immediate penetration and requested that it report the penetration turn. 755 then reported leaving 28 000 ft. There were no &her reports from the flight in connection with this procedure. At 0830 the offices of Aeronautical Radio at Los Angeles, Denver and Salt Lake City heard an emergency message from the United flight.. . . . " United 736, Mayday, midair collision, over Las Vegas. " At the same time, as nearly as can be determined, there was an unrecorded emergency transmission from the F-1 00F. This message was heard by the VFR controller and by the two pilots of another F-100F. All were agreed that the first portion of the emergency transmission was "Mayday, Mayday, this is 755. " The last part of the message was either, "We've had a flameout" or 'We're bailing out." The aircraft collided at 21 000 ft over a position later determined to be about 9 miles southwest of the Las Vegas VOR station, on Victor Airway 8, approximately 1-3/4 miles to the right (southeast) of the centerline. Both aircraft fell out of control and crashed killing the 47 persons on board the DC-7 and both pilots of the F-100F.
Probable cause:
The probable cause of this collision was a high rate of near head-on closure at high altitude; human and cockpit limitations; and the failure of Nellis Air Force Base and the Civil Aeronautics Administration to take every measure to reduce a known collision exposure.
Final Report:

Crash of a Martin 404 in Las Vegas

Date & Time: Nov 15, 1956 at 1504 LT
Type of aircraft:
Operator:
Registration:
N40404
Survivors:
Yes
Schedule:
Kansas City – Topeka – Wichita – Amarillo – Santa Fe – Albuquerque – Las Vegas – Los Angeles
MSN:
14104
YOM:
1951
Flight number:
TW163
Crew on board:
3
Crew fatalities:
Pax on board:
35
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9431
Captain / Total hours on type:
639.00
Copilot / Total flying hours:
9926
Copilot / Total hours on type:
105
Aircraft flight hours:
10451
Circumstances:
Trans World Airlines Flight 163 is a regularly scheduled domestic operation between Kansas City, Missouri, and Los Angeles, California, with intermediate stops at Topeka and Wichita, Kansas; Amarillo, Texas; Santa Fe and Albuquerque, New Mexico; and Las Vegas, Nevada. A scheduled crew change is made at Albuquerque. There, on November 15, 1956. Captain Arthur G. deFabry, First Officer James P. Rapattoni, and Hostess Anne J. Zeman boarded Flight 163 as its crew to complete the remaining segments. The flight was routine to Las Vegas where it landed at 1440. During the short ground time at Las Vegas the aircraft was serviced and the crew performed routine duties for continuation of the flight to Los Angeles. There was no apparent need for maintenance on the aircraft and none was performed. An Instrument Flight Rules flight plan was prepared and filed because of instrument weather conditions over the latter portion of the flight segment to Los Angeles. Weather conditions at Las Vegas, however, were clear. At 1449 Captain deFabry, seated in the captain’s position, taxied N 40404 from the Las Vegas terminal to runup position beside runway 7 where the required pretakeoff checks were accomplished. The aircraft and equipment responded normally. The flight was issued an instrument clearance by Air Route Traffic Control. At this time, according to the company load manifest, the gross weight of the aircraft was 41.801 pounds, well under the maximum allowable for takeoff, 43,650 pounds. The load was properly distributed with respect to the center of gravity limitations of the aircraft. With Captain deFabry operating the aircraft, Flight 163 took off at 1456. The takeoff was routine and was followed by a climbing left turn to gain altitude and establish a southwesterly course toward Los Angeles. At 1501, when over the northern perimeter of the city, First Officer Rapattoni radioed the Las Vegas tower stating the flight was returning to the airport, engine out. The Las Vegas tower controllers immediately notified all other traffic to remain clear and alerted emergency equipment. Flight 163 was cleared to land, any runway, and informed that the wind was calm. Captain deFabry elected to use runway 7 and First Officer Rapattoni notified the tower. Emergency equipment was then dispatched into position on the taxiway parallel to that runway. N40404 was soon observed on a wide base leg for runway 7 and as it turned onto the final approach. Position and altitude of the flight seemed normal. As the aircraft drew closer its extended gear could be seen and its left propeller was clearly visible, stopped and feathered. As the aircraft passed over the runway threshold its alignment position, and altitude seemed good; however, to nearly all observers excessive speed was apparent. The aircraft floated a considerable distance down the runway before touching it. It then bounced several times, after which an application of power was heard, obviously :m an attempt to go around. The Martin climbed, veered to the left, and its left wing gradually lowered. It seemed to “struggle” to continue flight and its airspeed decreased visibly. Seconds later the aircraft struck the ground, left wing low, just inside the airport boundary. Weather conditions at the time of the accident were clear, visibility 65 miles, and the wind was calm. A large cloud of dust, raised by the accident, hung over the scene and gradually lifted nearly vertically in evidence of the calm wind.
Probable cause:
The Board determines that the probable cause of this accident was that during an emergency situation the captain failed to reduce speed during the latter portion of a single-engine approach; this excessive speed resulted in an overshoot and an attempted go-around which was beyond the performance capability of the aircraft under existing conditions. The following findings were reported:
- The prior segments of the flight, the pretakeoff cheeks, and the takeoff at Las Vegas were normal,
- Shortly after takeoff the left engine No. 2 cylinder exhaust valve push rod failed causing backfiring, loss of power, and engine roughness; these conditions necessitated taking the engine out of operation by feathering its propeller,
- Emergency single-engine operation was established, the McCarran tower was notified, and the flight returned to the airport to land,
- The base leg and final approach to runway 7 were normal with respect; to alignment, position, and altitude,
- The flight crossed the threshold with excessive airspeed and floated 2.749 feet before touching the runway,
- A series of bounces occurred as unsuccessful attempts were made by Captain deFabry to force the aircraft on the runway,
- Believing the aircraft could successfully go around at the speed and in the configuration which existed the captain attempted unsuccessfully to do so,
- Prior to the accident company pilot training with respect to single-engine performance of the Martin 404 in the balked landing situation was inadequate,
- Examination showed there was no malfunction of the right engine, landing gear and flap hydraulic systems, or the ADI system.
Final Report:

Crash of a Douglas MC-54M on Mt Charleston: 14 killed

Date & Time: Nov 17, 1955
Type of aircraft:
Operator:
Registration:
44-9068
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Burbank - Homey
MSN:
27294
YOM:
1945
Crew on board:
4
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
14
Circumstances:
The four engine aircraft was completing a flight from Burbank to the secret base 51 (aka Homey) located near Groom Lake, Nevada, carrying a crew of four and 10 passengers, atomistics, engineers and scientists who were taking part to the Lockheed U-2 reconnaissance aircraft building program. Due to the fact that the flight was secret, the crew did not have any radio contact with ATC. Enroute, the crew encountered poor weather conditions with thunderstorm activity and low visibility. While flying in clouds at an altitude of 11,300 feet, the aircraft hit the slope of Mt Charleston about 50 feet below the summit, killing all 14 occupants.
Probable cause:
It was determined that the aircraft was off course at the time of the accident, probably because the crew became lost in the clouds.

Crash of a Douglas SC-47A near Hawthorne: 7 killed

Date & Time: Aug 19, 1955
Operator:
Registration:
42-108944
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Reno - Reno
MSN:
13288
YOM:
1944
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The crew left Reno-Stead Airport on a classified mission with six other similar aircraft. While cruising in limited visibility at an altitude of 6,000 feet, the airplane hit the slope of a mountain located in the Gillis Mountain Range, about 12 miles northeast of Hawthorne. The wreckage was found few feet below the summit and all seven crew members were killed.
Probable cause:
It is believed that the accident was the consequence of a controlled flight into terrain.

Crash of a Douglas C-47D near Wells: 6 killed

Date & Time: Dec 10, 1952
Operator:
Registration:
43-49553
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Peterson - Reno
MSN:
15369/26814
YOM:
1944
Location:
Crew on board:
5
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
While overflying a mountainous area located south of Wells, the crew encountered extreme turbulences and severe downdrafts. The aircraft lost height and eventually hit the east slope of Mt East Humbold, about 13 miles southwest of Wells. All six occupants were killed.
Probable cause:
While flying under IFR, the pilot did not maintain sufficient drift correction to stay within the airway, and extreme downdrafts caused the aircraft to descend approximately 1,300 feet below the assigned altitude.

Crash of a Boeing B-17G Flying Fortress in Nevada: 2 killed

Date & Time: Nov 10, 1952
Registration:
N5116N
Flight Phase:
Survivors:
Yes
Site:
MSN:
8416
YOM:
1944
Location:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Crashed in unknown circumstances in the Nevada desert. Two crew members were killed while a third occupant was injured.

Crash of a Boeing B-29F-100-BW Superfortress into Lake Mead

Date & Time: Jul 21, 1948
Type of aircraft:
Operator:
Registration:
45-21847
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
13741
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
This version was an electronic reconnaissance aircraft used in Arctic conditions. It crashed into Lake Mead, during a research flight. The crew of five was able to scramble away before the plane sank. It has been located by sonar in 170 feet of water, largely intact except for 3 missing engines (number two, three and four). The flight was for a secret missile guidance system that allowed navigation by tracking of the Sun. A low pass over calm water with pilot error put it into the lake. The aircraft plummeted from high altitude down to as close to the lake as possible. Unfortunately, Captain Robert M. Madison lost his depth perception and plowed the huge plane into the lake at 230 mph. The impact tore off all but one of the engines and sent the plane skipping along the lake surface. When she eventually stopped, she began to take on water and started to sink. Fortunately, all of the crew was able to escape into life rafts and wait for rescue.
Source: http://www.advanceddivermagazine.com/articles/B29/B29.html

Crash of a DDouglas C-47A-5-DL in Elko: 20 killed

Date & Time: Sep 5, 1946 at 0132 LT
Registration:
NC57850
Survivors:
Yes
Schedule:
New York – Cheyenne – Elko – San Francisco
MSN:
9214
YOM:
1943
Location:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
20
Captain / Total flying hours:
2944
Copilot / Total flying hours:
1339
Aircraft flight hours:
2137
Circumstances:
The aircraft was reported over Elko, Nevada, at 0121 and the pilot stated to the Aircraft Communicator at Elko that he had the field n and that he anticipated no difficulty in landing. The latest weather information was transmitted to the pilot and acknowledged by him: Ceiling measured 200 feet, thin overcast; lower thin scattered clouds at 100 visibility 7 miles; wind ENE at 6 mph; altimeter setting 30.14. No further transmission was received from the flight. Elko radio made several attempts to contact Aircraft 850 without success and, at approximately 0133, notified Airway Traffic control that radio contact was no longer being maintained with the flight. Salt Lake City Air Traffic Control requested Battle Mountain radio to attempt to contact the aircraft in the event the pilot had elected to continue to his alternate. However, although several attempts were made, no contact was established with the flight. United Air Lines' Flight 16, of September 4, 1946, en route to Salt Lake City on Airway Green 3, was called by the United Air Lines station at Salt Lake City and requested to check the vicinity of Elko for any sign of fire or other indications of an aircraft accident. The time of this contact was 0200, at which time Flight 16 was approximately 5 miles east of Elko Range Station. The Caption of Flight 16 returned to Elko and scanned the area in the vicinity of the airport. On approaching the airport the flight crew of the United Air Lines' DC-3 observed an intense fire approximately 2 miles west and almost directly in line with Runway 23 of the Elko Airport. This information was transmitted to the United Air Lines' ground station at Elko, Nevada, and Salt Lake City, Utah. The fire warden at Elko was immediately notified of the location of the fire and was requested to proceed to the scene of the fire. Personnel from the C. A. Communications Station at Elko arrived at the scene of the fire at approximately 0230 and found that the aircraft had crashed near the top of a ridge, the elevation of which was approximately 11' feet above that of the field, and at a point approximately 2 1/2 miles west of the west and of Runway 23 at Elko Airport. At this time the wreckage was found to be burned severely and, with the exception of two passengers, one of whom died shortly afterward, all occupants had been fatally injured in the aircraft.
Probable cause:
On the basis of the above findings, the Board determines that the probable cause of this accident was the pilot's action in continuing a landing approach after having lost visual contact with the airport under conditions of dense ground fog. A contributing factor was the pilot's unfamiliarity with the terrain in the immediate vicinity of the airport.
Final Report: