Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!ut-sally!seismo!brl-tgr!wmartin
From: wmartin@brl-tgr.ARPA (Will Martin )
Newsgroups: net.columbia,net.space
Subject: Shuttle launch delays
Message-ID: <1221@brl-tgr.ARPA>
Date: Fri, 3-Jan-86 14:47:20 EST
Article-I.D.: brl-tgr.1221
Posted: Fri Jan  3 14:47:20 1986
Date-Received: Sun, 5-Jan-86 01:40:36 EST
Distribution: net
Organization: USAMC ALMSA, St. Louis, MO
Lines: 23
Xref: watmath net.columbia:1757 net.space:5100

I've been wondering just what determines the length of a delay or
postponement of a shuttle launch when some defect is discovered
while the assembled craft is already fueled and there is only a short
time remaining in the countdown. Sometimes things are slipped a few
hours, other times until the next day, and then there will be abrupt
jumps to much longer delays, like several weeks.

Could someone in the know post a short summary of what sorts of delays
what kinds of discovered problems will cause? Something like:

Shuttle computer software bug    .....   1 day for patching & reloading

SRB Engine Safety-related failure  ...   3 weeks for return to vehicle
					 assembly building & replacement
and so on...

Also, how long does removing the liquid fuel & oxidizers take? How long can
the fueled shuttle sit on the pad while still fueled-up?

Thanks!
Will Martin

UUCP/USENET: seismo!brl-bmd!wmartin   or   ARPA/MILNET: wmartin@almsa-1.ARPA