TWA Flight 800

For the documentary, see TWA Flight 800 (film). For the 1964 crash in Rome, see TWA Flight 800 (1964).
"Flight 800" redirects here. For other uses, see Flight 800 (disambiguation).

Trans World Airlines Flight 800
The reconstructed wreckage of TWA 800, stored by the NTSB at Calverton Executive Airpark
Accident
DateJuly 17, 1996 (1996-07-17)
SummaryIn-flight breakup due to explosion in center wing fuel tank
SiteAtlantic Ocean, near East Moriches, New York, United States
40°39′N 72°38′W / 40.650°N 72.633°W / 40.650; -72.633
Aircraft
Aircraft typeBoeing 747-131
OperatorTrans World Airlines
IATA flight No.TW800
ICAO flight No.TWA800
Call signTWA 800 HEAVY LIFEGUARD[1]
RegistrationN93119
Flight originJohn F. Kennedy Int'l Airport,
New York City, United States
StopoverParis-Charles de Gaulle Airport,
Paris, France
DestinationLeonardo da Vinci Airport,
Rome, Italy
Occupants230
Passengers212
Crew18
Fatalities230
Survivors0

Trans World Airlines Flight 800 (TW800/TWA800) was a scheduled international passenger flight from John F. Kennedy International Airport (JFK) in New York City to Fiumicino Airport (FCO) in Rome with a stopover at Charles de Gaulle Airport (CDG) in Paris. On July 17, 1996, at approximately 8:31 p.m. EDT, twelve minutes after takeoff, the Boeing 747-100 serving the flight exploded and crashed into the Atlantic Ocean near East Moriches, New York.[2]: 1 

All 230 people on board died in the crash; it is the third-deadliest aviation accident in U.S. history. Accident investigators from the National Transportation Safety Board (NTSB) traveled to the scene, arriving the following morning[2]: 313  amid speculation that a terrorist attack was the cause of the crash.[3][4][5] The Federal Bureau of Investigation (FBI) and New York Police Department Joint Terrorism Task Force (JTTF) initiated a parallel criminal investigation.[6] Sixteen months later, the JTTF announced that no evidence of a criminal act had been found and closed its active investigation.[7]

The four-year NTSB investigation concluded with the approval of the Aircraft Accident Report on August 23, 2000, ending the most extensive, complex, and costly air disaster investigation in U.S. history up to that time.[8][9] The report's conclusion was that the probable cause of the accident was the explosion of flammable fuel vapors in the center fuel tank. Although it could not be determined with certainty, the likely ignition source was a short circuit.[2]: xvi  Problems with the aircraft's wiring were found, including evidence of arcing in the fuel quantity indication system (FQIS) wiring that enters the tank. The FQIS on Flight 800 is known to have been malfunctioning; the captain remarked about "crazy" readings from the system about two minutes and 30 seconds before the aircraft exploded. As a result of the investigation, new requirements were developed for aircraft to prevent future fuel-tank explosions.[10]

Accident

All times in this article are Eastern Daylight Time (EDT) (UTC−4).
N93119 in 1995
N93119, the aircraft involved in the accident, at Paris-CDG in May 1995.
Upper deck windows of N93119
The close-up view of N93119's front fuselage, in 1972, showing the seven plugged windows on the upper deck. These plugs were blown out following the explosion of Flight 800.

The aircraft involved, manufactured in July 1971, was a Boeing 747-131 registered as N93119. The aircraft was purchased new by Trans World Airlines in 1971. It had completed 16,869 flights in 93,303 hours of operation and was powered by four Pratt & Whitney JT9D-7AH turbofan engines.[2]: 6  On the day of the accident, the airplane departed from Ellinikon International Airport in Athens, Greece as TWA Flight 881 and arrived at John F. Kennedy International Airport at about 4:38 p.m. The aircraft was then refueled and the crew was changed. The crew was led by 58-year-old Captain Ralph G. Kevorkian, who had flown for TWA for 31 years and the U.S. Air Force for nine years and had logged 18,700 flight hours, including 5,400 on the Boeing 747.

Captain/check airman Steven E. Snyder, 57, had flown for TWA for 32 years and had logged 17,200 flight hours, including 4,700 on the Boeing 747. Flight engineer/check airman Richard G. Campbell Jr., 63, had flown for TWA for 30 years and the U.S. Air Force for 12 years and had logged 18,500 flight hours, including 3,800 on the Boeing 747. Also with the crew was 25-year-old flight engineer trainee Oliver Krick, who previously served as a business pilot for four years and had 2,500 flight hours, including 30 on the Boeing 747. Krick had flown for TWA for 26 days and was starting the sixth leg of his initial operating experience training.[2]: 4–6  Flight 800 was actually a training flight for Kevorkian, and he was seated in the captain's (left) seat. Captain Snyder was seated in the first officer's (right) seat monitoring Kevorkian's progress. Flight Engineer Campbell was seated in the cockpit jump seat. Flight engineer trainee Krick was seated in the flight engineer's seat being monitored by Campbell.[2]: 4–6 [11][12] The NTSB Final Report gives Oliver Krick's age as being 24.[2]: 5  The TWA press release gives 25. (TWA was correct, as Krick turned 25 on July 14, three days before the crash.)[11]

The ground-maintenance crew locked out the thrust reverser for engine No. 3 (treated as a minimum equipment list item) because of technical problems with the thrust reverser sensors during the landing of TWA 881 at JFK, before Flight 800's departure. Additionally, severed cables for the engine’s thrust reverser were replaced.[13] During refueling of the aircraft, the volumetric shutoff (VSO) control was believed to have been triggered before the tanks were full. To continue the pressure fueling, a TWA mechanic overrode the automatic VSO by pulling the volumetric fuse and an overflow circuit breaker. Maintenance records indicate that the aircraft had numerous VSO-related maintenance writeups in the weeks before the accident.[2]: 31 

TWA 800 was scheduled to depart JFK for Charles de Gaulle Airport around 7:00 p.m., but the flight’s pushback was delayed until 8:02 p.m. by a disabled piece of ground equipment and a passenger/baggage mismatch.[2]: 1  After the owner of the baggage in question was confirmed to be on board, the flight crew prepared for departure, and the aircraft pushed back from Gate 27 at the TWA Flight Center. The flight crew started the engines at 8:04 p.m. However, because of the previous maintenance undertaken on engine No. 3, the flight crew only started engines No. 1, No. 2, and No. 4. Engine No. 3 was started 10 minutes later during taxi at 8:14 p.m. The initial departure was uneventful, with the 747 taking off from Runway 22R five minutes later at 8:19 p.m.[14]

Flight path of TWA 800: The colored rectangles are areas from which wreckage was recovered.[2]: fig. 21, p. 64 

TWA 800 then received a series of heading changes and generally increasing altitude assignments as it climbed to its intended cruising altitude.[2]: 2  Weather in the area was light winds with scattered clouds,[2]: 256  with dusk lighting conditions.[2]: 4  The last radio transmission from the airplane occurred at 8:30 p.m., when the flight crew received and then acknowledged instructions from Boston Center to climb to 15,000 feet (4,600 m).[15]: 4 [16][17] The last recorded radar transponder return from the airplane was recorded by the Federal Aviation Administration (FAA) radar site at Trevose, Pennsylvania, at 8:31:12 p.m.[2]: 3 

Burning wreckage of Flight 800 on the surface of the Atlantic Ocean

Thirty-eight seconds later, David McClaine, the captain of Eastwind Airlines Flight 507, operated by a Boeing 737-221 registered N221US (which had suffered a near-crash of its own a month prior)[18] reported to Boston ARTCC that he "just saw an explosion out here", adding, "we just saw an explosion up ahead of us here ... about 16,000 feet [4,900 m] or something like that, it just went down… into the water."[19] Subsequently, many air traffic control facilities in the New York and Long Island areas received reports of an explosion from other pilots operating in the area.[19] Many witnesses in the vicinity of the crash stated that they saw or heard explosions, accompanied by a large fireball(s) over the ocean, and observed debris, some of which was burning while falling into the water.[2]: 3  Various civilian, military, and police vessels reached the crash site within minutes of the initial water impact. They searched for survivors but found none,[2]: 86  making TWA 800 the second-deadliest aircraft accident in United States history at that time, only exceeded by American Airlines Flight 191.[20]

