Fire Onboard a Spaceship

  • #36
Strato Incendus said:
Okay, since I’m tired of being stuck at even just planning the midpoint catastrophe in my sci-fi story set on a generation ship
Sorry, I haven't been following these threads very closely. What is the timing of this midpoint? I mean, how many years since the voyage started, or how many generations have passed?
 
Physics news on Phys.org
  • #37
Thanks again for your ideas! :smile: Perhaps I gave up on the fire idea too soon.

This morning, I was thinking about the inverse problem — the heat systems failing in some areas, making them too cold to inhabit. However, the ship needs such thorough insulation against the cold from space that even with a failed heating, the affected areas of the ship probably wouldn’t drop to space temperature right away.

Also, giving off heat if there is no air to give it off to (=outside the ship) is, for all I’ve heard on “Because Science”’s video on realistic space battles, not as easy as most people would believe when they think of how cold space itself is.

DaveC426913 said:
**anybody remember this from the original Battlestar Galactica? They were under attack by the Cylons,
This is what I meant by other sci-fi stories having the luxury of just dropping a random alien attack in there. A military strike by an alien civilisation is like intentional sabotage by crew members, but on steroids. Because they can employ actual weapons designed to destroy spaceships, and do so in a targeted manner.

Without aliens to cause the damage, though, the only threat I have at my disposal in my setting is the mindless cosmos itself.

pinball1970 said:
First part was Newton's third law! I liked the film, it stressed me out though.
Thanks for the video link! ;) It certainly looked believable to me.

Especially the way the fire can suddenly come towards you as you’re trying to put it out — kind of like pouring water on burning fat. That is indeed something I could see taking out a lot of crew members — however, by the same token, they’d only try that once before reconsidering their strategy, after all the survivors have witnessed it happen to their crewmates.

gmax137 said:
Sorry, I haven't been following these threads very closely. What is the timing of this midpoint? I mean, how many years since the voyage started, or how many generations have passed?
Pretty much exactly 100 years into the journey (100 years and 3.5 months); the fifth generation born on the ship is in their twenties.

Note that Generations One, Three, and Five are the major generations, with Two and Four being smaller ones in between. Generation Three are the children of Generation One; Generation Five are the children of Generation Five (much like Millennials are the children of Boomers, but there’s Generation X in between).
 
  • #38
Strato Incendus said:
Pretty much exactly 100 years
OK, so how about a loss of technical knowledge? Not overall knowledge, but understanding/appreciation of specific design choices. Over 100 years, lots of equipment is rebuilt, repaired, modified to keep running or to run better. The original designers were good and did their best, but 100 years of service would show problems not originally considered, and the crew would have had to solve numerous equipment issues, often with minor (or even major) modifications. That's what happens in our world.

So what if over time, some seemingly innocuous changes are made due to ignorance or misunderstanding, and then a confluence of events leads to a disastrous outcome? Something that "shouldn't" have happened under the original design. I have seen this happen, where a well intentioned "fix" to one problem nullifies the intended "safe response" of the system to an upset event.

This avoids the "oh but they would have thought of that" problem, and you can make the result whatever you want -- the air purifying quits, or the heaters/coolers all go out, or the lighting fails, or the ship is vented to space...anything.
 
  • Like
Likes ShadowKraz and Strato Incendus
  • #39
pinball1970 said:
Hollywood do it this....https://youtu.be/pmjfPsc3o_k?si=J0O-Y0RopWeYXP6a

First part was Newton's third law! I liked the film, it stressed me out though.
"The film" being Gravity, for those who don't want to click through.
 
  • Like
Likes pinball1970
  • #40
gmax137 said:
So what if over time, some seemingly innocuous changes are made due to ignorance or misunderstanding, and then a confluence of events leads to a disastrous outcome? Something that "shouldn't" have happened under the original design. I have seen this happen, where a well intentioned "fix" to one problem nullifies the intended "safe response" of the system to an upset event.
The Hyatt Regency Walkway collapse is a good example of this. Although the "fix" happened before the bridge was even constructed. Some engineer didn't understand the critical need for a certain arrangement of rods and nuts to hold the walkways up, and decided to change it - based on his current assessment - without re-doing an analysis of the whole system.

https://en.wikipedia.org/wiki/Hyatt_Regency_walkway_collapse
1719526191066.png

https://www.enr.com/articles/38400-why-engineers-must-remember-the-kansas-city-hyatt-tragedy

The Devil is in the Details is the take away here for story-writing. A specific cause of a snowballing failure might help the reader understand how engineers, who are otherwise perfectly competent, can make bad decisions when not enough data is available.
 
  • Like
Likes ShadowKraz, Strato Incendus and gmax137
  • #41
Real world engineering failures are interesting, fictional ones sound boring. Do you want to recreate Airport 1975 or The Towering Inferno in space? The detail and complexity of real world failures like Titanic are interesting but no one wants to read a bunch of made up jargon about spacecraft mechanics
 
  • Like
Likes Strato Incendus
  • #42
BWV said:
Real world engineering failures are interesting, fictional ones sound boring. Do you want to recreate Airport 1975 or The Towering Inferno in space? The detail and complexity of real world failures like Titanic are interesting but no one wants to read a bunch of made up jargon about spacecraft mechanics
You're probably right. Depends on the skill of the author to keep it from "sounding boring."

Edit: the usual trope is, some rich bastard cut corners leading to the failure... talk about boring...
 
  • Like
Likes Strato Incendus
  • #43
gmax137 said:
Depends on the skill of the author to keep it from "sounding boring."
I'll give my usual, and usually rejected quote by Stephane Malarme: "To suggest is to create; to define is to kill."

