Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Wednesday September 04 2019, @07:31AM   Printer-friendly

About a week ago, the 18th Space Control Squadron, US Air Force, relayed warning data to the European Space Agency.

The data indicated that there was a non-negligible collision risk between ESA's Aeolus satellite and Starlink44, an active SpaceX satellite, at 11:02 UTC on Monday, 2 September.

As days passed, the probability of collision continued to increase, and by Wednesday, August 28, ESA's Ops team decided to reach out to Starlink to discuss their options. Within a day, the Starlink team informed ESA that they had no plan to take action at that point. By Thursday evening, ESA's probability threshold for conducting an avoidance manoeuvre had been reached, and preparations were made to lift Aeolus 350 meter in orbit. By Sunday evening, chances of a collision had risen to 1 in 1000, and commands were sent to the Aeolus satellite, which triggered a total of 3 thruster burns on Monday morning, half an orbit before the potential collision. About half an hour after the collision prediction time, Aeolus contacted base, and normal measurement operations could continue.

What the SpaceX satellite was doing in ESA's Aeolus orbit is not clear.

ESA has taken the opportunity to point out that, given SpaceX plans to put up 20,000 of those things, handling monitoring and avoidance semi-manually, and by mail, is no longer practical.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: -1, Spam) by Anonymous Coward on Wednesday September 04 2019, @10:06AM (2 children)

    by Anonymous Coward on Wednesday September 04 2019, @10:06AM (#889468)

    How does this affect anyone at all? Why is this news?

    I'll be censored to -1 for asking this important question because you people know I'm right and this doesn't matter. Rather than answer my question, you'll bury my post. It's shameful.

    It's not like there was actually a collision. This doesn't matter and you people know I'm right.

    Imported from Slashdot

    Starting Score:    0  points
    Moderation   -1  
       Spam=1, Total=1
    Extra 'Spam' Modifier   0  

    Total Score:   -1  
  • (Score: 2) by tangomargarine on Wednesday September 04 2019, @08:06PM (1 child)

    by tangomargarine (667) on Wednesday September 04 2019, @08:06PM (#889672)

    If we get enough satellite collisions to cause Kessler Syndrome [wikipedia.org] you can be damn sure it'll impact you. So much for GPS, for one thing. and various other things [bbc.com]

    I'll be censored to -1 for asking this important question because you people know I'm right and this doesn't matter. Rather than answer my question, you'll bury my post. It's shameful.

    Whining like this is really just inviting people to do so. If you don't like the article, don't read it.

    --
    "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
    • (Score: 3, Insightful) by deimtee on Thursday September 05 2019, @01:49AM

      by deimtee (3272) on Thursday September 05 2019, @01:49AM (#889788) Journal

      Almost any collision reduces kinetic energy. You will never get a collision that raises perigee. You might get a few pieces with a higher apogee, but in that case their orbit will be more eliptical and they will de-orbit even faster.
      Kessler Syndrome requires you start high and the debris works its way down. Even if these two collided it would be at 320km, the chance of any piece getting out to 36,000km is zero.

      --
      If you cough while drinking cheap red wine it really cleans out your sinuses.