John Whitley Radio Interview -- indepth discussion about coming oil shortages (11/30/99)

greenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread

John Whitley discusses in detail the coming oil shortages on an 11/30/99 Jeff Rense Radio broadcast.

For an archived listing of Real Audio broadcasts in which he was interviewed, go to Jeff Rense - Sightings. See 3/31, 4/15, 5/25, 7/19, 8/20 & 11/30/99 (OIL SHORTAGES) shows:

[http://www.broadcast.com/shows/endoftheline/99archives.html]

John Whitley New World Order Intelligence Update website address:

[http://www.inforamp.net/~jwhitley/index.htm]

Press: "DAILY Y2K AND POST-Y2K NEWS AND ARTICLES FROM A GLOBAL RANGE OF NEWSPAPERS, MAGAZINES AND POST-Y2K NEWS SOURCES"

-- Patrick Lastella (Lastella1@aol.com), January 16, 2000

Answers

11/30/99? Has his opinion been updated in the past 6 weeks on this topic?

-- Hokie (Hokie_@hotmail.com), January 16, 2000.

OIL TROUBLE

Peter Asher (1/16/00; 12:25:47MDT - Msg ID:23000) OIL: (From Michael Hyatt's Bug Watch Forum) http://www.michaelhyatt.com

12/31/99 - Turkey resets clocks to 1980 on oil pipelines 1/2/00 - Motiva's 220,000 b/d Norco, La oil refiner down due to "unexplianed power outage" -220,000bbd 1/3/00 - Nigerian Oil plant down - locals causing problems. 1/3/00 - Shell oil in Singapoer reduces oil output 20%. No explanation.-100,000bbd 1/4/00 - Coastal Eagle Point NJ Oil refinery down. Internal loss of generating power? -140,000bbd 1/4/00 - Coastal Corpus Christi oil refinery, FCC problem. - 103,000bbd 1/4/00 - Equilon's Wood River, Ill oil refiner down due to "unspecified crude unit problem" -210,000bbd 1/5/00 - PDVSA & Hess is diverting a cargo of oil back to Europe, was headed to US. 1/7/00 - Motiva's Delaware oil refinery down due to fire. -110,000bbd 1/14/00 - BP Amoco, Yorktown, down due to mechanical failure. - 62,000bbd

ALSO

the box (ANGEL) Jan 16, 19:44 I read it on reuters ( under "oil" ) Columbias main pipeline has been blown up twice. The first time on jan 1, they just fixed it and one day latter it was blown up again. Reuters mentioned it carried about 350,000 barrels a day. @ANGEL: Re, your 16:56 posting question, re: (TheBox) Jan 16, 17:32 . . .pipeline sabotage. . .No word in any recent newspostings of SEV, altho, as you probably know, SEV's CEO is none other than the illustrious Dr.Schlessinger, former CIA head, Dept. of Energy head. . .SEV would certainly be possible beneficiary of any such sabotage. . .Curious bedfellows, to say the least. Where did you get your original news anyhow? TIA, TheBox.

-- Andy (2000EOD@prodigy.net), January 16, 2000.


The reason I refer to McAlvany and others' previous interviews is because they already laid out the progression of events far beyond the "rollover myth", which is what it has become. This needs to be repeated until it's gotten: only around 5% of glitches were predicted to occur around the beginning of the year. These people have ALREADY presented the big picture far beyond, and irrespective of, the rollover date. This is playing out. The issue of oil is now coming to play behind the scenes. The reports are ominous. It's not coming out in the open yet. Supplies are, and will be, dwindling. This is fact, not opinion. Take ANY area related to Y2K that was unremediated and predicted to fail. They will still fail. Nothing has changed. Reports concerning oil are real, not fabricated. Simple arithmetic tells all. A 5% drop in oil would have serious international repurcussions. We're talking about pipelines exploding, reductions and shutdowns now of an alarming degree. Read the reports. Each day it's becoming worse. But we're talking about an eventual possible drop off of far, far beyond 5% so as to make the number look insignificant. This is not alarmist, it's starting to happen right now. These OPEC countries admitted themselves, to being in catastrophic shape for the date problem. This didn't go away. When will we once again start re- examining the facts and stop squibbling over the 1/1/2000 date as the all in all determinent of the state of Y2K? It's the year 2000 problem, meaning the whole year and beyond. One day soon a lot of people are going to wake up and say, "oh yeah, gee, you know, the problem never DID go away. It really DIDN'T fix itself. I guess I should have stuck with the statistical facts before-hand and not believed the myth that if nothing occured by the 1st then it never will." This is not about "who's right or wrong", though how many are taking it to that level? Or about "see, I told you" in the end. It's about people's lives and souls at stake here, and I've been listening to this forum for weeks now, and it's once again time to sound an alarm in my opinion. I see and sense the direction things are taking behind the scenes. I think Y2K has just crossed another threshold. One from innocence, debate and uncertainty to "open your eyes and see what's really happening". Look at the reports. Get a feel for what's "going down". "Doomers" and "alarmists" may have been sounding the alarm for a long time way in advance. But it's time for someone to stand up and say, "this is coming down right under your very nose and the time for disbelief is over." It may have seemed like "the boy who cried wolf" up till now. But remember, the wolf finally came and no one believed the final warning. This is not meant to fan the stupid and senseless flame of "proving who's right" with this issue. That solves nothing. How 'bout people sticking to the facts about how non- compliant things really were prior to the rollover and still are. And that we wouldn't see much happening until about now. This week could be interesting, not just because it's around the time things are predicted to become apparent, but because from the reports coming in, particularly with oil, -- the life blood of the industrial world -- there is definitely a sense that things may have now progressed to the next stage. The sense of "quietness" or "waiting" feels over. The time of witnessing problems may in fact now be at hand.

-- Patrick Lastella (Lastella1@aol.com), January 16, 2000.

Moderation questions? read the FAQ