Showing posts with label Citizen Investigative Team. Show all posts
Showing posts with label Citizen Investigative Team. Show all posts

Sunday, June 1, 2008

THE PHYSICAL EVIDENCE {masterlist}

THE PHYSICAL EVIDENCE {masterlist}
The Frustrating Fraud
Last updated January 2 2008


This post is to organize the sub-posts dealing with the analysis of the physical evidence at the Pentagon attack scene. I am not a structural engineer, forensic scientist, or airplane mechanic. I'm a janitor, but have enough common sense, basic scientific knowledge, and ability to visualize spatial dynamics and physical processes to give my analysis some worth. Some of this is just conjecture, some backed by some research. And most importantly, I’m driven by a desire to actually figure out what makes the most sense, and not be ruled by mystery and speculation. Initially my research was to decide how far off-track Pentagon Strike and 911 In Plane Site really was, but since then I have put together a plausible explanation for what physically happened there that morning centered around the impact of a plane rougly the size and shape of a Boeing 757 and seemingly painted with the American Airlines standards. It's not the only possibility, but as I'll demonstrate it's probable, likely, or at at least as plausible as any other theory, putting the lie to the myriad claims it could not be so.

Just as I was posting this starting late in 2006, the new paradigm of no-757 hoaxing was emerging – Citizen Investigative Team and the witnesses whose geometry logically rules out an impact by a missile, drone, 757, anything, with all the points of evidence addressed below fabricated independently, some in real-time, to indicate a plane strike on the official path. To demonstrate how remarkably convoluted that would be all I need do is keep plugging away at the details like I have been and take as leads the points they think they can twist into making their silly case seem to make sense. To address the witness verification, logic, geometry, and honesty aspects of CIT, I’ve gone out on several limbs listed in a separate masterlist.

In piecing this together I’ve drawn on official and governmental sources, FOIA released documents shared by others, published personal accounts, and mostly on many hundreds of photographs and the published opinions of various theorists. I'm indebted in tiny part to 911 IPS/Loose Change/Hufschmid et al for getting me started and wondering, but indebted massively to the groundbreaking works of John Judge, Mark Robinowitz, Jim Hoffman, Russell Pickering, Joel van der Reijden, Scott Bingham, and various others for showing and addressing in a sane manner ALL the evidence available and thus allowing me closer to the reality of the situation. So in drawing on the works of others, there are only so many new ideas here. What I do is try to understand a point at the basic level, verify it by what I know or can learn, and then simplify and convey the core ideas in my own way. There are no math or science prerequisites for understanding the evidence of this crime scene as I've boiled it down.

In fact, as some have pointed out, the Pentagon may have become such a focus of flawed theories because of the simplicity of the crime scene. The WTC was almost volcanically destroyed and buried, but the Pentagon was basically a five-story office building left almost totally intact. The impacted section was primarily on a single floor of the building and of course inside the plane. Identification of plane parts and bodies would be easier by orders of magnitude than the New York crime scene. And if no such evidence existed, many reasoned, this would become the “weakest link” in the official story. The scant evidence available does not bear them out – this is someone’s weakest link, but not the government’s.

> ATTACK PATH DAMAGE AND QUESTIONS
- Precision Low-Rider: The remarkably anomolous final attack altitude - admittedly quite a feat for a hulking 757. And yet...
- The widely-cited unmarked lawn: A plane so low and yet not quite THAT low. Again suspicious but ultimately a red herring IMO. It seems that however unlikely, it flew that razor's edge of altitude, pushing the envelope to the maximum.
- From the Blind Spot to the Empty Side: The lack of radar coverage over the attack route and the stroke of "luck" that had the plane hit the just-renovated and partly empty side of the building.
- The "undamaged" light poles: Testifying the 'official' flight path and altitude, were these clipped by the plane, popped with FX, or planted in advance?
- Analysis: Poles 1 and 2 proportions, shear height, clues to final plane bank, just a hint of getting into the Lloyd issue...
- Map of the crime Scene and the "obstacle Dodge." The heliport, attack path, generator, etc. mapped out and explained. Excellent resource to be updated soon to reflect the below.
- Vent Structure Damage: If the plane could be said to have hit the ground before impact, this is where it did so.
- Twisted Orange Trailers: Analysis of scrap metal at the scene with some angles and stuff. Pretty cool.
- Cookie Identification Team: The damage points that line up so well they're called 'cookie-cutter,' or too perfect, by critics. Generator trailer, fencem vent retaining wall, tree damage, general impact hole.
- Like Two Bulldozers: A new view highlights the consistency of the damage path with a 757 strike or some damn good fakery.

> IMPACT DAMAGE

- The Entry Wounds: Analyzing the tiny "16-foot hole" so many insist could not have allowed a 757. It's actually 90 feet wide.
- The "16-foot hole challenge." coming soon.
- The outer wall: how many inches of what?: External Wall construction notes - 18" of steel-reinforced concrete? 13" of brick reinforced limestone? Or what?
- Support columns Masterlist: The "intact support columns" thought to preclude a 757 - anlysis with thee linked sub-posts demonstrating incorrect official reports, questioning the status of columns 15-17aa, and the PentaCon guys' analysis of "intact" column 14aa on the second floor.
- Pentagon Foundation Damage?
- Right Wing Damage Continuity

> DEPTH OF PENETRATION
- Early revisionist accounts decided only one ring was damaged. I run rings around their deeply flawed analyses (from 2001 and 2002) for no big plane at the Pentagon. They should have learned by now, but it doesn't seem they have.
- Nine feet of Steel Reinforced Idiocy: Plane penetrates 300 feet, fraud logic penetrates nothing.
- Punch-Out Page - intro on the punch-out hole at the end of the plane's alleged penetration, masterlist of more posts on the hole.

> FIRE:
- No fires? "A Stool Sample of IPS Evidence."
- Impact fireball: Fireball Fakery: Challenge to CIT

> THE PLANE PARTS:

- Part I: The Engines: Parts that could be from almost any engine - including a 757's.
- Part II: Landing Gear: a wheel and a landing gear that look like those from a 757.
- Part III: the Scrap Over the Scraps: Fuselage segments from an American Airlines jet.
- The Flight Data Recorder {masterlist}: Found intact, with altitude, speed, etc details programmed in, and coming out weird. A lot to cover... especially the animation.

>THE BODIES:
-
Faces of Death, the Moussaoui Edition: The government's release of new evidence in mid-2006 as the Moussaoui case closes - are we seeing the Flight 77 victims here?
- also covered at the end of the
nine feet of idiocy piece.

Thursday, February 21, 2008

CHAD BROOKS, 2001: LEFT? BEHIND?

CHAD BROOKS, 2001: LEFT? BEHIND?
Adam Larson / Caustic Logic
The Frustrating Fraud
February 5 2008
video added 2/21 3am
final update 2/22 3am


2006 vs 2001: The Left Hand Knows Not…
One of The PentaCon’s two uniformed witnesses to the North-of-the-Citgo flight path is Sergeant Chadwick Brooks, video-verified on location at FOB lot 6, where he saw the plane approach the Pentagon from the west. I agree with CIT’s assessment that we can’t pinpoint an exact parking spot, but I think it’s safe to say he’s in the right row – having driven west from the Citgo station, he parked in the westernmost row of the main part of the lot. He is facing west when he affirms that ‘this exactly where you were standing when you got out of the car, after you saw the plane coming.” From there, Brooks tells CIT “we were able to see everything,” indicating a flight path originating above, ahead, and to the right, traced with his finger descending back and to his right. The path he describes is entirely north of the station, if barely. This looked good for the case, and even better when he drew a different line further north later on.

This graphic then depicts the account presented verbally in the PentaCon:
However, both stories seem to conflict with what Brooks described two months after the event, when both he and officer Lagasse were interviewed for a US Library of Congress project. Brooks gave a 14-minute audio interview, recorded November 25, 2001, apparently by the Utah State University folklore archive, on behalf of the LoC. [MP3 listen/download link] One of officer Brooks’ more interesting revalations is this, at 01:22: “One of our assignments that day was at 11:00 we were supposed to be at the heliport, the actual crash site, for, uh.. a dignitary coming in.” This can only be President Bush, scheduled to arrive at the Pentagon via helicopter at 12:00, after returning to the Capitol from Florida. This was of course cancelled after the 9:38 crash of Flight 77.

The interview shows a very real human, nervous on his recollection; I counted at least nineteen instances of the word ‘literally.’ He spoke of dealing with the injured, and of “sheer terror.” “It felt like a lifetime,” he said, and “it felt like everything was in slow motion. My mind just didn’t register.” Indeed, his description of the plane’s approach includes several periods of “a few seconds later” and the like; read literally, the whole attack would have taken perhaps a couple of minutes. In reality it took only 2-3 seconds from his position to impact, plus however long he saw it in the distance first. Almost poetically, he noted the poignant feeling of “knowing that there were people on the plane at the time just literally flying over me. What were they thinking? I know they had to see us.”

And what side of the plane would he himself have been visible from (if the shades weren’t pulled)? It’s less specific than his 2006 interview, and I can’t make a 100% assertion at this point. However, he places himself in a parking lot near the Citgo, and at 02:12 he says:

“I just happened to look up to my left up in the air and just seeing a plane. A few seconds shortly after that I heard what seemed to be a tractor trailer coming behind me […] I looked to my left and lo and behold I notice that the plane was going awfully low […] I saw the plane just go nose dive into the Pentagon.”

