.

.
Library of Professor Richard A. Macksey in Baltimore

POSTS BY SUBJECT

Labels

Monday, May 7, 2012

911 - Pentagon Witnesses


Killtown's
Did Flight 77 really crash into the Pentagon?


Eyewitness' testimony has been color coded as the following...
Supports conspiracy -  Describes something very different than an American Airlines Boeing 757 or other suspicious stuff. Supports official claim - Describes a large aircraft, a Boeing 757, or something very similar (i.e. 727, 747).
Aircraft hitting ground 
- Describes the aircraft hitting the ground which conflicts with the lawn photos.
Aircraft hitting light poles 
- Describes aircraft hitting light poles which is consistent with the light pole evidence..
Second Plane
 - Describes seeing a second plane in the area at the time of the crash other than the military jetfighters who arrived later.
Odd/Unique/Strange 
- Testimony that has not been corroborated or seems to contradict everybody.
Trajectory of aircraft
 - Describes the altitude and action of the aircraft as it flew in.
Description of interest 
- Describes something of a particular interest.
 
Witnesses...
Steve Andersonsaw a commercial jet barrel into the Pentagon. "To say it was like a dream is an understatement," he says. "It was unbelievable. This giant, incredible, orange ball of fire shot into the air."
(More) - A few moments later, as I was looking down at my desk, the plane caught my eye.  I thought to myself that I couldn't believe the 
pilot was flying so low.  I watched in horror as the plane flew at treetop level, banked slightly to the left, drug it's wing along the ground and slammed into the west wall of the Pentagon exploding into a giant orange fireball. Then black smoke. Then white smoke.
Maurice L. Bease,Sergeant, Marines- had worked around Marine aviation long enough to know what a fly-by was, and it sounded like one as he stood outside his office near the Pentagon on Sept. 11. Turning around expecting to see a fighter jet fly over, he saw only a split-second glimpse of a white commercial airliner streaking low toward the building, and him! He did not even have time to duck before it plowed into the side of the Pentagon around the corner and about 200 yards from where he stood.
Mickey BellSingleton Electric foreman- The jet came in from the south and banked left as it entered the building, narrowly missing the Singleton Electric trailer and the on-site foreman. Bell had just left the trailer when he heard a loud noise. The next thing he recalled was picking himself off the floor, where he had been thrown by the blast.  Bell, who had been less than 100 feet from the initial impact of the plane, was nearly struck by one of the plane's wings as it sped by him.
(More) - The full impact of the closeness of the crash wasn't realized until coworkers noticed damage to Bell's work vehicle. He had 
plastic and rivets from an airplane imbedded in its sheet metal, but Bell had no idea what had happened.
Richard BenedettoUSA TODAY reporter- saw the plane slam into the Pentagon. "It sounded like an artillery shell. It hit on the west side of the building, near the helipad."
Sean BogerAir Traffic Controller and Pentagon tower chief"I just looked up and I saw the big nose and the wings of the aircraft coming right at us and I just watched it hit the building."  "It exploded. I fell to the ground and covered my head. I could actually hear the metal going through the building." The crew, Boger and Spc. Jacqueline Kidd, air traffic controller and training supervisor, prepared for President George W. Bush to arrive from Florida around 12:30 p.m.
James R. Cissellformer photojournalist
(Note that this witnesses says his original witness report was skewed by the media.)

''Out of my peripheral vision,'' Cissell said, ''I saw this plane coming in and it was low - and getting lower.  ''I thought, 'This isn't really happening.That is a big plane.' Then I saw the faces of some of the passengers on board,'' Cissell said.  Then the plane, which was taking out telephone and power lines on its way in, hit the building.  While he remembers seeing the crash, Cissell remembers none of the sounds.  ''It came in in a perfectly straight line,'' he said.  ''It didn't slow down. I want to say it accelerated. It just shot straight in.'' - cincypost.com

 Proof That 'Flight 77' Eyewitness Report Skewed
"James R. Cissell, an eyewitness to the object that struck the Pentagon on September 2001, is furious with a Cincinnati newspaper for falsely attributing quotes to him that he never made.
The Cincinnati Post reported Cissell's comments in a September 12 story headlined, 'I saw the faces of some of the passengers.'
James R. Cissell contacted us to express his anger at the newspaper for taking his comments completely out of context.
The Cincinnati Post article, which you refer, angered me greatly after reading it. It is almost completely fiction based loosely on an interview I did with a Cincinnati Post reporter Kimball Perry who called me in response to an on air phone report that I did for Channel 12 in Cincinnati."
Cissell relates what he actually told the reporter.
"The reporter took extreme creative license not only with the title but also with the story as a whole. Why he felt the need to sensationalize anything that happened on September 11 is beyond me. My words to the reporter were, "I was about four cars back from where the plane crossed over the highway. That it happened so quickly I didn't even see what airline it was from. However, I was so close to the plane when it went past that had it been sitting on a runway, I could have seen the faces of passengers peering out." - prisonplanet.com (07/30/06)
Richard CoxArlington County Police Dept.
 - On September 11, 2001, at approximately 9:37 a.m., ACPD Corporal Barry Foust and Officer Richard Cox, on patrol in south Arlington County, saw a large American Airlines aircraft in steep descent on a collision course with the Pentagon.

