77 and 93 on 911

Why would Osama bin Laden want to kill Dubya, his former business partner?
By James Hatfield

July 3, 2001

WASHINGTON, D.C. ? The airliner crashed between two and three hundred feet from my office in the Pentagon, just around a corner from where I work.

I'm the deputy General Counsel, Washington Headquarters Services, Office of the Secretary of Defense.

A slightly different calibration and I have no doubt I wouldn't be sending this to you. My colleagues felt the impact, which reminded them of an earthquake. People shouted in the corridor outside that a bomb had gone off upstairs on the main concourse in the building. No alarms sounded. I walked to my office, shut down my computer, and headed out.

Even before stepping outside I could smell the cordite.
Then I knew explosives had been set off somewhere."
McSweeney's

The second plane looked similar to a C- 130 transport plane, [Keith Wheelhouse] said. He believes it flew directly above the American Airlines jet, as if to prevent two planes from appearing on radar - while at the same time - guiding the jet toward the Pentagon.
Daily Press, September 14, 2001

Kelly Knowles, a First Colonial High School alumnus who now lives in an apartment a few miles from the Pentagon, said some sort of plane followed the doomed American Airlines jet toward the Pentagon, then veered away after the explosion.

At the same time, [Keith Wheelhouse] and his sister, Pam Young, who lives in Surry, were preparing to leave a funeral at Arlington National Cemetery, which is less than a mile from the Pentagon, when they watched the jet approach and slam into the Pentagon. Both of them, as well as at least one other person at the funeral, insist that there was another plane flying near the hijacked jet.
Daily Press, September 15, 2001

Off to the west, Sucherman saw another plane climb steeply and make a sharp turn. "I thought, 'Is this thing coming around to make a second attack? If there is another explosion, we're toast.'" - eWeek

As we watched the black plume gather strength, less than a minute after the explosion, we saw an odd sight that no one else has yet commented on. Directly in back of the plume, which would place it almost due west from our office, a four-engine propeller plane, which Ray later said resembled a C-130, started a steep decent towards the Pentagon. - Cloth Monkey

Within moments there was a very loud bang, which seemed to come from the direction of Henderson Hall. At least, all the heads turned towards Henderson. It is possible that this was a secondary explosion from the Pentagon or possibly an F-16 going supersonic.[...] The only large fixed wing aircraft to appear was a gray C-130, which appeared to be a Navy electronic warfare aircraft, he seemed to survey the area and depart in on a westerly heading. - Our Net Family

[Keith Wheelhouse] and at least two other witnesses to the Pentagon attack were troubled that Pentagon spokesmen had until now said they were unaware of a C-130 being in the area at the time. In the days immediately following the Sept. 11 hijackings, the Pentagon had no knowledge of the C-130's encounter, because........all reports were classified by the Air National Guard. [!]
Daily Press, October 17, 2001

Sunday, September 16, 2001

By Bill Heltzel and Tom Gibb, Post-Gazette Staff Writers

Two other airplanes were flying near the hijacked United Airlines jet when it crashed in Somerset County, but neither had anything to do with the airliner's fate, the FBI said yesterday.

In fact, one of the planes, a Fairchild Falcon 20 business jet, was directed to the crash site to help rescuers. The request for the jet to fly low and obtain the coordinates for the crash explains reports by people in the vicinity who said a white or silver jet flew by moments after the crash.

Lt. Col. Steve O'Brien started his day at the controls of a Minnesota National Guard C-130 cargo plane. He and his crew were heading back to the Twin Cities after moving military supplies around the Caribbean. About 9:30 a.m., O'Brien throttled the lumbering plane down a runway at Andrews Air Force Base, just southeast of the District of Columbia.

"When we took off, we headed north and west and had a beautiful view of the Mall," he said. "I noticed this airplane up and to the left of us, at 10 o'clock. He was descending to our altitude, four miles away or so. That's awful close, so I was surprised he wasn't calling out to us.

"It was like coming up to an intersection. When air traffic control asked me if we had him in sight, I told him that was an understatement - by then, he had pretty much filled our windscreen. Then he made a pretty aggressive turn so he was moving right in front of us, a mile and a half, two miles away. I said we had him in sight, then the controller asked me what kind of plane it was.

"That caught us up, because normally they have all that information. The controller didn't seem to know anything."

O'Brien reported that the plane was either a 757 or 767 and its silver fuselage meant it was probably an American Airlines jet. "They told us to turn and follow that aircraft - in 20-plus years of flying, I've never been asked to do something like that. With all of the East Coast haze, I had a hard time picking him out.

"The next thing I saw was the fireball. It was huge. I told Washington the airplane has impacted the ground. Shook everyone up pretty good. I told them the approximate location was close to the Potomac. I figured he'd had some in-flight emergency and was trying to get back on the ground to Washington National. Suddenly, I could see the outline of the Pentagon. It was horrible. I told Washington this thing has impacted the west side of the Pentagon."

O'Brien asked the controller whether he should set up a low orbit around the building but was told to get out of the area as quickly as possible. "I took the plane once through the plume of smoke and thought if this was a terrorist attack, it probably wasn't a good idea to be flying through that plume."

He flew west, not exactly sure where he was supposed to land. Somewhere over western Pennsylvania, O'Brien looked down at a blackened, smoldering field. "I hoped it was just a tire fire or something, but when I checked with Cleveland center, he told me he'd just lost a guy off the scope pretty close to where we saw it. By then, we were able to patch in AM radio, so we heard about all the planes. It was like a domino effect - a really bad day for airplanes."

Independent.co.uk
13 August 2002 15:34 BDST

Unanswered questions: The mystery of Flight 93

Some conspiracy theorists will say that the plane was shot down by a missile, perhaps a heat-seeking missile that honed in on one of the plane's engines - a theory possibly substantiated by the 2,000yd flight of the 1,000lb engine part, but arguably refuted by consistent eye-witness accounts, including Lee Purbaugh's, that when last sighted the plane was not emitting smoke.

Others might say, as they have done about a TWA flight that fell to the sea in 1996 after taking off from New York, that the plane was a victim of electromagnetic interference. In the case of the TWA flight, the argument, put forward in a series of exhaustive articles written in the New York Review of Books by the Harvard academic Elaine Scarry, is that it happened accidentally. However, as Scarry's articles relate, documentation abounds showing that the Air Force and the Pentagon have conducted extensive research on "electronic warfare applications" with the possible capacity intentionally to disrupt the mechanisms of an aeroplane in such a way as to provoke, for example, an uncontrollable dive. Scarry also reports that US Customs aircraft are already equipped with such weaponry; as are some C-130 Air Force transport planes. The FBI has stated that, apart from the enigmatic Falcon business jet, there was a C-130 military cargo plane within 25 miles of the passenger jet when it crashed. According to the Scarry findings, in 1995 the Air Force installed "electronic suites" in at least 28 of its C-130s - capable, among other things, of emitting lethal jamming signals.