Rebuttal to the Berndt/Balettie Spaghetti

The true cause of the 51-L catastrophe cannot be established
by edict, nor is it negotiable politically. It is determinable in
the courts. (Below reposted because of popular demand.)

==============================================
'Technical Summary of an O-Ring Cover-Up'
(requested by Pentagon efficiency expert
A. Ernest Fitzgerald on July 4, 2003)

NASA's fault-tree analysis failed to consider that Challenger's solid
rocket boosters could have crossed paths within the 51-L fireball.
A crossing necessarily negates Rogers' postulated "right-aft O-ring
burnthrough."

In a hearing on February 7, 1986, Dr. Feynman inquired: "Can I ask
a dumb question? Do we know on which side which rocket is
afterwards? Did they go like this and cross or do they look like they
went that way?" NASA put Feynman off, and Rogers sidetracked
him. Dr. Feynman did not know about NASA's black ID band until
I told him, in late 1987.

For photo/recovery identification, NASA paints a black ID band 18''
high around the nose of the space shuttle's *left* solid rocket booster.
Rogers ignored this ID band in his report, most notably at the crucial
fireball exit. Instead, Rogers conjectured a "R-SRB burnthrough" for
identification.

Rogers' ID relies on an enhanced 15-second film strip ending in
explosion. However, in JSC's '51-L Mission History Video,' the
continuation of this film strip leaves no doubt that the *flared* booster
sported the ID band.

On January 22, 1986, in a pre-Challenger technical report requested by
Senator Grassley's office, I warned: "... and 'cold flows' run at Pad B
were a failure, costing much waste of time and money. Tom Wiley can
testify to this. The net result of all this would be delays in launching
from Pad B, and delays in Centaur launches. I also learned from Bill
Bassler, Centaur 'single-point-of-contact' in LSOC CMO, that the
waste of hydrogen was deliberate, ..."

The terminal LH2 leaks were at the base of the left booster. It became
super-cooled during prelaunch scrubs. A thrust imbalance resulted.
That caused a right-aft leak in the hydrogen tank at lift-off, later
aggravated by 5000-plus degree heat from continuous R-Aft RCS
firings at 59 seconds. The pre-explosion chamber pressures of the two
boosters (relative to each other and to their respective lift-off pressures)
were to be expected.

NASA could not identify the key piece of lower booster debris by serial
number, or by *any other* of NASA's standard identification methods.

The Rogers Report admits that no direct view exists of the location from
which black smoke at lift-off and an assumed burnthrough at 59 seconds
originated. Live launch-day video refutes NASA's "burnthrough" copies.
Congressional subpoena of the originals should lead to credible closure.

John Thomas Maxson (www.mission51l.com)
=================================================

In sci.space.policy John Maxson wrote:
The true cause of the 51-L catastrophe cannot be established
by edict, nor is it negotiable politically. It is determinable in
the courts. (Below reposted because of popular demand.)


There does not appear to be any demand for reposting this. Those
interested can read it in google.

--
Sander

+++ Out of cheese error +++

I'm sorry that you're unable to keep up with appearances.
Those interested can also read it here, in this thread.

(I forgot to mention that Fitzgerald limited me to one-page.
I'd like to see a combined effort here by Berndt and Balettie,
or one by Jay Windley, where the limit is one page.)

--
John Thomas Maxson, Retired Engineer (Aerospace)
Author, The Betrayal of Mission 51-L (www.mission51l.com)


Sander Vesik wrote in message
...
In sci.space.policy John Maxson
wrote:

The true cause of the 51-L catastrophe cannot be established
by edict, nor is it negotiable politically. It is determinable in
the courts. (Below reposted because of popular demand.)


There does not appear to be any demand for reposting this. Those
interested can read it in google.

--
Sander

Sander Vesik wrote:
There does not appear to be any demand for reposting this. Those
interested can read it in google.


I'm loving the new Mozilla 1.4. I've set a newsgroup fileter just now
so that if the sender of a post is JTM, then that post is marked as
"read" so that I never see it, and then the entire thread is marked as
"ignore". I hope it works. Just killfiling him doesn't go far enough
IMO. There are too many who respond to him and their followup posts
have continued to interfere with my enjoyment of the group. By ignoring
every thread from now on into which he feels the need to interject his
bull****, I don't think I'm going to be missing a whole lot. I'm
especially interested to see if this will work in threads where he
changes the subject line. That seems to be one of his favorite
duplicitous tricks.

--
bp
Proud Member of the Human O-Ring Society Since 2003

It's too bad you need filters to do what you don't have the
intelligence and the will power to do yourself.