The 'Other' Tragedy
"The hijacked jetliner, traveling at 350 miles an hour, was only about 100 feet from the ground when it cruised over Arlington police officer Richard Cox's head, just a quarter mile from the Pentagon. "It was low enough for me to see the reflection of cars and trees and buildings on its underside as it passed by," he says. "It was low enough for my heart to stop." - USNews (12/10/01)
Steve DeChiaroengineerAs he reached the west side of the building he saw a light post bent in half.
"But when I looked at the site, my brain could not resolve the fact that it was a plane because it only seemed like a small hole in the building," he said. "No tail. No wings. No nothing." - GoMemphis.com (08/01/02)
Michael DiPaula41, project coordinator Pentagon Renovation TeamHe left a meeting in the Pentagon just minutes before the crash, looking for an electrician who didn't show, in a construction trailer less than 75 feet away. "Suddenly, an airplane roared into view, nearly shearing the roof off the trailer before slamming into the E ring. 'It sounded like a missile,'  DiPaula recalls . . . Buried in debris and covered with airplane fuel, he was briefly listed by authorities as missing, but eventually crawled from the flaming debris and the shroud of black smoke unscathed.
Daryl Donley"It just was amazingly precise," Donley... said of the plane's impact. "It completely disappeared into the Pentagon."
Steve Eidentruck driverHe took the Highway 95 loop in the area of the Pentagon and thought it odd to see a plane in restricted airspace, thinking to himself it was odd that it wasflying so low.  "You could almost see the people in the windows," he said as he watched the plane disappear behind a line of trees, followed by a tall plume of black smoke.
Penny Elgas
The plane was directly over the cars in front of my car, the plane seemed to be not more than 80 feet off the ground and about 4-5 car lengths in front of me. It was far enough in front of me that I saw the end of the wing closest to me and the underside of the other wing as that other wing rocked slightly toward the ground. I remember recognizing it as an American Airlines plane -- I could see the windows and the color stripes.
In my adrenaline-filled state of mind, I was overcome by my visual senses. The day had started out beautiful and sunny and I had driven to work with my car's sunroof open. I believe that I may have also had one or more car windows open because the traffic wasn't moving anyway. At the second that I saw the plane, my visual senses took over completely and I did not hear or feel anything -- not the roar of the plane, or wind force, or impact sounds.
The plane seemed to be floating as if it were a paper glider and I watched in horror as it gently rocked and slowly glided straight into the PentagonAt the point where the fuselage hit the wall, it seemed to simply melt into the building. I saw a smoke ring surround the fuselage as it made contact with the wall. It appeared as a smoke ring that encircled the fuselage at the point of contact and it seemed to be several feet thick. I later realized that it was probably the rubble of churning bits of the plane and concrete. The churning smoke ring started at the top of the fuselage and simultaneously wrapped down both the right and left sides of the fuselage to the underside, where the coiling rings crossed over each other and then coiled back up to the top. Then it started over again -- only this next time, I also saw fire, glowing fire in the smoke ring. At that point, the wings disappeared into the Pentagon. And then I saw an explosion and watched the tail of the plane slip into the building.
Barry FoustCorporal, Arlington County Police Dept.On September 11, 2001, at approximately 9:37 a.m., ACPD Corporal Barry Foust and Officer Richard Cox, on patrol in south Arlington County, saw a large American Airlines aircraft in steep descent on a collision course with the Pentagon.
Fred Gaskinsnational editor at USA TODAY"(The plane) was flying fast and low and the Pentagon was the obvious target," who was driving to his job... near the Pentagon when the plane passed about 150 feet overhead. "It was flying very smoothly and calmly, without any hint that anything was wrong."
Gilah Goldsmithpersonnel attorney at the Pentagon- "We saw a huge black cloud of smoke," she said, saying it smelled like cordite, or gun smoke.(cordite - A smokeless explosive powder consisting of nitrocellulose, nitroglycerin, and petrolatum that has been dissolved in acetone, dried, and extruded in cords.)
Afework Hagoscomputer programmer- was on his way to work but stuck in a traffic jam near the Pentagon when the plane flew over. "There was a huge screaming noise and I got out of the car as the plane came over. It was tilting its wings up and down like it was trying to balanceIt hit some lampposts on the way in.""Afework Hagos, a consultant who was commuting to his job, saw the plane bank around and fly into the Pentagon, its wings see-sawing before it disappeared. ''It created a huge smoke,'' Hagos said, before a man in an FBI windbreaker whisked him off to get his eyewitness account." - Boston Globe (09/12/01)
Terrance Kean35 - who lives in a 14-story building nearby, heard the loud jet engines and glanced out his window.  "I saw this very, very large passenger jet," said the architect, who had been packing for a move. "It just plowed right into the side of the Pentagon. The nose penetrated into the portico. And then it sort of disappeared, and there was fire and smoke everywhere. . . . It was very sort of surreal."
D. S. Khavkin - my husband and I heard an aircraft directly overhead. At first, we thought it was the jets that sometimes fly overhead. However, it appeared to be a small commercial aircraft. The engine was at full throttle.  First, the plane knocked down a number of street lamp poles, then headed directly for the Pentagon and crashed on the lawn near the west side the Pentagon.
Kelly Knowles22- Another Hampton Roads native says she saw a second plane in the air over the Pentagon as a hijacked jet plunged into the five-sided military fortress Tuesday.
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.
"Thank God somebody else saw that. There was most definitely a second plane," Knowles said. "It's so frustrating because nobody knows aboutthe second plane, or if they do they're hiding it for some reason."
FBI spokesmen say they have not heard about it, although both Knowles and Keith Wheelhouse, the Virginia Beach man, were interviewed by FBI agents. A Pentagon official said late Friday no other plane was flying with the jetliner. But he said it was possible a military plane was in the area at the time of the attack.
Planes never pass over her Fairfax County apartment, she said, so when a low-flying, high-speed plane buzzed the high-rise, she jumped up, ran to the windows and saw the rear of a jet heading toward Washington, D.C. A few seconds later, a second plane that seemed to be chasing the first passed over at a slightly different angle, she said. - Daily Press/Newport News (09/15/01) [Reprinted at:  cooperativeresearch.org]
Allan LindsleyArmy Captain, Physicians Assistant for Emergency Medical Services at Dewitt Army Community Hospital, Ft. Belvoir, VA."At the time we could walk right up to the building. I walked right down, I was within 100 meters of the building, right in front of the crash site.
I didn’t see any of the plane. By then, the floors had collapsed.
Two FBI agents looking for airplane parts closer to the building walked into a yellow jacket nest and got stung several times.
I walked by that and looked up on the outer ring and you could see right at the crash site, and you could see filing cabinets and a computer monitor sitting there. They weren’t blackened, they didn’t look like they’d been moved, it looked like somebody had just driven by and broke a hole and nothing was touched. That was on the outer ring.
A lot of water, you could tell there were broken pipes and stuff, you could see that. You could see where the fire had extended almost a complete length to the left of the crash site and to the right, it only went maybe five windows over. I was told that that was because of the new construction that they were doing and fire walls had been put in. You could tell that to the right the structural integrity was much better. To the left is where they were really having to do a lot of shoring up of the building. To the right there was more steel, and to the left there wasn’t as much steel in it. So they’ve been replacing that." -Soldiers to the Rescue/Responding in the Pentagon [HTML]
Lincoln LiebnerArmy Captain
"An eye-witness says an American Airlines passenger jet flew low straight into the Pentagon and crashed into the first floor of the building.
I saw this large American Airlines passenger jet coming in fast and low," said Army Captain Lincoln Liebner.
"My first thought was I've never seen one that high. Before it hit I realised what was happening," he said.
Captain Liebner says the aircraft struck a helicopter on the helipad, setting fire to a fire truck.
"We got one guy out of the [fire truck] cab," he said, adding he could hear people crying inside the wreckage.
Captain Liebner, who had cuts on his hands from the debris, says he has been parking his car in the car park when the crash occurred." - Australian Broadcasting Corp (09/12/01) [Reprinted with Wayback Machine]
(More)
From his vantage point, Maj. Leibner looked up and saw the plane come in. "I was about 100 yards away," he said. "
You could see through the windows of the aircraft. I saw it hit."
Excerpts from an interview with Major Lincoln Leibner, who worked in Cables Office of the Office of the Secretary of Defense in the Pentagon.
"I was just about to make my turn up the sidewalk towards one of the entrances when I heard jet engines. It was not the normal jet track into National Airport, which is very, very different. I turned my head about maybe 90 degrees towards the sound of the engines, which were very loud. I fully expected to see A-10s or F-15s or something, and I saw the American Airlines airplane coming down. I watched the entire terminal descent into the building. It’s probably the loudest noise I ever heard in my life. I have heard artillery very close. I have heard rock concerts, but nothing came close to that noise. I watched the entire airplane go into the building. I was personally shook by whatever percussion, and not hit, and the fireball from my angle wasn’t as dramatic as I have subsequently seen on the file tape.
I got to the building. Remarkably, there was no debris from the airplane. In the immediate area around the Pentagon, the grass was all scorched and blackened. Windows were obviously knocked out and you could hear a fire inside the building but the fires weren’t that prevalent at that point. It was just smoke, and it wasn’t even all that bad.
One man in the ambulance with me had no idea what happened, kept asking whether it was a bomb.
I told them what I had seen and what I gather is that I was the first personal account that he had. Even at this point, I don’t believe the Secretary was confident that, in fact, a civilian airliner had hit the building. I think they still speculated about a bomb, a cruise missile, a small aircraft, but I was glad I was able to give useful information. I told them the plane came in full throttle, level, flaps up, wheels up, wasn’t crashed into the building, was flown into the building.
The Secretary was essentially incredulous, but, then again, maybe that was just his manner. He asked me if I was sure. And as I said, I was close enough to look into the windows of the airplane as it flew passed. There was no doubt in my mind what I had seen." - Soldiers to the Rescue/Responding in the Pentagon [HTML]
David Marra23, information-technology specialist"It was 50 ft. off the deck when he came in. It sounded like the pilot had the throttle completely floored. The plane rolled left and then rolled right. Then he caught an edge of his wing on the ground." There is a helicopter pad right in front of the side of the Pentagon. The wing touched there, then the plane cartwheeled into the building.
Father Stephen McGraw - "I did not hear anything at all until the plane was just right above our cars." McGraw estimates that the plane passed about 20 feet over his car, as he waited in the left hand lane of the road, on the side closest to the Pentagon.  "The plane clipped the top of a light pole just before it got to us, injuring a taxi driver, whose taxi was just a few feet away from my car. "I saw it crash into the building," he said. "My only memories really were that it looked like a plane coming in for a landing. I mean in the sense that it was controlled and sort of straight. That was my impression," he said.
William Middleton Sr.was running his street sweeper through the cemetery when he heard a harsh whistling sound overhead. Middleton looked up and spotted a commercial jet whose pilot seemed to be fighting with his own craft.  Middleton said the plane was no higher than the tops of telephone poles as it lurched toward the Pentagon. The jet accelerated in the final few hundred yards before it tore into the building.
Terry MorinThe aircraft was essentially right over the top of me and the outer portion of the FOB.  I estimate that the aircraft was no more than 100 feet above me in a slight nose down attitude.  The plane had a silver body with red and blue stripes down the fuselage. I believed at the time that it belonged to American Airlines, but I couldn’t be sure. It looked like a 737 and I so reported to authorities.  Within seconds the plane cleared the 8th Wing of BMDO and was heading directly towards the Pentagon.  Engines were at a steady high-pitched whine, indicating to me that the throttles were steady and full.  The flight path appeared to be deliberate, smooth, and controlled.  I could now only see the tail of the aircraft.  I then confirmed that the aircraft had been flown directly into the Pentagon without hitting the ground first or skipping into the building.
Christopher MunseyNavy Times reporter"I couldn’t believe what I was now seeing to my right: A silver, twin-engine American Airlines jetliner gliding almost noiselessly over the Navy Annex, fast, low and straight toward the Pentagon, just hundreds of yards away.
The plane, with 
red and blue markings, hurtled by and within moments exploded in a ground-shaking “whoomp,” as it appeared to hit the side of the Pentagon."
Eileen MurphyHead Nurse of the Minor Surgery Clinic at the DiLorenzo TRICARE Health Clinic"I knew it was a crash site before we got there, and I didn’t know what it was going to look like. I couldn’t imagine because the building is like rock solid. I expected to see the airplane, so I guess my initial impression was, “Where’s the plane? How come there’s not a plane?” I would have thought the building would have stopped it and somehow we would have seen something like part of, or half of the plane, or the lower part, or the back of the plane. Soit was just a real surprise that the plane wasn’t there." - Soldiers to the Rescue/Responding in the Pentagon [HTML]
Vin Narayananreporter USA Today"The plane exploded after it hit, the tail came off and it began burning immediately... driving near the Pentagon when the plane hit.
(More) -
Then I looked up to my left and saw an American Airlines jet flying right at me. The jet roared over my head, clearing my car by about 25 feet. 
The tail of the plane clipped the overhanging exit sign above me as it headed straight at the Pentagon.  The windows were dark on American Airlines Flight 77 as it streaked toward its target, only 50 yards away.  But the Pentagon's wall held up like a champ. It barely budged as the nose of the plane curled upwards and crumpled before exploding into a massive fireball.
The people who built that wall should be proud. Its ability to withstand the initial impact of the jet probably saved thousands of lives.
I hopped out of my car after the jet exploded, 
nearly oblivious to a second jet hovering in the skies.
Steve O'BrienLt. Col., pilot of the Minnesota National Guard C-130 cargo plane seen flying around the PentagonLt. 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 PennsylvaniaO'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.
He finally landed at the Youngstown, Ohio, airport." - Highbeam.com/Star Tribune (09/11/02) [Reprinted at:  cooperativeresearch.org]

