Earlier quoted context omitted.
The article mentions that at the time they said that, the probability of collision wasn't that high. So, it looks totally OK to say they didn't have plans to move it, then, since it means they didn't believe there really was any risk of collision if they both stayed in their current paths. At that time, ESA's query was probably to ensure they didn't have any plans for maneuvers that would raise the probability. > “Th…
At the time they said that, yes, probability of impact was low. But then the probability got much, much, much higher. 10x the probability at which maneuvers are typically made. And we can't chalk it up to what or how SpaceX might have interpreted it. We know interpretation was not the problem. They freely admit that they never saw further messages because of a bug in their process, so we don't need to imagine their i…
No, what I said about interpretation was about the first query when it was a 1 in 50,000 chance. For the message they missed, we don't need to imagine their interpretation because they can't interpret a message they never received.
> Even if we were going to that extent though, clearly such an interpretation doesn't comport itself to how these things are resolved within the community of satellite operators.
At the level of the community, I don't see a problem here. ESA tried to contact SpaceX to agree on a course of action; SpaceX couldn't be contacted because of a bug on their end, so ESA acted on its own to resolve the situation from its end.
I can see a problem if they plan to be a significant portion of all space traffic and they can never be relied on to be contactable in case of problems arising from their satellites. However, this happening once doesn't seem like negligence.