Hugh Lewis Profile picture
Apr 1, 2022 29 tweets 14 min read Read on X
Earlier this week Elon Musk set out his team's expectations for #Starlink satellites over the next 18 months. I thought I would use this month's #SOCRATES analysis to see what the Starlink team should expect in terms of conjunctions & manoeuvres over that period & beyond [1/n]
Before I start, I'd like to offer my thanks to @planet4589 for creating a page on his website with data that enabled me to move forwards with a critical part of the analysis. Thanks also go to @TSKelso for ongoing support and provision of SOCRATES data via @CelesTrak [2/n]
This month we open with the number of conjunctions within 5 km or less predicted for each week from December 2018 to the end of March 2022. Something extraordinary has happened because of #Starlink and the ASAT test in November: a 400% increase in less than 3 years [3/n]
The 1 km conjunction data show a similar increase although it's a little more muted. The last #SOCRATES report from 31 March 2022 predicted 7513 conjunctions within 1 km or less for the first week of April. [4/n]
Work by @COMSPOC suggests that conjunctions involving fragments caused by the intentional destruction of Cosmos 1408 will come in 'squalls' over the next year spacenews.com/russian-asat-d…. We're currently in one of the year's worst. [5/n]
Looking at the predicted conjunctions with a collision probability greater than 1-in-10,000 (a common manoeuvre threshold) we see a similar increase in the count, but now it seems to be dominated by events involving #Starlink & not events involving Cosmos 1408 debris. [6/n]
Here's the predicted count for conjunctions with collision probability greater than 1-in-100,000 (the threshold used by #Starlink for manoeuvres). There is some involvement by Cosmos 1408 debris here but again #Starlink dominates. [7/n]
If we now focus only on conjunctions within 5 km involving #Starlink satellites (but excluding Starlink-on-Starlink events) we continue to see the non-linear trend through time in spite of a modest reduction in the count over the last month (2nd-order poly has R^2 = 0.983). [8/n]
It's a similar story for the conjunctions within 1 km: a small reduction in the count since last month but an ongoing non-linear increase overall (2nd-order poly has R^2 = 0.975). [9/n]
The count for conjunctions with a collision probability greater than 1-in-10,000 & involving #Starlink shows the same trend (remember the number of conjunctions are taken from each #SOCRATES report, which covers predictions for a 7-day period). [10/n]
Here's where we start to get a sense of the operational implications arising from all of these conjunctions, because the autonomous collision avoidance system employed by #Starlink triggers a manoeuvre if the collision probability is greater than 1-in-100,000 [11/n]
The #SOCRATES data suggest about 210 manoeuvres are made every week, or 30 per day. [12/n]
When we add all of the (predicted) manoeuvres, we find that #Starlink passed an important threshold in March: 10,000 collision avoidance manoeuvres. A 3rd-order poly fits the line shown in the graph with R^2 = 1.0 (hence the manoeuvre rate would have a 2nd-order poly fit) [13/n]
Here's where the data from @planet4589 comes in. Jonathan provided me with a count of the number of #Starlink satellites in orbit (amongst other things). This means that I can extend the analysis to look at how the satellite count affect the conjunctions & manoeuvres [14/n]
This is how the number of #Starlink satellites in-orbit (operational & failed) affects the number of conjunctions within 5 km predicted by #SOCRATES (these are only conjunctions involving Starlink & excluding Starlink-on-Starlink) [15/n]
These are the data for the corresponding conjunctions within 1 km [16/n]
And for the conjunctions with collision probability greater than 1-in-100,000 [17/n]
Finally, we get to the relationship between the number of #Starlink satellites in orbit and the collision avoidance manoeuvre rate (shown as the number per day) [18/n]
You may have spotted the trendlines in the last few graphs. We can now use those to make predictions about the number of conjunctions & manoeuvres that might be expected once the number of satellites in orbit reaches 4200 [19/n]
A brief warning before I show you the prediction results: many things could affect the models (trendlines), including fragmentation events, space weather, solar activity, non-Starlink launches, so please approach with caution. Nevertheless, the results are... astounding [20/n]
The model suggests that 4200 #Starlink satellites in orbit would result in 56,200 conjunctions within 5 km per week involving Starlink (but excluding Starlink-on-Starlink). Extrapolating to 32,000 Starlink satellites & we might see 3 million conjunctions per week [21/n]
The 1 km conjunction model suggests that 4200 #Starlink satellites in orbit would result in 1980 conjunctions per week involving Starlink, but more than 100,000 conjunctions per week once the constellation reaches 32,000 satellites [22/n]
And finally, the model suggests that 4200 #Starlink satellites in orbit would require a total of 105 collision avoidance manoeuvres per day. That's roughly equivalent to 1 out of every 40 Starlink satellites manoeuvring on a daily basis, on average. [23/n]
Extrapolating to a #Starlink constellation with 32,000 satellites in orbit suggests 5425 collision avoidance manoeuvres per day (nearly 2 million per year) involving 1 out of 6 satellites in the constellation, on average. [24/n]
The last tweet is why I tend to talk about the 'burden' that is placed on operators and regulators by large constellations of satellites. [25/n]
That's not all. The law of very large numbers will tell you that very low probability events can happen if given enough opportunities. Even with an autonomous system taking action at a relatively low probability level, we might expect to see a #Starlink collision [26/n]
Then, of course, we have 'lethal non-trackable' objects. It's not possible to manoeuvre for things we cannot track. Even if we track them, the number of conjunctions increases to even higher levels, possibly resulting in a change to accepted collision probability levels... [27/n]
...that result in fewer manoeuvres but the neglect of greater risk. [28/n]
That's it for this month's #SOCRATES & #Starlink analysis. Thanks for reading this far. [29/29]

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Hugh Lewis