A story about how people react to a fire is a story. A story about a fire...not so much. An arson investigation? Less still.
 
  • Like
Likes Strato Incendus
  • #44
Vanadium 50 said:
I'll give my usual, and usually rejected quote by Stephane Malarme: "To suggest is to create; to define is to kill."

A story about how people react to a fire is a story. A story about a fire...not so much. An arson investigation? Less still.
I agree with all of that. But it is @Strato Incendus 's story.
 
  • #45
Vanadium 50 said:
An arson investigation? Less still.
Unless it's a murder mystery. I've read some pretty good "locked room" spaceship murder mysteries.
 
  • Like
Likes BillTre
  • #46
Thanks for your ideas once again!

The Hyatt Regency Walkway is indeed a catastrophe I had already looked up once - don't know quite for which occasion - but I recalled it as soon as you mentioned it.

The place where this would fit together with "loss of (details of the) technical knowledge" over the span of 100 years would probably be the nuclear-fusion drive, since that's the one piece of technology that gets deactivated after the first 25 years into the mission - and has to be turned on again right at the time of the plot events of the first main book.

The fusion reactor itself of course has to remain engaged for the ship's overall power supply, but the drive must be deactivated during the coasting phase.


Major loss of knowledge, such as with the grounders in The 100, who forget the entire origin of their customs and traditions completely over a fairly short lifespan, still seems unbelievable to me on a ship that has a computer server comparable to that of the USS Enterprise (except it's based on internet resources). Plus, the commanding officers have always paid attention to the narratives they feed the population, including the stories and myths they employ for being "functional" for the mission. Hence, the crew are not going to forget about their purpose, where they're coming from (as ensured by "Ancestral Awareness Day"), nor for what reason their ancestors once left Earth (the image of WR 104 is everywhere on board, as a constant reminder of the threat of the universe that they're up against).

Details however, such as using two nuts vs. one nut on a beam, and for what purpose, that is indeed something I could see somebody forgetting - or simply not inferring correctly - without seeming downright incompetent.

So, I guess this is the time where those of you who are somewhat of an expert on nuclear fusion - and the approaches currently proposed to realise it - can shine!
:smile: Specifically, by suggesting some details (if you know any) that two different generations of engineers might have different views on - which could then lead to such fatal misunderstandings as with the Hyatt Regency Walkway.

Any ideas on that in particular? (Even if it moves away from the thread's main topic - we might still get back to the fire idea if this one doesn't lead to any solutions...)
 
  • #47
Think about emergent properties and behaviors - things that cant be deduced from theory or from lab tests. Phenomena that only manifest under full scale long term operations.

And/or read up on experimental craft in the military. See what kinds of things only showed up with prototype testing.
 
  • Like
Likes Strato Incendus and ShadowKraz
  • #48
Thanks for your suggestions! ;) A couple things to consider:

1) We’re talking about a technology that currently does not exist yet (neither nuclear fusion as a reliable energy source, nor as a space drive in particular — and the latter is the thing that would need to cause the problems in this case).

2) Since we’re talking about the braking sequence, it’s not the comparison “lab test vs. active usage”, since the drive already was in active use during the acceleration phase. Rather, it should be a detail about how the drive operates during acceleration that was known to Generation Zero (who are all dead by now), but maybe not even to Generation One anymore. Or any remaining Generation-One members (like the protagonist’s grandparents) could be the ones warning the active crew about these details, to serve as a setup for the issue later, so that it doesn’t come out of nowhere.

Alternatively, it could be something that is NOT a problem during acceleration, but BECOMES a problem during braking. The primary difference is of course that the ship turns around for braking, but I think we’ve discussed the implications of that at length before. So turning the ship alone by itself may not be enough to explain where technical problems suddenly arise from.
 
  • #49
I'm thinking about a problem that could arise during the turn around phase being caused by zero gravity. *Something* was not quite welded/riveted properly (maybe an earlier fix that didn't take into account the turn around maneuver and zero g- lost knowledge*) and the flip plus zero g caused it to catastrophically change position, and the problem involves a radiation leak strong enough that it fatally dosed the crew members dealing with it. Possibly the fire(s) breaking out are caused by another aspect of the problem... over pressures breaking (coolant?) pipes and shorting out electrical systems? adding radiation to the fire emergency and killing the firefighters? Remember, the ship will be experiencing different stress on its structure during acceleration than it will during the turn around. This can explain why the repair failed.
*Maybe the part should have been riveted rather than welded (SR-71 ref) or vice versa?

The zero g idea came to me when a friend of mine mentioned an episode of House, M.D. while we were talking about something completely different. The patient's issue was caused by a defect in her abdomen; her kidneys were not anchored properly, and during her wedding celebration, one tore lose. She would be fine laying down, but upright she had issues.
 
  • Like
Likes Strato Incendus
  • #50
ShadowKraz said:
Remember, the ship will be experiencing different stress on its structure during acceleration than it will during the turn around. This can explain why the repair failed.
This is related to the question which way the ship turns around: "Vertically" or "horizontally"?
Also, how long does the rotating sequence take?


The last time we thought about this, I had the rotating sequence completed within a few seconds - given the speed at which the ship is still coasting at this point, I thought the deflector lasers could only clear the path ahead for so many million kilometres. @DaveC426913 considered the time I allocated for completing the rotating sequence far too short, as far as I recall. ;)

If we now use the dispersed dust cloud in front of the ship as a deflector instead, lasers are no longer required to clear debris ahead of the ship away - or at least the ship won't have to rely on them alone.

Conversely, this makes it even less likely that anything will collide with the ship - since now, we have a passive shield in form of the dust cloud, rather than an active shield made up of deflector lasers, the latter of which could potentially fail.