A Minnesota guard crew witnessed hijackers crashing American Airlines Flight 77 into the Pentagon on September 11, 2001, and were also the first to report the smoke of United Airlines Flight 93 minutes after it went down in Pennsylvania.
Lt. Col. Steve O'Brien was at the controls of the C-130 aircraft on that day. His crew had just departed Andrews AFB on what he thought would be a normal flight home to Minnesota. But what he and his crew witnessed defies odds and will forever be woven into the fabric of the history of the infamous day.
"You just wonder how you could be in those two geographic locations at those exact times and witness those events," O'Brien told 5 EYEWITNESS NEWS.
On September 11, 2001, O'Brien's plane had just taken off when air traffic controllers asked him to identify and follow Flight 77, which was suspected of being a hijacked plane. O'Brien saw that plane pass directly in front of his Minnesota National Guard C-130 aircraft.
"We told them we did have it in sight, and they asked us to follow the suspect aircraft." O'Brien remembered. "In 20 years of flying I'd never been asked to do that, especially following a commercial jetliner."
A few minutes later, O'Brien saw the first horrific sight of his day: American Airlines Flight 77 had hit the Pentagon.
"We were having a hard time keeping up with that aircraft, but we saw the explosion on the ground."
After that, O'Brien and his crew headed west toward home. But over Pennsylvania, air traffic controllers asked him and his crew if they saw another aircraft in trouble.
The crew of the C-130 saw the smoke from United Airlines Flight 93, which had crashed just 2 minutes earlier.
"You feel like you are a part of history," O'Brien said. "Even if you were not directly involved, you had a chance to witness it." - 5 Eyewitness News(12/25/04)
John O’Keefe“I don’t know whether I saw or heard it first -- this silver plane; I immediately recognized it as an American Airlines jet,” said the 25-year-old O’Keefe, managing editor of Influence, an American Lawyer Media publication about lobbying. “It came swooping in over the highway, over my left shoulder, straight across where my car was heading.
“The eeriest thing about it, was that it was like you were watching a movie. 
There was no huge explosion, no huge rumbling on ground, it just went ‘pfff.’ It wasn’t what I would have expected for a plane that was not much more than a football field away from me.
“The first thing I did was pull over onto the shoulder, and when I got out of the car 
I saw another plane flying over my head, and it scared ...me, because I knew there had been two planes that hit the World Trade Center. And I started jogging up the ramp to get as far away as possible.
“Then the plane -- 
it looked like a C-130 cargo plane -- started turning away from the Pentagon, it did a complete turnaround.
Mary Ann OwensGannett News Service employee"Instantly I knew what was happening, and I involuntarily ducked as the plane passed perhaps 50 to 75 feet above the roof of my car at great speed," Owens said. "The plane slammed into the west wall of the Pentagon. The impact was deafening. The fuselage hit the ground and blew up."
(More) - Gripping the steering wheel of my vibrating car, I involuntarily ducked as the wobbling plane thundered over my head. Once it passed, I raised slightly and grimaced as 
the left wing dipped and scraped the helicopter area just before the nose crashed into the southwest wall of the Pentagon.
Steve Patterson43, graphics artistsaw a silver commuter jet fly past the window of his 14th-floor apartment in Pentagon City. The plane was about 150 yards away, approaching from the west about 20 feet off the ground.
He said the plane, which 
sounded like the high-pitched squeal of a fighter jet, flew over Arlington cemetary so low that he thought it was going to land on I-395. He said it was flying so fast that he couldn't read any writing on the side.
The plane, 
which appeared to hold about eight to 12 people, headed straight for the Pentagon...He said the plane, which approached the Pentagon below treetop level, seemed to be flying normally for a plane coming in for a landing other than going very fast for being so low. Then, he said, he saw the Pentagon "envelope" the plane and bright orange flames shoot out the back of the building.
"It looked like a normal landing, as if someone knew exactly what they were doing," said Patterson, a graphics artist who works at home. "This looked intentional."
Christine Peterson I was at a complete stop on the road in front of the helipad at the Pentagon; what I had thought would be a shortcut was as slow as the other routes I had taken that morning.  I looked idly out my window to the left -- and saw a plane flying so low I said, “holy cow, that plane is going to hit my car” (not my actual words).  The car shook as the plane flew over.  It was so close that I could read the numbers under the wing.  And then the plane crashed.  My mind could not comprehend what had happened.  Where did the plane go?  For some reason I expected it to bounce off the Pentagon wall in pieces.  But there was no plane visible, only huge billows of smoke and torrents of fire.
Maybon PollockSergeant First Class, NCOIC Logistics in the DiLorenzo TRICARE Health Clinic."At that point we were able to see the last part of the plane, where it stopped, basically. It was a big 8 by 10 or bigger, I’m just guessing, hole in the wall.You could see the tire, the landing gear, were just forward of it.
I was more impressed, I was truly impressed, with how the building stood up, after they told me the
size of the plane. And then I was in awe that I saw no plane, nothing left from the plane. It was like
it disintegrated as it went into the building
." - Soldiers to the Rescue/Responding in the Pentagon [HTML]
Lon RainsEditor at Space NewsWith the Pentagon to the left of my van at about 10 o’clock on the dial of a clock, I glanced at my watch to see if I was going to be late for my appointment.
At that moment I heard a very loud, quick whooshing sound that began behind me and stopped suddenly in front of me and to my left. In fractions of a second I heard the impact and an explosion. The next thing I saw was the fireball.
I was convinced it was a missileIt came in so fast it sounded nothing like an airplane. Friends and colleagues have asked me if I felt a shock wave and I honestly do not know.
Rick Renzia law student''The plane came in at an incredibly steep angle with incredibly high speed,''... was driving by the Pentagon at the time of the crash about 9:40 a.m.  The impact created a huge yellow and orange fireball, he added. Renzi, who was interviewed at the scene by FBI agents, said he stopped his car to watch and saw another plane following and turn off after the first craft's impact.
Steve Riskus, 24"I took these pictures less then 1 minutes after I watched the american airlines 757 airplane crash into the pentagon on september 11 2001. I left shortly after the picture were taken in fear of further attacks.
Feel free to contact me anytime if you have questions about my pictures.
Yes, I did actually see the plane impact the building.
Steve Riskus
steveriskus[at]aol[dot]com
AIM: youthenraged" - criticalthrash.com
(Note that this is Steve's personal account posted on his own website which he created on Sept. 10, 2001!)
James S. Robbinsa national-security analyst & NRO contributorI was looking directly at it when the aircraft struck. The sight of the 757 diving in at an unrecoverable angle is frozen in my memory, but at the time, I did not immediately comprehend what I was witnessingThere was a silvery flash, an explosion, and a dark, mushroom shaped cloud rose over the building.
Tom Seibert, 33,  a network engineer at the Pentagon"We heard what sounded like a missile, then we heard a loud boom,"  "We were sitting there and watching this thing from New York, and I said, you know, the next best target would be us. And five minutes later, boom."
Noel SepulvedaMaster Sgt., Air ForceHe saw the plane fly above a nearby hotel and drop its landing gearThe plane’s right wheel struck a light polecausing it to fly at a 45-degree angle, he said. The plane tried to recover, but hit a second light pole and continued flying at an angle. "You could hear the engines being revved up even higher," Sepulveda said.  The plane dipped its nose and crashed into the southwest side of the Pentagon.  "The right engine hit high, the left engine hit low," Sepulveda said. "For a brief moment, you could see the body of the plane sticking out from the side of the building. Then a ball of fire came from behind it." - dcmilitary.com (04/19/02)
Levi Stephens23, courier Armed Forces Information ServiceAccording to one witness, "what looked like a 747" plowed into the south side of the Pentagon, possibly skipping through a heliport before it hit the building.  Personnel working in the Navy Annex, over which the airliner flew, said they heard the distinct whine of jet engines as the airliner approached.  "I was driving away from the Pentagon in the South Pentagon lot when I hear this huge rumble, the ground started shaking … I saw this [plane] come flying over the Navy Annex. It flew over the van and I looked back and I saw this huge explosion, black smoke everywhere."
Joel SuchermanUSA Today Editor"My first thought was he's not going to make it across the river to [Reagan] National Airport. But whoever was flying the plane made no attempt to change direction," Sucherman said. "It was coming in at a high rate of speed, but not at a steep angle--almost like a heat-seeking missile was locked onto its target and staying dead on course."
"
I didn't feel anything coming out of the Pentagon [in terms of debris]," he said. "A couple of minutes later, police cars and fire trucks headed to the scene." Ironically, the passage of emergency vehicles got traffic moving again, which was now crunching over twisted metal Sucherman guessed was the skin of the plane.
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.'"
(Video) - "
I did not see the engines, I saw the body and the tail; and it was a silver jet with the markings along the windows that spoke to me as an American Airlines jet, this was not a commercial, excuse me, a business jet, it was not a lear jet, it was a bigger plane than that."
Tim TimmermanA pilot who saw the impact... said it had been an American Airways 757. "It added power on its way in," he said. "The nose hit, and the wings came forward and it went up in a fireball."
(More) - And then it came out, and I saw it hit right in front of -- 
it didn't appear to crash into the building; most of the energy was dissipated inhitting the ground, but I saw the nose break up, I saw the wings fly forward, and then the conflagration engulfed everything in flames. It was horrible. It was a Boeing 757, American Airlines, no question.
Jose Velasquez, NEXCOM Citgo station supervisor"I knew something was wrong. The planes come more from the north and west [to land at Reagan National Airport] not from the south. And not so low." His gas station, open only to Department of Defense personnel... Velasquez says the gas station's security cameras are close enough to the Pentagon to have recorded the moment of impact. "I've never seen what the pictures looked like," he said. "The FBI was here within minutes and took the film."
Alan WallacePentagon Firefighter - was standing outside his fire station when he looked across the nearby interstate and saw a white airplane with orange and blue trim heading almost straight at him. It slammed into the building just a couple hundred feet from him. "When I felt the fire, I hit the ground," he said.
(More) - 
President Bush was scheduled to fly from Florida that afternoon, and his helicopter, Marine One, would carry him to the Pentagon. That meant Secret Service everywhere and their cars blocking the driveway.
So the meticulous 
Wallace moved the fire truck out of the way, parking it about 15 feet from the Pentagon.
Wallace looked up and saw the gleam of a 
silver jetliner. But it was flying too low. Maybe less than 25 feet off the ground.
"I yelled to Mark, 'Let's go!'" He bolted to the right and a second later felt the searing heat of the blast behind him. 
He hit the ground and rolled under a parked van as a fireball engulfed his fire truck, then blew through the nearby firehouse.
So Wallace switched on the truck's radio. "
Foam 61 to Fort Myer," he said. "We have had a commercial carrier crash into the west side of the Pentagon at the heliport, Washington Boulevard side. The crew is OK. The airplane was a 757 Boeing or a 320 Airbus."
Mike Walters"I looked off, I was, you know I looked out my window. I saw this plane, a jetAmerican Airlines jet coming, and I thought this doesn't add up. It's really low. I mean, it was like a cruise missile with wings, went right there and slammed right into the Pentagon, a huge explosion, a great ball of fire. Smoke started billowing out and then it was just chaos on the highway as people either tried to move around the traffic and go down either forward or backwards." - CNN (03/07/02)
 Keith Wheelhouse
"Her brother, Wheelhouse, of Virginia Beach, spotted the planes first. The second plane looked similar to a C- 130 transport plane, he 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.
As the hijacked jet started its descent, "it's like it stepped on its gas pedal," Wheelhouse said. "As soon as he did that, the second plane banked off to the west."
Wheelhouse's account of a second plane is unlike everything else that has been reported about the attack. Some initial reports on television said a second airliner might be headed for the Pentagon, but authorities later dismissed that. A Norfolk-based FBI agent interviewed Wheelhouse Wednesday evening.
A possible explanation for the second plane could be a plane landing at nearby Ronald Reagan National Airport. The Pentagon is between the cemetery and the airport. But Wheelhouse insists he was not confused by other air traffic.
After the attack on the Pentagon, reporters in Washington saw Air Force planes patrolling the skies over the capital.
Wheelhouse said it's possible the second plane was a military plane, but the military has not said it had a plane shadowing the hijacked jet." - Daily Press/Newport News (09/14/01) [Reprinted at:  cooperativeresearch.org]

"FBI spokesmen say they have not heard about it, although both Knowles and Keith Wheelhouse, the Virginia Beach man, were interviewed by FBI agents. A Pentagon official said late Friday no other plane was flying with the jetliner. But he said it was possible a military plane was in the area at the time of the attack.
At the same time, 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.
Wheelhouse said the second plane looked like it may have been a C- 130 transport plane, but the other three witnesses say they're not sure what the plane looked like." - Daily Press/Newport News (09/15/01) [Reprinted at:  cooperativeresearch.org]
Dave WinslowAP reporter"I saw the tail of a large airliner ... It ploughed right into the Pentagon."
Pam Young - Perhaps more remarkable is her insistence that a second plane was flying near and along the same path as the hijacked jet. - Daily Press/Newport News (09/14/01) [Reprinted at:  cooperativeresearch.org]
At the same time, 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/Newport News (09/15/01) [Reprinted at: cooperativeresearch.org]
 Unidentified Witnesses...
Air Force senior enlistee(Chris Plant, CNN correspondent)PLANT: Well, and speaking to people here at the Pentagon, as they're being evacuated from the building. I'm told by several people that there was, in fact, an explosion.

I was told by one witness, an Air Force enlisted - senior enlisted man, that he was outside when it occurred. He said that he saw a helicopter circle the building. He said it appeared to be a U.S. military helicopter, and that it disappeared behind the building where the helicopter landing zone is - excuse me - and he then saw fireball go into the sky.

It's a very tense situation obviously, but initial reports from witnesses indicate that there was in fact a helicopter circling the building, contrary to what the AP reported, according to the witnesses I've spoken to anyway, and that this helicopter disappeared behind the building, and that there was then an explosion. That's about all I have from here. - CNN (09/11/01)
Arlington worker - Another Arlington worker who declined to be interviewed in front of the media told a story that the military historians had not heard in the 244 interviews they had conducted through last week. The man said a mysterious second plane was circling the area when the first one attacked the Pentagon. -South Coast Today/Pittsburgh Post-Gazette (12/20/01)


Sunday, May 6, 2012

911 - Critique of David Ray Griffin regarding Calls from 9-11 Planes


Critique of David Ray Griffin regarding Calls from 9-11 Planes

by Paul Zarembka, Professor of Economics, SUNY at Buffalo
October 14th 2011
ITHP.org
David Ray Griffin's response to this article is posted below.
-- "The present essay provides various types of evidence that the calls [from 9/11 planes] were, indeed, faked." (Griffin, 2011, p. 101)
Watching and participating for almost ten years in the movement to expose the truth about what happened on September 11, 2001, I have come to feel that some are trying too hard to prove that the government is lying. A population can be manipulated not only by lies but also by sprinklings of truths, half truths, and distortions. Indeed, offering some truths is an effective means of undermining critics who argue for lies everywhere. 

A self-confident movement does not need to be exposing just lies and only lies. It can examine evidence and draw disparate conclusions about differing accuracies of the huge amount of material to work with. I have felt that the work of David Ray Griffin, a leading commentator on September 11, is an example of turning up stones everywhere with the word "lie" written on them. He seems called upon to write about everything having to do with September 11 in order to turn over stones everywhere. Why?

I hadn't thought to put this worry to paper until I carefully read Griffin's Chapter 5 "Phone Calls from the 9/11 Planes: How They Fooled America" that appears in his just published 9/11 Ten Years Later (2011, Northampton, MA: Olive Branch).


CeeCee Lyles' Call
To set the stage, I offer an initial example that a critique of Griffin's chapter is necessary. This is for what he considers "the most direct evidence of fakery" in the phone calls. Griffin offers the tape recording of the phone call from UA 93 flight attendant CeeCee Lyles to her husband Lorne Lyles at 9:47 a.m. on September 11, 2001. He reproduces the text of what CeeCee says on Lorne's answering machine. After CeeCee completes her message, a female voice is heard in the background, "You did great" (www.youtube.com/watch?v=fUrxsrTKHN4). Griffin then asks, "How could anyone not take this whispered comment as clear evidence that the 'CeeCee Lyles' message was a fake?"He goes on to write a paragraph by way of explanation:
    To call it a "fake" means that the message was not what it purports to be. It could have been a fake produced by voice morphing. Or it could have been CeeCee Lyles reading a script she was forced to read -- in which case, the whispered message might have been by a person coaching her. But in either case, the message was not authentic.
Noting also that the government itself provided this tape at the 2006 Moussaoui trial, Griffin concludes that "this whispered comment undermines the official story about 9/11" (for this material, see pp. 115-16).

There is an alternative simple explanation that Griffin fails to even mention: Flight assistant CeeCee Lyles was sitting next to another woman and CeeCee had discussed with her an intention to call her husband. The other woman simply supported CeeCee in how she handled herself with that phone message.

This possible explanation is ignored altogether by Griffin. It cannot be ignored and thus rendered so improbable as not worth being put to paper. (I asked five persons -- none of whom support the official story about September 11th -- to interpret who likely said, "You did great". Four said that this woman would likely be on the plane. One of them added that if that woman were a government agent, the government would have cut off that "You did great" in the recording when presented as evidence at the Moussaoui trial. Two offered that a quick claim of a fake would be "ridiculous".) 
-----------------------------------------

A Response to Paul Zarembka about Phone Calls from the 9/11 Planes

by David Ray Griffin
October 22, 2011
ITHP.org

Professor Paul Zarembka has written a critique of a chapter of my recent book, 9/11 Ten Years Later: When State Crimes against Democracy Succeed.1 The chapter in question is entitled "Phone Calls from the 9/11 Planes: How They Fooled America." I thank Dr. Zarembka for taking my chapter seriously enough to write his critique.2 However, I submit that my chapter not to be guilty of the charges he levels.
At the beginning of his critique, Zarembka states that I seem intent on "exposing just lies and only lies" -- on "turning up stones everywhere with the word 'lie' written on them." A computer search shows that my chapter contains no instances in which I used the term "lie," "lies," or "lying." I certainly did, to be sure, suggest that various aspects of the official story are false. This would be grounds for reproach if these suggestions were based on errors, and Zarembka suggests that they often are. Indeed, to adopt his formulation, he seemed to be intent on turning up stones everywhere with the word "error" written on them. But the charge that my chapter is filled with errors cannot be maintained.
At the conclusion of Zarembka's critique, he said that he found "weakness" in my chapter's "internal logic." This charge by Zarembka, however, reflects the fact that he simply failed to understand the logic of some of my arguments, or certain facts relevant to those arguments.

Sliding Over Deena Burnett's Testimony
My chapter, as I said in a statement quoted at the head of Zarembka's essay, "provides various types of evidence that the calls [from 9/11 planes] were . . . faked." I clearly presented the testimony of Deena Burnett as providing the most important example of this evidence for fakery: The first section of my chapter was devoted to her testimony, and I devoted far more space to it than to anything else. And yet Zarembka began his critique by discussing a recorded message by flight attendant CeeCee Lyles, which I had discussed later and to which I devoted less then a page. I did refer to the Lyles message as providing the "most direct evidence of fakery," but I did not thereby mean that she provided the strongest evidence.3 That distinction, I indicated, belonged to the calls received by Deena Burnett. And yet Zarembka provided an extremely brief treatment of the Burnett calls.
As to why I presented the Burnett calls as the strongest evidence for fakery: Deena told the FBI on the day of the attacks that she had received "three to five cellular phone calls" from her husband, Tom Burnett, calling from United 93.4 "Only one of the calls," the FBI report added, "did not show on the caller identification as she was on the line with another call."5 The FBI later indicated that she had received (only) three calls. If we accept that as a correct statement of fact, then Deena's testimony would have been that her Caller ID showed two of the calls she received from her husband to have been from his cell phone.
And yet, it is now generally agreed, her husband could not have made cell phone calls from United 93, which was at the time over 40,000 feet in the air. And when in 2006, the FBI's report on phone calls from the 9/11 planes became public in relation to the Moussaoui trial, this report said of Tom Burnett that his calls were made from seat-back phones. The FBI's report thereby avoided the problem of endorsing technologically impossible phone calls.
But the FBI's report thereby created another problem: How to explain why Deena Burnett reported that her phone's Caller ID indicated that some of the calls from her husband were made on his cell phone. One possible answer would be that she had misremembered. But she made her statement to the FBI on 9/11 itself, only hours after the event. Another possible answer would be that she lied. But there appears to be no conceivable reason why she would have done this. It seems inescapable, therefore, that her Caller ID did indicate that the messages were from Tom Burnett's cell phone. But how is that possible? If, as the FBI now says, Tom used a seat-back phone to call Deena, how could his cell phone number have appeared on Deena's Caller ID?
This question must be answered by anyone who wants to think of the phone calls from the 9/11 planes as authentic. But no one has provided an answer. Zarembka, while seeming to deny that the Burnett calls provide evidence for fakery, fails to address this issue.
Zarembka's very brief treatment of these calls seems to be devoted to the suggestion that Deena Burnett's testimony was unreliable. He first states that "she said he [Tom] called four times," whereas the government stated that "there were only three calls." Was Zarembka thereby suggesting that, if Deena was mistaken about the number of calls, she might have also been confused about other matters? If so, Zarembka's argument is groundless: He evidently missed the fact, quoted in my chapter, that Deena on 9/11 told the FBI that she had received "three to five cellular phone calls" from Tom.6 So even if one accepts the accuracy of the government's statement that she had received (only) three calls from Tom, her statement cannot be faulted as inaccurate.
In any case, Zarembka then states what seems to be his main reason for doubting Deena's statement: "Deena's statement that Tom called from his cell phone has been revealed to be unsupported by phone company records. 'The call Burnett made from the cell phone [says a 9/11 Commission memorandum] did not show up on the cell phone bill. . . .'7 [T]he government claims a record for Tom using an air phone, showing a 'CS' credit card being used and approved three times."8
Having provided this information, Zarembka states: "Griffin does not cite this important report." As Zarembka's statements indicate, he seems to believe that the government's records settle what did and did not happen.
I, by contrast, believe Deena Burnett's testimony that she saw Tom's cell phone number on her Caller ID. I do not believe, of course, that Tom had used his cell phone to call her from United 93: My chapter was based partly on evidence that cell phones in 2001 could not be used to make calls from airplanes flying at high altitudes. So of course Deena's belief that Tom used his cell phone to call her would not be supported by the phone company records. Indeed, Deena herself, as I mentioned in my chapter, wondered how Tom could have called her from the air. But I can see, as I have said, no way of denying that Tom's cell phone number appeared on her Caller ID.
Whereas Zarembka evidently takes government records as indisputable, the government sometimes provides fabricated records. I have elsewhere shown, for example, that the government provided false records that were used to "prove" that on September 10, 2001, Mohamed Atta and another al-Qaeda operative, Abdul al Omari, drove a rented Nissan Altima to Portland (Maine), stayed overnight in a motel, and then took an early flight the next morning back to Boston to catch American 11. Although they made the transfer, the official story says, their luggage did not, and after American 11 crashed into the World Trade Center, the authorities found treasure trove of information in this luggage that proved al-Qaeda's responsibility for the attacks.
As to why I consider these documents false: According to press stories of September 12, 2001, two al-Qaeda operatives named Adnan and Ameer Bukhari had driven the rented Nissan Altima to Portland, stayed overnight, and then took the early morning flight back to Boston in time to catch American 11. As for Mohamed Atta, he had remained in Boston. The treasure trove of material proving al-Qaeda's responsibility was found in a rented Mitsubishi, which Atta had left in the parking lot of Boston's Logan Airport.
But on September 13, it was discovered that neither of the Bukharis had died on 9/11: Adnan was still alive, and Ameer had died the previous year. The next day, the press stories started changing, and by September 16, what is now the official story had been fully developed. By October 5, moreover, the FBI had provided witnesses and videos purportedly proving that Atta and al-Omari had been in Portland on September 10.9 The FBI even had an affidavit, signed by a judge on September 12, stating that "American Airlines personnel at Logan discovered two bags [checked to passenger Atta] that had been bound for transfer to AA11 but had not been loaded onto the flight."10
So, although the FBI originally had physical evidence showing that the Bukharis had taken the Nissan to Portland and that Atta had left a rented Mitsubishi at the Boston airport, the FBI was able to provide photos and documents "proving" that Atta and al-Omari had taken the Nissan to Portland. This episode illustrates the fact that the government can provide official-looking documents to prove almost anything. I would not, therefore, allow official-looking telephone records to override Deena Burnett's testimony, given on 9/11 itself, that the calls she received indicated that they were made from her husband's cell phone.
Moreover, whereas Zarembka evidently takes Flight 93's telephone records as proof that Tom Burnett had swiped his credit card three times, what Zarembka refers to for this flight are not the original database records, but merely summary records, which could easily have been doctored (as shown by the fact that two cell phone calls, which obviously did not come from the onboard telephone system, were tacked on at the bottom).
Because of Zarembka's apparent faith in official-looking documents, he seems to hold that Deena's testimony, insofar as it conflicts with the government's data, can be disregarded. His only statement concerning Deena's testimony about Tom's cell phone -- which I presented as the most important evidence -- is sandwiched between statements about official reports. He says: "Griffin does not cite this important report, but focuses on Deena's affirmations as to Tom's cell phone number having been displayed on her screen. Meantime, the government claims a record for Tom using an air phone. . . ."
Zarembka, thinking I should have cited the FBI report showing that Tom used an onboard phone, slides over the fact that Deena had affirmed that Tom's cell phone number was displayed by her Caller ID. I have argued that this fact -- especially in the context of the other evidence that the 9/11 calls were inauthentic -- constitutes an unanswerable problem for the FBI's position on the Burnett calls and, thereby, for the entire story about calls from the 9/11 planes. (The calls to Deena Burnett could have been faked only if someone had engaged in advance planning to make these calls. And, as I argued in my chapter: "This planning would disprove the official account of 9/11, according to which the planes were taken over in a surprise operation. And if the official account is false on this point, then it must be supposed that all of the purported calls were faked.") To argue that Deena's testimony about Tom's cell phone number can simply be disregarded, one would need to give a plausible account as to why she would have given this account in spite of its falsity.

Why Did "Tom Burnett" Decline to Talk to the Children?
Deena Burnett, assuming that she was talking to her husband, said that the "kids" wanted to talk to him. But "Tom Burnett" declined, saying: "Tell them I'll talk to them later."11 I reported having found it "difficult to believe that the real Tom Burnett, dealing with a real situation, would have responded in this way." Zarembka, however, said: "Given that Tom had three very young daughters and was in an emergency situation, I find this easy to believe."
This brief argument contains two reasons for his view: There was an "emergency situation," and the children were "very young." I do not see how this combination of reasons could explain why the real Tom Burnett, in the situation described in the official story about United 93, would have declined the chance to speak to his children.
Would Tom Burnett have declined because his children were very young? They were, according to Deena, asking to talk to their father. If they were not too young to ask to talk to him, they were not too young for him to talk to them.
What about the "emergency situation"? A central fact about this situation would have been that Tom Burnett would have been aware that he was almost certainly going to die in the next few minutes. He could not have believed that he would "talk to [his children] later." I do not believe, in any case, that many fathers would turn down the probably last opportunity to talk to their young children.
Which is to say: I find it difficult to believe that the real Tom Burnett, knowing that his plane was likely going to crash in Pennsylvania, would have said to his wife: "Tell [the children] I'll talk to them later."

Voice Morphing
The second topic discussed by Zarembka is voice morphing. Zarembka's treatment can be summarized thus: (1) For Griffin, faked calls could be explained only by voice morphing. (2) Voice morphing of passengers or flight attendants who were added to the flight at the last minute would have been unlikely. (3) Therefore, it is unlikely that calls could have been faked. However, points 1 and 2 are both false.
In relation to the first point, Zarembka says: "Griffin relies on morphing because he needs a mechanism to explain the documented calls as faked, yet has no other alternative to offer to explain the calls as faked." However, I said: "[T]he idea that the calls to Deena Burnett . . . were faked should not be simply equated with the idea that these calls were produced by voice morphing. Rather, that is only one way in which they might have been faked." Then, after quoting some statements in which I had made this point in earlier writings, I discussed the "repeater hypothesis," explaining why it could not explain most of the calls, after which I said: "the failure of the repeater hypothesis does not necessarily mean that the voice-morphing hypothesis is correct. There may still be another way in which the phone calls from the planes could have been faked." I then concluded by saying: "We need to keep a clear distinction between the evidence for a phenomenon that needs to be explained (called by philosophers of science the explanandum) and the explanation for that phenomenon (the explanans). We might reject all the available explanations. But that rejection will not do away with the explanandum, which in this case is the evidence that reported phone calls from the planes were faked."
Turning now to point 2: Voice morphing certainly provides the best presently available explanation as to how the calls could have been faked. Zarembka suggests that it could not explain how phone calls of last-minute additions to the flight manifests could have been faked. But his conclusion is based on two false premises, namely: (2a) "some ten minutes of the real person's voice is needed to achieve a reliable imitation"; and (2b) voice morphing technicians would not be able to gather the information needed about passengers and flight attendants who had been added to the flight manifest near to the last minute.
With regard to 2a: Zarembka based his statement about the need for "ten minutes of the real person's voice" on this statement by journalist William Arkin: "By taking just a 10-minute digital recording of [anyone's] voice," voice morphing experts can "clone speech patterns and develop an accurate facsimile." But this statement does not pretend to state what is absolutely necessary. In fact, I had said: "[A]ccording to Arkin's article, the capacity to morph voices in 'near real time' using a ten-second voice sample had been developed by early 1999."
Equally important is Zarembka's error with regard to 2b. There likely would have been years of preparation for this operation. During this period, all of the voice samples and other information needed about possible flight attendants and possible passengers could have easily been gathered and stored. But Zarembka ignores this fact.
For example, quoting the fact that "[flight attendant] Renee May was only assigned to Flight 77 during the morning of 9/11," Zarembka says: "[V]oice morphing of her call to her parents would have been quite difficult." But there would have been numerous phone calls from and to Renee May in the previous year, which could have been recorded, and during which a file containing personal information about her could have been developed. With regard to the passengers who made last-minute changes: The government could have gotten voice samples from phone calls to the airliners in the previous years, or by hacking into other telephone calls. And besides, as mentioned earlier, the government had developed the "capacity to morph voices in 'near real time' using a ten-second voice sample."
In sum: The technology of voice morphing can easily account for faked calls from passengers and flight attendants. And there may be still another way, presently unknown to most of us, to explain the fact that various elements in the 9/11 calls suggest that they were inauthentic.

Cell-Tower Handshaking at 580 MPH
I had suggested that, although the reported 9:58 AM cell-phone calls by Edward Felt and CeeCee Lyles were accepted by the FBI as indeed cell phone calls, these reported calls "would have to be rated as very unlikely."
Zarembka begs to differ. In the first place, he points out, the "5,000 feet" elevation that is commonly cited is the elevation above sea level, not above the ground, and the above-ground altitude of a plane in Shanksville would be 2,230 feet. That is a good point. However, according to A. K. Dewdney -- who had one time had a regular column in Scientific American -- cell phone calls from airliners more than 2,000 feet above the ground would be "highly unlikely."12
In the second place, the lower a flight, the greater the "handshake" problem. Zarembka suggests that the calls by Felt and Lyles would not have encountered that problem, because "both calls were short." But in this context, these reported calls would be considered quite long: Felt was reportedly able, after reaching the dispatcher, to tell him about the hijacking; and Lyles was able to tell her husband that her plane had been hijacked, that the hijackers were "forcing their way into the cockpit," that she loved her husband, and that she heard passengers screaming.
In any case, less important than the length of the calls was whether the plane was flying too fast and low for them to complete handshakes. "Any airliner at or below this altitude [of 2,000 feet above the ground], flying at the normal speed of approximately 500 mph, would encounter the handoff problem," wrote Dewdney. "An aircraft traveling at this speed would not be over the cellsite long enough to complete the electronic 'handshake' (which takes several seconds to complete) before arriving over the next cellsite, when the call has to be handed off from the first cellsite to the next one."13
Accordingly, even the reported cell phone calls by Felt and Lyles must be considered very unlikely.

Calmness
Another argument I employed -- drawing on an essay entitled "'Shockingly Calm': The Phone Calls From the Planes on 9/11," by the careful scholar who uses the alias "Shoestring 9/11" -- was that supposed calls from 9/11 planes by passengers and flight attendants were much calmer than we would have expected from authentic calls.
Zarembka criticized me on the assumption that I claimed that there were no exceptions. Given that assumption, he could easily point out exceptions (such as the fact that Lorne Lyles and the father-in-law of Jeremy Glick reported hearing screaming), and then make his charge: "Griffin is not entitled to cite only that which might sustain his argument. . . , while ignoring contrary pieces of evidence." However, if I were arguing that there were no exceptions to the calm I would not have pointed out that "Todd Beamer," after having long seemed calm, expressed fear when it became likely that the passengers on United 93 were going to die, telling Lisa Jefferson: "I know we're not going to make it out of here,"14 after which he cried out: "Oh my God, we're going down! We're going down! Jesus help us."15
My argument was not that everyone was calm all the time. Rather, what I pointed out was that the calmness was remarkable -- that the people making these calls were much calmer than any of us would expect under the described circumstances.
With regard to the flight attendants in particular, Zarembka argues that the calmness of the flight attendants was not remarkable: "Calmness on the part of professionals is what they are trained to do." However, people who know this still described the calmness of some of the flight attendants as remarkable. A United Airlines manager described Sandy Bradshaw, a flight attendant on United 93, as "shockingly calm."16When the family of Betty Ong, a flight attendant on American 11, heard the recording of her call, they "couldn't believe the calm in Betty's voice."17

The Still-Connected Calls of Beamer and Glick
One reason for saying that the phone calls were faked, I said, was the fact that two of the alleged calls from United 93 remained connected long after this flight reportedly crashed: the Todd Beamer call remained connected for over 65 minutes, and the Jeremy Glick call remained connected for two hours and six minutes. How could that possibly be, if the official story were true? According to that story, United 93, going 580 miles per hour, crashed into a field in Pennsylvania. Such a crash would have instantly disconnected all calls. Would the fact that these two calls remained connected for over an hour not prove that the calls were not coming from UA 93?
But Zarembka has only a four-word response to the fact that these calls remained connected for over an hour: "This is a puzzle." In Zarembka's eyes, it appears, the failure of the Glick and Beamer calls to disconnect when their plane crashed does not prove that the calls were placed from somewhere else. They merely constitute a puzzle.

"Todd Beamer" Passing Up the Chance to Talk to Beamer's Wife
What about the fact that the man presenting himself as Todd Beamer did not want to talk to Lisa Beamer (Todd's wife)? This man had lots of time, spending 13 minutes talking to a Verizon supervising operator, Lisa Jefferson. There would have been no reason why he could not have used some of this time to call Lisa Beamer. Indeed, Lisa Jefferson even offered to try to reach her "and patch her call through." But "Todd" declined, with the excuse that he didn't "want to upset her unnecessarily," because "[s]he's expecting our third child in January."
Calling this excuse unbelievable, I said that it revealed "Todd Beamer" to have been an impersonator.
Zarembka, however, deems the reason given by this man for not calling Lisa Beamer to be credible. But is it? "Todd" said that he did not want his pregnant wife to be upset. But is this not absurd? If this had really been Todd Beamer, would he not have realized that his wife would very soon be upset by the news of his death, so that the question of whether she was upset immediately or a few hours later would not matter much? And did it not occur to him that she would likely be even more upset if she learned that he had turned down a last opportunity to talk to her?
In deeming my argument "unpersuasive," Zarembka says that one would need "to speculate for a reason differing from the stated one of Todd's wife's pregnancy." But a reason is very close at hand: It is likely that the man was an impersonator, and that he was not certain that his impersonation was good enough to fool Todd Beamer's wife.
But Zarembka, after expressing his opinion that the man presented as Todd Beamer had provided a perfectly good rationale for not talking to Lisa Beamer, recommended that readers turn to Rowland Morgan's discussion of the alleged Beamer calls, which Zarembka considers "more convincing." And yet Morgan said: "The contrast between a young man facing his end and his refusal to speak to his wife is implausible."18

Ignoring the FBI's Evidence about Barbara Olson
Having treated my discussion of the Burnett calls very briefly, Zarembka gives an even briefer treatment of my second longest discussion of evidence for fakery: the reported phone calls from Barbara Olson. According to her husband -- Solicitor General Theodore "Ted" Olson -- she had called him twice from American 77, with the first call lasting "about one (1) minute"19 and the second one "two or three or four minutes."20
It appears, however, that this story could not have been true, for several reasons. In the first place, the story told by Ted Olson, as purportedly told to him by his wife -- the story according to which three or four slight men armed with only knives and box-cutters held off 60 passengers and crew members -- was extremely implausible.
Second, there seemed to be no way that Barbara Olson could have made calls from American 77: Her flight at the time of the calls was too high for cell phone calls, and the FBI, in any case, indicated in 2004 that there were no cell phone calls from this flight. (To repeat: The FBI said: "All of the calls from Flight 77 were made via the onboard airphone system."21 ) The Boeing 757s equipped for American Airlines, moreover, evidently had no onboard phones for use by passengers and crew. These facts, especially when combined with the implausibility of the Olson story, had provided strong reasons to doubt the truth of that story prior to 2006. But in that year, the FBI's telephone evidence about American Flight 77 was made public as part of the FBI's evidence for the Moussaoui trial, and it said, in effect, that the Olson story could not have been true: Whereas Ted Olson had said that he had received two calls from his wife, one of which lasted about a minute and the second of which lasted at least twice as long, the FBI report said that Barbara Olson attempted (only) one call, that it was "unconnected," and that it (therefore) lasted "0 seconds."22
How does Zarembka treat this information? First, he does not mention the fact that what had been the dominant press account in the first several years -- that Barbara Olson had used her cell phone -- has now been ruled out by the FBI.
Second, he says that I ruled out her using "an air phone" on the basis of "[c]laiming" that "air phones were unavailable to passengers on American Airlines Boeing 757s." By speaking about what I was merely "claiming," Zarembka seems to suggest that American Flight 77 might have actually had working onboard phones.
Third, at this point, Zarembka does not mention the information about Flight 77 made available by the FBI in 2006. He merely says: "Griffin is unsatisfied with leaving it there and provides some other abnormalities." Zarembka then recommends "[Rowland] Morgan's 2010 extensive discussion of the alleged Olson calls."
Morgan's book-length essay, which I cited many times, is indeed excellent. And one of the factors making it excellent is its report about the crucial information that Zarembka failed to mention: that the telephone data contained in the evidence for the Moussaoui trial says that "Mrs. Olson had only made one call, an unconnected call, by unidentified phone type, and that she had never spoken to her husband."23 Why Zarembka did not consider this information worthy of mention, I do not know.
Instead of mentioning this information, Zarembka concluded his brief treatment of the Olson calls by saying: "Olson had been originally scheduled to fly on September 10" -- which was Zarembka's way of indicating that it would have been difficult for Barbara Olson's calls to her husband to have been morphed. This suggests that, in spite of the evidence that she could not have used either a cell phone or a seat-back phone, and in spite of the FBI's indication that she did not complete a call to her husband, Zarembka still believes that she somehow made the calls. I cannot understand what kind of thought process led him to this conclusion.24

Not More Passenger Calls?
I had begun the eighth section of my chapter by saying: "Another reason for doubting the authenticity of the 9/11 phone calls is the very small number of passengers who, according to the official story, took advantage of the opportunities to make phone calls." Zarembka, meaning to lift up another stone with "error" written on it, writes: "[I]n the process of listing each of the four planes . . . , he [Griffin] seems to forget that a few pages earlier he had made a full argument that air phones were unavailable for flights AA 11 and AA 77 as they were using Boeing 757s."
However, although there are errors in relation to this point, they are by Zarembka. In the first place, he said that American 11 (as well as American 77) was a Boeing 757. But American 11 was a 767, hence it presumably had onboard phones.25 Zarembka should, therefore, have responded to the problem about the official story of American 11 raised by Rowland Morgan: "There were about 76 passengers sitting unsupervised in business and coach while the alleged hijackers were locked away. . . . All of them sat facing seatback phones. . . and no passenger called 9-1-1?"
A more important error made by Zarembka is that he evidently failed to note that I was discussing American 77 within the framework of the official story. Within this story, there is no acknowledgment of the evidence that Boeing 757s -- and hence American 77 -- had no working onboard phones that could be used by passengers and flight attendants. This is shown by the fact that flight attendant Renee May is listed by the FBI as having used an onboard phone to call her parents from American 77, and Barbara Olson is listed as having tried to make a call.
Within that framework -- according to which passengers and flight attendants could have used seat-back phones on American 11 and 77 and United 175 and 93 -- it would indeed be surprising that there would have been so few calls.

Conclusion
Zarembka has suggested that my treatment of the "phone calls from the 9/11 planes" often portrays the official story as being false when the evidence does not support such a severe verdict. But Zarembka's critique failed at virtually every point.26 Zarembka also concluded his critique by stating that my chapter suffers from problems of "internal logic." But no instances of this failure have been shown. Rather, what Zarembka saw as problems in logic were actually misreadings of my arguments, as I hope my rebuttal has made clear.
_____________________________________
Notes
1David Ray Griffin, 9/11 Ten Years Later: When State Crimes Against Democracy Succeed (Northampton, Olive Branch [Interlink Books], 2011).
2Paul Zarembka, "Critique of David Ray Griffin regarding Calls from 9-11 Planes," ITHP, October 14, 2011 (http://ithp.org/articles/davidraygriffincritique.html).
3I consider the Lyles message to be a fake because, after the message to CeeCee's husband was stated, there was a pause, followed by a barely audible voice saying: "You did great." It would appear that those who made the (fake) recording public failed to notice that the recording was still on when the "You did great" statement was made. Zarembka, however, believes that this statement did not mean that the Lyles statement was a fake. Rather, Zarembka suggests: "Flight assistant CeeCee Lyles was sitting next to another woman and CeeCee had discussed with her an intention to call her husband. The other woman simply supported CeeCee in how she handled herself with that phone message." This, however, is a matter of judgment, which is why I consider the Lyles call to provide weaker evidence than the Burnett and Olson calls. (One's interpretation of the "You did great" statement will depend in part on one's view of the "phone calls from the planes": If one believes that the Burnett and Olson calls were authentic, then one would be likely to accept Zarembka's interpretation, whereas if one is convinced that they are fakes, the one will probably regard the Lyles call as a fake.
4"Interview with Deena Lynne Burnett," Federal Bureau of Investigation, September 11, 2001 (http://intelfiles.egoplex.com/2001-09-11-FBI-FD302-deena-lynne-burnett.pdf).
5Ibid.
6Ibid. Zarembka evidently based his statement that Deena said "four" on a memorandum prepared by the 9/11 Commission in April of 2004; see 9/11 Commission Memorandum for the Record, prepared by John Raidt, Aril 26, 2004 (http://media.nara.gov/9-11/MFR/t-0148-911MFR-00260.pdf). But this document, prepared two and a half years after 9/11, surely cannot be taken as more authoritative than the FBI's report on 9/11 itself of what she said.
79/11 Commission Memorandum for the Record, prepared by John Raidt, Aril 26, 2004 (http://media.nara.gov/9-11/MFR/t-0148-911MFR-00260.pdf).
8Citing www.911myths.com/images/c/c3/Team7_AirfoneRecords.pdf.
9The evolution from the first story to the second one has been documented in "Where Did Authorities Find Atta's Treasure Trove of Information," Ch. 16 of David Ray Griffin, 9/11 Contradictions: An Open Letter to Congress and the Press (Northampton: Olive Branch, 2008).
10This affidavit is available at Four Corners: Investigative TV Journalism (http://www.abc.net.au/4corners/atta/resources/documents/fbiaffidavit3.htm).
11"Transcript of Tom's Last Calls to Deena," Tom Burnett Family Foundation (http://www.tomburnettfoundation.org/tomburnett_transcript.html).
12A. K. Dewdney, "The Cellphone and Airfone Calls from Flight UA93," Physics 911 (http://physics911.net/cellphoneflight93.htm).
13Ibid. In the case of United 93, the handshake problem for a plane traveling 500 mph would have been mitigated by the fact that the plane, according to the official story, was coming down at a steep angle. But this mitigation would have been partly canceled out by another feature of the official story: that the plane was reportedly traveling at 580 miles per hour.
14Douglas Holt, "Call Records Detail How Passengers Foiled 2nd Washington Attack," Chicago Tribune, September 16, 2001 (http://www.accessmylibrary.com/coms2/summary_0286-6765842_ITM).
15Lisa D. Jefferson and Felicia Middlebrooks, Called (Chicago: Northfield Publishing, 2006), 47.
16Staff Report, 9/11 Commission, August 26, 2004: 40 (http://www.archives.gov/research/9-11/staff-report.pdf).
17Jennifer Julian, "One of the Last Calls," ABC 11 Eyewitness News, September 11, 2002 (http://web.archive.org/web/20021107235946/http://abclocal.go.com/wtvd/news/091002_NW_LastCall.html).
18Rowland Morgan, Voices, 2010 (http://www.radiodujour.com/pdf/voices-book.pdf).
19"Interview with Theodore Olsen [sic]," 9/11 Commission, FBI Source Documents, Chronological, September 11, 2001, Intelfiles.com, March 14, 2008 (http://intelfiles.egoplex.com:80/2008/03/911-commission-fbi-source-documents.html).
20"America's New War: Recovering from Tragedy," Larry King Live, CNN, September 14, 2001 (http://edition.cnn.com/TRANSCRIPTS/0109/14/lkl.00.html).
21"T7 B12 Flight 93 Calls- General Fdr- 5-20-04 DOJ Briefing on Cell and Phone Calls From AA 77 408," Federal Bureau of Investigation, May 20, 2004 (http://www.scribd.com/doc/18886083/T7-B12-Flight-93-Calls-General-Fdr-52004-DOJ-Briefing-on-Cell-and-Phone-Calls-From-AA-77-408).
22United States v. Zacarias Moussaoui, Prosecution Trial Exhibit P200054. This FBI's report on phone calls from AA 11 can be viewed more easily in an article by Jim Hoffman, "Detailed Account of Phone Calls from September 11th Flights" (http://911research.wtc7.net/planes/evidence/calldetail.html).
23Morgan, Voices, 5.
24Also, given the fact that Barbara Olson had been speaking regularly on CNN, I do not understand why Zarembka thinks that a last-minute change of flight would have made it difficult to morph her voice.
25Zarembka later noticed his error here, as he indicated in a comment to his essay.
26The one point I grant, in part, is with regard to the CeeCee Lyles message followed by a voice saying: "You did great." Although I do not think Zarembka's interpretation more likely than mine, I would admit that it would at least be plausible - if viewed in abstraction from the various types of evidence, discussed in my chapter, that the "phone calls from the planes" had been faked. But it should not be viewed in abstraction. It should especially be viewed in the light of the Burnett calls, with which I started my chapter.