imc indymedia

Los Angeles Indymedia : Activist News

About Us Contact Us Calendar Publish RSS
Features
• latest news
• best of news
• syndication
• commentary


KILLRADIO

VozMob

ABCF LA

A-Infos Radio

Indymedia On Air

Dope-X-Resistance-LA List

LAAMN List




IMC Network:

Original Cities

www.indymedia.org africa: ambazonia canarias estrecho / madiaq kenya nigeria south africa canada: hamilton london, ontario maritimes montreal ontario ottawa quebec thunder bay vancouver victoria windsor winnipeg east asia: burma jakarta japan korea manila qc europe: abruzzo alacant andorra antwerpen armenia athens austria barcelona belarus belgium belgrade bristol brussels bulgaria calabria croatia cyprus emilia-romagna estrecho / madiaq euskal herria galiza germany grenoble hungary ireland istanbul italy la plana liege liguria lille linksunten lombardia london madrid malta marseille nantes napoli netherlands nice northern england norway oost-vlaanderen paris/Île-de-france patras piemonte poland portugal roma romania russia saint-petersburg scotland sverige switzerland thessaloniki torun toscana toulouse ukraine united kingdom valencia latin america: argentina bolivia chiapas chile chile sur cmi brasil colombia ecuador mexico peru puerto rico qollasuyu rosario santiago tijuana uruguay valparaiso venezuela venezuela oceania: adelaide aotearoa brisbane burma darwin jakarta manila melbourne perth qc sydney south asia: india mumbai united states: arizona arkansas asheville atlanta austin baltimore big muddy binghamton boston buffalo charlottesville chicago cleveland colorado columbus dc hawaii houston hudson mohawk kansas city la madison maine miami michigan milwaukee minneapolis/st. paul new hampshire new jersey new mexico new orleans north carolina north texas nyc oklahoma philadelphia pittsburgh portland richmond rochester rogue valley saint louis san diego san francisco san francisco bay area santa barbara santa cruz, ca sarasota seattle tampa bay tennessee urbana-champaign vermont western mass worcester west asia: armenia beirut israel palestine process: fbi/legal updates mailing lists process & imc docs tech volunteer projects: print radio satellite tv video regions: oceania united states topics: biotech

Surviving Cities

www.indymedia.org africa: canada: quebec east asia: japan europe: athens barcelona belgium bristol brussels cyprus germany grenoble ireland istanbul lille linksunten nantes netherlands norway portugal united kingdom latin america: argentina cmi brasil rosario oceania: aotearoa united states: austin big muddy binghamton boston chicago columbus la michigan nyc portland rochester saint louis san diego san francisco bay area santa cruz, ca tennessee urbana-champaign worcester west asia: palestine process: fbi/legal updates process & imc docs projects: radio satellite tv
json version - view hidden posts

Operation Pearl 9-11

by Sheepdog's dig Wednesday, Sep. 17, 2003 at 6:57 PM

What really happened? Here's a good analysis that accounts for a group of questions. Maybe we should ask Kissenger.

Operation Pearl

by Professor A. K. Dewdney

August 2003

Editor's note: Some people have said that this account of the events of September 11th 2001 (a detailed extension of the Valentine-Plissken Hypothesis) is "too convoluted to understand". Actually it's quite simple. Here's a synopsis for those who have a slight comprehension problem or don't have time to read it all:

Four commercial passenger jets (American Airlines Flights 11 and 77 and United Airlines Flights 93 and 175) take off and shortly after the pilots are ordered to land at a designated airport with a military presence.

Two previously-prepared planes (one a Boeing 767, painted up to look like a United Airlines jet and loaded with extra jet fuel) take off and are flown by remote control to intercept the flight paths of AA 11 and UA 175 so as to deceive the air traffic controllers.

These (substituted) jets then fly toward Manhattan; the first crashes into the North Tower and (eighteen minutes later) the second crashes into the South Tower.

A fighter jet (under remote control), or a cruise missile, crashes into the Pentagon.

Back at the airport the (innocent) passengers from three of the Boeings are transferred to the fourth (UA 93).

This plane takes off, flies toward Washington, and is shot down by a U.S. Air Force jet over Pennsylvania, eliminating the innocent witnesses to the diversion of the passenger planes.

Under cover of darkness later that evening the other three Boeings are flown by remote control out over the Atlantic, are scuttled and end up in pieces at the bottom of the ocean.

1 Summary

