Partnair Flight 394

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

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

Partnair Flight 394
File:Partnair CV-580 LN-PAA.jpg
LN-PAA in 1987
Accident summary
Date 8 September 1989
Summary Improper maintenance, rudder malfunction due to substandard parts
Site 18 km north of Hirtshals, Denmark
Passengers 50
Crew 5
Injuries (non-fatal) 0
Fatalities 55 (all)
Survivors 0
Aircraft type Convair CV-580
Operator Partnair
Registration LN-PAA [1]
Flight origin Oslo Airport, Fornebu, Oslo, Norway
Destination Hamburg Airport, Hamburg, West Germany

Partnair Flight 394 was a chartered flight which crashed on 8 September 1989 off the coast of Denmark 18 km north of Hirtshals. All 50 passengers and 5 crew members on board the aircraft perished, making it the deadliest civilian aviation accident involving an all-Norwegian airline company.[1] It was also the highest death toll of any aviation accident involving a Convair 580, and the biggest airplane accident in Denmark. It was caused by use of unapproved aircraft parts in repairs and maintenance.[2]

Aircraft

The aircraft, registered LN-PAA, was a 36-year-old Convair CV-580 operated by the charter airline Partnair. The plane had switched owners several times and had various modifications.[2][3] The aircraft had multiple previous registrations, N73128, EC-FDP, PK-GDS, HR-SAX, JA101C, N770PR and C-GKFT and had been rebuilt after a landing accident in 1978.[4][5] The most significant modification was a change from piston engines to turboprop engines in 1960; this added more horsepower to the aircraft.[3] A Canadian company that specialized in servicing Convairs was the owner of the aircraft before Partnair acquired it. LN-PAA was one of the most recently acquired aircraft in the Partnair fleet.[2] At the time of the crash, there were 2 other Convair 580 in the Partnair fleet.

Background

At the time of the accident Partnair was in financial difficulty. The airline's debts were such that, on the day of the accident flight, Norwegian aviation authorities had notified Norwegian airports to not allow Partnair aircraft to depart since Partnair had not paid several charges and fees.[2]

Flight

The Convair 580 aircraft was en route from Oslo Airport, Fornebu, Norway to Hamburg Airport, West Germany. The passengers were employees of the shipping company Wilhelmsen Lines who were flying to Hamburg for the launching ceremony of a new ship. Half of the employees of the company's head office were on board. Leif Terje Løddesøl, an executive of Wilhelmsen, said that the atmosphere in the company was "very very good" prior to the accident flight. He said that some of the employees "maybe" had been to prior naming ceremonies, which he described as "quite exciting." A regular employee on the flight, one of the top-performing employees in the company, had been asked to give the speech during the launching ceremony. Løddesøl said that it was not often that a "normal person" in the company was chosen to read the speech at the naming ceremony.[2]

The flight crew consisted of Captain Knut Tveiten (59) and First Officer Finn Petter Berg (59). Tveiten and Berg were close friends who had flown together for years. Both pilots were very experienced, with close to 17,000 flight hours each. Berg was also the company's Flight Operations Manager.

Before the flight, the crew found that one of the two main power generators had not worked since 6 September, and the mechanic who inspected the aircraft was unable to fix it. In the Norwegian jurisdiction an aircraft is only allowed to take off if it has two operable sources of power.[2][3] Also the aircraft's Minimum Equipment List required two operating generators.[3] The first officer decided that he would run the auxiliary power unit (APU) throughout the flight so that the flight would have two sources of power and therefore be allowed to leave. The pilots did not know that one of the three APU mounts was broken, and the resulting vibration would be a factor in the accident flight. The airport refused to let the flight go until the catering bill was paid. Before the aircraft took off, the first officer left the cockpit to pay the catering company. As a result of this, the plane was delayed almost an hour, finally departing at 3:59 p.m.[2][3]

As the Partnair aircraft passed over the water at planned cruising attitude - 22,000 feet,[3] a Norwegian General Dynamics F-16 Fighting Falcon fighter jet passed by it. The fighter pilot was startled by the sudden appearance of the aircraft and contacted Oslo air traffic control. He believed that the radar data were false and that the aircraft was closer to his jet than his on-board computer had indicated.[6]