1) He ‘happened to look up’ and to his left to see the plane at some distance
2) Then he heard a sound that seemed to come from behind him
3) Then he saw it again on his left, descending. Ahead or behind unclear.
4) At some point in this process he also mentions getting out of the car.
5) Then he saw the impact, which was about 2.5 seconds after passing over him.


Now, everything so far indicates that he had driven into the parking spot, not backed in, and saw the plane ahead of him in the distance. If this were indeed the case, the sound coming from behind him could be the 757's roar bouncing back off the Pentagon's west wall. For the plane to be ahead of him to his left, remain on his left, descend and move west-east as all evidence suggests it did, it could only be on a line south of the Citgo and more-or-less on the official path, where all the poles and columns and people were damaged. This would be a big problem for his later north side claim that helps rule out the impact he thinks happened anyway.

The Case For East
Craig Ranke has left several comments below, along with a few craters I deleted, and my responses. It almost seems he was trying to confuse/intimidate the story into submission. “Up is down, north is south, left is right in Caustic Illogic's world. Anything to cast doubt and confuse. […] He describes the plane on the north side in both interviews. This is 100% clear. You are losing all grip on reality.” You don’t draw flak unless you’re over the target, some say.

Ranke seems to feel Brooks backed in to the spot, facing east towards the Pentagon before the plane approached, and a flight on his left means a north path coming in from behind him, left of the station just like he said. “Dummy...... If the plane came from "behind" him as he said then to his left is north, right? If he did not back in to the space then why would he describe the plane as coming from behind him? How do you not understand this?” I do understand this scenario, which is why I anticipated that would be his answer and even offered it myself as his best bet.
What was his basic starting direction before he got out of the car, when he first saw a plane to the west and on his left? His 2006 interview does not help clarify this question at all; CIT only asks him about his position after getting out of the car; by then he was clearly facing towards the plane, which is west unless he only got out after it passed him. In fact they don’t ask him any details about his first sighting, and the impression one gets watching the video is that it just appeared unannounced over the trees about 100 feet from him. This is just as well since Brooks was clearly mistaken about the north path and might have screwed up the other parts too.
Considering CIT’s take, to be fair, it is entirely possible he backed in, and as a cop that makes some sense, to be prepared to pull out. He’d be facing east as the plane snuck up from the west, and he does mention a sound behind him. It’s possible he saw the plane behind him at a distance before hearing it behind him. Compared to some other assertions CIT has wrung out by twisting the evidence hard enough, this seems a reasonable possibility.

And this is the only interpretation open if we believe his 2006 testimony which clearly places it north.

A Clarification

My previously take, which is reflected in this video version [Youtube page link] and the original posting of this article, included this clever but not entirely applicable observation:

“If this is the case, that Brooks was facing east at the time, then at the least we have a case of him placing himself backwards in the scene in his ‘06 recreation, where he is generally facing west and trying to remember it that way, having to switch hands and basic bodily directions to accommodate the twist. What odd witness behavior when CIT originally touted six reasons to believe their witness' North-side claims, including point 2: "The simple right or left nature of their claim"

I’d like to amend this point without fully retracting it; as noted above he never actually re-enacts this first sighting at all. This is all after he saw the plane either ahead or behind and got out to watch it. For that time he’s facing the right way, just in some kind of error when he puts up his right hand and describes it north. Therefore, I would not necessarily believe it even if CIT tracked him down and got him to confirm he was backed in. I’m curious only in the clues offered by the original Chad Brooks of 2001.

The Case for West
1) That he would happen to look back over his shoulder, from inside the car, with no prior cues he mentions, makes less sense than his ‘happening’ to just glance up, or catch a subtle glint, if facing towards the approach. From this angle, west makes more sense.

2) The sound coming from behind him is not problematic for a west direction. It could either be the 757 having passed that far, on his left, or more likely reverb. Consider this from Terry Morin’s account, facing south at the Navy Annex just before the plane came in from the west:

“I started to hear an increasingly loud rumbling behind me and to my left. As I turned to my left, I immediately realized the noise was bouncing off the 4-story structure that was Wing 5. One to two seconds later the airliner came into my field of view.”

This case is clear; the sound to his left and behind was off the building, and the plane came in from his right. Less clearly Brooks says “shortly after [first seeing the plane] I heard what seemed to be a tractor trailer coming behind me. Well, it felt like it was coming from behind me,” he added. This last indicates the actual plane was coming from ahead. As in Morin’s case, this could well be sound deflection off something behind him, like the Pentagon, or perhaps something smaller and closer, and his qualifier indicates as much.

3) Again, as I just found out via stumbling, I’m needlessly replicating the works of Pickering.

They Knew
Russell Pickering is of course the trailblazing PentagonResearch.com proprietor who won the ear of the Loose Change guys and near single-handedly persuaded them to at least entertain the obvious. Back in the pre-PentaCon era, as a moderator at the Loose Change Forum, he posted this observation to fellow mod Ranke (as Lyte Trip) on September 10 2006, in response to their growing fascination with north-side Lagasse and a then-unnamed Citgo employee:

“We also have Brooks who was in the parking lot across the street from the Citgo (and Lagasse and the employee) who puts the plane on his left or in the mechanical damage path to the south. He was the only one between the Annex and 27 that was not under a canopy and claims to have had a clear view.”

Pickering was drawing on the 2001 interview, and admitted that Brooks “does not indicate which way he was facing.” But all things considered, the conclusion was clear enough that he offered this difference between Brooks and Lagasse: “Brooks placed the aircraft to the south of the Citgo hitting the poles," whereas "Lagasse said, "I was on the Starboard side of the aircraft" but claims he saw it hit the poles too.”

So Russell felt Brooks’ pre-PentaCon story matched a south path, which Pickering championed and Ranke disparaged. Three days later he added, almost as a taunt, “you have an officer who was only 300 feet away from the Citgo who was not under a canopy and facing the approach path in one manner or another you have totally discounted.” [emph mine]

So was he always a north path witness, or was Chad Brooks 2001 left behind when, less than two months after the post above, he met Ranke and/or Marquis and their camera? What were the Citizen Investigators thinking as they stood in front of him, and enthusiastically absorbed his ‘didn’t actually see the poles clipped,’ plane-on-the-right story without any question? I was unable to find any post-November dialog about the irony of this twist, either from Pickering or the CIT side.

Friday, February 8, 2008

RIGHT WING DAMAGE CONTINUITY

RIGHT WING DAMAGE CONTINUITY
Adam Larson / Caustic Logic
The Frustrating Fraud
February 10 2008


Citizen Investigative Team’s number one claim to fame is of course their trailblazing eyewitness account verification, proving a north-of-the-Citgo flyover of the Pentagon. But garnering less attention is their groundbreaking work on exploring the ‘smoking gun’ physical evidence there was no impact from any airliner. Besides the witnesses, and before they were known of at all, CIT felt they had a strong anti-crash case, based on research into the ‘anomolous’ physical evidence at the site of the anomalous (alleged) impact of a 757 into the Pentagon.

Among the prime points they have made and that I’ve so far addressed is the presence of Column 14AA on the second floor, and the lack of foundation damage. The next claim I will examine and answer to the best of my ability is “why is there no continuity to the "wing damage" when it tilted up its right wing? It looks as if the facade simply fell off in this section.” This question was posted along with the two above and several others at Above Top Secret.com, and illustrated with these two high-res Jason Ingersoll photos:
The area shown here is just south of the main impact hole, the first and second floors of the section just upgraded to withstand bomb blasts. In the middle span there is much visible damage: a windowless panel recently backed with 10” of steel-reinforce concrete, intact but missing most facing and partially scooped-out. Perhaps most odd is another panel of presumably the same type right below it entirely gone, along with two weaker window/door panels just to the right of these. Some limestone facing is removed from the frame to the right of that, but at the left and right are areas of little or no visible damage, labeled in red “no wing.” On first blush this might seem like pretty anomalous damage, considering the alleged wing impact angle (see below); put simply, there’s too much damage on the first floor, and apparently not enough on the second.

The photo below is overlaid with a light grid representing the intact structural frame. Intact panels within the grid are lightened as well, whereas removed or intensely damaged panels are left un-tinted. The partial plane outline is based on the ASCE’s graphics, layered to scale and outlined. Areas shaded red are where the problem is, those marked ‘no wing’ above.
Considering how much continuity of damage there should be, we need to consider many factors, like these:
1) The strength of the wing at various point in optimal conditions
2) Actual wings strength/integrity after impacting light poles, generator, etc.
3) The mass and speed behind the wing (with the fuselage already shredding inside)
4) By the alleged impact angle, the entire right wing would have impacted near-simultaneously
4) Portions of the building impacted – horizontal resistance (floor slab) vs. vertical resistance (columns, wall panels, windows)
5) The possibility of other projectiles (cargo trailers, equipment, etc) and/or the deflagration plume of a pre-impact wing explosion contributing to the extra damage on the ground floor.

Considering these, one red area is near the wing’s mid-point just over and south of the engine. This is a very strong part of the wing, but it met the floor slab at a shallow angle – near parallel - with at least ten feet of it hitting edgewise either the slab or the very bases of the columns anchored to it above. At this point, the building wins and shows no immediately visible scars. The other problem area is nearer the wing’s tip, a weaker point, meeting ordinary columns and façade, if the outer wing was even still attached at that point. The wall south of CL 20 shows nary a sign of impact, so apparently building wins there as well, which somehow doesn’t surprise me.

