If a Voyager crashes into something, would we know?
A recent question asked about the feasibility of using Voyager 2 to detect objects in the Oort cloud. The answers indicate, among other issues, the instruments on-board the Voyagers would likely be insufficient to perform such detection.
However, in theory there is at least one way to detect objects without any specialized equipment: direct collision. The Voyagers are moving very fast, so such a collision would probably render the craft non-functional.
I'd like to separate the "detecting collisions" problem from the various ones raised in the other question, so rather than Oort cloud objects let's suppose one of the Voyagers collides with some previously undetected object tomorrow. In that case, Would we be able to distinguish a crash from other possible failures?
communication voyager impact
add a comment |
A recent question asked about the feasibility of using Voyager 2 to detect objects in the Oort cloud. The answers indicate, among other issues, the instruments on-board the Voyagers would likely be insufficient to perform such detection.
However, in theory there is at least one way to detect objects without any specialized equipment: direct collision. The Voyagers are moving very fast, so such a collision would probably render the craft non-functional.
I'd like to separate the "detecting collisions" problem from the various ones raised in the other question, so rather than Oort cloud objects let's suppose one of the Voyagers collides with some previously undetected object tomorrow. In that case, Would we be able to distinguish a crash from other possible failures?
communication voyager impact
4
I would think an occultation would be a better way to discover an object crossed a Voyager's path than a crash. My guess is that a crash would be indistinguishable from other events which might result in an abrupt end of communications. With an occultation, we can guess the distance of the object based on size approximations, using the duration of signal loss. Of course, we can't rule out some kind of instrument malfunction in that case either, but if the signal loss doesn't recur, it is less likely to be instrument malfunction.
– called2voyage♦
Dec 11 '18 at 15:54
4
Of course, occultations and crashes are both unlikely, given how vast the expanse of space is.
– called2voyage♦
Dec 11 '18 at 15:56
add a comment |
A recent question asked about the feasibility of using Voyager 2 to detect objects in the Oort cloud. The answers indicate, among other issues, the instruments on-board the Voyagers would likely be insufficient to perform such detection.
However, in theory there is at least one way to detect objects without any specialized equipment: direct collision. The Voyagers are moving very fast, so such a collision would probably render the craft non-functional.
I'd like to separate the "detecting collisions" problem from the various ones raised in the other question, so rather than Oort cloud objects let's suppose one of the Voyagers collides with some previously undetected object tomorrow. In that case, Would we be able to distinguish a crash from other possible failures?
communication voyager impact
A recent question asked about the feasibility of using Voyager 2 to detect objects in the Oort cloud. The answers indicate, among other issues, the instruments on-board the Voyagers would likely be insufficient to perform such detection.
However, in theory there is at least one way to detect objects without any specialized equipment: direct collision. The Voyagers are moving very fast, so such a collision would probably render the craft non-functional.
I'd like to separate the "detecting collisions" problem from the various ones raised in the other question, so rather than Oort cloud objects let's suppose one of the Voyagers collides with some previously undetected object tomorrow. In that case, Would we be able to distinguish a crash from other possible failures?
communication voyager impact
communication voyager impact
asked Dec 11 '18 at 15:40
Kamil Drakari
39039
39039
4
I would think an occultation would be a better way to discover an object crossed a Voyager's path than a crash. My guess is that a crash would be indistinguishable from other events which might result in an abrupt end of communications. With an occultation, we can guess the distance of the object based on size approximations, using the duration of signal loss. Of course, we can't rule out some kind of instrument malfunction in that case either, but if the signal loss doesn't recur, it is less likely to be instrument malfunction.
– called2voyage♦
Dec 11 '18 at 15:54
4
Of course, occultations and crashes are both unlikely, given how vast the expanse of space is.
– called2voyage♦
Dec 11 '18 at 15:56
add a comment |
4
I would think an occultation would be a better way to discover an object crossed a Voyager's path than a crash. My guess is that a crash would be indistinguishable from other events which might result in an abrupt end of communications. With an occultation, we can guess the distance of the object based on size approximations, using the duration of signal loss. Of course, we can't rule out some kind of instrument malfunction in that case either, but if the signal loss doesn't recur, it is less likely to be instrument malfunction.
– called2voyage♦
Dec 11 '18 at 15:54
4
Of course, occultations and crashes are both unlikely, given how vast the expanse of space is.
– called2voyage♦
Dec 11 '18 at 15:56
4
4
I would think an occultation would be a better way to discover an object crossed a Voyager's path than a crash. My guess is that a crash would be indistinguishable from other events which might result in an abrupt end of communications. With an occultation, we can guess the distance of the object based on size approximations, using the duration of signal loss. Of course, we can't rule out some kind of instrument malfunction in that case either, but if the signal loss doesn't recur, it is less likely to be instrument malfunction.
– called2voyage♦
Dec 11 '18 at 15:54
I would think an occultation would be a better way to discover an object crossed a Voyager's path than a crash. My guess is that a crash would be indistinguishable from other events which might result in an abrupt end of communications. With an occultation, we can guess the distance of the object based on size approximations, using the duration of signal loss. Of course, we can't rule out some kind of instrument malfunction in that case either, but if the signal loss doesn't recur, it is less likely to be instrument malfunction.
– called2voyage♦
Dec 11 '18 at 15:54
4
4
Of course, occultations and crashes are both unlikely, given how vast the expanse of space is.
– called2voyage♦
Dec 11 '18 at 15:56
Of course, occultations and crashes are both unlikely, given how vast the expanse of space is.
– called2voyage♦
Dec 11 '18 at 15:56
add a comment |
1 Answer
1
active
oldest
votes
Most likely no.
Voyager downlink communication (via its radio link to NASA's Deep Space Network (DSN) is not continuous. You can check the contact schedule at this Voyager site. If everything looks fine during one DSN contact period, and then at the next contact period there's no signal at all, there are myriads of possible causes, ranging from failure of the radio system or the attitude control system that points the antenna to Earth, to running into something.
If it runs into something, that something doesn't need to be very large. Voyager 1 is receding at nearly 17 km/s, Voyager 2 at ~15.4 km/s, so a BB-sized ice particle could sever the connection to the RTG (the radioisotope battery that powers everything). If rocky or metallic, it could penetrate the multi-layer insulation covering the bus and blast a hole in the main propellant tank...there are multiple soft spots. In any case, all we would know is that when we tried again to contact the craft, we heard nothing.
If, on the other hand, something happened while we were in contact, the radio signal's strength profile would give some clues, though not necessarily definitive. Most failure modes would have the signal die off rather slowly, some faster, some slower. For instance, complete loss of attitude control would have it die off very slowly, with a well-determined profile as the direction to Earth drifts through the HGA's main beam, then into side lobes. Catastrophic rupture of the main propellant tank (very unlikely!) would have it die off in tens of milliseconds, but not between individual bits of data, at the current downlink rate of 160 bps.
There are very few scenarios that would interrupt downlink mid-bit, and collision with something big is one of them. But there is more than one fast-loss scenario. An example might be catastrophic failure of the X-band transmitter's traveling wave tube (TWT), something like breaking the lead to the internal helix coil, though I suppose they would try later to see if they get an S-band signal. A power glitch that smoked both the S-band and X-band TWTs might prevent that. Anyway, there are non-collision events that could interrupt comm mid-bit. They are unlikely, but then again, so is running into something big.
The net result: we wouldn't know for sure.
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
7
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
2
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
1
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
1
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
|
show 3 more comments
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "508"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f32766%2fif-a-voyager-crashes-into-something-would-we-know%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most likely no.
Voyager downlink communication (via its radio link to NASA's Deep Space Network (DSN) is not continuous. You can check the contact schedule at this Voyager site. If everything looks fine during one DSN contact period, and then at the next contact period there's no signal at all, there are myriads of possible causes, ranging from failure of the radio system or the attitude control system that points the antenna to Earth, to running into something.
If it runs into something, that something doesn't need to be very large. Voyager 1 is receding at nearly 17 km/s, Voyager 2 at ~15.4 km/s, so a BB-sized ice particle could sever the connection to the RTG (the radioisotope battery that powers everything). If rocky or metallic, it could penetrate the multi-layer insulation covering the bus and blast a hole in the main propellant tank...there are multiple soft spots. In any case, all we would know is that when we tried again to contact the craft, we heard nothing.
If, on the other hand, something happened while we were in contact, the radio signal's strength profile would give some clues, though not necessarily definitive. Most failure modes would have the signal die off rather slowly, some faster, some slower. For instance, complete loss of attitude control would have it die off very slowly, with a well-determined profile as the direction to Earth drifts through the HGA's main beam, then into side lobes. Catastrophic rupture of the main propellant tank (very unlikely!) would have it die off in tens of milliseconds, but not between individual bits of data, at the current downlink rate of 160 bps.
There are very few scenarios that would interrupt downlink mid-bit, and collision with something big is one of them. But there is more than one fast-loss scenario. An example might be catastrophic failure of the X-band transmitter's traveling wave tube (TWT), something like breaking the lead to the internal helix coil, though I suppose they would try later to see if they get an S-band signal. A power glitch that smoked both the S-band and X-band TWTs might prevent that. Anyway, there are non-collision events that could interrupt comm mid-bit. They are unlikely, but then again, so is running into something big.
The net result: we wouldn't know for sure.
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
7
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
2
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
1
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
1
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
|
show 3 more comments
Most likely no.
Voyager downlink communication (via its radio link to NASA's Deep Space Network (DSN) is not continuous. You can check the contact schedule at this Voyager site. If everything looks fine during one DSN contact period, and then at the next contact period there's no signal at all, there are myriads of possible causes, ranging from failure of the radio system or the attitude control system that points the antenna to Earth, to running into something.
If it runs into something, that something doesn't need to be very large. Voyager 1 is receding at nearly 17 km/s, Voyager 2 at ~15.4 km/s, so a BB-sized ice particle could sever the connection to the RTG (the radioisotope battery that powers everything). If rocky or metallic, it could penetrate the multi-layer insulation covering the bus and blast a hole in the main propellant tank...there are multiple soft spots. In any case, all we would know is that when we tried again to contact the craft, we heard nothing.
If, on the other hand, something happened while we were in contact, the radio signal's strength profile would give some clues, though not necessarily definitive. Most failure modes would have the signal die off rather slowly, some faster, some slower. For instance, complete loss of attitude control would have it die off very slowly, with a well-determined profile as the direction to Earth drifts through the HGA's main beam, then into side lobes. Catastrophic rupture of the main propellant tank (very unlikely!) would have it die off in tens of milliseconds, but not between individual bits of data, at the current downlink rate of 160 bps.
There are very few scenarios that would interrupt downlink mid-bit, and collision with something big is one of them. But there is more than one fast-loss scenario. An example might be catastrophic failure of the X-band transmitter's traveling wave tube (TWT), something like breaking the lead to the internal helix coil, though I suppose they would try later to see if they get an S-band signal. A power glitch that smoked both the S-band and X-band TWTs might prevent that. Anyway, there are non-collision events that could interrupt comm mid-bit. They are unlikely, but then again, so is running into something big.
The net result: we wouldn't know for sure.
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
7
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
2
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
1
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
1
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
|
show 3 more comments
Most likely no.
Voyager downlink communication (via its radio link to NASA's Deep Space Network (DSN) is not continuous. You can check the contact schedule at this Voyager site. If everything looks fine during one DSN contact period, and then at the next contact period there's no signal at all, there are myriads of possible causes, ranging from failure of the radio system or the attitude control system that points the antenna to Earth, to running into something.
If it runs into something, that something doesn't need to be very large. Voyager 1 is receding at nearly 17 km/s, Voyager 2 at ~15.4 km/s, so a BB-sized ice particle could sever the connection to the RTG (the radioisotope battery that powers everything). If rocky or metallic, it could penetrate the multi-layer insulation covering the bus and blast a hole in the main propellant tank...there are multiple soft spots. In any case, all we would know is that when we tried again to contact the craft, we heard nothing.
If, on the other hand, something happened while we were in contact, the radio signal's strength profile would give some clues, though not necessarily definitive. Most failure modes would have the signal die off rather slowly, some faster, some slower. For instance, complete loss of attitude control would have it die off very slowly, with a well-determined profile as the direction to Earth drifts through the HGA's main beam, then into side lobes. Catastrophic rupture of the main propellant tank (very unlikely!) would have it die off in tens of milliseconds, but not between individual bits of data, at the current downlink rate of 160 bps.
There are very few scenarios that would interrupt downlink mid-bit, and collision with something big is one of them. But there is more than one fast-loss scenario. An example might be catastrophic failure of the X-band transmitter's traveling wave tube (TWT), something like breaking the lead to the internal helix coil, though I suppose they would try later to see if they get an S-band signal. A power glitch that smoked both the S-band and X-band TWTs might prevent that. Anyway, there are non-collision events that could interrupt comm mid-bit. They are unlikely, but then again, so is running into something big.
The net result: we wouldn't know for sure.
Most likely no.
Voyager downlink communication (via its radio link to NASA's Deep Space Network (DSN) is not continuous. You can check the contact schedule at this Voyager site. If everything looks fine during one DSN contact period, and then at the next contact period there's no signal at all, there are myriads of possible causes, ranging from failure of the radio system or the attitude control system that points the antenna to Earth, to running into something.
If it runs into something, that something doesn't need to be very large. Voyager 1 is receding at nearly 17 km/s, Voyager 2 at ~15.4 km/s, so a BB-sized ice particle could sever the connection to the RTG (the radioisotope battery that powers everything). If rocky or metallic, it could penetrate the multi-layer insulation covering the bus and blast a hole in the main propellant tank...there are multiple soft spots. In any case, all we would know is that when we tried again to contact the craft, we heard nothing.
If, on the other hand, something happened while we were in contact, the radio signal's strength profile would give some clues, though not necessarily definitive. Most failure modes would have the signal die off rather slowly, some faster, some slower. For instance, complete loss of attitude control would have it die off very slowly, with a well-determined profile as the direction to Earth drifts through the HGA's main beam, then into side lobes. Catastrophic rupture of the main propellant tank (very unlikely!) would have it die off in tens of milliseconds, but not between individual bits of data, at the current downlink rate of 160 bps.
There are very few scenarios that would interrupt downlink mid-bit, and collision with something big is one of them. But there is more than one fast-loss scenario. An example might be catastrophic failure of the X-band transmitter's traveling wave tube (TWT), something like breaking the lead to the internal helix coil, though I suppose they would try later to see if they get an S-band signal. A power glitch that smoked both the S-band and X-band TWTs might prevent that. Anyway, there are non-collision events that could interrupt comm mid-bit. They are unlikely, but then again, so is running into something big.
The net result: we wouldn't know for sure.
answered Dec 11 '18 at 17:32
Tom Spilker
8,2911948
8,2911948
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
7
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
2
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
1
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
1
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
|
show 3 more comments
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
7
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
2
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
1
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
1
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
Would we know if the trajectory of Voyager was altered by a significantly large comet? I believe another answer stated the largest theoretical comet size to be ~300km (or something along those lines) if this perturbed the path of voyager, but did not sever the connection via impact or anything else, would we be able to know?
– Magic Octopus Urn
Dec 11 '18 at 17:50
7
7
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
@MagicOctopusUrn You bet! Such an alteration would change the Doppler shift on the radio signal's carrier, and spacecraft Doppler tracking is exquisitely sensitive to that. We'd know in a heartbeat that something bent our trajectory!
– Tom Spilker
Dec 11 '18 at 17:57
2
2
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
What's the smallest significant deviation in trajectory that can be detected? Are we talking in the ballpark of a change in velocity of around ~.00001m/s or something much larger?
– Magic Octopus Urn
Dec 11 '18 at 18:14
1
1
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
@MagicOctopusUrn You may be interested in this question, though I don't know that it answers the minimum detectable change.
– Kamil Drakari
Dec 11 '18 at 18:52
1
1
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
@MagicOctopusUrn, if the Pioneer anomaly is any indication, we should be able to track a change measured in parts per million, or possibly parts per billion.
– Mark
Dec 11 '18 at 23:02
|
show 3 more comments
Thanks for contributing an answer to Space Exploration Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f32766%2fif-a-voyager-crashes-into-something-would-we-know%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
I would think an occultation would be a better way to discover an object crossed a Voyager's path than a crash. My guess is that a crash would be indistinguishable from other events which might result in an abrupt end of communications. With an occultation, we can guess the distance of the object based on size approximations, using the duration of signal loss. Of course, we can't rule out some kind of instrument malfunction in that case either, but if the signal loss doesn't recur, it is less likely to be instrument malfunction.
– called2voyage♦
Dec 11 '18 at 15:54
4
Of course, occultations and crashes are both unlikely, given how vast the expanse of space is.
– called2voyage♦
Dec 11 '18 at 15:56