It is possible to produce the appearance of a terrorist attack on the United States by means that do not employ terrorists, as such, but by the simple substitution of one aircraft for another, particularly when the transponders of the aircraft involved are turned off. The only people who need to be deceived by such an operation are the radar operators at air traffic control (ATC) centers.

The scenario explored here, called Operation Pearl (after Pearl Harbor), has been described in sufficient operational detail that sound judgments can be made about a) feasibility and b) consistency with evidence on the ground. At the time of this writing it is probably the best available description of what probably took place on September 11, 2001.

Under the Operation Pearl scenario, the passengers of all four flights died in an aerial explosion over Shanksville, PA and the remaining three airliners are at the bottom of the Atlantic Ocean.

2 Introduction



Since March of 2002, persons probing the web for further information about the 9/11 attacks could not fail to encounter, sooner or later, a scenario advanced by Carol Valentine. Called the "Flight of the Bumble Planes" (Valentine 2002), it allegedly came from an informant who would only identify himself as "Snake Plissken," the name of the hero of the movie, Escape from New York (footnote 1).



The informant outlined the basic hijacking method in an email message to Carol Valentine, comparing it to a flight of bumble bees. Watching bees as they buzz around among flowers, it is very difficult to follow individual bees, since they are always passing close to one another.



This metaphor translates into the flight of two aircraft in a confined locale of airspace. If the separation between them is small enough, radar operators will see not two aircraft, but one. On the morning of September 11, 2001, according to this scenario, all four "hijacked" aircraft landed at a single airport or air base, transferring their passengers to a single aircraft, the one that crashed in Pennsylvania. Meanwhile, remotely controlled aircraft of various types carried out the actual attacks. The scenario, as presented by Valentine, consists of little more than I have presented here.



Of course, there is a vast difference between an outline and a detailed operational plan. It may turn out, for example, that any attempt to imagine how a specific scheme is implemented runs into snags, as in the attempt by Spencer (2003) to get all four aircraft to one air base long enough for the combined list of over 200 passengers to board a single aircraft, take off and crash near Shanksville, Pennsylvania. Spencer, however, assumed that the takedown of aircraft coincided with the turning off of transponders. In the present paper the scenario is modified to allow takedown prior to the turning off of transponders, assuming that takedown occurred at the first deviation of each aircraft from its flight plan. The refurbished scenario has now been completed to a level of detail that makes it possible to evaluate its feasibility, as well as its consistency with the evidence, as presently acquired and developed.



A scenario named Ghost Riders in the Sky was previously constructed by the author (Dewdney 2002). The purpose of that scenario was simply to demonstrate that alternate scenarios that fitted all the facts (as then understood by the author) could be constructed. The scenario involved killing all the passengers and flight crew with a fast-acting nerve agent, then triggering a software patch in the aircraft flight control systems to direct the aircraft to their various destinations. However, when it became evident that no Boeing 757 had actually struck the Pentagon (see The Pentagon Evidence, also on this website), the scenario was rendered invalid. The Ghost Riders scenario, like the Bush-Cheney scenario, required that the aircraft that struck their respective targets were as advertised, two 767s and two 757s.

The fact that the Ghost Riders scenario must now be rejected illustrates the nature of this inquiry. As in science, hypotheses must be formulated, then tested against the available evidence. If found wanting in the light of that evidence, they must be rejected. It is normal in any scientific inquiry to formulate and analyze more than one hypothesis before one is found that actually works. The same remark also applies to criminal investigations.

3 The Evidence Filter



Any scenario constructed to account for the events of September 11 2001 must pass a graduated test, as embodied in the following items. These fall into three classes:



Suspicious circumstances



Four of the named hijackers were not in the United States.

The WTC towers collapsed without adequate heat stress.



Smaller aircraft accompanied Flights 77 and 93.



Most of the alleged hijackers were rather poor pilots.



Evidence of the alleged hijackers developed too quickly.



Westward excursion of Flights UA93 and AA77 are inexplicable as terrorists hurrying to targets."

Anomalies



The US Air Force failed to intercept any of the flights.



The hijackers' names did not show up on passenger lists.



The hijackers' faces did not appear on boarding gate videos.



Black boxes were missing from all but one flight.

Contradictions



The Pentagon was not struck by a large passenger aircraft.



Cellphone calls alleged to have been made by passengers were essentially impossible.

A successful scenario must at least explain the contradictions and account for a majority of the anomalies. It is of course desirable that it also account for the suspicious circumstances, but no scenario need stand or fall in this regard.