--
John Thomas Maxson, Retired Engineer (Aerospace)
Author, The Betrayal of Mission 51-L (www.mission51l.com)



Bruce Palmer wrote in message
et...
Sander Vesik wrote:

There does not appear to be any demand for reposting this. Those
interested can read it in google.

I'm loving the new Mozilla 1.4. I've set a newsgroup fileter just now
so that if the sender of a post is JTM, then that post is marked as
"read" so that I never see it, and then the entire thread is marked as
"ignore". I hope it works. Just killfiling him doesn't go far enough
IMO. There are too many who respond to him and their followup posts
have continued to interfere with my enjoyment of the group. By ignoring
every thread from now on into which he feels the need to interject his
bull****, I don't think I'm going to be missing a whole lot. I'm
especially interested to see if this will work in threads where he
changes the subject line. That seems to be one of his favorite
duplicitous tricks.

--
bp
Proud Member of the Human O-Ring Society Since 2003

In sci.space.policy Bruce Palmer wrote:
Sander Vesik wrote:
There does not appear to be any demand for reposting this. Those
interested can read it in google.


I'm loving the new Mozilla 1.4. I've set a newsgroup fileter just now
so that if the sender of a post is JTM, then that post is marked as
"read" so that I never see it, and then the entire thread is marked as
"ignore". I hope it works. Just killfiling him doesn't go far enough
IMO. There are too many who respond to him and their followup posts
have continued to interfere with my enjoyment of the group. By ignoring
every thread from now on into which he feels the need to interject his
bull****, I don't think I'm going to be missing a whole lot. I'm
especially interested to see if this will work in threads where he
changes the subject line. That seems to be one of his favorite
duplicitous tricks.

i'm just trying to make the newsgroup look like something else than a
huge pile of junk threads. it can be quite shocking if you make a pause
of reading it for a couple of weeks 8-(


--
bp
Proud Member of the Human O-Ring Society Since 2003


--
Sander

+++ Out of cheese error +++

Sander,

I agree. This Maxson guy, of whom I've only recently had the pleasure
of hating, reminds me of a similar jerk-off named Burt Fisher, a ham
operator who used to post in the ham radio group in the early 90's about
how all hams were underachievers.

It was like the universe calling the pot black. He went on and on about
how awful hams are, and at the same time, was purportedly a huge
enthusiast of ham radio. It just smelled bad.

Under closer scrutiny, and by specific questions, he failed to pass the
expert test. He barely passed the novice test.

He is probably great at pushing paper, but was unable to answer
correctly my question about how to saturate a transistor. This is
Engineering 101, and he failed, this 'expert', and teacher of
high-school kids, in hardware.

My guess is that this JTM idiot is probably a great paper pusher, and
might even think that he is smart. Unfortunately, he never really
answers questions that are asked to him, which makes me think that he
has a lot of words but not a lot of brains.

*plonk* he goes.

All the best,
Dave



Sander Vesik wrote:

In sci.space.policy Bruce Palmer wrote:

Sander Vesik wrote:

There does not appear to be any demand for reposting this. Those
interested can read it in google.


I'm loving the new Mozilla 1.4. I've set a newsgroup fileter just now
so that if the sender of a post is JTM, then that post is marked as
"read" so that I never see it, and then the entire thread is marked as
"ignore". I hope it works. Just killfiling him doesn't go far enough
IMO. There are too many who respond to him and their followup posts
have continued to interfere with my enjoyment of the group. By ignoring
every thread from now on into which he feels the need to interject his
bull****, I don't think I'm going to be missing a whole lot. I'm
especially interested to see if this will work in threads where he
changes the subject line. That seems to be one of his favorite
duplicitous tricks.


i'm just trying to make the newsgroup look like something else than a
huge pile of junk threads. it can be quite shocking if you make a pause
of reading it for a couple of weeks 8-(


--
bp
Proud Member of the Human O-Ring Society Since 2003





--

Please yank that last "t" from my email address.
It's "net", not "nett". You know how to do that,
but the spammers won't.

In newsave Bushong typed:

My guess is that this JTM idiot is probably a great paper pusher,

No, he's not. His book is a laborious and torturous read. Brain
damagingly bad. Clean toilet paper is of much greater social and
personal value.

and
might even think that he is smart. Unfortunately, he never really
answers questions that are asked to him, which makes me think that he
has a lot of words but not a lot of brains.

*plonk* he goes.
--
Mike
__________________________________________________ ______
"Colorado Ski Country, USA" Come often, Ski hard,
Spend *lots* of money, Then leave as quickly as you can.

Killing a whole tread for just one clown sounds pretty drastic, though.