ShadowKraz said:
The zero g idea came to me when a friend of mine mentioned an episode of House, M.D. while we were talking about something completely different. The patient's issue was caused by a defect in her abdomen; her kidneys were not anchored properly, and during her wedding celebration, one tore lose. She would be fine laying down, but upright she had issues.
Yes, I remember that episode. ;)


Perhaps I'm overcomplicating this. I recently thought of the movie "Don't Look Up" again, as my prequel bears some similarity with it (though most of this I came up with before watching "Don't Look Up"). With regards to technical failure in space...

...the reason why the mining droids trying to mine the comet fail is never actually explained. The viewer is free to assume somebody simply miscalculated during their design, since the whole idea was framed as unreliable from the beginning. Also, with this film being a satire, the actual (thematic) "reason" the droids fail is just "because of the inventor's greed".

Given how hard-sci-fi I've been about the construction of the ship itself thus far, though, I can't get by with just a thematic justification for a random accident happening. While the focus of the story is on psychological and philosophical aspects - not on the engineering aspects - I still want the engineering aspects to be sound enough not to catapult a more technically-minded reader out of the story.

And since my ship has already survived for a century when the story begins, "somebody miscalculated during the construction" is a harder sell. Basically, the only remaining variable which somebody could have miscalculated - aside from wear and tear of the materials over the course of the century that has passed - is indeed the turn-around-and-brake sequence, since that is something the ship does for the first time during my story. At least from interstellar speeds; in the prequel, as they move the ship around between the moon and the orbit of Earth, obviously it has to turn around and brake, too - but from a much slower travelling speed.


So would you suggest something breaking from the rotation of the ship itself?
Or should I stick with the problem of the ship getting pierced by something (which can basically only be a very small dust particle at this point)?
 
  • #51
Strato Incendus said:
The last time we thought about this, I had the rotating sequence completed within a few seconds - given the speed at which the ship is still coasting at this point, I thought the deflector lasers could only clear the path ahead for so many million kilometres. @DaveC426913 considered the time I allocated for completing the rotating sequence far too short, as far as I recall. ;)
The rate limiting factor will be the lateral stresses on the ship during its rotation.

For an operation that's meant to happen only once during the whole trip, you wouldn't want to over-engineer the structures designed to resist these lateral forces, since mass is at a premium. You would therefore make the turnover as slow as possible.

Perhaps that's what went wrong. Perhaps the original design had it being rotated over hours instead of seconds, but that was based on an inaccurate estimation of how much time they had protection using the lasers. With a shortened window of safety, they'd have to speed up the turnover. Something is bound to break loose.
 
  • Like
Likes ShadowKraz and Strato Incendus
  • #52
DaveC426913 said:
Perhaps that's what went wrong. Perhaps the original design had it being rotated over hours instead of seconds, but that was based on an inaccurate estimation of how much time they had protection using the lasers. With a shortened window of safety, they'd have to speed up the turnover. Something is bound to break loose.
Ooh… I think I like where this is going! :biggrin: Thanks a lot!

So basically, the lasers can’t clear enough space in front of the ship to allow for as slow a braking sequence as anticipated. Two follow-up questions:

1) One way to address this issue would be to simply add more lasers all around the ship. If it rotates much more slowly, it will be easier for the lasers to be accurate even during rotation, won’t it?
The main way to dismiss this would be to argue that extra laser cannons add extra mass… but then again, the ship has a lot of other stuff on board which is probably heavier. So being stingy when it comes to the lasers wouldn’t make sense.

2) What about the dust-cloud solution you considered so brilliant, and which we hadn’t thought of until recently? ;) If this renders lasers redundant, we’ll have to come up with a different reason for flipping the ship faster than intended.
 
  • #53
Strato Incendus said:
What about the dust-cloud solution you considered so brilliant, and which we hadn’t thought of until recently? ;) If this renders lasers redundant, we’ll have to come up with a different reason for flipping the ship faster than intended
I figured it wasn't about inadequate lasers so much as they hit a pocket of dense interstellar dust that wasn't in their predicive models.

They can't predict that very well when first plotting the trip and it's just bad luck that they came upon the cloud right at turn over. A risk they knew about on launch yet nonetheless unavoidable.

Ejecting a defensive cloud ahead of the ship is all well and fine but if the onslaught of interstellar dust is dense enough it will deplete the defensive cloud faster than ideal, requiring a dangerous, but unavoidable, fast turnover.
 
  • Like
Likes ShadowKraz and Strato Incendus
  • #54
DaveC426913 said:
I figured it wasn't about inadequate lasers so much as they hit a pocket of dense interstellar dust that wasn't in their predicive models.

They can't predict that very well when first plotting the trip and it's just bad luck that they came upon the cloud right at turn over. A risk they knew about on launch yet nonetheless unavoidable.
Wow, that’s great! Believe it or not, that was precisely the idea I had last night when thinking about this. 🤯 Perhaps it’s simply the most straightforward, “Ockham’s razor” explanation. I’m glad I didn’t post it, though, because the fact that you came up with this independently from me suggests to me it will intuitively make sense to the reader, too. :wink:

Last night, I was wondering whether the pocket of dense interstellar dust should be “caused” by something (so that it feels less like plot convenience), or if it should indeed be the randomness of space you can encounter at any moment — the latter would fit thematically, since the crew kind of see the surrounding universe / cosmos as the external enemy that’s always out to kill them.

This is why I’m so fond of your suggestion, because it moves the cause the of the problem back to the ship’s exterior. Even though this thread has moved away from the original idea of a fire breaking out on board (which could of course still happen as a result of this), a fire inside the ship would ultimately have felt more like human failure at best, and deliberate sabotage at worst.