It must be remarked that the only scenario ever supplied to the public via the official media was the Bush-Cheney scenario, that Arab hijackers seized control of the four aircraft and proceeded to pilot them into national landmarks, killing both themselves and their passengers. Clearly, the Bush-Cheney scenario, considered in detail, explains none of the suspicious circumstances, none of the anomalies and is directly contradicted by the facts adduced in the third category. As scenarios go, it is a distinct failure.

4 Technical Elements



The two major technical aspects of the Operation Pearl scenario involve radar and remote control. Radar technology has been with us since World War Two, some 60 years ago. Remote control technology has been around in various forms for at least twenty years. With a basic understanding of both radar and remote control in relation to 9/11, it becomes possible for the average citizen to think for himself or herself.



4.1 Radar Substitution



A radar screen is essentially a circular CRT (cathode ray tube - like a television screen) that displays aircraft within the circular airspace represented on the screen. Radar operators are the only people who can be aware of what planes are in the sky and where they are going. The vast majority of people are completely unaware of what is going on in any large volume of airspace and, when an aircraft passes overhead, can usually not tell one type from another, let alone what airline or aviation company may own it. This observation, while something of a commonplace, has important implications. If an organization wishes to substitute one aircraft for another without anyone knowing it, the only people it has to deceive are the radar operators.



The resolution of a radar screen is the size of the smallest point that can appear there, approximately two millimeters in diameter - a "blip." A typical radar screen, less than a meter in diameter, could therefore be described as less than 500 "blips" wide. If the airspace represented on the screen were 500 kilometers in diameter (approximately 300 miles, a not atypical size), each blip would represent a piece of airspace that is more than 500/500 = 1 kilometer wide.



In other words, as soon as two aircraft get within a kilometer of one another, there would be a tendency for their respective blips to merge. With half a kilometer separation or less, the two aircraft could easily appear as one.



Of course, two aircraft that are that close together run a distinct risk of collision - unless they are at different altitudes. Radar screens are two-dimensional in that they represent airspace in the same way as a map, with the vertical dimension of altitude suppressed. Thus, without additional information in the form of a displayed altitude number, it is impossible for a radar operator to tell whether two merged blips represent a potential collision or not. Altitude information is displayed if an aircraft's transponder is turned on, otherwise, the radar operator has no idea of the altitude at which an aircraft happens to be flying.



If one aircraft happens to be within a half kilometer of another, whether above that aircraft or below it, the radar operator will see only one aircraft, as long as the two maintain a horizontal separation that is no greater than half a kilometer (about 500 yards).



Imagine now two aircraft, both headed for the same approximate point on the radar screen, both with their transponders turned off. One is well above the other but, as the blips merge, both planes swerve, each taking the other's former direction. The operator would simply see the aircraft cross and would have no way to realize that a swap had taken place.



There are many other swapping patterns available. For example, one plane could apparently catch up and "pass" another when, in fact, it slowed after the blips merged, even as the other speeded up.



Another method involves the replacement aircraft climbing out of a valley where it would be invisible to distant radars, even as the other aircraft descended into the valley. Again, a radar operator would see a more or less seamless flight without realizing that he or she had been momentarily seeing not one, but two aircraft on the radar screen.



Of course, if the transponders are turned on, as explained in the next section, such confusion is less likely to occur. Even in this case, however, the deception can be complete if the aircraft switch transponder codes.



4.2 Aircraft transponders



Every commercial passenger jet carries a transponder, a device that emits a special radio message whenever it senses an incoming radar wave. The signal carries the transponder code, a multi-digit number that serves to identify the particular aircraft to radar operators at air traffic control centers. The purpose of the code is to make it clear to ATC operators which plane is which. Other information sent by the transponder includes the altitude at which the aircraft is flying. Transponders were implemented many years ago precisely for the reason that radar blips are otherwise easily confused. Transponders make the radar operator's job much easier.



The pilot of an airliner can turn the transponder on or off in the cockpit. He or she can also change the code by keying in a new number.



Transponder codes for all aircraft departing from a given air traffic control region are assigned by the ATC authority more or less arbitrarily. The only important criterion for the numbers so assigned is that they all be different. It sometimes happens that an aircraft entering the control area carries the same transponder code as another aircraft that is already in the area. In such a case, one of the pilots is requested to change his or her code to avoid confusion.



4.3 Remote Control



A remote control system of the type used in this scenario uses a signal interface that does two things: It reads signals from a ground station and sends signals back to it. Both sets of signals must pass through the aircraft's antenna system. In the Boeing 757 and 767 the antenna system is located in the forward belly of the aircraft.



