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]
The justification appears to be based on "growth of the commercial space industry" & "disruption to satellite operations due to the increased need for collision avoidance maneuvers" & not on any lack of effectiveness of the "25-year rule" to limit the rate of debris growth [4/n]
Indeed, the @NASA ODPO study cited in the proposed ruling shows that the "25-year rule" is highly effective at reducing the orbital debris population & any gains coming from a change to a "5-year rule" are not significant [5/n]
Unfortunately, the reporting of the ODPO study in the Orbital Debris Quarterly Newsletter (here: orbitaldebris.jsc.nasa.gov/quarterly-news…) is limited so I offer some additional insights below using results from simulation studies conducted using our DAMAGE model [6/n]
Firstly, it's important to have some understanding of how the "25-year rule" & the "5-year rule" can be implemented by operators [7/n]
A satellite ending its mission at a high altitude (e.g. higher than 650 km) will likely have a residual orbital lifetime greater than 25 years. With a manoeuvre to a different orbit, the remaining orbital lifetime can be reduced below the 25-year limit. [8/n]
In the example shown above, the new orbit has an apogee at the same altitude as the original orbit but the perigee is lower, where the atmospheric density is greater. This higher atmospheric density leads to a higher level of drag & a swifter orbital decay. [9/n]
The use of an elliptical orbit is efficient from a propellant/delta-V perspective but is not the only solution. Another option is to manoeuvre to a circular disposal orbit, again taking advantage of higher atmospheric density at lower altitudes, but this is costly. [10/n]
Keeping these explanation in mind, we can now look at the results of simulations where these manoeuvres have (and have not) been implemented by spacecraft & rocket stages. Here are results equivalent to those in the @NASA ODPO study [11/n]
@NASA The results show that the "25-year rule" is highly effective at reducing the growth of the debris population, regardless of how the rule is implemented, but the adoption of a "5-year rule" doesn't provide a significant additional benefit. [12/n]
@NASA Focusing on collisions we see a slightly different picture: yes the "25-year rule" is still effective, but now we see there is a difference depending on how the rule is implemented. At the same time, there is still only a marginal benefit from a change to a "5-year rule" [13/n]
So what is going on? Well, by looking at the perigee altitude of the disposal orbits (used in the simulation) we can start to understand how the lifetime (25 or 5 years) & how the rule is implemented might make a difference to the outcome. [14/n]
Mindful that in our simulations, satellites target orbital lifetimes of 25 years (or 5 years) & do not aim to de-orbit as soon as practically possible, & that they have variable mass & area characteristics, we see how the residual lifetime determines the perigee altitude [15/n]
Implementing a "25-year rule" via circular orbits tends to put orbits around 625 km but for elliptical orbits the perigees are around 500 km. A "5-year rule" tends to put the perigees at around 400 km altitude (caveat: depends on the atmospheric model & other assumptions) [16/n]
So now when we look at *where* the collisions occur in the simulations, for each of the cases, a pattern/correlation emerges [17/n]
There is a lot to unpack in this plot! I've repeated the annotations in the thread below & offered some additional insights [18/n]
Firstly, the "25-year rule" & the "5-year rule" lead to a decrease in the number of collisions above 625 km altitude. It is this reduction that makes post-mission disposal so effective as a #SpaceDebris mitigation measure. [19/n]
The "5-year rule" is generally no more effective than the "25-year rule" above 875 km altitude. Here, the original orbital lifetimes are measured in millenia so a change to orbits with lifetimes of 25 years is, in relative terms, the same as a change to 5 years [20/n]
The "5-year rule" is generally a little more effective than the "25-year rule" at altitudes between 425 km and 875 km, where the original orbital lifetimes are measured in decades to perhaps centuries. [21/n]
The "25-year rule" leads to an *increase* in the number of collisions below 625 km (compared with the case where no post-mission disposal occurs). When the "25-year rule" was first investigated, this effect was observed by @NASA & others. [22/n]
@NASA If circular disposal orbits are used in conjunction with the "25-year rule" these lead to an increase in the number of collisions in the region between 525 km & 625 km. [23/n]
@NASA Although difficult to see in the plot, the results also show that the "5-year rule" leads to an increase in the number of collisions at and below 425 km, roughly where the ISS can be found. [24/n]
@NASA So, in the process of significantly reducing the number of collisions at higher altitudes, the "25-year rule" & the "5-year rule" lead to a small increase in the number of collisions at lower altitudes. It can be argued that the benefits outweigh the drawbacks. [25/n]
@NASA Considering close approaches - the events that feature so prominently in the arguments presented by the @FCC in its proposed ruling - we see patterns similar to those previously seen for collisions: significant benefits at higher altitudes but drawbacks at lower altitudes. [26/n]
What we don't see in these results is a significant reduction in close approaches or collisions at the altitudes currently being dominated by commercial space industry & human spaceflight. Instead we see the opposite. [27/n]
In addition, the simulations did not include the large constellations that are expected to populate the lower regions of LEO, at the altitudes where we see the drawbacks arising from the "25-year rule" & the "5-year rule" [28/n]
The @FCC concludes that the arguments for a change to a "5-year rule" are "persuasive" & that the change is "warranted". I'm probably going out on a limb by saying that the evidence doesn't appear to support these statements. At the very least, further research is needed. [29/n]
@FCC With other agencies, such as @esa, looking to adopt an immediate de-orbit approach - which would resolve some/all of the issues I identified in the thread above - I think the proposed ruling represents a missed opportunity & falls short of what is needed. [30/n]
@FCC@esa I hope this thread has been interesting and useful! I'd like to thank my MSc student, Chloe Price, for some of the simulation results & for helpful discussions. [31/31; fin]
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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]
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]
#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]
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]
#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]
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]
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]
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]
There's a strong focus on the collision avoidance capabilities of the #Starlink satellites rather than on the services that inform those capabilities. Ryan Hiles and co-authors presented a hugely valuable insight on this aspect at @amoscon last year amostech.com/TechnicalPaper…
The impact of #Starlink on the work of @SpaceForceDoD is explained clearly, as are the steps taken to manage the screening burden that has emerged with growing numbers of #Starlink satellites. That burden is continuing to grow (exponentially by my estimates)