Passengers and crew

Love's Embrace, a statue of Pam Lychner and her daughters, Shannon and Katie, in Spring Valley Village, Texas. All three were killed on board TWA Flight 800.

On board TWA 800 were 230 people, including 18 crew and 20 off-duty employees,[21] most of whom were crew meant to cover the Paris-Rome leg of the flight. Seventeen of the 18 crew members[21] and 152 of the passengers were Americans; the remaining crew member was Italian, while the remaining passengers were of various other nationalities. Notable passengers included:[21]

In addition, 16 students and five adult chaperones from the French Club of the Montoursville Area High School in Pennsylvania were on board.[26][27]

Initial investigation

The NTSB was notified at approximately 8:50 p.m. on the day of the accident. A full "go team" was assembled in Washington, D.C., and arrived on the scene early the next morning.[2]: 313  Meanwhile, initial witness descriptions led many to believe that the cause of the crash was a bomb or surface-to-air missile attack.[28][29][30] As the NTSB does not investigate criminal activity, the United States Attorney General is empowered to declare an investigation to be potentially linked to a criminal act and to require the NTSB to relinquish control of the investigation to the FBI.[31] In the case of TWA 800, the FBI initiated a parallel criminal investigation alongside the NTSB's accident investigation.[32]

Search-and-recovery operations

Search-and-recovery operations were conducted by federal, state, and local agencies, as well as by government contractors.[2]: 363–365  Personnel in an HH-60 Pave Hawk helicopter of the New York Air National Guard witnessed the explosion from about eight miles (13 km) away and arrived at the scene of the explosion while debris was still falling into the water, forcing the crew to retreat. They reported their sighting to the tower at Suffolk County Airport. Remotely operated vehicles (ROVs), side-scan sonar and laser line-scanning equipment were employed to search for and investigate underwater debris fields. Victims and wreckage were recovered by scuba divers and ROVs. Later, scallop trawlers were used to recover wreckage embedded in the sea floor.[2]: 63  In one of the largest diver-assisted salvage operations ever conducted, often working in very difficult and dangerous conditions, more than 95% of the airplane wreckage was eventually recovered.[32][33]: 1  The search-and-recovery effort identified three main areas of wreckage underwater, which were classified by color.[2]: 65  The yellow, red, and green zones contained wreckage from the front, center, and rear sections of the airplane, respectively.[2]: 65–74  The green zone with the aft portion of the aircraft was located the farthest along the flight path.[2]: 71–74 

Wreckage recovered with tangled and damaged wires attached[2]: fig.24, p.80 

Pieces of wreckage were transported by boat to shore and then by truck to leased hangar space at the former Grumman Aircraft facility in Calverton, New York for storage, examination, and reconstruction.[2]: 63  The facility became the command center and headquarters for the investigation.[2]: 363–365  NTSB and FBI personnel were present to observe all transfers to preserve the evidentiary value of the wreckage.[2]: 367  The cockpit voice recorder and flight data recorder were recovered by U.S. Navy divers one week after the accident, and the machines were immediately shipped to the NTSB laboratory in Washington, D.C. for analysis.[2]: 58  The victims' remains were transported to the Suffolk County Medical Examiner's office in Hauppauge, New York.[34]: 2 

Tensions in the investigation

Relatives of TWA 800 passengers and crew, as well as the media, gathered at the Ramada Plaza JFK Hotel.[35] Many waited until the remains of their family members had been recovered, identified and released.[36]: 1 [37]: 3–4  This hotel became known as the "Heartbreak Hotel" for its role in hosting families of victims of several airliner crashes.[38][39][40]

Many grieving relatives became angry because of TWA's delayed confirmation of the passenger list,[35] conflicting information from agencies and officials[41]: 1  and mistrust of the recovery operation's priorities.[42]: 2  Although NTSB vice chairman Robert Francis stated that all bodies were retrieved as soon as they were spotted and that wreckage was recovered only if divers believed that victims were hidden underneath,[42]: 2  many families were suspicious that investigators were not truthful or were withholding information.[42]: 2 [43]: 7 [41]: 1–2 

Anger and political pressure were also directed at Suffolk County medical examiner Charles V. Wetli as recovered bodies backlogged at the morgue.[33]: 3 [43]: 5 [41]: 1–2  Under constant pressure to identify victims with minimal delay,[34]: 3  pathologists worked long hours. While some victims' bodies were generally intact, most others were burned, fragmented, skeletonized, or decaying, necessitating identification using DNA testing and dental records.[43]: 5  As the primary objective was to identify all remains rather than to perform detailed forensic autopsies, the thoroughness of the examinations was highly variable.[34]: 3  Ultimately, the remains of all 230 victims were recovered and identified, and the final victim identification occurred more than 10 months after the crash.[34]: 2 

With lines of authority unclear, differences in agendas and culture between the FBI and NTSB resulted in discord.[43]: 1  The FBI, assuming that a criminal act had occurred,[43]: 3  saw the NTSB as indecisive. Expressing frustration at the NTSB's unwillingness to speculate on a cause, one FBI agent described the NTSB as "No opinions. No nothing."[43]: 4  Meanwhile, the NTSB was required to refute or minimize speculation about conclusions and evidence, frequently supplied to reporters by law-enforcement officials and politicians.[33]: 3 [43]: 4  The International Association of Machinists and Aerospace Workers, an invited party to the NTSB investigation, criticized the undocumented removal by FBI agents of wreckage from the hangar where it was stored.[44]

Witness interviews

An FBI witness statement summary (with personal information redacted)[45]: 41 

Although considerable discrepancies existed among the many witness accounts, most had seen a "streak of light," described by 38 of 258 witnesses as ascending,[2]: 232  moving to a point where a large fireball appeared. Several witnesses reported that the fireball divided into two parts as it descended toward the water.[2]: 3  Intense public interest arose regarding the witness reports, as did much speculation that the reported streak of light was a missile that had struck TWA 800, causing the airplane to explode.[2]: 262  These witness accounts were a major reason for the initiation and duration of the FBI's criminal investigation.[46]: 5 

Approximately 80 FBI agents conducted interviews with potential witnesses daily.[46]: 7  No verbatim records of the witness interviews were produced; instead, the agents who conducted the interviews wrote summaries that they then submitted.[46]: 5  Witnesses were not asked to review or correct the summaries.[46]: 5  Included in some of the witness summaries were drawings or diagrams of what the witnesses had observed.[45]: 165 [47]: 184 

Within days of the crash, the NTSB announced its intent to form its own witness group and to interview witnesses to the crash.[46]: 6  After the FBI raised concerns about nongovernmental parties in the NTSB's investigation having access to this information and possible prosecutorial difficulties resulting from multiple interviews of the same witnesses,[46]: 6  the NTSB deferred and did not interview witnesses. A safety board investigator later reviewed FBI interview notes and briefed other board investigators on their contents. In November 1996, the FBI agreed to allow the NTSB access to summaries of witness accounts in which personally identifying information had been redacted and to conduct a limited number of witness interviews. In April 1998, the FBI provided the NTSB with the identities of the witnesses, but because of the time that had elapsed, a decision was made to rely on the original FBI documents rather than on reinterviewed witnesses.[2]: 229 

Further investigation and analysis