Hugh Lewis Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ProfHughLewis

May 15, 2023
Welcome to this month's look at #Starlink conjunction risk mitigation manoeuvres. Through 30 April 2023, I estimate that Starlink satellites have made a total of > 45,000 manoeuvres to mitigate the risk of colliding with other space objects [1/n] Graph showing the cumulativ...
A better relationship to consider is the one between the (cumulative) number of manoeuvres and the (cumulative) number of Starlink satellites launched. The growth is a non-linear function of the number of Starlink satellites [2/n] Graph showing the cumulativ...
Here, I looked at the manoeuvre estimates/reports in 6-monthly intervals, corresponding to the reporting periods used by SpaceX. Additionally, I added a prediction to the end of 2024 based on an exponential fit through 30 April 2023. [3/n] Graph showing the number of...
Read 6 tweets
Sep 15, 2022
I've been thinking about the new proposed @FCC "five-year rule" for #SpaceDebris mitigation & wanted to share some analysis & thoughts. Whilst I think the intentions are good I believe the implications of the change are poorly understood. Let me explain... [1/n]
As @brianweeden's excellent thread explains, "The new proposed ruling would require all FCC licensed satellites that end their life in LEO to re-enter the atmosphere within 5 years, and ideally ASAP." [2/n]
The justification provided by the @FCC is that "a shorter benchmark would promote a safer orbital debris environment." [3/n] Image
Read 31 tweets
Sep 14, 2022
Latest analysis for #Starlink & #OneWeb shows these two constellations accounted for 42% of all close approaches within 5 km predicted by #SOCRATES at the end of August, with Starlink alone accounting for 29%. [1/n]
On average, #SOCRATES predicts that each #Starlink satellite will now experience 1 close approach within 5 km with a non-Starlink object every day, and each #OneWeb satellite will experience 3.4 close approaches with a non-OneWeb object every day. These rates are increasing [2/n]
Here's the same data from [2/n] plotted with respect to the number of satellites in each constellation in orbit, clearly showing #SOCRATES predicts that #OneWeb satellites experience more close approaches (within 5 km) per satellite than the #Starlink satellites [3/n]
Read 13 tweets
Jul 5, 2022
A follow-on from yesterday's thread with a note about averages. In a #SOCRATES report from 30 June 2022 the average collision probability for each #Starlink conjunction was 3.7E-6 but the range of values can be broad (chart shows data since 2019) [1/n]
Chart showing frequency of conjunctions at different collisi
#SOCRATES predicted some events with a collision probability > 1E-2 (1-in-100) & some with a probability < 1E-7 (1-in-10,000,000). The average value might seem to be almost negligible & you might think all conjunctions would be similar, but that's not the case [2/n]
In addition, some #Starlink & #OneWeb satellites experience more conjunctions than others. Most satellites experience relatively few encounters but a few satellites are involved in a relatively large number (charts shows data for 7 days from 30 June 2022) [3/n] Chart showing the frequency that Starlink and OneWeb satelli
Read 8 tweets
Jul 4, 2022
Welcome to my (delayed) monthly analysis of @CelesTrak #SOCRATES conjunctions. Since 1 March 2019, SOCRATES has predicted about 9 million unique conjunctions within 5 km involving active or derelict payloads. This is a thread focused on those involving #OneWeb & #Starlink [1/n] Chart showing the average daily number of conjunctions withi
#OneWeb payloads have accounted for ~500,000 unique conjunction predictions since 1 March 2019 (5.5% of all predictions made), while #Starlink payloads have accounted for ~1.1 million (12.5%) [2/n]
On 1 March 2019 #SOCRATES predicted ~3860 unique conjunctions within 5 km. On 30 June 2022 the corresponding number was ~10,160, an increase of ~160%. #Starlink accounted for ~2570 (25%) & #OneWeb accounted for ~1250 (12%) [3/n]
Read 14 tweets
Apr 27, 2022
In advance of my monthly analysis of #Starlink conjunction data I wanted to share some additional analysis undertaken over the last few days. It's a work in progress but here's a thread looking a little deeper at the #SpaceX approach to #Starlink orbital space safety [1/n]
#SpaceX provided some relatively detailed information about its approach in a briefing to the #FCC (here: ecfsapi.fcc.gov/file/108107102…) and in an update on the website (here: spacex.com/updates/index.…) [2/n]
My focus has mostly been on understanding the implications relating to the choice of the probability threshold for collision avoidance manoeuvres. With the #SOCRATES #Starlink data now running across nearly 3 years we can gain some insights that may be useful [3/n]
Read 35 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


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

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

Become Premium

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(