This is a good article. Click here for more information.

Hughes Airwest Flight 706

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Hughes Airwest Flight 706
260px
A Hughes Airwest DC-9-31 similar to the one in the collision, but with a different livery
Accident summary
Date 6 June 1971
18:11 PDT
Summary Mid-air collision, pilot error
Site San Gabriel Mountains,
Los Angeles County,
California, United States
Total fatalities 50
Total survivors 1
First aircraft
Type McDonnell Douglas DC-9-31
Operator Hughes Airwest
Registration N9345
Flight origin Los Angeles, California
1st stopover Salt Lake City, Utah
2nd stopover Boise, Idaho
3rd stopover Lewiston, Idaho
4th stopover Pasco, Washington
Last stopover Yakima, Washington
Destination Seattle, Washington
Passengers 44
Crew 5
Fatalities 49 (all)
Survivors 0
Second aircraft
Type F-4B Phantom II
Operator U.S. Marine Corps
Registration 151458
Crew 2
Fatalities 1
Survivors 1
Photograph of a similar U.S. Marine Corps F-4B Phantom II.
A U.S. Marine Corps F-4B Phantom II similar to the one involved

Hughes Airwest Flight 706 was a regularly scheduled flight operated by Hughes Airwest, from Los Angeles, California, to Seattle, Washington, with numerous intermediate stops. On Sunday, June 6, 1971, the Douglas DC-9-31 serving the flight collided in mid-air with a U.S. Marine Corps F-4B Phantom II over southern California.

Flight 706 had departed Los Angeles just after 6 pm, en route to Seattle, with stopovers in Salt Lake City, Utah; Boise, Idaho; Lewiston, Idaho; Pasco, Washington and Yakima, Washington. Completing a cross-country flight, the F-4B Phantom was arriving from Naval Air Station Fallon in Nevada to land at Marine Corps Air Station El Toro near Irvine. Its pilot and all 49 passengers and crew aboard the civilian airliner died in the collision over the San Gabriel Mountains, near Duarte. Only the radar intercept officer of the F-4B survived. The crash of RW 706 prompted the US Armed Forces to agree both to reduce the number of military aircraft operating under visual flight rules in civilian air corridors, and to require military aircraft to contact civilian air traffic controllers.

Flight histories

Flight 706 was a scheduled passenger flight from Los Angeles International Airport, California and Seattle–Tacoma International Airport, Washington. The McDonnell Douglas DC-9-31 aircraft had accumulated 5,542 airframe hours since entering service in 1969.[1] The aircraft was operating under the livery and name of Air West, the airline that had been recently purchased by Howard Hughes and rebranded Hughes Airwest.[2]

The aircraft was piloted by Captain Theodore Nicolay, 50, who had logged 15,490 hours of total flying time, with 2,562 hours in DC-9s. His co-pilot was First Officer Price Bruner, 49, who had 17,128 total hours flying time and 272 hours in DC-9s.[1][2] Other crew members included three flight attendants: Joan R. Puylaar, 34; Patricia Shelton, 28; and Helena Koskimies, 30.[2]

Flight 706 departed from Los Angeles at 6:02 p.m. PDT for Salt Lake City, Utah, the first of five intermediate stops en route to Seattle. Control of the flight was transferred to Los Angeles Air Route Traffic Control Center at 6:06 p.m. and passed through 12,000 feet (3,700 m) at 6:09 p.m. and instructed to head 040 (magnetic) until receiving the Daggett VOR, then direct.[1][2] Flight 706's acknowledgement of this instruction was the last radio transmission received from the aircraft.[2]

The U.S. Marine Corps F-4B-18-MC Phantom II, Bureau Number (BuNo) 151458, coded '458', had been in operation since April 15, 1964. At the time of the accident it was assigned to Marine Fighter Attack Squadron 323, Marine Aircraft Group 11, 3rd Marine Air Wing, though it had been operated by various squadrons prior to that. The fighter plane was piloted by 1st Lt. James R. Phillips, 27. The Radar Intercept Officer was 1st Lt. Christopher E. Schiess, 24. The jet and its crew were based at MCAS El Toro.[2]