But further in on the wing, which was after all attached to a barreling 90-ton jetliner at about 460 kts, there should have been some instant damage to the frame. Countering this CIT point at the forums, I’ve previously used the following two images of the damaged panel between columns 18 and 19, cropped from Jocelyn Agustino hish-res photos taken – yes, I’m aware - about a week after the event: The missing brick has a linear edge with a certain slope relative to horizontal. The concrete backing damage has its own similar overall slope. The slab and column damage as well exhibit a similar but shallower slope. The damage is manifested at different heights due to the nature of the materials, their order in layering, etc., but all share a moderate right-high slope that is consistent with the alleged wing tilt of the 757 at impact.
Seen from something of a side view, as above, it’s clearly visible that the columns are disjointed, with the upper floor’s lower ends apparently buckled inward, or the lower ones outward, it’s not entirely clear. Referring to this area of damage, the ASCE’s Pentagon Building Performance Report noted:

“Just above the second-floor slab, the exterior columns on column lines 18 and 19 exhibited aligning gashes that seem to indicate impact by the right wing of the aircraft [...] An area of broken limestone of the facade over the exterior column on column line 20 also aligned with these gashes.” [p 27/28 - emph mine]

Referring to these photos presented as evidence, and apparently missing the majority of information in them, Ranke said “the damage does NOT match a "wing". […] A single broken column does not match a "wing" and does not have to have been fabricated on purpose to match a wing.” He decided I was “incorrectly or deceptively trying to attribute damage to the "plane" that did not exist immediately after the violent event,” rather than to the collapse or some other later event. [source]

In fact, noting the lack of all this damage visible before the collapse, I attribute it to a chain of events unlocked by the plane’s impact. Let’s look at a different kind of continuity of wing damage - continuity through time. At impact the initial damage would be done in a tiny fraction of a second. Some of this – the missing and damaged panels - was externally visible. There would also be damage, especially along the stronger frame, that would be internal and less visible.

Considering both obvious and possibly latent damage, let’s look at a sequence of pictures from the morning of 9/11, at different points between 9:38 and 10:15 or so. In Steve Riskus’ photo at left, taken about one minute after impact, CL18 is framed by magenta markers and a line of fire just to its right. This long-shot is too unclear on its own, but compared to the Darryl Donley photo at center and taken at least five minutes after, it shows a flaming seam at its far right that matches, if more dimly. The Ingersoll shot at right was taken several minutes later and after a coating of fire retardant foam. While the facing is broken fairly clean on the column edge, the “no plane” damage area to the left of that remains unchanged; the column and its facing remain - counter-intuitively - intact.

At lower left in the top photo below, note a major crack in the horizontal frame just to the left of column 18. I speculate that at this point, the area there is holding together by weight and habit, but ready to shear, crumble, and scatter along the fault lines introduced by the big thud at 9:38, waiting for a further violent event to trigger the fractures into rifts.
Then the collapse, immediately after which the bottom shot was taken. The facing around the damaged panel has fallen away, but the brick and concrete backing remain about the same. Below that, something has left the whole corner of the frame above and left of column 18 missing, presumably in the pile large of rubble that formed at the foot of the collapsed zone. Perhaps it was some massive pressure that has stripped away the top of that column, exposing re-bar. Although the separation came after the collapse, the point of give is right about there in the red zone of ‘no plane damage.’ And I’m pretty sure column 19 on the right also shows its later damage at this point, and even before collapse, though that’s less clear. Coincidence? If there was no continuity of wing damage, then why is there no continuity of the column here?


Referring to Augustino's post-shoring photos of the alleged wing gash, Ranke told Above Top Secret.com member Dark Blue Sky, in no uncertain terms:

“You can't use a post collapse photo if you are trying to assert it was from the alleged impact. Catherder used the same image for the same reason and it's deceived many 10's of thousands of people. Please don't help. There is nothing possible about the damage to the Pentagon in relation to a 757 impact.” [source]

Referring to a blurrier version of the bottom post-collapse shot above that clearly shows the breach of column 18, Ranke furter explained “it's quite clear that even after the collapse the left column was not completely breeched as it was after supports were added days later.” [source] Wrong. It might have been worse by the time of Augustino's photos, but it could only be less clear here due to being a head-on shot. The top of the column’s casing is gone, the corner of the frame is gone, lengths of rebar are exposed, and column 19 seems to have its damage as well, visible even before the collapse.

In summary then, all things considered, the answer to CIT’s original question is that there is about as much continuity to the right wing damage as there should be, which is little that was plainly visible after impact, but more that revealed itself after the collapse. And again I'm only left wondering if they really misread the evidence this wrong or are just pretending to have done so.

Tuesday, February 5, 2008

A FORK IN THE ROAD

A FORK IN THE ROAD: THE ANOMALOUS MEMORIAL
Adam Larson / Caustic Logic
The Frustrating Fraud
February 4 2008 3am


Looking at the testimony of Sgt. Chadwick Brooks as presented in The PentaCon, I found this sideline that, the more I look, gets more and more interesting. When asked where the plane he saw came in from, the Defense Protective Services officer pointed back to some trees and an oddly looming three-pronged structure in the near distance behind them. This curious form is seen above relative to the Citgo’s north canopy, with Brooks seeming to wear it like a crown and Lagasse looking back towards it almost as if noticing it for the first time and wondering ‘what is that thing?’ That’s what I was thinking anyway. It could serve almost no practical purpose, and looked like a work of art or monument of some sort, and right next to Arlington National Cemetery. So I dug in and found matching images for “memorial” + “Arlington” + “three spires.”

I quickly found that it was a recently-completed memorial to Air Force airmen who have died in the service of their country. MSNBC ran an Associated Press article about its dedication on October 14 2006 (less than a month prior to the Lagasse-Brooks interview). Just south of the cemetery, on a hill overlooking the Pentagon’s west side, roughly 30,000 people attended and listened to the keynote address by President Bush:

"Under these magnificent spires, we pay tribute to the men and women of the Air Force who stand ready to give all to their country. And looking from this promontory to a place once filled with smoke and flames, we remember why we need them." [1] [Youtube video of dedication ceremony]

A squadron of Thunderbirds then buzzed the area, executing the famous “bomb burst’ maneuver the memorial was meant to evoke. Usually done with four jets, the monument’s three upward arcs are based on the “missing man formation” traditionally flown at Air Force funerals. The first official ceremony was held the next day when the Secretary of the Air Force laid a memorial wreath at the base of the spires, capping the completion of a 30 million dollar, fifteen-year struggle to get them erected. [2]

The Air Force Memorial Foundation (AFMF) was formed and given 501(c)(3) status in 1992 to pursue a memorial, led by a five-man advisory committee including Ross Perot Jr. [2] The foundation was mostly funded by private contributions; Wayne Madsen wrote about how the project was funded “largely […] with donations from Lockheed Martin, Boeing, Northrop Grumman, Raytheon, United Technologies, and even the United Arab Emirates Air Force.” [3] The original plan was to place the memorial at Arlington Ridge, near the Marines’ Iwo Jima memorial, but all through the 1990s the AFMF remained locked in extended legal battles with the Marine Corps over this plan. In October 2000 President Clinton signed legislation to give them more time, and the DoD offered an alternate site at the east end of the Navy Annex, near the intersection of Columbia Pike and South Joyce Street. This offered the foundation a way around more costly litigation and the opposition of Congressional ex-Marines, but planning for the Arlington Ridge location continued.

The board members were still weighing their options when the 9/11 attacks occurred, including a near fly-by [see below] of the alternate site by Flight 77 on its way into the Pentagon. Some time in October 2001, the AMFM chronology states, the board of directors “acknowledges realization for relocation” to the Annex grounds. Over the next two months as the nation dealt with Afghans and Anthrax, Congress worked to include the site change as a rider on the 2002 Defense Authorization Bill, which President Bush signed on December 28, officially giving the Foundation up to three acres of the Naval Annex property on which to build. [2]

In 2002 the AFMF gathered its funds, solidified the site, and selected Pei Cobb Freed & Partners to design the memorial. It would be the final project for architect James Freed, previously responsible for the US Holocaust Memorial Museum. [4] In 2003 they got the paperwork lined up; in February the FAA decided the giant arcs would not be a "hazard to air navigation."” [2] Formal groundbreaking of the site was held in September 2004, foundation work done in 2005, and construction of the spires began in February 2006. On September 22 the last of fifteen spire segments was installed and the monument essentially completed, three weeks before the dedication ceremonies. [2]

Not everyone is a fan; Wayne Madsen wrote of how the monument sits “jutting into the sky and dominating the Washington, Dc skyline […] reminiscent of something Nikita Khrushchev would have built honoring the Soviet space program in a Soviet Potemkin city.” [3]

I’m not sure yet of the relevance of this memorial to my study of the Pentagon attack and those studying it, but a few oddities are at least worthy of note:
First, obviously, is its location; Madsen noted the spires jut out of a spot “right on the Pentagon crash flight path.” Can this be pure coincidence? It must be, most would think, since the site was selected a year before 9/11. And it’s not exactly on the path anyway; to be more precise, it’s placed along the line of a right-over-the-Citgo-flight path, between the CIT-crafted North path and the official one on which tons of damage happened five years before the spires went up, one year after the site was offered, and a few weeks before it was accepted.

Looking across the Annex from the west, I’m reminded of Edward Paik’s drawn flight paths that, oddly enough, point almost right to the monument, which was being assembled at the time he drew them.
Seen from this view it seems almost like a giant pitchfork they wish had been there to stop the plane that day, a symbolic retroactive warding-off of evil spirits. It is placed just a bit too far to the north, but even if they had truly meant to mark the very spot (presumably a post-9/11 decision to shift it a bit), this is the closest they could get without tearing out the curve of Columbia Pike. Even the most dedicated symbolism must sometimes yield to necessity.

