Comment by yokem55
15 days ago
The solution here is for Spacex to tighten up their planned reentry corridors. At this point they should have more than enough experience in their ops to narrow down the likely debris field to a narrow strip that can be easily flown around instead of the huge swath of Indian Ocean they'd been allowing for.
It's for the starship test flights. Given the nature of the program, the areas are currently "large":
https://x.com/planet4589/status/1765586241934983320/photo/2
It says they had to delay several flights over a period of a few weeks. Starship isn’t flying anywhere near that often. These are routine Falcon 9 flights and they should be able to have very tight windows in time and space.
My reading is that SpaceX was loose with their windows because it’s easier and they didn’t think it mattered in a remote part of the ocean. Now that there’s an actual reason, they’ll probably tighten it up.
No, these are delays for anticipated Starship reentries over the Indian ocean. Falcon 9 doesn't reenter there. They keep on scrubbing and rescheduling the launch, that's why it's been several times in the past few weeks.
Don't they typically dispose of falcon 9 second stages over the Indian Ocean? That would be happening much more often than test flights.
Second stage and satellite disposal target is typically Point Nemo in the Pacific Ocean, 2688 kilometers away from the Pitcairn Islands, Easter Islands and Antarctica.
Nobody is flying or sailing at Point Nemo. The keepout zone typically has a massive 1000km diameter, but approximately 0 impact on anybody.
2 replies →
Those probably already have the tight reentry corridor the parent comment requests
1 reply →
Remember that part of the current testing program includes testing whether or not they can reliably relight their engines on orbit in order to do things like a controlled re-entry. Given the nature of that testing I imagine there's very little room for narrowing their re-entry corridors. If the test succeeds they may re-enter earlier and if it fails they'll re-enter later... or laterally different... either way lighting up the engines for the test probably changes the trajectory of the spacecraft.
The one thing they can do is be sure the original trajectory that gets them to space intersects the Earth within some reason so that if things don't go as planned it doesn't go too far afield.
At best this article is a complaint about communication of whether or not a launch is happening. And even that's hard to really do reasonably: weather, maybe a stuck valve during the countdown, maybe a leisure boat close to the launch site enters the exclusion area... all of those things have happened and prompted changes in launch times and many of those things are outside of SpaceX control.
So seems to me you can lock up the airspace on a "just in case" basis with lots of advanced warning but also reserving lots of time that you won't really need in the end... you know... just in case... , or lock it up much less, but at the cost of relatively short notice to others that might want to use it. Either way you'd still get the article protesting... it's just the complaint would be different.
They will be tightening them as the starship program continues. It's just still in a testing stage right now.
I also want to point out SpaceX still does a better job than some competitors (ahem, ariane, which gets a pass because it's the eurocrat's baby therefore must be good)
The solution here is for them to nail landings. This is a temporary problem during testing. Hopefully there will only be one or two more launches that reenter over the Indian Ocean before they start landing the ship at the launch pad instead.
Their last few rentries have been extremely tight, doing simulated landings on the water right next to a prepositioned camera buoy. The position of the buoy is almost certainly less precise than the rocket itself.