'458' had been a part of a cross-country flight of two aircraft when its radio failed while landing at Mountain Home Air Force Base in southwest Idaho. The aircraft was ordered to effect repairs at Mountain Home AFB and then to return to MCAS El Toro. Diagnostic tests at Mountain Home revealed that the aircraft had an inoperative radio, inoperative transponder,[3] oxygen system leak, and a degraded radar system. Maintenance personnel were able to fix the radio and confirm the oxygen leak, but the base did not have the necessary personnel to repair either the transponder or the radar.[2]

Lt. Phillips, the pilot, received permission from his superiors to fly the F-4B with an inoperative transponder.[4] As the fighter proceeded to NAS Fallon in Nevada, the oxygen leak worsened until the system was disabled completely, and the pilot was instructed to fly at low altitude. The Phantom II departed NAS Fallon at 5:16 p.m. following a flight plan routing across the Fresno, Bakersfield, and Los Angeles air corridors.[2]

Flight 706 was operating under instrument flight rules (IFR). Under IFR procedures, the pilot guides the aircraft using the cockpit's instrument panel for navigation, in addition to radioed guidance from air traffic controllers and ground radar.[5] BuNo 151458 was operating under visual flight rules (VFR). At the time of the accident, VFR require pilots to "see and avoid[6]" other aircraft, a doctrine that dates back to early aviation. The "see and avoid" rule requires pilots of all aircraft flying in VMC to be maintain vigilance for other aircraft flying in their vicinity, in addition to traffic advisories from ATC.[4]

Collision

File:Hughes air west N9345.gif
Animation of the collision from two perspectives. Each starts five seconds prior and continues an additional five seconds after impact.

Near the Bakersfield Flight Service Station, the crew of '458' decided to deviate east from their flight plan to avoid heavy air traffic in the Los Angeles area. Lt. Phillips was forced to climb to 15,500 feet (4,700 m) from 1,000 feet (300 m) because of deteriorating weather conditions. Meanwhile, shortly after takeoff, Flight 706 received two radar traffic advisories, neither of which indicated the presence of '458'.[2]

Soon after reaching 15,500 feet (4,700 m), the fighter's DME (radio) showed MCAS El Toro was 50 miles (80 km) away.[1]The pilot of '458' then performed an aileron roll, a flight maneuver that rolled the aircraft 360° in order to allow the pilot to observe any air traffic above or below the aircraft.[4] Lt. Schiess, the Radar Intercept Officer, was operating the fighter's radar, which was unable to detect any aircraft due to its deteriorated condition.[7][8] Because of the stowed position of the scope, he had been leaning forward and looking downward at the instrument. Between three and ten seconds prior to the collision, he glanced up and observed the DC-9 in his peripheral vision and shouted a warning to the pilot. The pilot attempted an evasive roll but was unable to clear the oncoming airliner.[2]

At about 6:11 p.m., Flight 706 and '458' collided at about 15,150 feet (4,620 m) altitude, over the San Gabriel Mountains in the vicinity of Duarte.[2][9] The collision tore the F-4's tail off, and the DC-9's cockpit was shorn off as a result. The stricken airliner "cartwheeled" through the air and plunged downwards. Witnesses in nearby Duarte described hearing a loud noise and seeing two flaming objects falling from the sky. A second explosion shook the area as the DC-9 hit the mountain.[10] Lt. Schiess, the Radar Intercept Officer, ejected from the F-4B and parachuted to safety; Lt. Phillips, the pilot, was unable to eject in time, and was killed.[11] The F-4B crashed on Mount Bliss, approximately 1 mile (1.6 km) from the airliner wreckage. Burning debris from the collision and subsequent crashes set off numerous small brush fires in the area.[9] Wreckage was scattered across a mile of nearly inaccessible terrain in the Angeles National Forest.[12]

Investigation

File:Hughes Airwest Flight 706 collision area.png
Collision area. Source: NTSB accident report.[2]