A second oddity that stands out to me is its height – the highest of the three spires rises 270 feet above “the 3-acre elevated promontory site.” [2] This number sticks to me because of the radar altimeter reading in the last recorded frame of Flight 77’s FDR; 273 feet above ground level. This was probably not recorded adjacent to the memorial site, but rather a ways back. Nonetheless, it almost seems someone was trying to place those spears right at the belly of that plane if it should ever come back and try the same thing. However, it seems by looking at a few photos that the tallest spike is pointing northwest, which is not where the FDR shows it coming from, and it becomes clear I’m probably just reading too much into this.

Thirdly, the timing of its construction with CIT’s 2006 research trips means there was a brand new, gaudy, overwhelming structure being built right in the zone people were remembering their flight paths from. With the monument often cited as being ‘right on the flight path,’ it can’t be ruled out that it could have inserted some distortion into their recollections of where the flight path was.

Finally, I’m astonished that I’m just now learning about this. I may’ve heard a mention here or there, but had never been specifically aware of this mammoth trident amongst the contended flight paths. For one thing, it’s not shown in the supposedly current satellite views at Google Maps I’ve been looking at regularly for the last year and a half (hence the graphic I made, above). So now I’m aware of it and up-to-date, and would like to close on a poignant note speaking back to the subject of memorials to those who’ve given their all for whatever they’re calling ‘freedom’ these days, Wikipedia’s entry notes: “Although the current [memorial] design is somewhat overshadowed by the Navy Annex at Fort Myer, that facility is slated for demolition by 2010 with the site to be used for the southward expansion of Arlington National Cemetery.” [4]

Sources:
[1] Long-awaited Air Force Memorial dedicated
Arlington monument honors the memory of those fallen in youngest service. Associated Press. updated 8:12 p.m. ET, Sat., Oct. 14, 2006 http://www.msnbc.msn.com/id/15264524/
[2] http://www.airforcememorial.org/memorial/chronology.asp
[3] http://www.disgrunt.com/blog/2006/12/05/weird-horns-statue-dominates-washington-skyline/
[4] http://en.wikipedia.org/wiki/United_States_Air_Force_Memorial

Sunday, February 3, 2008

EASTMAN AND THE DECOY THEORY

LAGASSE AND EASTMAN PART 1: EASTMAN AND THE DECOY THEORY
Adam Larson / Caustic Logic
The Frustrating Fraud
January 12 2008
Last update 2/25/08


Update 2/13: I’ve made numerous edits for flow, tightened of parts that rambled, improved grammar and spelling to compensate for limited English proficiency of Lagasse, Eastmann, Desmoulins, and myself.

Intro: The North Path Star Witness
The purpose of this ambitious three-part series is to explore the roots of Sergeant William Lagasse, a Pentagon Force Protection Service dog handler, as a witness to the Pentagon attack. For those who don’t know, Lagasse is arguably the star witness of the flyover-theory-promoting video The PentaCon, produced by Citizen Investigation Team (CIT) and released early 2007. Lagasse is the most convincing of their four witnesses of the north-of-the-Citgo flight path that proves, no matter what Lagasse himself says, that the silver 757 he saw must have flown over the building instead of into it. Among their growing cast of witnesses, the good Sergeant is also the longest-running and in many ways most perplexing player of the north-path tragicomedy. He was brought to their attention, if not directly funneled to them, by controversial 9/11 researcher Dick Eastman. It was Eastman who discovered the officer in 2003 and publicized his north-of-the-Citgo account. This is a curious episode worth looking at in some detail and in context, which is where this story will begin.

The Only Way?
Yakima, Washington-based e-mail warrior and 9/11 researcher Richard “Dick” Eastman is trained in economics, and is apparently a religious man; an acquaintance has described him as a "fool in Christ" and notes his “high cost of Christian discipleship standards.” [link] Adopting a fiercely populist, libertarian, anti-N.W.O. stance, he seems excitable and is said to have gotten rather belligerent and confrontational with fellow 9/11 researchers, quickly dismissing them as complicit in the cover-up if they happen to disagree with him. Eastman is well-known to be staunchly ‘anti-Zionist,’ and sometimes accused of anti-Semitism; he’s wondered aloud, as many have, if 9/11 were a Mossad operation, but for the woes of the world he doesn’t blame all Jews, just the ‘86%’ who support Zionism [source]

I suspect there’s at least some truth to some of Eastman's broader concerns, or the ones he appeals to, and I appreciate his emphasis on grassroots, de-centralized action to fundamentally alter the way things work. But then I disagree strongly again with his ideas on waking up the masses; in a supposed farewell letter issued early 2004, he summed up 9/11 in context of his world view. What was needed was to:

“...discredit the entire ruling elite in government, big business, big finance, big law, big media, big organized crime, big defense - and there is only one way to do that to the degree necessary, only one way to discredit the entire structure so as to bring it down by instant popular demand - and that way is to expose the truth about the 9-11 black-op false-flag inside-job mass-murder frame-up - and the only way to expose the frame-up is with the evidence that shows beyond all possibility of doubt that the Pentagon was not hit by a Boeing airliner.” [emphases mine]

By this definition we’re all screwed. Luckily I also feel his assessment of our global options was wrong and there’s still hope even though an airliner did crash itself into the Pentagon. Either way, he feels his no-757 case was a serious boon to the cause of Truth and global justice – if not its only salvation.

In early 2003 evidence was more scant than it is now, and mystery flourished with Meyssan and others insisting on a missile or small drone strike. Amid the gathering din, one research piece by Eastman rose above for its ambition (three parts!) and apparent sophistication of info-mulching: What convinced me that Flight 77 was not the Killer Jet, published by the equally concerned American Patriot Friends Network. As with other no-757 impact theories, Eastman’s analysis rests heavily on the physical evidence that ‘disproves’ a 757 impact; he found the entry hole "too small to accommodate a Boeing 757 [with] a width of no more than 10 feet.” (90 feet wide in reality) He marveled at the unmarked lawn, and decided the debris evidence available at the time was ‘portable’ and so probably planted.

He also found that the famous security camera stills showed a blackish missile hidden from view but trailed by white missile exhaust (based on a common mix of errors I’ve explained here). But the key problem with the missile theories then purporting to explain these same misread ‘oddities’ was the widespread awareness of dozens of eyewitness reports of a 757 flying in that way and even impacting. Eastman was among the first to find a way to (apparently) acknowledge this class of evidence with bizarre treatment that still allowed a non-impact scenario, and the Flyover theory was born.

The Killer Jet, the Light Poles, and the Decoy
In essence his theory, at least as it stood at that point, is this: the decoy he insists on calling Flight 77, a large two-engine silver airliner painted with American Airlines standards as seen by many, flew in from the west, while a drone ‘killer jet’ came in synched, below it and from a similar angle, fired a missile, and then itself impacted the Pentagon as Flight 77 passed over and disappeared. Eastman offered “a profile of the remote-controlled killer jet,” in essence a "‘non-standard’ General Dynamics F-16 aircraft.” There were no eyewitness reports of an F-16, just one ear-witness (whom Eastman doesn’t even cite) who thought the jet sounded like one. An F-16 has a single engine centered in the rear compared to the two massive RB-211 engines under a 757’s wings. “Only one engine broke through the C-ring,” Eastman states based on something or other (actually neither engine seems to have made it that far); “The one engine is on a line from the downed lamp posts to the entry hole to the last exit hole -- indicating a single engine jet.” A Boeing as said to have done all damage and widely reported as impacting low is three times as long as an F-16 and at least thrice as massive, and thus seems a better match for the damage necessary to reach the exit hole. But if the entry hole were only ten feet across, no Boeing could have entered, so F-16 it must be.

Also take note that the five downed light poles match a 757’s wingspan of 124 feet, and know that an F-16’s wingspan is 33 feet. The accused killer doesn’t seem a candidate to take down the poles, and at first Eastman denied any were downed; “Ron Harvey says that 5 poles were downed. Ever hear that from any other source? […]I have not seen a picture of five downed poles. If there is one I would like to ask whether it was faked […] you will notice that in the picture Harvey does send that the downed poles are not shown with the Pentagon wreckage in the background. ” [link]Later he clarified “I have long acknowledged the existence of the poles as soon as I finally got my hands on an actual picture of one (Ron Harvey was not forthcoming with me at the time)" [link]

“In fact it was the pole data in contrast to the witness accounts.” Eastman continued, “that first suggested the presence of two converging aircraft paths.” In this construct, the impact/pole damage path still is attributed to the killer F-16 by the time of his 2003 piece, which explains “the light poles […were] hit by wind force concentrated in a vortex coming off the wings, rather than being hit by the aircrafts fuselage or wings, denting and fallen forward.” Yes, he thought (or said he did) that air was responsible for bending, cutting, and crimping these aluminum poles so acutely.
So his conclusion, based in part on the light poles, was of two converging flight paths, with the implausible F-16 doing the damage “while Flight 77 […] in fact flew over the building, concealed immediately from most witnesses by fire and smoke rising to the rear and by the "blend-in" environment of Reagan National [Airport],” where it ten landed. With that airstrip just a couple thousand feet behind the Pentagon, the incredibly tight loop required to reach it, according to French researcher Jean-Pierre Desmoulins, “shows how imagination can bring somebody who doesn't know physics and laws of flight to propose nonsense.” [link]