Examination of the cockpit voice recorder (CVR) and flight data recorder data showed a normal takeoff and climb,[15]: 4  with the aircraft in normal flight[48]: 2  before both abruptly stopped at 8:31:12 p.m.[2]: 3  At 8:29:15 p.m., Captain Kevorkian was heard to say, "Look at that crazy fuel flow indicator there on number four... see that?"[2]: 2  A loud noise recorded on the last few tenths of a second of the CVR was similar to the last noises recorded from other airplanes that had experienced in-flight breakups.[2]: 256  This, together with the distribution of wreckage and witness reports, indicated a sudden, catastrophic in-flight breakup of TWA 800.[2]: 256 

Possible causes of the in-flight breakup

Investigators considered several possible causes for the structural breakup: structural failure and decompression, detonation of a high-energy explosive device such as a missile warhead exploding either upon impact with the airplane or just before impact, a bomb exploding inside the airplane or a fuel-air explosion in the center-wing fuel tank.[2]: 256–257 

Structural failure and decompression

Close examination of the wreckage revealed no evidence of structural faults such as fatigue, corrosion, or mechanical damage that could have caused the in-flight breakup.[2]: 257  The breakup could have been initiated by an in-flight separation of the forward cargo door as had occurred in the Turkish Airlines Flight 981 or United Airlines Flight 811 accidents, but all evidence indicated that the door was closed and locked at impact.[2]: 257  The NTSB concluded that "the in-flight breakup of TWA flight 800 was not initiated by a pre-existing condition resulting in a structural failure and decompression."[2]: 257 

Missile or bomb detonation

A review of recorded data from long-range and airport surveillance radars revealed multiple contacts of airplanes or objects in TWA 800's vicinity at the time of the accident.[2]: 87–89  None of these contacts intersected TWA 800's position at any time.[2]: 89  Attention was drawn to data from the Islip, New York ARTCC facility that showed three tracks in the vicinity of TWA 800 that did not appear in any of the other radar data.[2]: 93  None of these sequences intersected TWA 800's position at any time.[2]: 93  None of the reviewed data showed radar returns consistent with a missile or other projectile traveling toward TWA 800.[2]: 89 

The NTSB addressed allegations that the Islip radar data showed groups of military surface targets converging suspiciously in an area around the accident and that an unidentified 30-knot radar track, 3 nautical miles (5.6 km; 3.5 mi) from the crash site, was involved in foul play, as evidenced by its failure to divert from its course and assist with the search-and-rescue operations.[2]: 93  Military records examined by the NTSB showed no military surface vessels within 15 nautical miles (28 km; 17 mi) of TWA 800 at the time of the accident.[2]: 93  In addition, the records indicated that the closest area scheduled for military use, warning area W-387A/B, was 160 nautical miles (296 km; 184 mi) south.[2]: 93 

The NTSB reviewed the 30-knot target track to determine why it had not diverted from its course to proceed to the area where the TWA 800 wreckage had fallen. TWA 800 was behind the target, and with the target's occupants likely looking forward, they would not have been in a position to observe the aircraft's breakup, subsequent explosions, or fireballs.[2]: 94  The occupants of the target track were unlikely to have been able to hear the explosions over the sound of their craft's engines and the noise of the hull traveling through water, especially if the occupants were in an enclosed bridge or cabin.[2]: 94  Further, review of the Islip radar data for similar summer days and nights in 1999 indicated that the 30-knot track was consistent with normal commercial fishing, recreational, and cargo-vessel traffic.[2]: 94 

  • Recorded radar data
  • Radar data showing vehicle and/or object tracks within 10 nautical miles (19 km; 12 mi) of TWA flight 800 just before the accident: fig. 25, p. 90 
    Radar data showing vehicle and/or object tracks within 10 nautical miles (19 km; 12 mi) of TWA flight 800 just before the accident.[2]: fig. 25, p. 90 
  • Three sequences of primary returns near TWA 800 that were only recorded by the Islip radar: fig. 26, p. 91 
    Three sequences of primary returns near TWA 800 that were only recorded by the Islip radar.[2]: fig. 26, p. 91 
  • Primary radar returns that appeared near the TWA 800 after 8:31:12 pm: The 30-knot track is at the bottom center of the image.: fig. 27, p. 92 
    Primary radar returns that appeared near the TWA 800 after 8:31:12 p.m.: The 30-knot track is at the bottom center of the image.[2]: fig. 27, p. 92 

Trace amounts of explosive residue were detected on three samples of material from three separate locations of the recovered airplane wreckage (described by the FBI as a piece of canvas-like material and two pieces of a floor panel).[2]: 118  These samples were submitted to the FBI's laboratory in Washington, D.C., which determined that one sample contained traces of cyclotrimethylenetrinitramine (RDX), another nitroglycerin and the third a combination of RDX and pentaerythritol tetranitrate (PETN);[2]: 118  these findings received much media attention.[49][50] In addition, the backs of several damaged passenger seats were observed bearing an unknown red/brown-shaded substance.[2]: 118  According to the seat manufacturer, the locations and appearance of the substance were consistent with adhesive used in the construction of the seats, and additional laboratory testing by NASA identified the substance as consistent with adhesives.[2]: 118 

Further examination of the airplane structure, seats, and other interior components found no damage typically associated with a high-energy explosion of a bomb or missile warhead ("severe pitting, cratering, petalling or hot-gas washing").[2]: 258  This included the pieces on which trace amounts of explosives were found.[2]: 258  Of the 5% of the fuselage that was not recovered, none of the missing areas was large enough to have covered all of the damage that would have been caused by the detonation of a bomb or missile.[2]: 258  None of the victims' remains showed any evidence of injuries that could have been caused by high-energy explosives.[2]: 258 

The NTSB considered the possibility that the explosive residue was the result of contamination from the aircraft's use in transporting troops during the Gulf War in 1991 or its use in a dog-training explosive-detection exercise about one month before the accident.[2]: 258–259  Testing conducted by the FAA's Technical Center indicated that residues of the type of explosives found on the wreckage would dissipate completely after two days of immersion in seawater (nearly all recovered wreckage was immersed longer than two days).[2]: 259  The NTSB concluded that it was "quite possible" that the explosive residue detected was transferred from military ships, ground vehicles, or the clothing and boots of military personnel onto the wreckage during or after the recovery operation, and that the residue was not present when the aircraft crashed into the water.[2]: 259 

Although it was unable to determine the exact source of the trace amounts of explosive residue found in the wreckage, the lack of any other corroborating evidence associated with a high-energy explosion led the NTSB to conclude that "the in-flight breakup of TWA flight 800 was not initiated by a bomb or missile strike."[2]: 259 

Fuel-air explosion in the center wing fuel tank

The wing center section of a Boeing 747-100, including the CWT[2]: fig. 4a, p. 13 
Scale-model test of a CWT fuel/air vapor explosion

To evaluate the sequence of structural breakup of the airplane, the NTSB formed the Sequencing Group,[2]: 100  which examined individual pieces of the recovered structure, two-dimensional reconstructions or layouts of sections of the airplane and various-sized three-dimensional reconstructions of portions of the aircraft.[2]: 100  In addition, the locations of pieces of wreckage at the time of recovery and differences in fire effects on pieces that are normally adjacent to each other were evaluated.[2]: 100  The Sequencing Group concluded that the first event in the breakup sequence was a fracture in the wing center section of the aircraft caused by an "overpressure event" in the center-wing fuel tank (CWT).[51]: 29  An overpressure event was defined as a rapid increase in pressure resulting in failure of the structure of the CWT.[2]: 85 

Because no evidence was found that an explosive device detonated in this (or any other) area of the airplane, the overpressure event could only have been caused by a fuel-air explosion in the CWT.[2]: 261  There were 50 US gal (190 L) of fuel in the CWT of TWA 800;[52] tests recreating the flight conditions showed the combination of liquid fuel and fuel-air vapor to be flammable.[2]: 261  A major reason for the flammability of the fuel-air vapor in the CWT of the 747 was the large amount of heat generated and transferred to the CWT by air-conditioning packs located directly below the tank;[2]: 298  with the CWT temperature raised to a sufficient level, a single ignition source could cause an explosion.[2]: 298 