The stricken airliner crashed onto Mount Bliss in the San Gabriel Mountains at an elevation of approximately 3,000 feet (910 m),[13] where the bulk of the wreckage landed in a gorge.[10] Fire department officials sent search and rescue helicopters[14] to the crash site, but efforts were hampered by thick fog.[10][15] Nine bodies were initially found at the crash site,[10] a number of them intact and still strapped into their seats.[13] News reports indicated that these bodies had apparently been thrown clear on impact, and had come to rest alongside the tail section of the aircraft.[12]

Some eyewitnesses reported that the F-4B's left wing struck the center of the airliner's fuselage immediately after performing a barrel roll.[16] Other witnesses claimed that the F-4B ripped a large hole in the fuselage of the DC-9, through which papers and luggage streamed as the crippled airliner fell. Though papers with the words "Air West" and the date of June 6 were collected by Sheriff's deputies, no luggage was recovered.[12]

The National Transportation Safety Board (NTSB) investigated the incident, assisted by the Marine Corps, Federal Aviation Administration (FAA), Hughes Airwest, and the Airline Pilots Association.[17] Early statements released by the NTSB revealed that the F-4B fighter had attempted to swerve away from the DC-9 immediately prior to impact, and that an additional 10 feet of clearance would have averted the entire collision. Additionally, the NTSB confirmed that the fighter had impacted the DC-9 in two places, with its left wing impacting the airliner's forward passenger cabin and the vertical stabilizer "slicing through" the cockpit.[3][18]

The DC-9 carried a primitive flight data recorder that recorded basic information about the aircraft's air speed, acceleration, heading, and altitude on metal foil tapes.[19][20] Additionally, the aircraft was equipped with a simple cockpit voice recorder that recorded all conversations that took place in the cockpit of the aircraft. The flight recorder was recovered by investigators on Thursday, June 10, 1971, and sent to Washington D.C. for analysis.[21] Though the voice recorder was also recovered, the thermal protective measures had failed and the recording tapes were destroyed by fire.[2]

Survivability

The NTSB determined that it had been impossible for any passenger aboard the Hughes Airwest DC-9 to survive the collision, disintegration, and crash of the aircraft. Though a severe ground fire ravaged both crash sites, the NTSB determined that all of the victims had died in the crash itself.[2]

It was determined, however, that both crewmembers aboard the Marine F-4B could have survived the collision. Further investigation by the NTSB revealed a design flaw in the ejector seat and canopy assemblies of the fighter plane whereby the pilot would probably not be able to eject if the radar intercept officer ejected first. Since the specific design of ejector seats installed in the F-4B were not intended to be fired through the aircraft's canopy, a circuit breaker kept the seat from ejecting if the canopy was in place. Once the canopy was manually unlocked, the ejector seat circuit was completed and could be fired. This specific design of ejector seat, however, had a tendency of being unable to complete the circuit in the pilot's ejector seat if the aft ejector seat was fired first. The F-4B aircraft were in the process of being modified with a newly designed canopy when the collision occurred. Aircraft based at MCAS El Toro were slated to begin upgrades in July 1971; at the time of the collision, BuNo 151458 was still operating with the original canopy configuration, and the pilot was consequently unable to eject from the aircraft.[2]

Probable cause and recommendations

The NTSB released their final accident report on August 30, 1972. The report concluded:

<templatestyles src="Template:Blockquote/styles.css" />

The National Transportation Safety Board determines that the probable cause of this accident was the failure of both crews to see and avoid each other, but recognizes that they had only marginal capability to detect, assess, and avoid the collision. Other causal factors include a very high closure rate, commingling of IFR and VFR traffic in an area where the limitation of the ATC system precludes effective separation of such traffic, and failure of the crew of BuNo458 to request radar advisory service, particularly considering the fact that they had an inoperable transponder.

— National Transportation Safety Board, Aircraft Accident Report, Hughes Air West DC-9, N9345, and U.S. Marine Corps F-4B, 151458, Near Duarte, California, June 6, 1971, August 30, 1972, p. 27.[2]