The best part is, going back to the issue of interstellar dust particles even allows me to keep the additional problem of a single dust particle piercing the ship hull (and potentially killing some people as it passes through the ship). This is something we’ve discussed at length before — I simply won’t specify the actual size of the dust particle, so that the debate doesn’t become about whether a particle of this size at 0.125 c would have destroyed the entire ship, or simply punched holes into the walls of several rings and/or water tanks (the latter of which are used for both shielding against radiation and as fuel storage for the nuclear-fusion drive).

In short: The dense dust cloud which the lasers can’t handle in time is what causes them to turn around faster than intended, and that causes friction on the ship’s structure. Given the setup of “the lasers can’t handle this much dust”, the odds of at least one speckle of dust piercing the ship would actually be higher, so this wouldn’t come out of nowhere.

DaveC426913 said:
Ejecting a defensive cloud ahead of the ship is all well and fine but if the onslaught of interstellar dust is dense enough it will deplete the defensive cloud faster than ideal, requiring a dangerous, but unavoidable, fast turnover.
Great! :) This means the ship had this extra layer of protection, but it was depleted — rather than the ship designers / earlier generations of crew members “simply having forgotten” about this option. I always prefer the “we had it, but it got destroyed” explanation (especially since the ship can only recycle its resources, not pick up any new ones) over “we forgot to include it at launch”.


I think you’ve once again solved a major issue for my story, @DaveC426913 — and more importantly, this time, it was one of the major plot holes that was keeping me stuck for several years! :D (I think I should probably include a “Dave” at some point in the prequel, among the ship designers… because the Exodus’s iconic dumbbell design was also your idea.) Many thanks once again for all of your ideas and effort! :biggrin:


Now all that’s left is to predict the characters’ responses to this issue:


1) The decision to turn the ship faster than intended has to be based on the commanding staff picking up the denser dust cloud prior to getting there.
This means they will now also anticipate any higher risk of the ship being hit by dust particles. That doesn’t mean they’ll be able to prevent them — however, it allows them to brace for impact:
Where would a responsible commander have the crew members go inside the ship if she must factor in that the lasers might not be able to vaporise all the dust particles in this dense cloud during the rotation process?
Would they be safer in the ring sections, or would the commander send everyone who isn’t needed elsewhere into the central trunk (“pipe”) of the ship, around which the rings rotate? Or maybe even to the front sphere of the ship, as it will be the first thing that no longer has to face the incoming barrage of interstellar particles?

2) The obvious alternative to “turning the ship around faster” would be “let’s keep coasting until we’ve passed the dust cloud, and only rotate the ship once we’ve made it through, at the intended rotation speed”. This would be the more cautious way of doing it, so I need to find a way to rule out this option in order to not make my commanding staff come off as reckless for deciding to turn the ship when it’s at its most vulnerable.
The easiest way would be to simply postulate that this dust cloud is so big that the ship would overshoot the target star by several decades if it kept coasting through the entire dust cloud. Even then, though, some could frame this as the preferable alternative to risking the lives of crew members.

Hence, if the commander decides, “this takes too long, we take the risk”, she could come off as selfish / impatient for prioritising getting to the destination star on time. Her own commitment to the mission is in fact more in line with “keeping everyone alive” than with “getting to the planet as fast as possible” — the latter would fit the pilot’s motivation, though, so I could let the pilot make that suggestion.



Two arguments that could convince the commander to take the rest of turning the ship around now and fast, rather than impatience on her own part, would be:

a) The current generation of crew members were promised they would be the ones to land on the surface of the planet. This is amplified by the fact that the commander raised the number of allowed (and suggested) children per family from 2 to 4 (the inciting incident of the plot).
If she now has to backpedal and say it will take much longer, and that this generation won’t be the one to land on the surface, after all — because they must overshoot the destination star in order to only brake once they’ve made it through the dust cloud — she will face a very disappointed and probably angry crew, because they were promised something else. The commander might also find herself having to take back the four-child policy (which would indeed go against her personal convictions).
Of course, all of this ends up backfiring, because the drive takes damage in this disaster, reducing its braking force, and thereby causing the ship to overshoot the target anyway — in fact, by a century. (This is something we developed in an earlier thread.)

On a thematic level: The commander could then conclude that she prioritised the crew’s well-being — their desire to be the ones to land on the surface — over the survival of everyone. This goes against her personal convictions (she’s all about “sacrifice of well-being in the name of preserving life”); however, her choice could be a result of listening to her bridge officers. Namely, the pilot and the navigator, both representing the “well-being” side of the argument.
With this quick-rotation move backfiring on everyone, it would incentivise the commander to not only double down on her own “survival above well-being” convictions, but it would also give her a reason to become less democratic in the wake of this event: If she hadn’t listened to her bridge staff, they would probably have overshot the target by just a few decades, not a century — and everyone would still be alive.

The “well-being” side, in turn, gets to point to an earlier situation, in which somebody suggested braking a little earlier so that the ship would be slow enough to one day pick up an ice deposit at the edge of the target solar system — extra water which could be stored in some of the depleted fuel/radiation-shielding tanks, and then pumped into the system to allow everyone a few more minutes of shower time per day. This is a suggestion that the commander rejected in order to make it to the target planet on time — after all, it was merely about convenience for the crew, a mere luxury, not essential to the success of the mission. However, in hindsight, if the ship had started braking that early, they would have turned around before even encountering the dust cloud.


b) The primary “selfless” reason to make it to the destination planet as quickly as possible is not what the crew members want, but what humanity back on Earth expects the crew of the generation ship to do: Colonise the planet to create a safe haven that more humans from Earth can escape to, before the impending gamma-ray burst from WR 104 hits the entire solar system.