Riskus Dyslexia and the ‘South’ Path
Attack witness and skateboarding enthusiast Steve Riskus, according to his own account, was “traveling on route 27 towards 395,” which means he was headed south with the Pentagon to his left, when the airliner “crossed my path from the right,” or west, “about 100ft in front of me and crashed into the pentagon.” Within seconds he was out of his car and taking photos of the scene, revealing his excellent view. “I could see the "American Airlines" logo on the tail as it headed towards the building,“ his seminal account clarifies, and Eastman is quite sure Riskus saw the Boeing decoy, but he also clearly states “I saw the plane hit the building,” even though it was the killer jet that did that. “From where Riskus was, the low and level approach of the killer jet was camouflaged by the "busy" background,” Eastman concluded, so he simply presumed the flyover jet is what caused the explosion. That’s it. The core assertion of this account is disposed of quickly, the remainder free to pilfer.

Riskus’ scene photos reveal his approximate location, across from the heliport tower just north of the impact point. The graphic at left is from the text-graphic Dick Eastman used to convey his position, which looks about right except one thing – at the bottom in red are labels southwest and northwest of crash, which do not line up with his description or the evidence. The poles were south of the impact, not north, and if Riskus were south, the Pentagon would be to his right, not left. Eastman clarifies that he thinks “Witness Steve Riskus was headed north on the turnpike, south of the crash site, when he saw Flight 77 pass by.” Just imagine for a moment this guy’s compass: east is to the left of north? He has the whole area half-backwards, and it carries through into his analysis of the killer jet’s “straight northwest to southeast line” taking out the light poles “north” of Riskus, “to that final hole where the bare engine of the plane exited.”

Eastman caught the error eventually (see part II), and it does not really effect his overall findings, anyway; if we re-orient his N-S axis while keeping the E-W, the decoy would fly north of the killer jet’s path, given Riskus’ standing 100-foot measurement. This roughly gives us a flight path very north of the Citgo, over the middle of Arlington National Cemetery. This is in no way a candidate for the light pole or building damage, and would have had to have flown over. If not for the dyslexia that has him reading north as south, this is the best evidence yet for a north path and flyover, an issue that will clarify itself and come into play in the next installment. By my measurements, the official 77 path/Killer Jet path would have crossed Route 27 roughly 1,000 feet ahead of Riskus, which leaves me wondering if 100 was a typo, a grossly imprecise estimate, or whatever Eastman took it for when he noted "there is no feasible path by which the killer jet could have hit those lamp posts, flown to within 100 feet of Riskus and then returned to the northwest to be able to enter at the crash point at an angle that would enable it to rendevous with the exit hole in the C-ring. No jet could do it, and especially no Boeing 757 airliner could do it." When J.P. Desmoulins looked at Riskus’ account he found that Eastman “developed this "100 ft" statement, making it one of the bases of his theory," while it seemed more likely that this number was "just an irrelevant statement" on Riskus' part, a casual and far-off estimate of an unprecedented sight.

Dividing One Plane Into Two
At one point Eastman confidently summarizes “all evidence and witness testimony presented in this paper are consistent with the [killer jet] thesis.” It’s in the use of eyewitnesses that the piece shines. It seems it was no simple task to see the patterns, and some careful prep work had to go into the process. To make 77 appear the over-passing decoy, he set about Minimizing impact accounts associated with it, as we’ve seen he dismissed Riskus as visually fooled but took a different tack with Tim Timmerman, following his cited account, which was clearly describing Flight 77, with the comment: “most significantly, he actually states that the plane he was watching "didn't appear to crash into the building"!!!!” [bold mine]. Really he said “it didn't appear to crash into the building; most of the energy was dissipated in hitting 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 right before impact, and I saw the airplane just disintegrate and blow up into a huge ball of flames.” Sounds like an account he shouldn’t have cited – a ground impact and then into the building is about the opposite of a flyover Eastman feels happened, which would make this witness a liar, which would leave one wondering why he’s quoting liars. In fact, Eastman once called Timmerman and Penny Elgas “two witnesses that I believe have lied about their experience.” [source]

In all Eastman analyzes sixteen witness accounts of the plane(s), not all verified by me as free of the selectivity shown with Timmerman’s, and divides all but three of them into “two distinct groups, each seeing a different plane, on a different path, at different altitude, with different sound, at different speeds.” Some saw “an airliner, shiny, red and blue markings, with two engines, in a dive, and flying "low" in terms of one or two hundred feet, and silent (engines idle)” Others saw “a plane that came in at tree-top level, at "20 feet" all the way, hitting lamp posts in perfect low level flight […] engines roaring; pouring on speed; smaller than a mid-sized airliner.”

If we combine the two descriptions we get a composite of the one plane official story. Conversely, by fragmenting the descriptors and creating two piles he creates two jets. Here is the roster: Timmerman, Campo, Munsey, Peterson, Riskus, Robbins, and one anonymous witness saw both the decoy Flight 77 and the impact of same, but either the part where they saw it hit was removed and ignored, or they were tricked. (Robbins “saw the Boeing that did not crash and the explosion and smoke made by the killer plane that did.”). O’Keefe saw the decoy Flight 77 and heard the killer. Vaughn saw the decoy but no impact. The account Eastman shares has Joel Sucherman seeing a “large plane” that was “not going to make it across the river to National Airport” as it passed too fast for him to see “any of the horror- struck faces inside.” Yep, Sucherman saw the F-16, since it “was 20 feet off the ground” and he actually re-prints “the plane slammed into the west wall of the Pentagon.” Gaskins gives nothing Eastman uses besides altitude clues (making it 77 he saw), while Liebner’s is inconclusive for lack of altitude clues. One anonymous “falls between the two categories,” using adjectives that could describe either decoy of F-16.

That’s 14 of the 16, and the final two comprise Eastman’s third category, seeing both planes; He reports that Kelly Knowles saw “two planes moving toward the Pentagon, one veering away as the other crashed.” Actually she was miles away, and saw only the tail of one plane pass and then another also disappeared to the east “a few seconds later.” This is almost certainly the C-130 cargo transport sent to examine the scene, passing over the Pentagon about two minutes after the crash. [source] Keith Wheelhouse was at Arlington National Cemetery when, as Eastman states, he "saw another plane flying near the jet that crashed." As widely reported, one article from three days after 9/11 implied they passed at the same time; “[Wheelhouse] 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.” While another article published the next day clarifies that Wheelhouse says the second plane was probably a C-130 [source, Eastman decided he saw the killer jet and the decoy.

Even as he dropped the known ID to bolster his two-plane theory, Eastman was aware of the C-130, and mentioned it once in the paper. He noted the cargo plane could have aerially planted the 757 debris indicating impact, especially the “wheel in the parking lot," as it passed "just 30 seconds later.” It is never mentioned in connection with two-planes accounts despite at least one that was quite clear on being a C-130 witness. Therefore, this graphic pretty well sums up how the killer jet theory works: [r-click, new window for full-size]

A Killer Theory… NOT
Here we have a proposition that Eastman calls “the only way” to “discredit the entire ruling elite […] to the degree necessary.” And this way, this bridge to victory offered up to support the weight of the world, is strewn with wrecked logic and supported by a teetering tower of poorly piled debris. As I have shown, the Killer Jet Theory is a laughable construct slapped together from misquoted quotes, vague words turned to hard geometry, and that geometry to ‘proof’ of something trumping hard, consistent facts. Its architecture is almost entirely of ‘errors’ too egregious to be accidental or to even be mistaken for such. Perhaps each one is a little tip-off to those paying attention that this theorizing isn’t meant to be taken seriously, a wink as he fleeces the less vigilant. A series of winks. A prolonged seizure of the eyelid.

But there are only so many so dumb, and Eastman must have been left a bit embarrassed by his own piece. The bridge was too rickety. Rescue, however, was just a few e-mails away. Already hinting at a decoy north path (if called a south path at the time) based on nearly nothing, out of nowhere a self-appointed debunker gives the only solid, clear, undeniable north path account yet – Enter William Lagasse and the next post in the series.

Wednesday, January 30, 2008

CIT'S C-130 FINDINGS RE: "FLIGHT 77"

CIT'S C-130 FINDINGS RE: "FLIGHT 77"
Adam Larson / Caustic Logic
The Frustrating Fraud
January 30 2008


Okay, so I'm banned for a week at the LCF for alluding to the well-known fact that Aldo Marquis is an asshole. [the events happen on page 8 of this thread, which is also about the C-130.] I will have more to write (and/or right) on this situation once I get some perspective. It's my first time being banned anywhere and I'm disappointed to find out my computer has been banned from allowing me to ever READ the forum, including the reason for my dismissal, or the answers CIT may or may not have offered to some questions I posed. Luckily I do have a old machine around to get around the IP block, and was barely able to read what followed. I'm not missing much it seems except continued evasion, decreased reason, argument from belligerence and incredible unchecked tirades from the CIT end. Really, some pretty insane activity from Aldo; it's like he wants out and has to do it the only way he knows - get banned for being to 'passionate' about 'truth' and 'justice' for people to handle.

On the other hand, Craig's response to my questions regarding witness Mrs. Hubbard were candid and useful.

But there was no response from either Aldo or Craig to these questions regarding their interpretation of the C-130 flight path and its 'actual' interaction with the fantasy flyover plane:

"Okay, I have a question about the outbound flight. Let's for a moment step back from the debate and go on the premise that your reading, north and west to just about over the capitol mall is correct, after which he describes his interaction with the plane, arcing from his left to north an then east, 10:00, 11:00 12;00 and descending. This part I agree with your reading, I think.

1) Is this graphic about right for what he saw that plane doing and about where?
2) You've mentioned reports of the plane being southeast of the capitol. Was this before or after this passage do you think?
3) Does he describe the plane as silver or white? Is this the flyover White Jet he saw or something else?
4) Do you think he may have been seen the C-130 and is mistakenly describing its flight path? (kidding)"