Computer modeling[2]: 122–123  and scale-model testing[2]: 123  were used to predict and demonstrate how an explosion would progress in a 747 CWT. During this time, quenching was identified as an issue, a phenomenon in which the explosion would extinguish itself as it passed through the complex structure of the CWT.[2]: 123  Because the research data regarding quenching were limited, a complete understanding of quenching behavior was not possible, and the issue of quenching remained unresolved.[2]: 137 

To better determine whether a fuel-air vapor explosion in the CWT would generate sufficient pressure to break apart the fuel tank and lead to the destruction of the airplane, tests were conducted in July and August 1997 using a retired Air France 747 at Bruntingthorpe Airfield, England. These tests simulated a fuel-air explosion in the CWT by igniting a propane-air mixture, which failed the tank structure from overpressure.[2]: 261  While the NTSB acknowledged that the test conditions at Bruntingthorpe were not fully comparable to the conditions that existed on TWA 800,[2]: 261  previous fuel explosions in the CWTs of commercial airliners such as those of Avianca Flight 203 and Philippine Airlines Flight 143 confirmed that a CWT explosion could break apart the fuel tank and lead to the destruction of an airplane.[2]: 261 

Ultimately, based on "the accident airplane's breakup sequence; wreckage damage characteristics; scientific tests and research on fuels, fuel tank explosions, and the conditions in the CWT at the time of the accident; and analysis of witness information,"[2]: 271  the NTSB concluded that "the TWA flight 800 in-flight breakup was initiated by a fuel/air explosion in the CWT."[2]: 63 

In-flight breakup sequence and crippled flight

  • Debris fields
  • Map showing the locations of the red, yellow, and green zones: fig. 22a, p. 66
    Map showing the locations of the red, yellow, and green zones[2]: fig. 22a, p. 66 
  • Wreckage found in each zone corresponded to specific areas of the aircraft: fig. 22b, p. 67
    Wreckage found in each zone corresponded to specific areas of the aircraft[2]: fig. 22b, p. 67 
  • The pathways the wreckage took as it fell to the ocean: fig. 22c, p. 68
    The pathways the wreckage took as it fell to the ocean[2]: fig. 22c, p. 68 
Slide from NTSB presentation of TWA 800 breakup sequence, illustrating structure and size of CWT

Recovery locations of the wreckage from the ocean (the red, yellow, and green zones) clearly indicated: (1) the red area pieces (from the forward portion of the wing center section and a ring of fuselage directly in front) were the earliest pieces to separate from the airplane; (2) the forward fuselage section departed simultaneously with or shortly after the red area pieces, landing relatively intact in the yellow zone; (3) the green area pieces (wings and the aft portion of the fuselage) remained intact for a period after the separation of the forward fuselage and impacted the water in the green zone.[51]: 3–4 

Frame from the CIA's animated depiction of how TWA Flight 800 broke apart: When the bottom of the aircraft blew out from the exploding fuel tank, cracks spread around the fuselage and severed the entire front section of the plane.

Fire damage and soot deposits on the recovered wreckage indicated that some areas of fire existed on the airplane as it continued in crippled flight after the loss of the forward fuselage.[2]: 109  After about 34 seconds (based on information from witness documents), the outer portions of both the right and left wings failed.[2]: 109, 263  Shortly after, the left wing separated from what remained of the main fuselage, which resulted in further development of the fuel-fed fireballs as the pieces of wreckage fell to the ocean.[2]: 263 

Only the FAA radar facility in North Truro, Massachusetts, using specialized processing software from the United States Air Force 84th Radar Evaluation Squadron, was capable of estimating the altitude of TWA 800 after it lost power due to the CWT explosion.[2]: 87  Because of accuracy limitations, these radar data could not be used to determine whether the aircraft climbed after the nose separated.[2]: 87  Instead, the NTSB conducted a series of computer simulations to examine the flightpath of the main portion of the fuselage.[2]: 95–96  Hundreds of simulations were run using various combinations of possible times the nose of TWA 800 separated (the exact time was unknown), different models of the behavior of the crippled aircraft (the aerodynamic properties of the aircraft without its nose could only be estimated), and longitudinal radar data (the recorded radar tracks of the east/west position of TWA 800 from various sites differed).[2]: 96–97  These simulations indicated that after the loss of the forward fuselage the remainder of the aircraft continued in crippled flight, then pitched up while rolling to the left (north),[2]: 263  climbing to a maximum altitude between 15,537 and 16,678 feet (4,736 and 5,083 m)[2]: 97  from its last recorded altitude, 13,760 feet (4,190 m).[2]: 256 

Analysis of reported witness observations

Most witness observations of a streak of light were determined by the NTSB to be consistent with the calculated flightpath of TWA 800 after the CWT explosion (screenshot from an NTSB animation).

At the start of the FBI's investigation, because of the possibility that international terrorists might have been involved, assistance was requested from the Central Intelligence Agency (CIA).[53]: 2  CIA analysts, relying on sound-propagation analysis, concluded that the witnesses could not be describing a missile approaching an intact aircraft, but were seeing a trail of burning fuel coming from the aircraft after the initial explosion.[53]: 5–6  This conclusion was reached after calculating how long the sound of the initial explosion took to reach the witnesses, and using that to correlate the witness observations with the accident sequence.[53]: 5  In all cases, the witnesses could not be describing a missile approaching an intact aircraft, as the plane had already exploded before their observations began.[53]: 6 

As the investigation progressed, the NTSB decided to form a witness group to more fully address the accounts of witnesses.[46]: 7  From November 1996 through April 1997, this group reviewed summaries of witness accounts on loan from the FBI (with personal information redacted) and conducted interviews with crewmembers from a New York Air National Guard HH-60 helicopter and C-130 airplane, as well as a U.S. Navy P-3 airplane that was flying in the vicinity of TWA 800 at the time of the accident.[46]: 7–8 

In February 1998, the FBI, having closed its active investigation, agreed to fully release the witness summaries to the NTSB.[46]: 10  With access to these documents no longer controlled by the FBI, the NTSB formed a second witness group to review the documents.[46]: 10  Because of the time that had elapsed (about 21 months) before the NTSB received information about the identity of the witnesses, the witness group chose not to reinterview the witnesses, but instead to rely on the original summaries of witness statements written by FBI agents as the best available evidence of the observations initially reported by the witnesses.[2]: 230  Despite the two and a half years that had elapsed since the accident, the witness group did interview the captain of Eastwind Airlines Flight 507, who was the first to report the explosion of TWA 800, because of his vantage point and experience as an airline pilot.[46]: 12 [54]

A frame from the NTSB's animation depicting how the noseless plane climbed erratically before descending into the ocean

The NTSB's review of the released witness documents determined that they contained 736 witness accounts, of which 258 were characterized as "streak of light" witnesses ("an object moving in the sky... variously described [as] a point of light, fireworks, a flare, a shooting star, or something similar.")[2]: 230  The NTSB witness group concluded that the streak of light reported by witnesses might have been the actual airplane during some stage of its flight before the fireball developed, noting that most of the 258 streak-of-light accounts were generally consistent with the calculated flightpath of the accident airplane after the CWT explosion.[2]: 262 

Thirty-eight witnesses described a streak of light that ascended vertically, or nearly so, and these accounts "seem[ed] to be inconsistent with the accident airplane's flightpath."[2]: 265  In addition, 18 witnesses reported seeing a streak of light that originated at the surface, or the horizon, which did not "appear to be consistent with the airplane's calculated flightpath and other known aspects of the accident sequence."[2]: 265  Regarding these differing accounts, the NTSB noted that based on their experience in previous investigations "witness reports are often inconsistent with the known facts or with other witnesses' reports of the same events."[2]: 237  The interviews conducted by the FBI focused on the possibility of a missile attack; suggested interview questions given to FBI agents such as "Where was the sun in relation to the aircraft and the missile launch point?" and "How long did the missile fly?" could have biased interviewees' responses in some cases.[2]: 266  The NTSB concluded that given the large number of witnesses in this case, they "did not expect all of the documented witness observations to be consistent with one another"[2]: 269  and "did not view these apparently anomalous witness reports as persuasive evidence that some witnesses might have observed a missile."[2]: 270 