Thus, there are still also good survival reasons to be “in a rush”. This is something a bridge officer on the “survival over well-being” side could invoke, while still arguing for “let’s turn the ship around now, and fast”. Same conclusion, different motivation. I think this would suit the commander’s first officer.


And the best part: For all the parallels I’ve set up between my ship and the Titanic (even though mine doesn’t get destroyed in this event), the course of events looks quite comparable: The Titanic crew used the fatal combination of “hard-a-starboard” and “reverse gear”; some have suggested the ship would have taken less damage even if it had passed through the iceberg head-on.
Turning the Exodus around in a rush and trying to brake, rather than coasting through the dust cloud at the previous speed while firing all lasers, is ultimately the decision that causes more damage to the ship. The Titanic parallels are also why I’d like to keep the part with the dust particle piercing the ship hull. However, that particle alone isn’t going to kill a lot of people (it doesn’t even have to kill anyone; it could just pierce a bunch of layers which then require quick fixing).

The damage to the ship’s structure as a result of rotating faster than intended is going to be the primary problem. If I set up the warning that the ship wasn’t built for this level of stress, that may give me some leeway to render the potentially ensuing problems as unpredictable. If the reader buys that, I can have a bunch of different, seemingly unrelated issues pop up on board, as a result of this fast turnaround: fires breaking out, pipes bursting, power cuts etc.

The cause is an external threat by the universe, but the consequences ultimately still stem from the characters’ decisions… Sounds like an optimal combination of what people commonly consider “good writing”.

As I’ve said: I really like where this is going now! :biggrin: It finally feels like all the pieces are coming together, both on a plot and character-motivation level / in-universe and on a thematic level.
 
  • #55
wow... I'm already hooked on this trilogy and you haven't even published it yet. When you do, I hope you post something tagging me so I can rush out, buy a copy, mail it to you, and have you sign it. I'll include postage to get it back to me.
 
  • Like
Likes Strato Incendus
  • #56
Strato Incendus said:
The primary “selfless” reason to make it to the destination planet as quickly as possible is not what the crew members want, but what humanity back on Earth expects the crew of the generation ship to do: Colonise the planet to create a safe haven that more humans from Earth can escape to, before the impending gamma-ray burst from WR 104 hits the entire solar system.

Thus, there are still also good survival reasons to be “in a rush”
Ehh...

Except that the goal of a "safe haven" was met as soon as the ship left Sol system. They're safe from the GRB.

Their highest priority switches to ensuring they survive to establish planetfall and rebuild. It would be counterproductive to do anything that might risk their safe colonization - including rushing it.
 
  • #57
That's why I said "safe haven that more humans from Earth can escape to". :wink: Obviously, the crew themselves are safe once they leave the Sol system - or, more accurately, the area of the cone of the gamma-ray burst (which is likely to extend a little beyond the Sol system).

However, the "duty" to even build the colony on the target planet in the first place - and do so quickly - arises from the responsibility the crew have to the people left on Earth. Otherwise, if it were just about their own survival, they could turn the generation ship into a permanent habitat, much like an O'Neill cylinder.

This gets more interesting once the crew must assume a different disaster struck Earth in the meantime - we've been going back and forth between the gamma-ray burst going off and a massive solar storm hitting Earth. Because now, the more individualistic people on the ship conclude their duty to the people on Earth - and thereby, their duty to the mission - has been rendered void. Whereas the more collectivist people on board conclude that it's now more important than ever that they ensure the survival of humanity - even if "humanity" only includes them.


ShadowKraz said:
wow... I'm already hooked on this trilogy and you haven't even published it yet. When you do, I hope you post something tagging me so I can rush out, buy a copy, mail it to you, and have you sign it. I'll include postage to get it back to me.
Thanks for your enthusiasm! :smile: Obviously, I will inform everyone on this forum if and when the first volume does eventually get released... the whole ship wouldn't exist without all of you.


So, getting back to these remaining to questions:

Strato Incendus said:
1) Where would a responsible commander have the crew members go inside the ship if she must factor in that the lasers might not be able to vaporise all the dust particles in this dense cloud during the rotation process? Would they be safer in the ring sections, or would the commander send everyone who isn’t needed elsewhere into the central trunk (“pipe”) of the ship, around which the rings rotate? Or maybe even to the front sphere of the ship, as it will be the first thing that no longer has to face the incoming barrage of interstellar particles?

Strato Incendus said:
2) The obvious alternative to “turning the ship around faster” would be “let’s keep coasting until we’ve passed the dust cloud, and only rotate the ship once we’ve made it through, at the intended rotation speed”. This would be the more cautious way of doing it, so I need to find a way to rule out this option in order to not make my commanding staff come off as reckless for deciding to turn the ship when it’s at its most vulnerable.
The easiest way would be to simply postulate that this dust cloud is so big that the ship would overshoot the target star by several decades if it kept coasting through the entire dust cloud.

Question 1) assumes they've already decided to turn the ship within the dense dust cloud;
Question 2) is the more pressing one - the last remaining puzzle piece - as this is the one potential plot hole that will prevent the reader from believing any of this if I don't address it.
 
  • Like
Likes ShadowKraz and DaveC426913
  • #58
