Path: utzoo!attcan!uunet!seismo!sundc!hadron!klr
From: klr@hadron.UUCP (Kurt L. Reisler)
Newsgroups: sci.space.shuttle
Subject: Re: ANSWERS: Reprogramming, plume, etc...
Message-ID: <786@hadron.UUCP>
Date: 4 Oct 88 13:58:48 GMT
References: <981@netxcom.UUCP> <1952@kalliope.rice.edu>
Reply-To: klr@hadron.UUCP (Kurt L. Reisler)
Organization: Hadron, Inc., Fairfax, VA
Lines: 28

In article <1952@kalliope.rice.edu> phil@Rice.edu (William LeFebvre) writes:
>In article <981@netxcom.UUCP> ewiles@netxcom.UUCP (Edwin Wiles) writes:
	[large portion of "dialog" deleted :-)]
>
>>	The crew boarding was delayed for aproximatly 30 Mins due to
>>	a simple 5A fuse burning out in the Commander's suit cooling
>>	fan.  Seem's they had some trouble locating a replacement.
>
>There were no available replacement fuses on the shuttle.  One had to be
>sent up from the ground.  BY DESIGN, nothing important is close to the
>launch pad---they probably had to send one out from the VAB, 3 miles away.
>They didn't necessarily have "trouble locating a replacement", they just
>had a long way to go to get it out to the pad.

Actually, from what I gathered while watching NASA Select, the fuses
were being kept in a technition's car at one of the roadblocks outside
of the safety zone.  Once it was determined that the problem was a blown
fuse (by that time 2 blown fuses) they were sent for and replaced, with
no loss of time in the countdown.

One thing I am curious about however.  What was done with (to) the
pilot of that private plane that buzzed the pad about 2 hours before
the launch?  NASA Select carried a portion of the CapComm dialog
informing the personel in the "White Room" not to be concerned about
the noise of the security aircraft as they chased a private plane out
of the restricted airspace.  They then cut to the view from a chase
plane (helecopter?) that was on the intruder's tail, the registration
numbers on the tail were clearly visible.