The outgoing signal from the aircraft would include a video signal from a camera located in the nose or other forward portion of the aircraft. Flight data such as control positions, airspeed and other instrument readings are also included in the outgoing signal. The incoming signal from the ground station would include the position of a virtual control yoke (governing direction of aircraft), thrust, trim, and other essential flight parameters.



The virtual pilot would sit in front of a reduced instrument panel and a video monitor. A simplified control yoke or "joystick" control would also be part of the operator's equipment. The remote pilot would watch the instruments, as well as the video image, making continuing adjustments in the aircraft's flight path, just as if he or she sat in the cockpit of the actual aircraft.



Many claims of the attacking aircraft being under "remote control" have appeared on the web since 9/11, but typically with little or no supporting documentation. The claim of a pre-installed anti-hijacking system (Vialls 2001) has proved impossible to verify. Similarly, claims that Global Hawk technology (USAF 98) was used are rampant, but do not quite fit the specific version of Operation Pearl presented here. For one thing, the Global Hawk system does not use remote visual guidance, but onboard navigation electronics that bypass the need for direct, minute-by-minute human control.



The system invoked for the attacks in Operation Pearl is based on the Predator unmanned surveillance vehicle (USAF undated), a modularized aircraft that can be broken into components for ease of shipping and rapid deployment. One of the components includes a remote guidance module which could be refitted to another aircraft (with appropriate modifications) without the need to strip a predator vehicle. The predator operates under remote human guidance from a ground station that, once deployed, would require as few as two human operators during a "secure" operation.



A second possibility involves a system known as a "flight termination system," manufactured by the System Planning Corporation. (SPC 2000) This system permits hands-on control of a nearly endless variety of aircraft, the control interface being to a large degree customizable. For the purposes of the Operation Pearl scenario, either of these systems might well be adaptable to the remote operations of nonmilitary jet aircraft.



Without question, however, the basic technology for the remote guidance of aircraft has been on hand for many years. For a large intelligence organization it would be a straightforward technical operation to install a remote control system in virtually any type of aircraft, whether a large commercial airliner or anything smaller. The aircraft carrying the installation would be available and prepared in advance, then substituted for the passenger aircraft it was meant to replace.



4.4 Electronic towing



An interesting but different form of remote control is invoked by the Operation Pearl scenario in the "cleanup" phase, namely the disposal of the three aircraft that did not crash in Pennsylvania or anywhere else. I call this facility "electronic towing," It consists of two "black boxes" that pick up signals from an aircraft's data bus, a shared electronic pathway travelled by all electronic signals that control the aircraft. (Spitzer 2000) Each black box can read the bus through the data bus monitor, as well as insert information into the bus. Because the connections are already available, installation of the boxes could be completed in a matter of hours on any aircraft. In this relatively simple form of remote control, one aircraft would be called the "slave," the other the "master." In addition, two 2-way radios allow the black boxes to communicate, specifically for the master box to send its signals to the slave box. Under identical conditions, the slave aircraft will do precisely what the master aircraft does. Such control signals could also be taped and replayed later to invoke in the slave aircraft exactly the same behavior as the master.



To initiate towing, the master aircraft takes off first, while the slave aircraft remains on the runway, completely unoccupied. As soon (or as late) as the pilot of the master aircraft wishes to, a recording of the master signals is played over the radio to the slave aircraft, which then takes off precisely as the master aircraft did. The slave will then follow the master wherever the pilot of the master wishes to go. With a short time delay in the control loop, the slave aircraft would appear literally to be towed by the master, always maintaining the same distance and position behind it. If the pilot of the master aircraft wished to "unhitch" the slave, he could simply cut the control signal. Over the ocean, the unhitched aircraft might fly until it runs out of fuel or it might be blown up by implanted explosives.



[to see the rest of the article and to save BW for IMC LA go to]

http://www.serendipity.li/wot/operation_pearl.htm#footnote_1

