Re: Iridium, Cosmos collide

From: B Gimle @ComHem (@ComHem)
Date: Thu Feb 12 2009 - 09:55:45 UTC

  • Next message: Brian Weeden: "Re: Iridium, Cosmos collide"

    I was looking at data for a previous high (>1%) collision risk on
    T.S.Kelso's SOCRATES
    and happened to save the output for Feb.08-14
    This collision was not on the list, but possibly this is where many
    operators get their warnings!
    ----- Original Message ----- 
    From: "Susan Kaltenbach" <>
    To: <>
    Sent: Thursday, February 12, 2009 2:04 AM
    Subject: RE: Iridium, Cosmos collide
    > I'm very confused.
    > With all the tracking done by our military and our highly skilled See-Sat
    > detectives, how could the collision have been a surprise? An important
    > component of tracking is to predict orbital paths, is it not? The only
    > thing
    > that makes sense to me is some kind of sudden orbital change.
    > I hope I'm not off topic here, but I always assumed that observing,
    > tracking, and predicting objects in orbit were all strongly associated.
    > And
    > I'm pretty stunned by the whole thing.
    > Susan Kaltenbach
    > PS - I haven't been receiving FPSPACE messages and I'm starved for
    > information. I hope it's just me and that their server isn't down.
    > -------------------------------------------------------------------------
    > Subscribe/Unsubscribe info, Frequently Asked Questions, SeeSat-L archive:
    Subscribe/Unsubscribe info, Frequently Asked Questions, SeeSat-L archive:

    This archive was generated by hypermail 2b29 : Thu Feb 12 2009 - 09:56:29 UTC