Strato Incendus said:
Question 2) is the more pressing one - the last remaining puzzle piece - as this is the one potential plot hole that will prevent the reader from believing any of this if I don't address it.
I think your postulate, that the cloud is much bigger than was previously estimated, is the best solution. I would point out, however, that coasting through it before turning the ship could be the factor that causes the crisis.
In order to not over shoot the destination, perhaps they use higher thrust and therefore expose the ship's structure to higher stresses than designed for... possibly causing several breakages or mis-alignments. Even a short period of higher thrust could cause these. The fire(s) could break out due to this; the fire systems fail or are at reduced function, other systems fail or have reduced function, etc. The higher g-force the crew experiences while trying to deal with these issues could lead to accidents among all of the repair crews. You won't need to have one big accident, but many smaller accidents.
Just spitballing while the coffee kicks in.
 
  • Like
Likes Strato Incendus
  • #59
ShadowKraz said:
I think your postulate, that the cloud is much bigger than was previously estimated, is the best solution.
While beginning to write the scene where the characters first discover the cloud, I started wondering whether this dust cloud might be to the destination star system what the Oort cloud is to the Sol system?

At the point of encountering the dust cloud, the ship has 25 years left to go, according to the original plans.
The last 25 years are the braking phase, just like the first 25 years were the acceleration phase. Based on the Relativistic Rocket calculator, the ship would cover 1.5 light-years during the acceleration phase, and the same distance during braking, for a total of about 3 light-years under power. Meaning, they discover the dust cloud at roughly a distance of 1.5 light-years to the destination star.

1.5 light-years is about the distance of the Oort cloud from Earth - this is in fact crucially relevant for the second prequel, where someone attempts to destroy the ship by having it collide with some object in the Oort cloud.

Of course, a G-type star like the sun may have a larger cloud, compared to an M-type red dwarf like Teegarden's Star. So the question is whether 1.5 light-years away from Teegarden's Star, the ship would already run into the outskirts of this star's "Oort cloud". I discovered that red dwarf stars have a much higher surface gravity than the sun; however, I'm not sure whether this would somehow still affect matter so far away from the star?


ShadowKraz said:
I would point out, however, that coasting through it before turning the ship could be the factor that causes the crisis.
Thanks for the alternative suggestion! ;) I think this is contingent on my question described above?

Since if this dust cloud isn't just "a random obstacle in space", but already marks the beginning of the Teegarden system, chances are the density of matter per unit of space is going to increase, the further the ship ventures into the Teegarden system, right?
 
  • #60
Strato Incendus said:
I discovered that red dwarf stars have a much higher surface gravity than the sun; however, I'm not sure whether this would somehow still affect matter so far away from the star?
The high surface gravity is due to the small radius of the star. At solar system distances the low mass of the red dwarf means its effect on other bodies is less (compared to more massive stars such as our sun).
 
  • Like
Likes ShadowKraz and Strato Incendus
  • #61
gmax137 said:
The high surface gravity is due to the small radius of the star. At solar system distances the low mass of the red dwarf means its effect on other bodies is less (compared to more massive stars such as our sun).
Thanks for the quick reply; indeed, I didn't really expect the surface gravity to still have an effect this far out - I was just hoping to somehow justify the range of this Oort cloud (and by "hoping", I mean "grasping at straws" ;) ).

Is there any way to calculate how close to an M-type red-dwarf star you'd have to get before encountering its equivalent of the Oort cloud (if it has one)?
 
  • #62
Of course, they will be expecting to encounter Teegarden's Oort Cloud so it can't exactly catch them by surprise. It would be a mission planning flaw to wait until they were almost on top of the target system's outer cloud to do their turn around procedure.

Here is a question: if some fraction (50%?) of the journey is spent coasting, when is the optimal time to turn the ship, all factors considered? As soon as feasible, as late as feasible? Somewhere in the middle?
 
  • Like
Likes ShadowKraz and Strato Incendus
  • #63
I'm glad you once again independently from myself came up with the same follow-up question that popped up in my head as I was writing this scene :wink:: Why not simply turn the ship around at the halfway point of the journey, in the interstellar medium, without having to brake right away?

The dust cloud can of course still be a problem, but only in the sense of "one speckle of dust might pierce the ship hull" - i.e., exactly what I had happen so far, except it would now not be happening while turning the ship around; rather, the ship would already be facing backwards, and the dust cloud would simply be so dense that it depleted the ship's own dust cloud, plus one speckle would also make it past the deflector lasers.

However, that once again restricts the damage the ship can take from the dust cloud to that of the impact of the speckle itself - the extra damage that turning the ship around too quickly would cause would now be off the table again, if the ship has already turned around several decades prior to that. 🤔


I guess I should have figured this idea sounded to good to be true... or rather, too good to actually work in the context of the story. Turns out, if you allow your characters to be smart within your head, they will try everything in their power to prevent the disaster from happening. I feel like a dungeon master who is constantly being outsmarted by the characters of his playgroup... and these characters don't even have other players steering them! 😅
 
  • Like
  • Haha
Likes ShadowKraz and DaveC426913
  • #64
Strato Incendus said:
I feel like a dungeon master who is constantly being outsmarted by the characters of his playgroup... and these characters don't even have other players steering them! 😅
Those darned players always screw things up! (long story about players outsmarting me by accident and completely ruining the dungeon)

As for the turn around...
the ship gets turned after the initial acceleration ends - it doesn't matter when, but we still have the issue with *something* going out of alignment and it doesn't get detected for the same reason as the kidney issue from post #49; it doesn't get detected because it doesn't look or act out of alignment with no acceleration applied. Once the braking acceleration is applied... it goes out of whack and crisis commences.
Yes, I know, design, engineering, and quality control are tight but errors and sabotage do happen even under the tightest regimes. Maybe sabotage during construction?

Yeah, I am kinda married to the idea. Tell me, however, to give it up and I will.
 
  • Like
Likes Strato Incendus
  • #65