I'm not being facetious or anything here; I'm truly baffled by the implications of the C-130 being just west of over the mall when "Flight 77" came in ahead of them from the left, curved to their north and east, descending on the way. From what I have seen and heard so far of CIT's take, that would put the plane looping north of the capitol, at some point prior to its impact. I therefore open this post to comments from CIT if they wish to explain their findings in more detail to help us all determine the SIGNIFICANCE of this interpretation. I'll copy all relevant comments and thoughts into this post before finalizing it. If they have nothing to offer, I'm going to take this path shown above as the best available reading of their C-130 findings regarding the path of "Flight 77."

I'd like to start with the above list of questions as offered at LCF on my way out, and add one more:
5) How much time do you gather elapsed after seeing this arc before O'Brien saw the explosion? "Three phone calls later" = roughly how many minutes? (a range is fine).
---
Update: After he ignored it at LCF and here, I posted these questions for Craig again in an Above Top Secret.com thread. He ignored it there as well but finally sent me an e-mail that reads as follows:
"You are dead wrong about our analysis and I refuse to discuss it in your disinfo thread at ATS or at your disinfo blog. You can wait for our new presentation scumbag.

Why do you keep intentionally spreading disinfo with your confusing ass, contradictory, deceptive ramblings? People see right through you Larson. You are blatantly deceptive. We have exposed you many times over and people do not have tolerance for your lies and spin any longer.

"The u-turn at the end is what is corroborated by eyewitness accounts, O'Brien's own account, and now also a video, taken by Anthony Tribby."

"A UFO for sure."

How can a UFO corroborate anything?

The placement of the UFO does not corroborate the RADES data anyway EVEN IF it is the C-130.

Why are you such a liar?

Why are you so dedicated to defending mass murder?

You disgust me."

---
[BTW: He's lying about the video and radar not matching, and the UFO is almost certainly the C-130. See my video he's talking about yourself here.]
So I’m left feeling like I must be onto something, but having to guess at what the deception I’m accused of actually is. They had been so damn sure it was just over the mall I figured it was leading up to something, but this didn’t seem quite right. It would give us an overall flight pattern like this:
At present then my guess is they have actually placed the C-130 somewhat south of the Capitol. As Craig had earlier said, hinting at a correlation with the Charter Boat Captain on the river south of Reagan National:

"We were always stumped with how O'Brien's account didn't make sense with the 2006 NTSB flight path of AA77 until we talked with our newest witness who was on the Potomac River who reveals that the NTSB flight path is false and that the plane came from the EAST of the river and looped around north timed perfectly with the explosion at the Pentagon!"
[source]

By this mapping above, 77 was looping north and east of the C-130 to NORTH OF THE CAPITOL 'timed perfectly' with the explosion a few miles to the southwest. So I'm left guessing that after all the yammering about how the plane could ONLY be right over the Capitol, that the English language mandates it, that anyone who places it any further south is a dishonest goal-post-moving scumbag... must be qualified. Only CIT is allowed to disregard the words of O'Brien saying "north and west" and a "beautiful view of the mall" to actually be well SOUTH of the mall AFTER ALL, to match up with the loop the Charter Boat Captain describes! The special privileges Citizen researchers afford themselves.

Now I'm unaware of just where the river witness places the flight path, but it's probably not as far south as it would have to be to approach the C-130 as shown on radar. But it is obviously further south than their original 'beautiful view' would necessitate, and shows that O'Brien's account is indeed open to interpretation in CIT's mind, whereas when I had tried to say the same thing as they were INSISTING on the infallibility of that graphic, they said things like this: "Power of suggestion, up is down, left is right, north is south. Lies.” [Craig responding to an incorrect assessment of my video] Or this: "Just because you said it Adam. You can change anything at anytime and it all makes sense. You can say anything, up is down and down is up. I understand.” [Asshole Marquis, both quotes from the LCF thread linked to at top]

So I am "dead wrong" in my direct reading of the same infallible evidence CIT has provided me. So their assessment was wrong. After they insisted it couldn't be. "Up" is "down" now I guess just because they say so, even tho it was a deceptive treasonous scumbag lie at first when I said it.

Duly noted, for the record, yet again... the hypocrisy never stops.

Wednesday, January 23, 2008

THE PREVIOUSLY SUSPICIOUS FATHER MCGRAW: REDUX-THE MASTER OPUS

CIT WITNESS VERIFICATION, PART 1: THE PREVIOUSLY SUSPICIOUS FATHER MCGRAW REDUX: THE MASTER OPUS
Adam Larson / Caustic Logic
The Frustrating Fraud
December 14 2007
Last updated 2/13 1am


FOREWORD 12/07: Since I published the first version of this piece a week ago, it has gotten more attention than I expected, both positive and of course negative. A dedicated denunciation at the CIT forum and two lightning discussion threads at Above Top Secret ensued – one locked and the other still active. Some points were ironed out, some challenges issued, some questions answered and others raised. I have worked some of the more relevant results back into my original piece to make it more accurate and informed. It’s now a long post – tedious in spots but hopefully worthwhile for anyone seriously into the whole PentaCon phenomena. The original is also available on request.
---
The CIT Magic
Lately I’ve been giving some thought to the process by which Citizen Investigative Team (CIT) verify alleged witnesses to the Pentagon attack. As CIT core member Craig Ranke explained in a recent phone discussion, previously published eyewitness accounts of a plane impact are all suspect.

“This is not eyewitness testimony, okay […] we need to talk about it for what it is, which are static words printed by the mainstream media. So until you speak with these witnesses direct and get their first-hand confirmation of these details, these words are merely hearsay. They aren’t evidence at all. That’s a fact.” [1]

The magic of CIT is of course their tracking down witnesses, preferably previously unpublished ones, and confirming what they really say they saw, removing the MSM distortions where applicable and countering MSM ignorance elsewhere. When it came to their Citgo witnesses featured in The PentaCon, they placed their locations carefully on a map, determined their point-of-view, and had them describe what they saw, clarify details, and draw one or more lines in satellite maps to verify the direction they saw the plane flying. When possible, verification was found that the witness truly was there. This sounds good enough, and the method has yielded numerous accounts confirming the north-of-the-Citgo flight path that necessitates a fly-over of the Pentagon and all physical evidence somehow faked in an elaborate and well-coordinated effort.

They insist they have not yet found a south path witness who actually saw the official flight path matching the damage both before and inside the building. As Lyte Trip, Craig explained to the JREF debunkers “We have searched high and low for a witness to go on record contradicting the citgo witnesses north of the station claim. If you can find one let us know.” [2] This lack of verified support for the ‘official’ path has led Craig and CIT to trumpet everywhere they’re still allowed “the unanimous north side of the citgo station claim,” the one that necessitates the unseen flyover and mind-boggling feats of fakery.

But is this really true? While the four main interviews presented in the PentaCon strongly indicate a north path and impact (one of which must be wrong), another interview they did in search of confirmation came out much more murky. As I read it anyway, this one raised some awkward problems for their north-side flyover-n-fakery claim, prompting an ugly solution.

McGraw Verifies
The witness in question is Father Stephen McGraw, a Catholic priest filmed on location after the attack ministering to the injured. Like Father Merrin in the Exorcist, he emerged from the mist of dubious photos and reports, let the team into his own church for a videotaped interview and verified his account for the enlightenment of all. Key portions at least of his interesting and telling interview are presented in their video From the Law to The Lord, viewable below.
Page link
Here is Father McGraw’s previous so-called ‘eyewitness account,’ the static words attributed to him by the mainstream media, and further compiled by researcher Eric Bart, the master (until the arrival of Arabesque of course) of gathering such ‘unconfirmed hearsay’:

"I was in the left hand lane with my windows closed. 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. "There was an explosion and a loud noise and I felt the impact. I remember seeing a fireball come out of two windows (of the Pentagon). I saw an explosion of fire billowing through those two windows. "He literally had the stole in one hand and a prayer book in the other and in one fluid motion crossed the guardrail," said Mark Faram, a reporter from the Navy Times who witnessed McGraw in the first moments after the crash.” [4]

This original account strongly supports the official story, and lends credence to that fateful light pole smashing into Lloyd England’s cab, which would become an obsession of CIT’s. The good news that the citizen investigators will most often mention about this interview is the witness’ failure to recall seeing the light poles actually get hit by the plane, and they take him on his word here, and use this to support their contention that no one saw this happen (except of course Lloyd) and therefore they were probably simply dragged into place by the road at some earlier time. This despite the fact that he was square in the middle of the poles-down zone, according to his post-confirmation placement in the video (which is an issue of contention, see below). Lights 1, 2, and perhaps 3 were down behind him before he was aware of anything wrong, and apparently he didn’t see poles 3, 4 or 5 downed ahead of him, with all of perhaps 0.1 seconds to sharpen up and pay attention to detail. He spoke of seeing the damaged taxi and light pole on the road by it (pole 1, behind him and to the left in the graphic here, directly from their video), and deduced after the fact how the evidence wound up the way it was.