As the aircraft neared the Danish coastline, 22,000 feet (6,706 m) over the North Sea, the tail section of the aircraft started to rattle.[2] The broken APU mount vibrated due to the bolts in the tail of the aircraft,[7][8] which were weaker than the authentic parts. The investigators concluded that the vibrations reached the same frequency and went into synchronization, a phenomenon known as resonance, causing a coupled harmonics force (similar to the one that caused the Tacoma Narrows Bridge collapse in 1940); the force of each vibration wave would add to that of another vibration, increasing in amplitude until the structure failed.[2]

With a rising level of vibration, a failure in the plane's tail section must have become evident to the crew. In the investigation, it was found that the crew triggered the fire extinguisher for the APU.[3] The rudder oscillated to its maximum limits and jammed to the left,[3] and the aircraft was forced into an abrupt left turn that caused it to roll over. The crew recovered for a brief moment. The rudder jammed to the left again and the shroud doors, which provide access to weights in the aircraft's tail that control the movement of the rudder, broke off. The aircraft went into a second roll, and its tail section disintegrated. The rest of the aircraft disintegrated on the way down to the sea.[2]

Investigation

Accident Investigation Board Norway (AIBN) investigated the disaster. Fifty of the 55 bodies were recovered. The recovered bodies were given autopsies in Denmark. Investigators used side-scan sonar to plot positions of wreckage. The pieces had settled over an area 2 kilometres (1.2 mi) wide. This told the investigators that the aircraft disintegrated in the air. The investigators re-constructed 90% of the aircraft.[2][3][page needed]

Some initial speculation in Norwegian press stated that a bomb brought down Partnair. In December 1988, a bomb had brought down Pan Am Flight 103. In addition, the Prime Minister of Norway Gro Harlem Brundtland had used that particular Partnair aircraft on her campaign trips. The Norwegian press believed that the crash was a failed assassination attempt. Witnesses of the crash said that they heard a loud noise as they saw the aircraft fall. The fact that the aircraft had disintegrated in the air gave credibility to the bomb theory.[2]

The cockpit voice recorder (CVR) usually records the final minutes of an accident flight. In the Partnair crash it had recorded the start of the flight and stopped shortly before the aircraft took off. From the maintenance records investigators found that, 10 years prior to the accident flight, the cockpit voice recorder had been modified so that the CVR would use the aircraft's generator instead of the aircraft's battery if full power was applied for takeoff.[3] As the generator was inoperative on this flight, this meant that power to the CVR cut out as the aircraft took off. An unpaid catering bill and the failed CVR led Norwegian investigators to scrutinize Partnair and the aircraft.[2]

The flight data recorder (FDR), an antiquated analog model, used a rotating metal foil strip and marking pins which scratched the strip. The FDR did not record all of the parameters that it was supposed to record, mainly vertical acceleration readings were missing and heading indications were abnormal.[3][page needed] The needle recorded some lines twice, initially confusing the investigators. The team sent the FDR to the American company which manufactured it.[2]

When the aircraft was re-assembled, investigators found small traces of high-powered military explosives. Members of the public believed that the traces could have been from a bomb or from the NATO war exercise "Operation Sharp Spear," which took place on the day of the accident flight near the flight path. Investigators found that the residue was not from a bomb, nor was it from a warhead, as there was not enough of it present. Finn Heimdal, an AIBN investigator, said in an interview that the residue appeared to be more like a contamination than any other possibility. The sea had old munitions as many battles had been fought off the coast of Denmark. Investigators concluded that the aircraft pieces acquired residue from the bottom of the sea.[2] In the AIBN investigations, no signs of explosives were found, and the traces of RDX military explosives were explained by contamination before the accident or due to storage.[3][page needed]