ShadowKraz said:
As for the turn around...
the ship gets turned after the initial acceleration ends - it doesn't matter when

Maybe over the generations the "turn around" takes on a kind of religious or faith-based aura. Some people want to do it as soon as the coast period begins, others want to wait, others think it signifies a lack of trust in the grand plan.
 
  • Like
Likes Strato Incendus
  • #66
ShadowKraz said:
the ship gets turned after the initial acceleration ends - it doesn't matter when,
The mission would be planned to turn the ship around at the optimal time, whch is not necessarily right after the onset of the coasting leg.

The question is: what factors would or could arise duing that time that should be taken into account. Obviously, safety of the ship and crew are paramount, but what occurences could be anticipated that might require the ship to remain in Acceleration Mode? Are there alternate mission configurations? Say, a backup in case higher-rez data of the taget system shows it to be uninhabitable? Do they account for interlstellar dust couds and be ready to go around them? (Note that whether they do or not, isn't the point. The point is what would they be planning for in Mission planning?)


It's not a great analogy, but when I am out sailing, and it's time to come in to the harbour, I switch to my motor and drop the sails. Despite the fact that I won't be needing the sails, it is my habit to not lash down and store the sails until I am at-dock. The reason for this is as a backup, in case my motor dies at the worst possible moment. I need to be able to raise the sails at a second's notice if I suddenly find myself drifting toward a lee shore. That's the kind of precautionary wisdom that has kept sailors alive.

This can be generalized to a principle about any shipboard activity: what if I do this now? What is the worst that can happen? What if I do it later? What is the worst that can happen? If there is no upside to stowing my sails early, but a very definite downside (no matter how unlikely), then the advantage weighs in favour of holding off.

But that works the other way for other tasks. Some tasks you want to do right away in case something unexpected happens. For example, reefing the sail (ie. shortening it) in anticipation of high winds. It is always better to reef early and decide to take it out if winds don't build (big upside, small downside), than it is to wait and have to reef in rising winds (small upside, very big downside).
 
Last edited:
  • Like
Likes ShadowKraz, Strato Incendus and gmax137
  • #67
DaveC426913 said:
The mission would be planned to turn the ship around at the optimal time, whch is not necessarily right after the onset of the coasting leg.

The question is: what factors would or could arise duing that time that should be taken into account. Obviously, safety of the ship and crew are paramount, but what occurences could be anticipated that might require the ship to remain in Acceleration Mode? Are there alternate mission configurations? Say, a backup in case higher-rez data of the taget system shows it to be uninhabitable? Do they account for interlstellar dust couds and be ready to go around them? (Note that whether they do or not, isn't the point. The point is what would they be planning for in Mission planning?)


It's not a great analogy, but when I am out sailing, and it's time to come in to the harbour,
Excellent points and I think the sailing analogy is good. I used to sail under Capt. Bligh... um, I mean, my Dad. He was ALWAYS about doing, or preparing to do, things earlier than absolutely necessary, such as reefing the sails. The boat was an old O'Day Daysailer, but it was good practice for life.
"The best laid plans of mice and men oft go awry."
 
  • #68
ShadowKraz said:
the ship gets turned after the initial acceleration ends
This would fit the goals of the youth rebel organisation in prequel 2, Turning Point, who are unhappy about having been turned into the first generation of unwilling crew members, and are trying to make the ship return to Earth.

Whether or not this goal is realistic or not is secondary (one forum user here has criticised a story with a plot like this as nonsensical in the past); Turning Point do not have to be guided by reason. In fact, their youthful passion may be the counterpoint to the ship's establishment, doing everything based on "the science".

However, even Turning Point understood that, if they wanted to have any chance at all to actually accelerate the ship back towards Earth, they'd have to turn it around before it reaches full coasting speed. After that, braking would merely cause it to get stranded in the interstellar medium.

Thus, their time of trying to make the ship brake and turn around early coincides with it traversing the actual Oort cloud. Therefore, a lot of the things we've discussed so far are not irrelevant - they might merely become crucial for the second prequel, rather than for the first main book. :)


If the ship turns around right after leaving the Sol system, the question is whether this happens as an intentional action on part of the ship's commanding officers - or if this is the consequence of Turning Point's actions: They may have succeeded in flipping the ship early (and perhaps, faster than they should have, given they were about two dozen plucky teenagers and twenty-somethings), but were stopped by security before they were able to complete their plan.

Then again, this doesn't make sense, as turning the ship around while it's accelerating will make it veer off course. This is one crucial difference to flipping the ship at the end of the coasting phase, since there is no continued acceleration as the ship is being rotated.

Thus, the more straightforward and believable explanation would be that the ship was rotated on purpose by the ones in charge, early after leaving the Oort cloud - which is simultaneously shortly after ending the acceleration phase - once they had entered the interstellar medium, where a lot less space dust could get in their way.

If they don't flip the ship right there and then, the question is indeed, as @DaveC426913 has asked:
What would be the upside of flipping it at the midpoint of the coasting phase, or even later?
Or conversely, what would be the downside of flipping it early?
 
  • #69
Strato Incendus said:
So the question is:
1) How does fire behave in zero gravity vs. in an environment of centrifugal gravity (=on the ring sections of the ship)?
2) What safety technology would the ship have against cases like this (maybe starting with whatever the ISS has for preventing fires on board)?
3) What levels of casualties would you expect, assuming a bunch of people are sent in to extinguish the fire as quickly as possible?
Looking for holly wood portrayals I came across the Apollo 1 accident in 1967.
Not something I was aware of till I saw the Apollo 1995 film.

If you want to take from real life.

The craft was on the ground doing tests and the fire started, the crew were dead before engineers could get the doors off which was 5 minutes later.

