Dilbert's pointy-haired boss?
I find it interesting that they are simultaneously looking for the root cause *AND* writing software to fix it.
Wondering if there's a Wally getting ready to code himself a minivan . . .
As if to underscore the need to avoid the Kessler Syndrome, a scenario in which cascading debris can make some orbits difficult to use, a Starlink satellite vented propellant and released debris following an onboard "anomaly" late last week. The incident, described by observers as "likely caused by an internal energetic source …
"They are currently looking for the root cause and... "
According to the article, aren't looking for the root cause, but instead "working to root cause and mitigate...". "root cause" is clearly a verb now, that I suspect means go through a set list of actions in some modern fashionable take on systems engineering without understanding what you are doing or why.
Shuffles off muttering to oneself "in my day ... etc. etc."
Unless it was a battery that ruptured because the software commanded something which shorted it out. Or it was a tank with a heater that the software boiled dry. Or it ruptured because the software started shaking the bird at something's resonant frequency. Lots of ways for software could cause the problem.
And don't get me started on the ways that software gets asked to fix up problems in the hardware. (Yes, I've been an embedded programmer. How did you guess?)
The likelihood of this being a purely mechanical failure in a tank is relatively small given the number of these birds which have been deployed. It's always non zero, and the number of birds obviously runs the risk of exposing that small chance.
Scott Manley's latest "data centres in space" video points out that they go into a low power mode when over oceans to aid in cooling - if that didn't happen for some reason then you very quickly have a potential software cause for a battery overheat and failure...
Not that I suspect that will turn out to be the issue, but it's one example of the type of things that software can get wrong and cause a hardware failure.
You don't need to know the origin of a rogue packet to block it's egress at the firewall. Likewise a function doesn't have to know how an argument came to be NaN to reject it. And there are plenty of other situations where you can mitigate a behaviour without understanding it's origin. Indeed, the willingness of software to allow a rogue behaviour is, in itself, a bug; even if it's not the root cause.
"If you are still trying to determine the root cause then what the hell are you "already in the process of deploying"?"
It's the same as Tesla sending out an OTA after one of their cars burst into flames in an underground car park before the car could be retrieved and examined. That sounded like they knew they had settings in the battery management system that were too close to the edge. It may have also been damage or a hardware fault and Tesla (Elon, the head of PR) thought that getting out in front with a "solution" to the problem as quickly as possible was better than learning what was wrong first. Model 3 has braking distance issue, send out an OTA the next day. How does a company do a full test of the new software in one day?
The satellite and debris are in a low orbit, which means the drag from the atmosphere will quickly remove the objects from orbit. IIRC, SpaceX deploys the satellites at a lower orbit and then has the satellites boost themselves to the operational orbit. That way, a DOA bird will de-orbit in a relatively short time.
In case of a real Kessler Syndrome event, the lowest orbits will be cleared out in a relatively short time, but the more useful orbits will need some sort of active clearing to become usable.
Yes, however the low initial orbit gives time to shakedown the birds and ensure and DOA ones come down very quickly.
There's a massive need to get some form of international agreement to actively bring down anything out past about 800km. Below that things clear out naturally in a reasonable timeframe
One of the biggest problems is that anything capable of deorbiting junk - whether a ground based system like a laser broom, or a space based tugboat - is also capable of deorbiting active hardware belonging to people who don't want it deorbited. That results in the simgle biggest impediment to solving problem being political, not technical. GIven human nature and politicians in particular, it's quite likely that agreements on cleanup won't ha[[en until something has already gone catastrophically wrong
"Why do we need to spend money on this? Nobody's been hurt in 75 years. Why do we need to worry about this now?"
Perhaps you should take a look at the Falcon 9 record and there are over 9300 closing in on 9400 Starlink satellites in orbit, almost but not all of them operational so I'm not surprised that ONE of them went boom. Obviously it would be much better for this to not happen but we are not very good at getting 100% no boom with complex space systems. And for the record I would like Elon to stay as far away from SpaceX as possible. Well at least I can dream.
Just a genuine question here. Can you point me to any data showing the number or percentage of Starlink satellites that remain operational? I have not been able to find even a crummy AI summary that offers that data. It's easy to find how many have been launched, but I just don't see anything hinting at reliability numbers.
Via Google using "how many starlink satellites in orbit are not operational" and Space.com
"As of Dec. 19, 2025, there are currently 9,357 Starlink satellites in orbit, of which 9,347 are working, according to Astronomer Jonathan McDowell, who tracks the constellation on his website."
Not sure how he determines which ones are operational and I the "AI" response said that 1200 were not operational. However that response doesn't say how many of these are due to not being in the correct orbit yet or why any of the others are nonfunctional such as being in the process of de-orbiting after reaching expected lifetime. I believe that neither are completely accurate for the reasons stated and further googling did not provide any useful information, at least that I saw.
P.S. I have found on at least three occasions where Google "AI" was blatantly wrong so add that to the reasons for being uncertain.
> Just a genuine question here. Can you point me to any data showing the number or percentage of Starlink satellites that remain operational?
You can download the dataset (and do your maths) from:
https://www.space-track.org/
If you don't want to create a free account to download the datasets, you can get a copy, updated in February 2025, from:
https://github.com/EnzoRg/space_debris/tree/main/data/raw
"And how many untrackable objects?"
Depends on your threshold of trackable, but rough rule of thumb is that for every trackable object, there are about 10 (smaller) untrackable ones.
If there are 100s of trackable bits of debris, that means 1000s of bits of total debris. Starlink satellites are only 575 kgs, so for one to turn into 1000s (or even 100s) of bits seems like it would have been a highly catastrophic event.
Images of the satellite in question seen to show it largely intact, so even "hundreds" of bits of trackable debris seems a bit of an exaggeration. https://x.com/michaelnicollsx/status/2002419447521562638?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E2002419447521562638%7Ctwgr%5E2197582c8443b96c2fa07bf9cd9fbb8e65f896cf%7Ctwcon%5Es1_c10&ref_url=https%3A%2F%2Fwww.space.com%2Fspace-exploration%2Fsatellites%2Fdoomed-spacex-starlink-satellite-photographed-from-orbit
"And you can design space craft in other languages."
In the US, you must be a "US Person" to work in aerospace. That doesn't exclude people born elsewhere, but the majority will be native USAins. Except for finance. Elon seems to prefer native born Indian people with thick accents for senior financial roles.
For any parents who bought toys for their kids, let's hope they remembered to bag some back up internal energetic sources.
Commiserations to anyone whose loved ones fully demised this year.
And whilst you are on holiday, don't forget to work to root cause and mitigate that wonky shelf.
How do these fcukers get jobs in science talking BS like this? They should be ashamed of themselves.