Metallurgist Terry Heaslip of the Canadian Company Accident Investigation and Research Inc. examined the aircraft skin from the tail and found signs of overheating, specifically that the skin had been flexed, through a phenomenon known as flutter. This caused investigators to further scrutinize the tail of the aircraft. The investigation team found that the APU, which was in the tail, had melted plastic parts from the cabin present inside the turbine. This indicated that the APU was operating; normally the APU would not be operating when the aircraft was in flight. The mechanic who had inspected the aircraft on the day of the accident flight told the investigators that one of the aircraft's two main generators had failed and that he was not able to repair the faulty generator. The investigators discovered that the APU had been operated to replace one of the main generators, and that one of the three APU mounts was broken. The mount was broken before the accident flight, and people on previous flights had said that they experienced vibration. One passenger of a previous flight said that the accident Convair had vibrated more than the company's other Convairs. Other passengers of previous flights did not mention any vibration.[2] According to AIBN, the decision of having the APU operating in flight, was denoted in the Flight Log.[3][page needed]

The two shroud doors on the aircraft tail were not present in the tail. The doors, constructed with an aluminium honeycomb liner, had reflective properties also found in aluminium foil. Heimdal, who had served in the military, knew that the doors would appear on radar. The unidentified objects – found at a high altitude by Swedish radar for 38 minutes – were likely the shroud doors, which had separated from the aircraft tail. The investigators found that the tail failed at 22,000 feet. If the rudder moved in a violent manner, the weights would also move violently and hit the shroud doors. Therefore the rudder had made a violent movement as the accident unfolded.[2][3][page needed]

Partnair said that the F-16 fighter jet had been flying at a faster velocity and closer to the Convair than reported in the media. Therefore the jet, which would have broken the supersonic barrier at that point, had flown too close and at supersonic speed near the Partnair plane. The pressure wave, resulting from the breaking of the sonic barrier, would have caused the Convair to disintegrate in mid-air.[2] Flygtekniska Försöksanstalten, a Swedish aviation technology research facility said that there was a 60% chance of this being the cause.[9] The Norwegian F-16 pilot testified that his aircraft was more than 1,000 ft (300 m) above the Convair. The investigators concluded that the F-16 would have had to have been within a few metres of the Convair to have affected the passenger aircraft; the investigators had no evidence that the two aircraft were that close together.[2] One aspect that had not been written in the final report is that the investigation had doubted radar information that it received and believed that the jet was traveling closer to the Partnair aircraft than the radar information stated; the pilot of the F-16 stated that he believed the radar data was false.[6] After the investigation concluded, the Thoresen brothers filed a lawsuit, but a ruling in the Norwegian lagmannsrett (intermediate court) dismissed this theory in 2004.[9] This F-16 flight had been part of AIBN investigations, and no connection to the accident was found.[3][page needed]

The manufacturer of the defective flight data recorder asked an ex-employee, the highest expert regarding the company's flight data recorders, to leave retirement to examine the FDR. The expert concluded that the needle supposed to have been recording the altitude had been shaking so much that it left another mark on the foil. The particular FDR was able to record for hundreds of hours; the expert unspooled the foil and found that the needle had been shaking for months. This told investigators that another component of the aircraft had been vibrating. The investigators charted the vibrations and found that two months before the crash, the vibrations stopped for two weeks. Afterward, the vibrations increased up to the accident flight. Investigators found that during the two-week period in July 1989 the aircraft received a major overhaul in Canada by the airline's previous owner. When the Canadian company made test flights and during the aircraft's first several passenger flights for Partnair, the FDR recorded almost no abnormal vibrations. When the investigators reviewed the maintenance records, they found that, during the overhaul, mechanics discovered wear on one of the four bolts/pins that connected the vertical fin to the fuselage. During the overhaul, the mechanic replaced one of the bolts/pins. The vibrations stopped after the bolt/pin was replaced. Investigators found the four bolts/pins that held the tail on to the fuselage. Heaslip found that the three bolts/pins that were not replaced were not authentic parts and were incorrectly heat-treated during manufacture. Therefore, each bolt had 60% of its intended strength. The three unreplaced bolts/pins were too weak for regular usage on the aircraft. After the period without vibration, the tail vibrated for 16 completed flights and the accident flight. The investigation team concluded that the usage of the APU (which had a broken mount) when combined with the vibrating tail (due to the wear and deformation of the substandard bolts/pins and associated sleeves) caused an aeroelastic oscillation that caused the aircraft's primary control surfaces to fail during the accident flight.[2]

