Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!udel!mvac!space
From: space@mvac.UUCP (Sci.Space netmail)
Newsgroups: sci.space.shuttle
Subject: holds in countdown
Message-ID: <8.UUL1.3#5131@mvac.UUCP>
Date: 18 Mar 89 16:58:00 GMT
Reply-To: mvac!space@udel.edu
Organization: TL**2
Lines: 19

This may be a nieve question, but I'll post it anyway:  Countdowns for launches
begin much earlier than the time alloted in the countdown timer (ie a launch is
set for 72 hours away, but clock says T-50 hours, or whatever).  I know that
'built in holds' are the reason why the two clocks do not agree, but my ques-
tion is why are they there?  If you *know* that you are going to stop the clock
for 1 hour and 20 minutes when the countdown clock says T-xxx, than why not 
just add one hour and 20 minutes to the countdown clock and just say that from
T-4:20 to T-3:00, there is no planned activity.  

thanks,
                         - tom lapp
==============================================================================
(Nope, Reply will *not* work.  Choose one from below to use for replying to
 me).                            
uucp:     ...!udel!mvac!space       BITNET: space!mvac%udel.edu@CUNYVM
Internet: mvac!space@udel.edu
          or
          space%mvac.uucp@udel.edu
-------------------------------------------------------------------------------