After missile visibility tests were conducted in April 2000, at Eglin Air Force Base, Fort Walton Beach, Florida,[2]: 254  the NTSB determined that if witnesses had observed a missile attack, they would have seen:

  1. a light from the burning missile motor ascending very rapidly and steeply for about 8 seconds
  2. the light disappearing for up to 7 seconds
  3. upon the missile striking the aircraft and igniting the CWT, another light, moving considerably more slowly and more laterally than the first, for about 30 seconds
  4. this light descending while simultaneously developing into a fireball falling toward the ocean.[2]: 270  None of the witness documents described such a scenario.[2]: 270 
Another frame from the CIA's animation depicting how the left wing of TWA Flight 800 was shorn off and created a second fireball

Because of their unique vantage points or the level of precision and detail provided in their accounts, five witness accounts generated special interest:[2]: 242–243  the pilot of Eastwind Airlines Flight 507, the crew members in the HH-60 helicopter, a streak-of-light witness aboard US Airways Flight 217, a land witness on the Beach Lane Bridge in Westhampton Beach, New York and a witness on a boat near Great Gun Beach.[2]: 243–247  Advocates of a missile-attack scenario asserted that some of these witnesses observed a missile;[2]: 264  analysis demonstrated that the observations were not consistent with a missile attack on TWA 800, but instead were consistent with these witnesses having observed part of the in-flight fire and breakup sequence after the CWT explosion.[2]: 264 

The NTSB concluded, "the witness observations of a streak of light were not related to a missile and that the streak of light reported by most of these witnesses was burning fuel from the accident airplane in crippled flight during some portion of the postexplosion, preimpact breakup sequence".[2]: 270  The NTSB further concluded, "the witnesses' observations of one or more fireballs were of the airplane's burning wreckage falling toward the ocean".[2]: 270 

Possible ignition sources of the center wing fuel tank

To determine what ignited the flammable fuel-air vapor in the CWT and caused the explosion, the NTSB evaluated numerous potential ignition sources. All but one were considered very unlikely to have been the source of ignition.[2]: 279 

Missile fragment or small explosive charge

Although the NTSB had already concluded that a missile strike did not cause the structural failure of the airplane, the possibility that a missile could have exploded close enough to TWA 800 for a missile fragment to have entered the CWT and ignited the fuel/air vapor, yet far enough away not to have left any damage characteristic of a missile strike, was considered.[2]: 272  Computer simulations using missile performance data simulated a missile detonating in a location such that a fragment from the warhead could penetrate the CWT.[2]: 273  Based on these simulations, the NTSB concluded that it was "very unlikely" that a warhead could have detonated in such a location where a fragment could penetrate the CWT without other missile fragments impacting the surrounding airplane structure, leaving distinctive impact marks.[2]: 273 

Similarly, the investigation considered the possibility that a small explosive charge placed on the CWT could have been the ignition source.[2]: 273  Testing by the NTSB and the British Defence Evaluation and Research Agency demonstrated that when the metal of the same type and thickness of the CWT was penetrated by a small charge, petalling of the surface occurred where the charge was placed, with pitting on the adjacent surfaces and visible hot-gas washing damage in the surrounding area.[2]: 273–274  Since none of the recovered CWT wreckage exhibited these damage characteristics and none of the areas of missing wreckage was large enough to encompass all the expected damage, the investigation concluded that this scenario was "very unlikely".[2]: 274 

Other potential sources

The NTSB also investigated whether the fuel-air mixture in the CWT could have been ignited by lightning strike, meteor strike, auto ignition or hot surface ignition, a fire migrating to the CWT from another fuel tank via the vent system, an uncontained engine failure, a turbine burst in the air conditioning packs beneath the CWT, a malfunctioning CWT jettison/override pump, a malfunctioning CWT scavenger pump, or static electricity.[2]: 272–279  After analysis, the investigation determined that these potential sources were "very unlikely" to have been the source of ignition.[2]: 279 

Fuel quantity indication system

Because a combustible fuel-air mixture will always exist in fuel tanks, Boeing designers attempted to eliminate all possible sources of ignition in the 747's tanks. To do so, all devices are protected from vapor intrusion, and voltages and currents used by the fuel quantity indication system (FQIS) are kept very low. In the case of the 747-100 series, the only wiring located inside the CWT is that associated with the FQIS.[citation needed]

For the FQIS to have been Flight 800's ignition source, a transfer of higher-than-normal voltage to the FQIS would have needed to occur, as well as some mechanism whereby the excess energy was released by the FQIS wiring into the CWT. The NTSB concluded, "the ignition energy for the CWT explosion most likely entered the CWT through the FQIS wiring."[2]: 294 [55]

Though the FQIS itself was designed to prevent danger by minimizing voltages and currents, the innermost tube of Flight 800's FQIS compensator showed damage similar to that of the compensator tube identified as the ignition source for the surge tank fire that destroyed a 747 near Madrid in 1976.[2]: 293–294  This was not considered proof of a source of ignition. Evidence of arcing was found in a wire bundle that included FQIS wiring connecting to the center wing tank.[2]: 288  Arcing signs were also seen on two wires sharing a cable raceway with FQIS wiring at station 955.[2]: 288 

The captain's CVR channel showed two "dropouts" of background power harmonics in the second before the recording ended (with the separation of the nose).[2]: 289  This might well be the signature of an arc on cockpit wiring adjacent to the FQIS wiring. The captain commented on the "crazy" readings of the number 4 engine fuel flow gauge about 2 1/2 minutes before the CVR recording ended.[2]: 290  Finally, the CWT fuel quantity gauge was recovered and indicated 640 pounds instead of the 300 pounds that had been loaded into that tank.[2]: 290  Experiments showed that applying power to a wire leading to the fuel quantity gauge can cause the digital display to change by several hundred pounds before the circuit breaker trips. Thus, the gauge anomaly could have been caused by a short circuit to the FQIS wiring.[2]: 290  The NTSB concluded that the most likely source of sufficient voltage to cause ignition was a short circuit from damaged wiring, or within electrical components of the FQIS. As not all components and wiring were recovered, pinpointing the source of the necessary voltage was not possible.

Report conclusions

The NTSB investigation ended with the adoption of the board's final report on August 23, 2000. The board determined that the probable cause of the TWA 800 accident was:[2]: 308 

[An] explosion of the center wing fuel tank (CWT), resulting from ignition of the flammable fuel/air mixture in the tank. The source of ignition energy for the explosion could not be determined with certainty, but, of the sources evaluated by the investigation, the most likely was a short circuit outside of the CWT that allowed excessive voltage to enter it through electrical wiring associated with the fuel quantity indication system.

In addition to the probable cause, the NTSB found the following contributing factors to the accident:[2]: 308 

  • The design and certification concept that fuel tank explosions could be prevented solely by precluding all ignition sources.
  • The certification of the Boeing 747 with heat sources located beneath the CWT with no means to reduce the heat transferred into the CWT or to render the fuel tank vapor noncombustible

During the course of its investigation, and in its final report, the NTSB issued 15 safety recommendations, mostly covering fuel tank and wiring-related issues.[2]: 309–312  Among the recommendations was that significant consideration should be given to the development of modifications such as nitrogen-inerting systems for new airplane designs, and where feasible, for existing airplanes.[56]: 6 

Controversy

See also: TWA Flight 800 conspiracy theories