During the course of the accident investigation, the NTSB attempted to recreate the conditions of the accident to determine the visibility of BuNo458 on June 6. They also calculated that their closing rate was about 1000 ft/s similar to the muzzle velocity of a .45 caliber gun.The NTSB, Federal Aviation Administration (FAA), and the Marine Corps flew a series of F-4B fighters along the flight paths described by Lt. Schiess, the radar intercept officer, and various witnesses. While the tests were sufficient to determine the difficulty in locating and identifying the fighter on the radar scope, the many other variables involved in the June 6 incident, including the deteriorated condition of '458', compromised the validity of the study. This inability to ascertain the exact actions and circumstances of the air traffic controllers led the NTSB to recommend that the FAA install both video and audio surveillance in all air traffic control areas.[2]

The NTSB report included a total of five recommendations for the FAA. These recommendations included: installing recorders for radar displays, installing audio conversation recorders at air traffic control facilities; establishing climb and descent corridors under ATC positive control in the vicinity of air terminals; and establishing more definitive procedures for receiving and handling the emergency transponder code 7700. Additionally, the NTSB strongly recommended that the FAA and the Department of Defense cooperate to develop a program, in areas where a large intermix of civil and military traffic exists, to ensure that appropriate graphical depictions of airspace utilization and typical flow patterns are prominently displayed at all airports and operational bases for the benefit of all airspace users. [2]

In addition to these recommendations, the NTSB also recommended that the Department of Defense restrict high-speed, low-altitude aircraft operation in civilian air corridors, consider collision avoidance technologies on military aircraft, and make military pilots aware of the FAA's radar advisory service.[2]

Aftermath

Congressmen Sherman P. Lloyd (R-Utah) and Henry S. Reuss (D-Wis) both decried the actions of the Marine jet fighter,[22] which media at the time indicated had been "stunting" prior to the collision. In actuality, the 360° aileron roll maneuver the fighter pilot executed was to observe any air traffic above or below the aircraft.[4][16][23] Lloyd said that military aircraft should be required to establish contact with air traffic controllers when entering high-traffic air corridors and around airports, while Reuss advocated the complete ban of military aircraft from any high-traffic civilian air corridors.[22] Senator Frank Moss (D-Utah) sponsored a bill in December that would require the installation of anti-collision gear on all aircraft by 1975.[24]

VFR and the "see and avoid" doctrine faced sharp criticism in the press.[25] Oscar M. Laurel, a member of the National Transportation Safety Board (NTSB) team investigating the crash, was widely quoted saying that now "may be a good time to take another look" at VFR flights near metropolitan areas.[19][20][26]

The validity of the "see and avoid" doctrine as a safe means of aircraft navigation was a point of contention between the NTSB and the Federal Aviation Administration (FAA). The NTSB had faulted the doctrine in several earlier collisions, including the 1969 collision of Allegheny Airlines Flight 853 with a privately owned Piper PA-28 and the 1967 collision of Piedmont Airlines Flight 22 with a privately owned Cessna 310. The FAA rebutted these findings and insisted that, regardless of the mode of operation, it is the duty of the aircraft pilot to be aware of any aircraft in his immediate vicinity.[25][27]

In March 1971, the NTSB released a report summarizing the findings of a study of midair collisions. The report indicated that 204 of 396 fatalities in U.S. jetliner crashes since 1967 had occurred in mid-air collisions. Additionally, near-miss situations involving jetliners occurred on average at least once per day, with the Los Angeles and New York areas noted as being especially high-risk. Finally, the report noted that the current trend in air casualties indicated that a further 528 people would die in mid-air collisions during the following ten years. These figures did not include the casualties from Flight 706.[25][28]

A FAA study in 1968 had found that a quarter of the 2,230 near-miss aircraft encounters reported that year had involved a military aircraft.[29] Following the in-flight collision of Flight 706, the FAA and the US Military agreed to cut down on VFR flights and operate instead under IFR. This transition would require military aircraft to file flight plans and obey civilian air traffic controllers.[29][30]

