31.03.2014 Views

REPORT OF THE - Archives - Syracuse University

REPORT OF THE - Archives - Syracuse University

REPORT OF THE - Archives - Syracuse University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

In a major inspection conducted May 8-23, 1989, the FAA found that major security<br />

violations still existed in Pan Am's Frankfurt operations.<br />

One FAA inspector wrote in the report dated June 7, 1989, that while the operations of<br />

the four other U.S. carriers operating at Frankfurt were "good," Pan Am was "totally<br />

unsatisfactory."<br />

Wrote the FAA inspector: "Posture [of Pan Am] considered unsafe, all passengers flying<br />

out of Frankfurt on Pan Am are at great risk."<br />

When the FAA Associate Administrator with responsibility for the security division<br />

learned of the May inspection results, he called a June 14 meeting with Pan Am officials,<br />

who presented a plan for corrective action while contesting some of FAA's allegations.<br />

Still, the security violations and deficiencies at Pan Am's Frankfurt station continued. An<br />

unannounced inspection in August of 1989 found that many of the same security<br />

problems from the May inspection remained uncorrected, especially unguarded airplanes<br />

and failure to search personnel maintaining the aircraft.<br />

Pan Am came to a September 12 meeting with FAA on security at Frankfurt with yet<br />

another "action plan." A later gathering, however, included a private session between the<br />

FAA Administrator and the chief executive officer of the airline. That same evening, a<br />

team of high-level Pan Am managers, accompanied by FAA security inspectors, flew to<br />

Frankfurt.<br />

Within one week, personnel changes at the station had been ordered and all security<br />

violations and deficiencies corrected. At the next FAA regular inspection, Pan Am at<br />

Frankfurt was rated a model station. This corrective action occurred nine months after the<br />

Flight 103 bombing.<br />

The bombing of Flight 103 occurred against the background of warnings that trouble was<br />

brewing in the European terrorist community. Nine security bulletins that could have<br />

been relevant to the tragedy were issued between June 1, 1988 and December 21, 1988.<br />

One described a Toshiba radio cassette player, fully rigged as a bomb with a barometric<br />

triggering device, found by the West German police in the automobile of a member of the<br />

Popular Front for the Liberation of Palestine - General Command (PFLP-GC). The FAA<br />

bulletin cautioned that the device "would be very difficult to detect via normal X-ray,"<br />

and told U.S. carriers that passenger/baggage reconciliation procedures should be<br />

"rigorously applied."<br />

On December 5, 1988, an anonymous telephone caller to the U.S. Embassy in Helsinki,<br />

Finland, said that sometime within the next two weeks a Finnish woman would carry a<br />

bomb aboard a Pan Am aircraft flying from Frankfurt to the United States. The FAA<br />

Security Bulletin on that threat was issued December 9.<br />

At the U.S. Embassy in Moscow, the senior staff, with concurrence of the Ambassador,<br />

decided that the warning should be made public. Thus the Helsinki threat information<br />

was publicly posted at the Embassy on December 14 and was generally made available<br />

throughout the 2,000-member community of Americans, including news media and<br />

private contractor personnel, in Moscow. For these Americans, Pan Am through<br />

Frankfurt was the most accessible and most commonly used route to the United States.<br />

The Commission found no passenger who changed his or her travel plans because of the<br />

Helsinki threat except one civilian who was scheduled to fly Pan Am to the United States<br />

through Frankfurt on December 16 and switched to a direct flight on December 18. While

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!