After the accident, former Joint Chief of Staff Thomas Moorer and former White House Press Secretary Pierre Salinger speculated that the airplane was destroyed by a missile, with a nearby U.S. Navy ship being the likely culprit.[57] The NTSB's conclusions about the cause of the TWA 800 disaster took four years and one month to be published. The FBI's earliest investigations and interviews, later used by the NTSB, were performed under the assumption of a missile attack, a fact noted in the NTSB's final report. Six months into the investigation, the NTSB's chairman, Jim Hall, was quoted as saying, "All three theories—a bomb, a missile, or mechanical failure—remain."[58] Speculation was fueled in part by early descriptions, visuals, and eyewitness accounts of the disaster that indicated a sudden explosion and trails of fire moving in an upward direction.

On June 19, 2013, the NTSB acknowledged in a press release that they received a petition for reconsideration of its investigation into the July 17, 1996, crash of TWA Flight 800.[59] In 2014, the NTSB declined the petition to reopen the investigation.[60] In a press release, the NTSB stated: "After a thorough review of all the information provided by the petitioners, the NTSB denied the petition in its entirety because the evidence and analysis presented did not show the original findings were incorrect."[61]

Aftermath

A wreath is cast into the Atlantic Ocean after a ceremony to honor the deaths of the passengers.

Many internet users responded to the incident; the resulting web traffic set records for internet activity at the time. CNN's traffic quadrupled to 3.9 million views per day. The website of The New York Times had its traffic increase to 1.5 million views per day, 50% higher than its previous rate. In 1996, few U.S. government websites were updated daily, but the United States Navy's crash website was constantly updated and had detailed information about the salvage of the crash site.[62]

The wreckage was moved to an NTSB facility in Ashburn, Virginia, that was custom-built for the purpose.[63][64] The reconstructed aircraft was used to train accident investigators until it was decommissioned in 2021.[65]

The reconstruction of Flight 800 used as a training aid in NTSB's Training Center in Ashburn, Virginia

On July 18, 2008, the United States Secretary of Transportation Mary E. Peters visited the facility and announced a final rule designed to prevent accidents caused by fuel-tank explosions. The rule required airlines to pump inert gas into the tanks. The rule covered the CWT on all new passenger and cargo airliners, and passenger planes built in most of the 1990s, but not on old cargo planes.[66] The NTSB had first recommended such a rule just five months after the incident and 33 years after a similar recommendation issued by the Civil Aeronautics Board Bureau of Safety on December 17, 1963, nine days after the crash of Pan Am Flight 214.[67]

The crash of TWA Flight 800, and that of ValuJet Flight 592 earlier in 1996, prompted Congress to pass the Aviation Disaster Family Assistance Act of 1996 as part of the federal aviation appropriations bill. Among other things, the act gives NTSB, instead of the particular airline involved, responsibility for coordinating services to the families of victims of fatal aircraft accidents in the United States. In addition, it restricts lawyers and other parties from contacting family members within 30 days of the accident.[68]

During the investigation, the NTSB and the FBI clashed with each other. The agencies lacked a detailed protocol describing which agency should take the lead when whether an event was an accident or a criminal act was initially unclear. At the time of the crash, 49 CFR 831.5 specified that the NTSB's aviation accident investigations have priority over all other federal investigations.[69] After the TWA flight 800 investigation, the NTSB recognized the need for better clarity. The NTSB sought and secured language[citation needed] to clarify the issue in 49 USC 1131(a)(2)(B), which was amended in 2000 to read:

If the Attorney General, in consultation with the Chairman of the [NTSB], determines and notifies the [NTSB] that circumstances reasonably indicate that the accident may have been caused by an intentional criminal act, the [NTSB] shall relinquish investigative priority to the [FBI]. The relinquishment of investigative priority by the [NTSB] shall not otherwise affect the authority of the [NTSB] to continue its investigation under this section

49 USC 1131(a)(2)(B)[31]

In 2005, the NTSB and the FBI entered into a memorandum of understanding (MOU) that stated that, "[i]n the immediate aftermath of a transportation accident, the NTSB is the presumptive lead investigative agency and will assume control of the accident scene." The FBI may still conduct a criminal investigation, but the NTSB investigation has priority. When investigative priority remains with the NTSB, the FBI must coordinate its investigative activities with the NTSB investigator-in-charge. This authority includes interviewing witnesses. The MOU states that: "[t]his procedure is intended…to ensure that neither NTSB nor FBI investigative activity unnecessarily complicates or compromises the other agency's investigation." The new statutory language and the MOU have improved coordination between the NTSB and FBI since the TWA Flight 800 accident. As of 2005, NTSB and FBI personnel conduct joint exercises. Each agency can call upon the other's laboratories and other assets. The NTSB and the FBI have designated liaisons to ensure that information flows between agencies and to coordinate on-scene operations.[70][non-primary source needed]

Heidi Snow, the fiancée of Flight 800 victim Michel Breistroff, established the AirCraft Casualty Emotional Support Services nonprofit group together with families of victims of Pan Am Flight 103.[71]

Memorials

TWA Memorial

The TWA Flight 800 International Memorial was dedicated in a 2-acre (8,100 m2) parcel immediately adjoining the main pavilion at Smith Point County Park in Shirley, New York, on July 14, 2004. Funds for the memorial were raised by the Families of TWA Flight 800 Association. The memorial includes landscaped grounds, flags from the 13 countries of the victims, and a curved black granite memorial with the names engraved on one side and an illustration on the other of a wave releasing 230 seagulls. In July 2006, an abstract black granite statue of a 10-foot-high (3.0 m) lighthouse was added above a tomb holding many of the victims' personal belongings. The lighthouse statue was designed by Harry Edward Seaman, whose cousin died in the crash, and dedicated by George Pataki.[72]

Destruction of wreckage

For almost 25 years, the wreckage of Flight 800 was kept by the NTSB and used as an accident-investigation teaching aid. By 2021, the methods taught using the wreckage were determined to no longer be relevant to modern accident investigation, which by then relied heavily on new technology, including three-dimensional laser-scanning techniques.[73]

As the NTSB did not wish to renew the lease for the hangar in which it had stored the reassembled accident debris, it decommissioned the wreckage in July 2021.[74] As the NTSB had agreements with the victims' families that the wreckage cannot be used in any kind of public memorial or be scuttled in the ocean, it plans to scan each piece of debris with a three-dimensional laser scanner, with the data being permanently archived, after which the wreckage will be destroyed and the metal recycled. Any parts of the plane that cannot be recycled will be disposed of in landfills.[75][76] Destruction of the wreckage was scheduled for completion before the end of 2021.[74] The wreckage was destroyed in June 2023 near the former Ashburn facility in which it was housed.[77]

See also

References