Problems: Not PentaCon Material
So far, this confirmation would seem helpful to the CIT case, and they have used it to support the no-pole-witnesses aspect of their program. But for all the reasons that can be found for McGraw supporting or not refuting the north side claim one problem is evident from the outset; north path necessitates a flyover, which requires a pull-up followed by a high-level non-impact. Neither is present in this video-verified account of a witness with a superb view.

Showing that verified accounts don’t always change much from their ‘static’ forbears, McGraw confirmed the words earlier attributed to him regarding its placement 20-25 feet “over the top of us,” before which it struck a light pole, and after which “it came in controlled and straight […] as if for a crash landing.” When asked, he couldn’t recall the generator trailer being hit but, he said he ‘picked up’ a memory from others of the plane bouncing on the lawn. It didn’t literally do this, but this persistent impression might be a clue that it was that low – which it would not be if ‘pulling up’ to fly over. His hand gestures repeatedly indicate a slight nose-down pitch consistent with an impact at the ground floor. He confirmed seeing flames billowing from the windows after the plane “disappeared basically into the building,” and when asked to clarify that it entered the building he responded “yes, yes, yes. I definitely watched as it disappeared into the building.”

To hear CIT talk, of all the witnesses who report seeing an impact, which is all of them so far who were in a position to see, all were allegedly deceived into seeing this despite the sly flyover through the engineered pyrotechnic blaze they merely took for the crash. But in our phone discussion Craig emphasized that “very few of these reports even […] are specifically saying they saw the jet enter the building. […] Most of them were not in a position to see the impact side of the Pentagon or even the Pentagon at all.” [1] This has no bearing on McGraw. Craig also frequently cites trees blocking the view of impact for some witnesses headed northbound on Route 27. For some northbound witnesses further south this is true. It’s not true for Father McGraw.

Based on CIT’s own placement of McGraw, he would have had a near perfect view of the final stretch of either scenario, and he says he saw it fly “over him,” then low enough he thought it bounced on the lawn, and finally a triple affirmation that he witnessed the direct impact along that line. Clearly in CIT land this cannot be. He’d see much of the pull-up and probably part of the over-flight, but as with all CIT-verified witnesses so far, he fails to mention these. Unlike the ‘many’ Craig wants to focus on, McGraw’s account has no excuses. The Father passes the shrubbery test, it seems, and has now verified that he watched the low level impact, which strongly implies the poles were also cut at that time by that craft.

Problems: A South Path Witness?
“[McGraw] says he did not see the approach. This is fact. He says he did not know the plane existed until it was over his head. This is fact. This means he SAYS that he is NOT a witness to what side of the gas station it flew. This is fact. His account is not a definitive north or south side account either way because of these FACTS." – Craig Ranke [7]

While the citizen investigators have never tried to pass McGraw off as a north-path witness, by CIT standards, the problems we’ve examined so far are not enough to bar his inclusion in the growing pool. For the team, McGraw’s failure to remember seeing the poles go down further confirms that they did not fall at that time, which could indicate a north path flyover. In our discussions, Craig insist there are no clues directly contradicting this trajectory, and some supporting it, and his report of impact is nothing new; all their Citgo witnesses report this as well. Craig finds it at least a lesser possibility that McGraw truly was “deceived in this 1 second military sleight of hand illusion just like the CITGO witnesses were.” [5]

However, they must know that at this close angle, no simple perspective trick will do to leave such a witness confusing an 80-foot-plus flyover with a ground-level impact no matter what side of some gas station it passed by. And no matter the tortured logic chains anyone might concoct, I believe Father McGraw is a south path witness, first and foremost because for so many other reasons I already believe the plane came in on a south path and I believe McGraw’s video-verified account. Previously I’d presented his south path testimony as self-evident fact. I wouldn’t do this without reason, but I was hasty, and the too-sure stance prompted a strong reaction from Ranke who claimed I ‘made it up.’ He went so far as to call my piece “nothing but a way for Larson to spread more speculative lies about our motives and methods in obtaining evidence while furiously defending the official story. […] the backwards logic is apparent and the most egregious that I have heard coming from anyone who allegedly doubts the official story.” [6] (emphasis mine: what the Hell is a 'speculative lie?')

As soon as debate was opened, I realized and admitted I’d been too dogmatic about the south path aspect of McGraw's account. Craig instantly declared “the entire premise of your blog is unjustified” and demanded “it should be taken down and retracted if you have a shred of integrity.” [5] Now even if I put any stock in Craig Ranke’s advice on how to maintain credibility, I’d still disagree that a full retraction is in order. However I need to moderate and clarify and, while I’m at it, solidify my position.

Keeping in mind the alleged position and orientation of the witness (as seen above, and facing north, or up.), and that the official plane would come up from behind him and from the left, I believe he is a south path witness for these reasons
1) The south path happened and I want to believe he was there and is honest.
2) His "just before it got to us" descriptor for where the plane hit the pole that hit the cab is a further clue of his perceived path; from behind and left to ahead and right. The only poles ‘before’ them on a L-R path, which either north or south would be, are to the left. This only describes poles 1+2, which were also behind McGraw. Everything else was to his right, so calling any other pole ‘before’ would be illogical.
3) The plane coming in ‘right over’ him makes most sense at the location he’s shown in the video if the official path were true.
4) McGraw’s ‘deducing’ the pole was clipped by the plane might indicate that the poles were knocked down on the flight path he saw. Which would make him a south path witness, since no poles on the north path were downed (4 and 5 are the closest, and the one Craig's hhinted towards). IF he weren’t fundamentally confused about where the pole were in relation to the north path he saw (like Lagasse was).
5) It seems to me that his gestures indicate back-to-front (south to north) motion as well as left-right. Gestures: “the sensation of something coming over the top of us” and gestures back to front twice (2:54 in the video) and later ‘he crashed right into the building’ accompanied by a forward flick of his hand (4:55). When indicating the cab’s position, he reaches far to the left or perhaps back and to the left (3:07-3:17). I failed to include it in this graphic, but at 3:40 McGraw distinctly turns his whole upper body to the left while reaching further left or behind to indicate “the evidence of the pole having been knocked over.” He is looking more forward than right as he recalls seeing the plane’s flight path after passing over him (4:14), when he’d be looking hard right if under the north path.
The subject's gestures: watch the video (embedded at the top) and judge for yourself.
6) Also just as a north path requires a fly-over, a real plane impact requires an approach from the southwest and would have the poles hit and ‘directly over’ McGraw in the location shown. He says this is what he saw – a real impact into the building.

However there are some points of ambiguity; as valuable as it is as evidence, there are always factors to keep in mind with eyewitness testimony, especially if it matches all evidence (??). As pointed out by Craig and others the following must be noted:
1) He did not see the plane before it passed over him, so his perception of the flight path would be limited (he did not see the approach).
2) He only cites seeing one pole, or perhaps only the top of it, after the fact, so it's possible he saw a different pole and ventrred later that was 'the one.' So what pole is the one 'before us' is not clear. #1 is still my best guess personally.
3) Motion from behind the witness to ahead is not entirely clear. Craig says I made it up, and my bias is known. I should have more carefully considered the perspective of his position – is he pointing left or left and back? Craig insists there is no front-back motion in his limited gestures, only left—right, which clearly describes the north path better than the south and therefore I’ve shown him a north path witness and should pull my piece quick before I embarrass myself. Nice try. The best we’re serving at this hour is inconclusive.
4) The two paths ‘converge’ on Route 27. Somewhat. But also the sense of ‘right over’ vs. ‘over-there’ would increase with low altitude, both illustrating and pre-moderating the following ambiguity:
5) The terms “above us” and his gestures from left to right are somewhat vague and could be used for either a north or a south path. ‘Above and slightly ahead of’ might be close enough to consider ‘above’ the position CIT used in their video. While ‘above’ and the location shown fits the south path better, L-R motion describes either path just fine.
6) His actual placement is vague and uncertain. What? Even After the CIT verification magic? I learned this late in the debate, throwing my whole analysis unexpectedly out of whack, but when I asked, Craig clarified “No he did not show us on a map." [5] "The only thing we have to go off of in regards to McGraw's location is his claim that he was directly under the plane this means he would be under the plane regardless of where it flew.” [5] So why was he placed in a spot in their video if he gave no spot? And a spot over which they "knew" no plane ever flew? Why indeed…
Solutions: ’A No-Path Witness?’
The foremost point Craig has raised in response to my analysis is that McGraw "says he did not see the approach” and so “is not a definitive north or south side account either way because of these FACTS." Certainly he was not presented as a witness to any path relative to the Citgo because he didn’t see it as it passed the Citgo. Sounds logical enough. Earlier I’d also noted the absence of the PentaCon trademark – the drawn flight path. Not surprising since they didn’t even plot his location or POV, and the reason is innocent enough; as Craig explains, “we did NOT know about Robert Turcios when we interviewed McGraw so the north or south path was not a focus of our questioning.” [7] So this was early in their search, prior to August 2006. Fair enough, they were just starting so perhaps I should cut them some slack on the point.

So without any north-seeking, south-skirting bias possible, it would seem, what flight path clues did they get from his testimony? Nothing conclusive, as we’ve seen. In fact we aren’t even sure where he was, or whether he was even there. I originally thought the location they picked in their map was the spot he says he was, but really, all we have is "his claim that he was directly under the plane.” So in their graphic they show him under the official path where they had already deduced no plane passed, not attempting to actually place him where he was but rather to “place him under the official path because we are typically discussing his account in the context of the official story.” [5] Please do remember that in CIT land, the official story is now a proven lie.