Shortly after the collision, on June 21, 1971, the Airline Pilots Association and Professional Air Traffic Controllers Organization issued a joint statement asking the FAA for a series of safety regulations that included a speed limit of 250 knots (290 mph) for aircraft operating under VFR. Other demands included the installation of transponders in all aircraft to amplify aircraft's presence on radar screens,[3] and the re-evaluation of VFR due to the increased complexity, congestion, and speed of modern air travel.[31]

The New York Times reported that the incidence of deaths in commercial aviation accidents had risen sharply in 1971, up from 146 deaths in 1970 and 158 deaths in 1969. Additionally, these deaths had occurred at a time when airlines were cutting back flights due to the economic recession, and airlines had flown about 6% fewer hours in 1971 than 1970. The eight fatal accidents of 1971 included three mid-air collisions and four landing approach crashes; one of these collisions, All Nippon Airways Flight 58, which also involved a military aircraft, became the deadliest air disaster worldwide at the time it took place with 162 deaths. Additionally, 1971 saw the crash of Alaska Airlines Flight 1866, at the time the worst single plane crash in US civil aviation history.[32]

Later that year, Hughes Airwest changed its livery to its signature all-yellow.[33][34][35][36][37]

Litigation

A week after the crash, the families of various passengers aboard Flight 706 began filing lawsuits and court papers against Hughes Airwest and, later, the government of the United States. The first filing was by the family of Keith A. Gabel, which filed a motion to perpetuate testimony in the Central District of California on June 16, 1971.[38] This motion requests that the court issue a court order for a person's deposition to be taken, and can be done prior to a lawsuit being filed under the Federal Rules of Civil Procedure.[39]

Lawsuits against the United States government were delayed six months by the Federal Tort Claims Act. In January 1972, the Gabel family filed a lawsuit against the United States that contained class-action allegations and sought a "declaratory judgment on the issue of liability." The Judicial Panel on Multidistrict Litigation decided to move all related court actions to the Central District of California. Eleven actions were transferred in July 1972.[38] The US District Court ordered the transfer of all 72 actions filed in other district courts to be transferred to the jurisdiction of the Central District on March 19, 1973.[40]

On August 30, 1972, all the cases were consolidated into a single case to determine liability. The cases against the United States, Hughes Airwest, and Hughes Air Corporation were consolidated into a single class-action lawsuit in October 1972. On April 5, 1973, Hughes Airwest and the US Government agreed not to contest the issue of liability. Most claimants settled by December 1973 for payments of various negotiated amounts.[38]

Dramatization

The story of the accident was featured on the thirteenth season of the Canadian TV series Mayday (known as Air Emergency in the US, Mayday in Ireland and Air Crash Investigation in the UK and the rest of world) in an episode entitled "Speed Trap".[41] It was also the feature of "Air Disasters" episode on The Smithsonian Channel.

See also

Mid-air collisions attributed to the "see and avoid[42]" doctrine

References

  1. ↑ 1.0 1.1 1.2 1.3 Accident description at the Aviation Safety Network. Retrieved on 2009-11-30.
  2. ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ http://www.law.cornell.edu/cfr/text/14/91.113
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 10.2 10.3 Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  16. ↑ 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ 25.0 25.1 25.2 25.3 25.4 25.5 Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ 38.0 38.1 38.2 Vincent v. Hughes Air West, Inc., 557 F2d 759, 771 (19th Cir. 1977).
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found. Provided by the Cornell University Law School website
  40. ↑ In Re Multidistrict Civil Actions Involving The Aircrash Near Duarte. US District Court, Central District, California. March 19, 1973. Accessed: 2011-01-19.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ http://www.law.cornell.edu/cfr/text/14/91.113

External links

Lua error in package.lua at line 80: module 'strict' not found.

Retrieved from "https://infogalactic.com/w/index.php?title=Hughes_Airwest_Flight_706&oldid=3284725"