ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Special Presentation to 9-11 Victim Families

Updated on April 8, 2020

Once the Seventh Hearing concluded in late January, 2004, the families of those murdered on September 11, 2001 were very upset with the lack of information presented. What was the government hiding? Why couldn’t that hearing have gone into more detail about what the brave crew members’ actions had accomplished? Did their actions save other flights from the same horrific fate? They needed closure! So when more than 100 family members were told that the FBI would hold a special presentation with more detailed information, they were encouraged that they would finally be able to start connecting the events of that morning.

On June 4, 2004, in Princeton NJ families gathered at the Radisson Hotel with great expectations. They needed to know who knew what and when and what the FBI, FAA, and the airlines did with that information. (Note 1) These were families that were not part of the 7 billion dollar settlement funded by the government that was offered to nearly 3,000 people by the end of 2003.

Once inside the hotel, they realized FBI agents were there to restrict items such as cameras, phones, recorders and any material that could be used to take notes. The agents were also there to keep civil attorneys and the media out. Those in charge explained some of the material they would cover would be about Zacarias Moussaoui who was thought at that time to be the 20th hijacker and whose case had yet to be heard in the courts. With that being said, nondisclosure agreements had to be signed, and bathroom visits would need an FBI escort. After the rules had been explained, they went into the ballroom where the PowerPoint presentation was to be given. Sadly, the three and a half hour briefing spent much of the time on Zacharias Moussaoui -- a topic which was irrelevant to the concerns of the families. They did, however, hear some tape recordings from passengers and inflight crew members on their phones.

What was really upsetting was hearing the tape of two American managers at headquarters in Systems Operations Control (SOC) saying, “Do not pass this along. Let’s keep it right here. Keep it among the five of us.” However in the Seventh Hearing, the top executive for American, Mr. Arpey, testified that at 8:40 they knew there had been stabbings on the plane and it was headed south from Boston toward New York and that the cockpit was not responding to calls from American headquarters. This timeline seems a bit off because flight attendant Amy Sweeney had been on the airline phone at least 15 minutes earlier relaying the grim details of the scene on board AA Flight 11. Flight attendant Betty Ong was also relaying information even earlier to Reservations in Raleigh, NC which was forwarded to the SOC. That center was at the heart of the whole American operations system, but instead of sharing the information with the airborne crews, they held back. If only the words that that had been given to the flying crews after the two Tower crashes had been, “Unusual hijackings, protect your cockpits.” But instead, both American and United kept their information to themselves. Jane Allen, the vice president of American’s 2400 flight attendants and who was responsible for their operations at their 22 bases kept her information within the headquarters walls, and even said to one of her subordinates, “I really am not interested in helping or participating.”

As the families departed the hotel on that late spring day, “extreme upset” would have been an understatement. Yet there was still a glimmer of hope because in less than two weeks the last hearing was supposed to cover the 9-11 timeline. Unfortunately, the families would be disappointed again as that hearing was changed to “The Plot” and how the terrorists got away with their attack.

Notes:

  1. Sheehy, Gail. Observer.com/2004/o6/911-tapes-reveal-ground-personnel-muffled-attacks, 6/21/04

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
    ClickscoThis is a data management platform studying reader behavior (Privacy Policy)