Why would they fail to determine witness location for anyone whose account they were interested in? As Aldo incredulously notes in the video, it is a bit odd that McGraw didn’t even realize it was the Pentagon he was in front of until after the strike. CIT apparently knew of this before and “Since he claims he is so unfamiliar with the area he grew up in that he didn't even know he was next to the Pentagon," Craig explicates, "it doesn't make sense to suggest he would have even been able to [place his location on a map].” [5]

Yes it does. Just because he can’t identify the building doesn’t mean he can’t say where he is in relation to it – or to the light pole hes talking about, or the plane. Yet all of this is now inconclusive; their failure to bother plotting his actual location is a squandered chance to collect valuable data and arguably invalidates the whole operation. Craig insists “everything we could think of was fully clarified,” and “his position could not be clarified any further. He says he was directly under the plane in the left lane northbound on route 27.” [5] This is the precise area of the too-wide fudge-zone we’re dealing with here. Not being aware of the north-path accounts yet, the guys were officially not thinking in terms of flight path yet, but they could hardly have verified this guy any more sloppily if they actively wanted to not discover his flight path.

Eventually Craig decided to class McGraw as a "NO PATHER," “since he specifcially claims he didn't see” the path, which he in fact did see and describes as ‘controlled and straight” into the building. Not the whole path of course, but enough to indicate a line that could be easily projected back if we but knew what it was. We have no geometry here, no structure, just a rubbery mesh of flexible words that could perhaps be pegged to the north path superstructure. No… not quite. So he goes on a different pile.

None of this makes sense in an effort to verify or confirm what a witness saw – but it does jive with a presumption of massive lying. When I mentioned McGraw ‘picking up’ a memory from others of the plane bouncing on the lawn, a clue against the pre-flyover pull-up, CIT responded “it indicates a propensity to deduce inaccurate information. Or it could be a deliberate "deduction" so you can make this very assertion.” Then they might include him only ‘in context of’ the official lie – an extension of it, an operative of some sort apparently sent in to lie about the impact and ‘deduce’ the poles as consistent, but clumsily give the lie away by failing to say he actually SAW THEM get hit or to pretend he clearly saw it to his left first, just south of some gas station he also couldn't name.

So if he wasn’t there, was he on the north path? Hypothetically, Craig conceded he may be a legitimate witness under the north path, fooled again by ‘sleight-of-hand’ into misreading the flyover (80 feet up) with an impact (ground level). But the clear presumption they proceeded on was that he wasn’t even there. In the video, Aldo notes his verification that he got out of his car about ‘45 seconds’ after the impact,’ but Mark Faram says the priest was crossing traffic to the Pentagon when he arrived ‘ten minutes later.’ Look at where he was (see graphic below - I placed him in the wrong lane) compared to the lawn he was photographed at later. Considering the traffic jam, walking/climbing time, the question of whether he walked down and then crossed the guardrail or vice-versa, and fuzzy rounding on either’s part, and we have how much of a reason to suspect he was trucked in later as another prop?

When I insist McGraw saw a path, if short, and could therefore never be a ‘no-pather,’ Craig let slip “Oh he did did he? It's funny how quick you are to shout conspiracy and accuse all 6 of the north side witnesses who prove the official story a lie as being deep cover operatives but you refuse to entertain the notion that a highly publicized official story witness like McGraw may have been involved.” First, I accuse no one of anything. Second: deep cover? Hardly! Their cover of logic and consistency being so shallow is the main problem. The problem in this case not the plausibility of their conspiracy theorizing, but the fact that this suspicion falls right on this possibly troubling account that they also handled too ineptly to get a reading off of. That is the only point I need make here.

Solutions: The Dark Lord’s Work?
CIT’s decision on how to handle this witness’ testimony is evident right in the intro text to the video published at their site: “This presentation features our interview with former Department of Justice attorney turned Catholic priest Stephen McGraw. We gave him the opportunity to tell his story on camera and to confirm or deny some of the suspicious details in his previously published account.” Indeed, McGraw was for five years a DoJ lawyer, before entering seminary and being ordained, curiously just three months prior to 9/11. His ties to Opus Dei [latin: The Lord’s Work], the mysterious Catholic sect that figures so strongly in The Davinci Code, is not explained in the video (but is here). But this and his previous DoJ connection were fused into a suspicion churning spiel by CIT narrator Aldo Marquis about FBI Director Louis Freeh and infamous Soviet double-agent Robert Hanssen, both Opus Dei and FBI and thus DoJ as well. “We should be more skeptical of highly publicized witnesses shrouded in dubious details who support the official story,” Craig also says, but with no concrete links it appears to be CIT themselves who are ‘shrouding him in dubious details’ when they mention the sect as being “favored by the Washington elite” and list its crimes as “espionage, perversion, government ties, and the well known dubious details surrounding this secret society." All these "are certainly relevant points,” Ranke reiterated, “when considering McGraw's high profile involvement with 9/11," and "if he isn't a traitor/spy like fellow Opus Dei sympathizer Robert Hanssen," the only other option worth considering, which I have shown to be highly implausible, is "that he was deceived in this 1 second military sleight of hand illusion just like the CITGO witnesses were." [5]

Whatever connection all this may have to McGraw, the suspicious just-ordained Father was (allegedly) on his way to administer rites at a funeral at Arlington when a suspicious ‘wrong turn’ brought him in front of the Pentagon. After I mentioned how he was stuck in traffic anyway and late for no reason already, and questioned the alleged oddity of his changing itinerary on account of 9/11 happeing right in front of his face,, Craig clarified “shirking his commitment to a mourning family waiting at the cemetery with their loved one in a casket is most definitely a questionable act.” [5] Perhaps questionable enough to suggest he wasn’t really on his way to a funeral at all?

All of this, once presented ‘in context,’ and what some take as an awkward or 'creepy' air about him, makes for some room for suspicion to flourish and clog the reliability conduit of this particular witness. The issue is not whether or not McGraw, or Opus Dei, is suspicious but rather why do they try so hard with this particular witness while giving the others a relatively free pass on the background check? I think the reason is plain to see and ties in nicely with their differing treatment of his location, point-of-view, and the like. These odd X-factors were certainly known as they decided which token south path witnesses they should interview who could be found just as suspicious - and at least as ambiguous - after their carefully-screened ‘verification.’

There’s been much hullabaloo from CIT over Arabesque and I accusing them of referring cab driver Lloyd England as ‘The Devil.’ As Craig explains “NEVER have we specifically called Lloyd or anyone "the devil.”” [8] Allow me to again clarify that I understand the term is used metaphorically; the overall plot - the attack, the cover-up, the whole sinister operation - was 'the devil.' Clearly however it’s a metaphor for something very bad and sinister, and Aldo says “I've spoken directly to operatives from the Pentagon attack. I have looked the devil in the eye.” [9] So someone they have talked to is a direct window onto this ‘devil’ of an operation. So if this was not about Lloyd, it was about someone, witting or unwitting, a part of this plot, and Aldo got close enough it sent a chill down his spine. In McGraw’s case in fact the metaphorical theology language suddenly becomes more apt. Perhaps he was the one Aldo was thinking about.

This behavior is what might be called, to quote Loose Change Forum member RacerX, “pissing in the witness pool,” and seems designed to clear the end they’re swimming in (I’m not sure if deep end or shallow end is the more appropriate metaphor). Fortunately we saw no charges of sexual abuse involvement alleged against this Catholic Priest, just vague insinuations of an Opus Dei/DoJ operative who ‘just happened’ upon the scene just in time to lend the weight of a priest’s testimony to the lies that would need to be sown. So other south path witnesses, step on up – CIT is still looking for you, and is very interested in hearing your story.
---
Sources:
[1] Phone discussion: Craig Ranke/Adam Larson. November 14 2007. http://frustratingfraud.blogspot.com/2007/11/cit-cl-phone-discussion.html Cited excerpt at 18:00 mark
[2] James Randi Educational Foundation Forums. JREF Forum->General Topics->Conspircy Theories->The testimony of Pentagon police officers SGT Lagasse and SGT Brooks->Page 4. http://forums.randi.org/showpost.php?p=2470954&postcount=150
[3] "From The Law To The Lord" Citizen Investigative Team. Video, 2007. http://www.thepentacon.com/LloydEngland_AccompliceVideo.htm#FromLawtoLord
[4] Bart, Eric. "It Was A Plane Bomb: Eyewitness Accounts." http://eric.bart.free.fr/iwpb/witness.html
[5] Above Top Secret.com. 9/11 Conspiracies->Stephen McGraw: alleged Pentagon attack witness->Various posts, pages 1-3. Thread started by Craig Ranke CIT, December 11 2007, 12:08 PM.http://www.abovetopsecret.com/forum/thread320389/pg1
[6] Ranke, Craig. "Adam Larson's review of From the Law to the Lord, regarding suspect witness Stephen McGraw." Dec 7 2007, 11:13 AM. CIT->Detractors->CIT response. http://z3.invisionfree.com/CIT/index.php?showtopic=43
[7] Ranke, Craig. Comment left 12/8/07 5:13 at this post. Link back from outside: http://frustratingfraud.blogspot.com/2007/12/previously-suspicious-father-mcgraw.html
[8] Ranke, Craig. CIT->Detractors->CIT response-> Caustic Logic and Arabesque's "devil" claim, more deceptive charachter assassination Dec 6 2007, 03:25 PM http://z3.invisionfree.com/CIT/index.php?showtopic=42
[9]