V50 mentioned the sub fire, I cannot imagine many things more horrific, trapped in an enclosed space with a fire rapidly spreading.

The “Gravity” fire was pretty cool looking, imagining this was not.
 
  • Like
Likes Strato Incendus and Astranut
  • #70
Thanks for getting us back to the main topic! ;) After all, we have been talking more about the origin of the damage to the ship, rather than about what the damage occurring inside the ship will actually look like.

To recap: The dust-cloud explanation is a good way of justifying why a dust speckle may pierce the ship at this specific point in time (rather than at any earlier point over the course of the coasting phase) — namely, because the ship enters the outskirts of the Oort cloud of Teegarden’s Star. If I set this up properly, not only should it feel less like plot convenience, but actually more like straight-up realism:
(“Yes, of course, once they enter the new star system, the density of matter per unit of space will increase, compared to the interstellar medium, because of the star’s gravity.”) Thinking about it, re-entry into a star system at full coasting speed (0.125 c) should be more dangerous, compared to accelerating out of a star system into the interstellar medium from a lower speed (assuming the low g forces that we’ve established for the acceleration, which is 0.048 m/s2).

However, ultimately, the damage done to the ship must probably occur from the dust speckle alone, rather than from the rotation process. Since my conclusion from the comments so far is that the ship would realistically be rotated at an earlier point in the story, while it is somewhere in the interstellar medium, so the risk of damage is lower. In fact, the exact point in time when to rotate the ship could be determined by noticing, “We’re in a particularly empty pocket of space right now, let’s use the opportunity to flip the ship!”

The ship’s range of vision is fairly limited, though, due to its own travel speed (0.125 c) compared to the speed of its sensors (1 c).

Hence, as far as how quickly the crew notices the higher density of the dust cloud:
  1. With the ship coasting at 0.125 c, they would cover 1 light-minute of distance within 8 minutes of ship time. The sensor signals can only work at light speed, so for any given speckle of dust in front of the ship, it would take one minute for the sensor signal to reach it, another minute for the reflected signal to get back to the ship. That would only leave the ship crew a time window of 6 minutes between first noticing the dust cloud and entering into it, right? Of course, they will expect the dust to get denser in general as they approach the target system. However, it may not be until they get the sensor data that they realise it’s denser than they anticipated.
  2. The deflector laser beams obviously can’t move faster than light either, so even if they failed completely, after having vaporised everything perfectly up to that point, the ship would have 8 minutes of reaction time left before encountering further dust speckles, correct?
  3. The higher density of the dust cloud as they enter the target star system no longer requires a failure of the deflector lasers in order for something to slip past, as @DaveC426913 pointed out. However, if the density of dust alone is what causes the problems now (rather than flipping the ship within such a dust cloud), I need an explanation why the ship doesn’t keep getting hit by more and more dust particles over the course of the story from then on.
    1. Perhaps some genius engineer makes a modification to the deflector lasers on the fly — perhaps within that critical time span of 8 minutes, before further impacts occur? Bonus points if the engineer sacrifices himself in the process. Perhaps he has to go to the back of the ship (which is now pointing forward) to manually adjust something on the deflector lasers?
    2. Spacewalks at this speed aren’t really possible, I’ve heard — however, that’s assuming a spacewalk that a character would survive. If he has to go outside to do something manually, he could die by radiation (because he’d be in front of the protective water tanks in the forward-pointing aft sphere), he could get pierced by the incoming barrage of dust speckles (even just a single one of them piercing his helmet would be enough), he could get fried by the engines as they turn on to brake (though in this scenario, there’s no reason to start the 25-year-long braking process while a crew member is still working outside), or he could simply slip and float away from the ship (which is kind of the biggest cliché, but of course an omnipresent danger in space).

For the rest of the crew, we need to get back to the question what exactly gets damaged on the inside, by the dust speckle that pierces the ship hull. I could have someone get ripped to shreds by the dust speckle passing through them — depending on whether this is the fate that befalls the engineer or not (I don’t wanna pull this twice in the same event, because “law of diminishing returns” in writing :D ). But either way, the speckle alone isn’t going to cause mass casualties, because the ship isn’t sufficiently densely populated for that.

I still like the idea of the speckle piercing some tank or pipe that contains an explosive gas. All it has to do on top of that is to also damage some wiring close to it, then you get some sparks, and boom, fire onboard galore. The obvious candidate here would be hydrogen, but pure hydrogen is of course hard to store, and not what you would want for the nuclear-fusion reactor anyway.

So I guess we’ll finally have to dig into the specifics of different types of nuclear-fusion reactors next. :smile:
But first, let’s address the remaining questions about the dust speckle listed above.
Once we know how the dust speckle got into the ship, then we can focus on the inside and imagine all the damage it can cause on its way through the ship.
 

Similar threads

Writing: Input Wanted Number of Androids on Spaceships
  • Sci-Fi Writing and World Building
Replies
21
Views
960
  • Sci-Fi Writing and World Building
Replies
17
Views
2K
  • Sci-Fi Writing and World Building
Replies
22
Views
3K
  • Sci-Fi Writing and World Building
Replies
18
Views
2K
  • Sci-Fi Writing and World Building
Replies
6
Views
1K
  • Sci-Fi Writing and World Building
4
Replies
118
Views
6K
  • Sci-Fi Writing and World Building
Replies
7
Views
1K
  • Sci-Fi Writing and World Building
Replies
15
Views
1K
  • Sci-Fi Writing and World Building
Replies
7
Views
2K
Writing: Input Wanted Captain's choices on colony ships
  • Sci-Fi Writing and World Building
Replies
4
Views
2K
Back
Top