Path: utzoo!utgpu!watserv1!watdragon!dahlia!mskucherawy
From: mskucherawy@dahlia.waterloo.edu (Murray S. Kucherawy)
Newsgroups: sci.space.shuttle
Subject: Re: Acronym Overload (was Re: Direct ascent trajectory)
Message-ID: <19827@watdragon.waterloo.edu>
Date: 16 Jan 90 04:11:32 GMT
References: <1641BARRY@RICEVM1> <1393@wrgate.WR.TEK.COM>
Sender: daemon@watdragon.waterloo.edu
Reply-To: mskucherawy@dahlia.waterloo.edu (Murray S. Kucherawy)
Organization: University of Waterloo, Ontario, Canada
Lines: 25

In article <1393@wrgate.WR.TEK.COM> dant@mrloog.WR.TEK.COM (Dan Tilque) writes:
>Houston, this is Columbia,... we have Acronym Overload, I repeat, Acronym
>Overload... please advise.
>
>In article <1641BARRY@RICEVM1> BARRY@RICEVM1.BITNET writes stuff with too
>many acronyms.  Some of them I knew but could someone else fill in the
>rest:
>
>OMS-{1,2} - Orbiter (? Orbital) Maneuvering System (This was a guess)
>MECO - ?
>TAL - ?
>RCS-1 - ?

OMS is Orbiter Maneuvering System (your guess was correct).
MECO is Main Engine Cut Off, an event in launch and ascent proceedings.
I don't know the other two off-hand, but I have them in my collection
of postings at home... if nobody has answered by the time I'm next on,
I'll post answers to the other two.

============================================================================
Murray S. Kucherawy                                    "Betcha byte a chip!"
E-Mail: mskucherawy@{dahlia | crocus}.{waterloo.edu | UWaterloo.ca | UUCP}
Faculty of Mathematics (Comp Sci), University of Waterloo, Waterloo, Ontario
Postmaster, UW Computer Science Club (watcsc.waterloo.edu)
System Manager, VAX/VMS Network, Board of Education, London, Ontario