LATEST COMMENTS ABOUT THIS ARTICLE
Listed below are the 10 latest comments of 87 posted about this article.
These comments are anonymously submitted by the website visitors.
TITLE AUTHOR DATE
let the game begin Sheepdog Wednesday, Sep. 17, 2003 at 7:14 PM
Yet some questions remain. nonanarchist Wednesday, Sep. 17, 2003 at 9:26 PM
OneEyedMan KPC Wednesday, Sep. 17, 2003 at 9:29 PM
"You praise me... nonanarchist Wednesday, Sep. 17, 2003 at 9:38 PM
implication/compartmentalization Sheepdog Wednesday, Sep. 17, 2003 at 10:08 PM
A fighter goes up loaded with warshots. nonanarchist Wednesday, Sep. 17, 2003 at 10:55 PM
Especially since... nonanarchist Wednesday, Sep. 17, 2003 at 10:56 PM
This is it! fresca Wednesday, Sep. 17, 2003 at 11:58 PM
thank you my three amigos Sheepdog Thursday, Sep. 18, 2003 at 2:50 AM
Of course it doesn't fresca Thursday, Sep. 18, 2003 at 3:00 AM
" Sheepdogs of the world! " Sheepdog Thursday, Sep. 18, 2003 at 3:23 AM
Well, of course fresca Thursday, Sep. 18, 2003 at 4:39 PM
Fresca you are so podrida anti-troll alert Thursday, Sep. 18, 2003 at 6:32 PM
you individuals.....tisk tisk... Sheepdog Thursday, Sep. 18, 2003 at 7:09 PM
"...is for not for the... nonanarchist Thursday, Sep. 18, 2003 at 7:29 PM
HISTORY WILL BE YOUR JUDGE jesus was an anarchist Thursday, Sep. 18, 2003 at 7:59 PM
^ nonanarchist Thursday, Sep. 18, 2003 at 9:08 PM
For what it's worth fresca Thursday, Sep. 18, 2003 at 9:27 PM
further details of the link Sheepdog Thursday, Sep. 18, 2003 at 9:32 PM
oh damn Sheepdog Thursday, Sep. 18, 2003 at 9:34 PM
Exactly fresca Thursday, Sep. 18, 2003 at 10:32 PM
FLT 93 the meat wagon Sheepdog Thursday, Sep. 18, 2003 at 10:41 PM
keep it tidy Sheepdog Thursday, Sep. 18, 2003 at 11:56 PM
Fresca and company you still podridos anti-troll alert Friday, Sep. 19, 2003 at 8:23 AM
Fresca and company you still podridos anti-troll alert Friday, Sep. 19, 2003 at 8:24 AM
Anti-troll nonanarchist Friday, Sep. 19, 2003 at 8:55 AM
"Liberals" Brandon T. Friday, Sep. 19, 2003 at 9:15 AM
dead link Time out Friday, Sep. 19, 2003 at 11:26 AM
My Apologies Brandon T. Friday, Sep. 19, 2003 at 12:49 PM
Sorry about that Brandon T. Friday, Sep. 19, 2003 at 12:51 PM
questions that bastard Friday, Sep. 19, 2003 at 6:28 PM
down with america anarchist Friday, Sep. 19, 2003 at 6:35 PM
Mo money....for the idiots that bastard Friday, Sep. 19, 2003 at 6:49 PM
I'd rather fix what we have bah! Friday, Sep. 19, 2003 at 6:56 PM
screw you anarchist/bah What you and your ilk propose doesn't "fix" a that bastard Friday, Sep. 19, 2003 at 7:09 PM
anarchist nonanarchist Friday, Sep. 19, 2003 at 10:05 PM
nonanarchist anarchist Friday, Sep. 19, 2003 at 10:08 PM
Well, you're certainly revolting, all right. nonanarchist Friday, Sep. 19, 2003 at 10:21 PM
Well, you're certainly revolting, all right. nonanarchist Friday, Sep. 19, 2003 at 10:24 PM
Maybe you could call this telephone number. DIA Friday, Sep. 19, 2003 at 10:28 PM
Sure. nonanarchist Friday, Sep. 19, 2003 at 10:41 PM
Stop spamming the newswire, nonanarchist. Anarchist Friday, Sep. 19, 2003 at 10:44 PM
Nope. nonanarchist Friday, Sep. 19, 2003 at 10:50 PM
If you have sworn to protect the Constitution... @ Friday, Sep. 19, 2003 at 10:54 PM
Yadda yadda yadda... nonanarchist Friday, Sep. 19, 2003 at 11:04 PM
Skippy would rather Sheepdog Friday, Sep. 19, 2003 at 11:46 PM
Tough guy, huh? nonanarchist Friday, Sep. 19, 2003 at 11:49 PM
well gee, Skippy Sheepdog Saturday, Sep. 20, 2003 at 12:13 AM
I repeat: tough guy. nonanarchist Saturday, Sep. 20, 2003 at 7:41 AM
who cares about your personal problems Billions Moron this War Monday, Sep. 22, 2003 at 3:44 PM
Yeah! nonanarchist Monday, Sep. 22, 2003 at 3:50 PM
and now for something completely different Billions Moron this War Monday, Sep. 22, 2003 at 4:14 PM
a few of my favorite things Billions Moron this War Tuesday, Sep. 23, 2003 at 12:03 AM
Please provide more info Jamie Tuesday, Sep. 23, 2003 at 11:51 AM
Please provide more info Jamie Tuesday, Sep. 23, 2003 at 12:06 PM
follow the rabit Billions Moron this War Tuesday, Sep. 23, 2003 at 12:56 PM
Of Course! mud Tuesday, Sep. 23, 2003 at 1:16 PM
Of Course! mud Tuesday, Sep. 23, 2003 at 1:19 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:34 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:36 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:36 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:36 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:36 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:40 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:42 PM
Jamie anti-troll alert Tuesday, Sep. 23, 2003 at 1:43 PM
YOU CREDIBILITY is ZERO anti-troll alert Tuesday, Sep. 23, 2003 at 2:01 PM
traders and traitors Rob Ricnmen Tuesday, Sep. 23, 2003 at 3:52 PM
conspiracy theories catch22 Tuesday, Sep. 23, 2003 at 4:38 PM
Conspiracy crap Der Spiegel Tuesday, Sep. 23, 2003 at 5:26 PM
I love this stuff... Rob AL Richmen Tuesday, Sep. 23, 2003 at 5:27 PM
9-11 OFFICIAL THEORY Der Spiegel Tuesday, Sep. 23, 2003 at 7:16 PM
9-11 OFFICIAL THEORY Der Spiegel Tuesday, Sep. 23, 2003 at 7:17 PM
9-11 OFFICIAL THEORY Der Spiegel Tuesday, Sep. 23, 2003 at 7:17 PM
9-11 OFFICIAL THEORY Der Spiegel Tuesday, Sep. 23, 2003 at 7:17 PM
9-11 OFFICIAL THEORY Der Spiegel Tuesday, Sep. 23, 2003 at 7:17 PM
9-11 OFFICIAL THEORY Der Spiegel Tuesday, Sep. 23, 2003 at 7:17 PM
9-11 OFFICIAL THEORY Der Spiegel 2 Tuesday, Sep. 23, 2003 at 7:20 PM
9-11 OFFICIAL THEORY Der Spiegel 2 Tuesday, Sep. 23, 2003 at 7:22 PM
9-11 OFFICIAL THEORY Der Spiegel 2 Tuesday, Sep. 23, 2003 at 7:22 PM
9-11 OFFICIAL THEORY Der Spiegel 2 Tuesday, Sep. 23, 2003 at 7:22 PM
It's interesting how the Left... nonanarchist Tuesday, Sep. 23, 2003 at 7:31 PM
spooky not like it. Frank deNile Tuesday, Sep. 23, 2003 at 8:48 PM
conspiracy theories bege Tuesday, Sep. 23, 2003 at 8:55 PM
coincidence theorists spanky Tuesday, Sep. 23, 2003 at 9:07 PM
POWERFUL EVIDENCE THAT AIR FORCE WAS MADE TO STAND DOWN ON 9-11 Mandrake Tuesday, Sep. 23, 2003 at 9:13 PM
Ansar al-Islam leader threatens to document his links to US Agence France-Presse Tuesday, Sep. 23, 2003 at 9:19 PM
Ansar al-Islam leader threatens to document his links to US Agence France-Presse Tuesday, Sep. 23, 2003 at 9:19 PM
Ansar al-Islam leader threatens to document his links to US Agence France-Presse Tuesday, Sep. 23, 2003 at 9:19 PM
Ansar al-Islam leader threatens to document his links to US Agence France-Presse Tuesday, Sep. 23, 2003 at 9:19 PM
things Spanky Tuesday, Sep. 23, 2003 at 10:29 PM
Well, gosh... nonanarchist Tuesday, Sep. 23, 2003 at 10:39 PM
snails that are dumb, sheep that wont cum Spanky Wednesday, Sep. 24, 2003 at 12:34 AM
more links. and then some Spanky Wednesday, Sep. 24, 2003 at 12:51 AM

© 2000-2018 Los Angeles Independent Media Center. Unless otherwise stated by the author, all content is free for non-commercial reuse, reprint, and rebroadcast, on the net and elsewhere. Opinions are those of the contributors and are not necessarily endorsed by the Los Angeles Independent Media Center. Running sf-active v0.9.4 Disclaimer | Privacy