Public Domain This article incorporates public domain material from websites or documents of the National Transportation Safety Board.

  1. ^ Ranter, Harro. "Aviation Safety Network > Accident investigation > CVR / FDR > Transcripts > CVR transcript TWA Flight 800 - 17 JUL 1996". mail.aviation-safety.net. Retrieved December 6, 2024.
  2. ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak al am an ao ap aq ar as at au av aw ax ay az ba bb bc bd be bf bg bh bi bj bk bl bm bn bo bp bq br bs bt bu bv bw bx by bz ca cb cc cd ce cf cg ch ci cj ck cl cm cn co cp cq cr cs ct cu cv cw cx cy cz da db dc dd de df dg dh di dj dk dl dm dn do dp dq dr ds dt du dv dw dx dy dz ea eb ec ed "In-flight Breakup Over The Atlantic Ocean, Trans World Airlines Flight 800, Boeing 747-131, N93119, Near East Moriches, New York, July 17, 1996" (PDF). Aircraft Accident Report. National Transportation Safety Board. August 23, 2000. NTSB/AAR-00/03. Archived (PDF) from the original on March 4, 2016. Retrieved January 5, 2016.
  3. ^ "What happened to Flight 800?". CNN. July 19, 1996. Archived from the original on November 4, 2019. Retrieved April 5, 2011.
  4. ^ Knowlton, Brian (July 24, 1996). "Investigators Focus Closely on Terrorism As Cause of Explosion: Chemicals Found on Jet Victims, U.S. Reports". The New York Times. ISSN 0362-4331. Archived from the original on February 2, 2017. Retrieved April 5, 2011.
  5. ^ Fedarko, Kevin; et al. (July 29, 1996). "Terror on Flight 800: Who wishes us ill?". Time. Archived from the original on January 31, 2014. Retrieved April 5, 2011.
  6. ^ "Aviation and criminal experts probe TWA crash". CNN. July 19, 1996. Archived from the original on June 1, 2019. Retrieved April 5, 2011.
  7. ^ "FBI: No criminal evidence behind TWA 800 crash". CNN. November 18, 1997. Archived from the original on June 22, 2019. Retrieved April 5, 2011.
  8. ^ "NTSB Board Meeting on TWA 800 August 23, 2000, Part 4". National Transportation Safety Board. Archived from the original on May 14, 2011. Retrieved April 5, 2011.
  9. ^ Tauss, Randolph M. (August 14, 2008). "The Crash of TWA Flight 800". Central Intelligence Agency. Archived from the original on August 5, 2011. Retrieved April 6, 2011.
  10. ^ Lowery, Joan (July 16, 2008). "Jet fuel-tank protection ordered". Seattle Post-Intelligencer. Associated Press. Retrieved April 5, 2011.
  11. ^ a b "Passenger and crew list, TWA Flight 800" (Press release). Trans World Airlines. July 19, 1996. Archived from the original on September 28, 2012. Retrieved January 9, 2010.
  12. ^ Redding, Cliff; Schwartzman, Paul (July 19, 1996). "Doomed Crewmen Called Hardy". New York Daily News. Archived from the original on December 3, 2016. Retrieved December 2, 2016.
  13. ^ "Airplane Performance Study – Attachment I: Boeing's TWA Flight 800 FDR Data Summary" (PDF). Docket No. SA-516, Exhibit No. 13A. National Transportation Safety Board. September 30, 1997. Archived (PDF) from the original on October 24, 2020. Retrieved November 14, 2010.
  14. ^ "TWA flight 800 | Background & Facts | Britannica". www.britannica.com. Retrieved December 6, 2024.
  15. ^ a b "Group Chairman's Factual Report of Investigation – Cockpit Voice Recorder" (PDF). Docket No. SA-516, Exhibit No. 12-A. National Transportation Safety Board. February 9, 2000. Archived from the original (PDF) on June 14, 2007. Retrieved November 7, 2012.
  16. ^ "Group Chairman's Factual Report of Investigation – Sound Spectrum Study" (PDF). Docket No. SA-516, Exhibit No. 12-B. National Transportation Safety Board. November 15, 1997. Archived (PDF) from the original on July 23, 2021. Retrieved July 10, 2019.
  17. ^ "Test Report Number: 03-RPT-0031 Underwater Acoustic Locator Beacon (CVR) Dukane Corporation" (PDF). Docket No. SA-516, Exhibit No. 12-C. National Transportation Safety Board. January 7, 1997. Archived (PDF) from the original on July 23, 2021. Retrieved July 10, 2019.
  18. ^ "The Flight 800 Investigation". twa800.com. Retrieved March 7, 2023.
  19. ^ a b "Air Traffic Control Group Chairman's Factual Report" (PDF). Docket No. SA-516, Exhibit No. 3-A. National Transportation Safety Board. September 12, 1997. Archived (PDF) from the original on July 23, 2021. Retrieved July 17, 2019.
  20. ^ Ranter, Harro. "ASN Aircraft accident Boeing 747-131 N93119 East Moriches, NY". Aviation Safety Network. Flight Safety Foundation. Archived from the original on January 12, 2012. Retrieved January 15, 2010.
  21. ^ a b c d "Passenger List: TWA Flight 800". The Washington Post. Associated Press. August 27, 1996. Archived from the original on May 14, 2011. Retrieved June 18, 2008.
  22. ^ "On behalf of NINO: Rico Puhlmann". www.stadtmuseum-nordhorn.de. Archived from the original on June 12, 2018. Retrieved October 8, 2018.
  23. ^ Nieves, Evelyn (July 20, 1996). "The Crash of Flight 800: The Passengers; Reunions and Homecomings Never Fulfilled and Sudden End to a Vacation". The New York Times. ISSN 0362-4331. Retrieved September 15, 2022.
  24. ^ "Ana Maria Shorter, Wife of Jazz Musician, Dies On Flight 800". AP News. July 17, 1996. Retrieved March 15, 2022.
  25. ^ "ABC Sports Producer Was On TWA Plane". Tampa Bay Times. July 19, 1996. Retrieved September 9, 2023.
  26. ^ Lucview, John (July 16, 2016). "Montoursville mourns: Flight 800 took away 'part of its future'". PennLive.com. Archived from the original on February 25, 2018. Retrieved February 25, 2018.
  27. ^ Burnstein, Ben (July 12, 2006). "Town still mourns 10 years after TWA 800". CNN. Archived from the original on July 27, 2016. Retrieved October 8, 2018.
  28. ^ "TWA 747 explodes off Long Island". CNN. July 17, 1996. Archived from the original on November 28, 2019. Retrieved January 11, 2010.
  29. ^ Malkin, Lawrence; Knowlton, Brian (July 19, 1996). "No Survivors Among 228 In N.Y. Jetliner Explosion". The New York Times. ISSN 0362-4331. Archived from the original on May 30, 2013. Retrieved January 11, 2010.
  30. ^ Thomas, Evan (July 29, 1996). "Death On Flight 800". Newsweek Magazine. Archived from the original on March 6, 2022. Retrieved January 11, 2010.
  31. ^ a b "49 USC 1131(a)(2)(B)". Archived from the original on February 21, 2020. Retrieved February 21, 2020.
  32. ^ a b "NTSB Board Meeting on TWA 800 August 22, 2000, Morning Session". National Transportation Safety Board. Archived from the original on January 13, 2006. Retrieved February 11, 2010.
  33. ^ a b c Thomas, Evan (August 5, 1996). "Riddle Of The Depths". Newsweek Magazine. Retrieved March 4, 2010.
  34. ^ a b c d "Medical/Forensic Group Factual Report" (PDF). Docket No. SA-516, Exhibit 19A. National Transportation Safety Board. Archived (PDF) from the original on July 23, 2021. Retrieved January 11, 2010.
  35. ^ a b Leland, John (August 5, 1996). "Grieving At Ground Zero". Newsweek Magazine. Archived from the original on March 6, 2022. Retrieved January 14, 2010.
  36. ^ Swarns, Rachel L. (August 7, 1996). "For Crash Victims' Families, A Painful Return to Routine". The New York Times. ISSN 0362-4331. Archived from the original on December 6, 2010. Retrieved February 26, 2010.
  37. ^ Gray, Lisa (October 23, 1997). "After the Crash". Houston Press. Archived from the original on July 28, 2012. Retrieved November 4, 2012. "The Ramada Inn at JFK was "Crash Central," the gathering place for the 230 victims' families, as well as investigators, the TWA 'go team', and the media."
  38. ^ Adamson, April (September 4, 1998). "Victims Knew Jet Was In Trouble Airport Inn Becomes Heartbreak Hotel Again". The Philadelphia Inquirer. Archived from the original on March 3, 2016. Retrieved March 9, 2014.
  39. ^ Nissen, Beth (November 17, 2011). "Hotel Near JFK Airport is Familiar With Airline Tragedy". CNN. Archived from the original on December 29, 2014. Retrieved March 9, 2014.
  40. ^ Chang, Ying; Lambiet, Jose; Jere, Hester (July 20, 1996). "A Heartbreak Hotel for Kin They wait, Weep at JFK Ramada". New York Daily News. Archived from the original on March 9, 2014. Retrieved March 9, 2014.
  41. ^ a b c Van Natter, Don Jr. (July 25, 1996). "Navy Retrieves 2 'Black Boxes' From Sea Floor". The New York Times. ISSN 0362-4331. Archived from the original on May 31, 2013. Retrieved March 4, 2010.
  42. ^ a b c Purdy, Matthew (July 30, 1996). "Airliner Bombings Are Reviewed For Similarities to T.W.A. Crash". The New York Times. ISSN 0362-4331. Archived from the original on December 26, 2013. Retrieved March 3, 2010.
  43. ^ a b c d e f g Sexton, Joe (August 23, 1996). "Behind a Calm Facade, Chaos, Distrust, Valor". The New York Times. ISSN 0362-4331. Archived from the original on March 8, 2016. Retrieved March 3, 2010.
  44. ^ International Association of Machinists and Aerospace Workers: Analysis and Recommendations Regarding T.W.A. Flight 800 Archived September 30, 2007, at the Wayback Machine
  45. ^ a b "Documents Pertaining to Witnesses 300-399" (PDF). Docket No. SA-516, Appendix E. National Transportation Safety Board. Archived (PDF) from the original on July 23, 2021. Retrieved March 4, 2010.
  46. ^ a b c d e f g h i j k "Witness Group Chairman's Factual Report" (PDF). Docket No. ?, Exhibit 4-A. National Transportation Safety Board. Archived (PDF) from the original on July 23, 2021. Retrieved January 12, 2010.
  47. ^ "Documents Pertaining to Witnesses 1-99" (PDF). Docket No. SA-516, Appendix B. National Transportation Safety Board. Archived (PDF) from the original on July 23, 2021. Retrieved March 4, 2010.
  48. ^ "Flight Data Recorder Group Chairman's Factual Report" (PDF). Docket No. 5A-516, Exhibit No. 10A. National Transportation Safety Board. Archived (PDF) from the original on July 23, 2021. Retrieved January 15, 2010.
  49. ^ van Natta, Don Jr. (August 31, 1996). "More Traces Of Explosive In Flight 800". The New York Times. ISSN 0362-4331. Archived from the original on October 5, 2018. Retrieved January 12, 2010.
  50. ^ "Source: Traces of 2nd explosive found in TWA debris". CNN. August 30, 1996. Archived from the original on October 5, 2018. Retrieved January 13, 2010.
  51. ^ a b "Metallurgy/Structures Group Chairman Factual Report Sequencing Study" (PDF). Docket No. 5A-516, Exhibit No. 18A. National Transportation Safety Board. Archived (PDF) from the original on July 23, 2021. Retrieved January 31, 2010.
  52. ^ "Fire in the sky" (PDF). System Failure Case Studies. National Aeronautics and Space Administration. Archived from the original on July 1, 2013. Retrieved June 30, 2013.
  53. ^ a b c d Tauss, Randolph M. "Solving the Mystery of the 'Missile Sightings'" (PDF). The Crash of TWA Flight 800. Central Intelligence Agency. Archived from the original (PDF) on August 5, 2011. Retrieved April 6, 2011.
  54. ^ "Witnesses 4 – Group Chairman Factual Report – Appendix Z – Interview transcript Capt. David McClaine" (PDF). Docket No. SA-516, Appendix Z. National Transportation Safety Board. March 25, 1999. Archived (PDF) from the original on July 23, 2021. Retrieved March 14, 2021.
  55. ^ In-flight breakup over the Atlantic Ocean, Trans World Airlines Flight 800 Boeing 747-131, N93119, near East Moriches, New York, July 17, 1996. Diane Publishing. 2000. pp. 294–. ISBN 978-1-4289-6207-1. Archived from the original on July 23, 2021. Retrieved March 10, 2021.
  56. ^ "National Transportation Safety Board Safety Recommendation" (PDF). National Transportation Safety Board. Archived from the original (PDF) on June 8, 2010. Retrieved January 16, 2010.
  57. ^ "Salinger's Accusations About TWA Flight 800 Resurface in New Documentary | the Georgetowner". July 22, 2013.
  58. ^ "Six months later, still no answer to the TWA Flight 800 mystery". CNN. January 17, 1997. Archived from the original on June 13, 2008. Retrieved June 18, 2008.
  59. ^ "Statement on Petition for Reconsideration of TWA 800 Investigation". www.ntsb.gov. Archived from the original on August 9, 2019. Retrieved February 26, 2020.
  60. ^ "NTSB Refuses to Reopen TWA Flight 800 Crash Probe". NBC News. July 3, 2014. Archived from the original on November 30, 2019. Retrieved July 10, 2019.
  61. ^ "NTSB Denies Petition on 1996 Crash of TWA Flight 800". www.ntsb.gov. Archived from the original on August 16, 2019. Retrieved July 10, 2019.
  62. ^ Barboza, David. "Many Hits, Some Misses: The Post-Crash Web Rush Archived July 20, 2016, at the Wayback Machine." The New York Times. August 6, 1996. Retrieved on June 5, 2009.
  63. ^ "Aircraft Boneyards". Boneyard. History Channel. Archived from the original on October 24, 2007. Retrieved August 9, 2007.
  64. ^ "NTSB Training Center". ntsb.gov. Archived from the original on December 28, 2013. Retrieved June 29, 2020.
  65. ^ "TWA Flight 800 wreckage in Ashburn to be decommissioned". InsideNova.com. February 25, 2021. Archived from the original on February 25, 2021. Retrieved February 25, 2021.
  66. ^ Wald, Matthew L. (July 16, 2008). "Rule Readied to Prevent Airliner Explosions". The New York Times. Archived from the original on July 20, 2016. Retrieved November 7, 2015.
  67. ^ "Pan Am Flight 214 CAB report (PDF) (Historical Aircraft Accident, 1963, Pan Am)" (PDF). Archived from the original (PDF) on May 26, 2013.
  68. ^ New York City Bar. "Report and Recommendations Regarding TWA Flight 800 Crash". nycbar.org. Archived from the original on September 8, 2015. Retrieved April 10, 2015.
  69. ^ "49 CFR 831.5" (PDF). Archived (PDF) from the original on February 21, 2020. Retrieved February 21, 2020.
  70. ^ "Improvements Resulting From NTSB's Recommendations". usa.gov. Archived from the original on April 18, 2015.
  71. ^ Angley, Natalie (February 10, 2015). "Coping with sudden loss after airplane crashes". CNN. Archived from the original on February 12, 2015. Retrieved February 12, 2015.
  72. ^ Katie, Thomas (July 18, 2006). "Remembering Flight 800". Newsday. Archived from the original on May 19, 2008. Retrieved June 18, 2008.
  73. ^ Freeze, Christopher. "NTSB'S Reconstruction of the TWA Flight 800 Fuselage to be Decommissioned". ALPA.org. ALPA.
  74. ^ a b Aratani, Lori (July 16, 2021). "Wreckage from TWA Flight 800 to be destroyed 25 years after crash". The Washington Post. ISSN 0190-8286. Archived from the original on July 16, 2021. Retrieved July 17, 2021.
  75. ^ Hemmerdinger, Jon. "After 25 years, NTSB to dismantle TWA 800 reconstruction". Flight Global. Archived from the original on July 17, 2021. Retrieved February 22, 2021.
  76. ^ "NTSB's TWA Flight 800 Reconstruction to be Decommissioned". www.ntsb.gov. National Transportation Safety Board. February 22, 2021. Archived from the original on February 22, 2021. Retrieved March 14, 2021.
  77. ^ "NTSB dismantles TWA Flight 800 wreckage in Loudoun County this week". wusa9.com. June 8, 2023. Retrieved January 16, 2024.
Wikimedia Commons has media related to TWA Flight 800 (1996).
Wikisource has original text related to this article:
External image
image icon Photos of N93119 at Airliners.net