AIBN investigations showed the aircraft to have been subject to abnormal vibrations in the empennage for an extended period. During the accident flight, there was with all probability a connection between the operating APU and a rising level of vibrations in the tail section. The investigation documents both the replacement of vertical stabilizer mounting bolts with insufficient properties and the mounting of the APU with a front support of "inferior design and unknown origin".[3][page needed]

The disaster investigation team concluded that three of the bolts/pins used to secure the tail section were counterfeit and inferior to the parts that should have been used. The metal in the bolts was not strong enough and failed when resonant vibration occurred in the auxiliary power unit.[2]

Aftermath

As a result of the accident, safeguarding against forged aircraft parts increased. Peter Friedman, an expert on forged parts, stated in an episode of the television programme Mayday (Air Crash Investigation, Air Emergency) that the Partnair accident was the "seminal event" that caused people around the world to recognize the proliferation of forged aircraft parts in parts inventories. The spare aircraft parts industry had little regulation in many places in the world at the time of the Partnair accident. The United States Department of Transportation (USDOT), which oversees the Federal Aviation Administration (FAA), examined the scope of the spare parts in the United States. The USDOT audited the FAA's inventory and found that 39% of the parts in the bins were forged. The fraudulent parts came from a parts broker that was prominent in the parts broker industry; 95% of the parts in that broker's inventory were forged. Mary Schiavo, the former inspector general of the USDOT, said that American parts brokers had "no regulation whatsoever." Schiavo said that an individual with a telephone and a fax machine could become a parts broker and could get his or her parts from a variety of sources, including junkyards, scrap facilities, older aircraft, aircraft involved in accidents and incidents, and illegal parts manufacturers. Forged parts were often less expensive than authentic parts. Friedman said that "bottom line-driven" airlines, including those on the verge of bankruptcy, wanted to cut costs, driving them to acquire false parts.[2]

The FAA investigated false parts and captured illegal parts dealers in sting operations. The FAA found that there was an industry for making thousands of worn and inferior parts to look like newly manufactured parts. At the time of the Partnair accident, aircraft parts were required to have documentation with signatures indicating that the parts were authentic. The FAA found that illegal business forged FAA tags to make the parts appear authentic. Schiavo said that many of the operators signed the tags with forged signatures of real inspectors. Friedman said that the tags had more monetary value than the actual illegal parts. The Americans initially believed that the proliferation of false parts mainly affected only smaller airlines; Schiavo said that smaller airlines and repair stations were usually the businesses that were the most likely to accept false parts. The FAA later found forged parts in larger operations; in particular Air Force One, the aircraft used by the President of the United States, had fraudulent parts. As a result illegal parts dealers faced arrests and convictions. Schiavo said that the most important action taken by the United States government regarding the proliferation of forged parts was to cause the convictions of the parts dealers. The FAA created a more rigorous documenting system to prevent the proliferation of fake aircraft parts. Airlines would receive criminal charges if they knowingly accept defective aircraft parts. In the 2000s, Schiavo said that forged parts are not proliferated as often because there is more regulation in that time period than in the 1980s and the 1990s.[2]

Dramatization

The Partnair crash is dramatized in the episode "Deadly Prize" ("Silent Killer," "Blown Apart") of the Canadian television documentary series Mayday (Air Crash Investigation, Air Emergency).[2]

Maps

The locations of the accident and the airports
Oslo
Oslo
Hamburg
Hamburg
Crash site
Crash site
Location of the accident and the airports
Crash site is located in Denmark
Crash site
Crash site
Crash site in Denmark

References

  1. Gregersen, M.; Jensen, S. & Knudson, P.J. (1995): The crash of the Partnair Convair CV-580 in the Skagerrak: identification of the deceased. Aviat. Space Environ. Med. 66: 158–163.
  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 2.19 2.20 2.21 2.22 2.23 "Deadly Prize." Mayday. [TV documentary series]
  3. 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 3.13 3.14 3.15 AIB-Norway's report on the accident (Norwegian original version) (Archive) – (English translation) (Archive)
  4. Flight International (1989) p16
  5. Letter in the Norwegian parliament to the Minister of Communications (in Norwegian)
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  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.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

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