, 7 tweets, 2 min read Read on Twitter
So, I've just had it confirmed from another ESA source that #SpaceX refused to move their #Starlink satellite when they were alerted to the risk of collision with #Aeolus, which was 1 in 1,000, ten times higher than the threshold for a collision avoidance manoeuvre. (1/5)
SpaceX sent a short email to ESA saying they would not move their satellite. It's not clear why - they didn't mention if the satellite was active or not, apparently (ESA weren't even aware what the satellite was). (2/5)
ESA have been pretty frustrated with SpaceX so far. There has been very little communication regarding Starlink, despite repeated attempts by ESA to contact them (this is the first email SpaceX had sent). (3/5)
As to why Aeolus had to move and not Starlink, my source just said "in space there are no rules". Basically, SpaceX said they wouldn't move. So Aeolus had to move.

(ESA said they were glad they knew one way or the other, however) (4/5)
As of yet SpaceX has not responded to a request for comment on this. I'll have a story up on @Forbes soon with full quotes. (5/5)
Here's the story for all coming to this thread. forbes.com/sites/jonathan…
To clarify on this in light of updated information from SpaceX, it's now clear the company didn't necessarily refuse to move its satellite, but rather declined to move it initially (when the risk was above the threshold), as did ESA, but did not respond when the risk was raised.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Jonathan O’Callaghan
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!