Star Wars Roleplay: Chaos
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
LE-X1
Lexon
If anyone wants to check my math (please do, if you can; I often find I make mistakes on this sort of thing), I was using the following data points:
Drongar (based on data here)
Radius: 6 259 000 m
Surface Gravity: 11.76798 m/s^2 (1.2g)
Mass: 6.90774081 x 10^24 kg
Vessel (based on data here)
Total surface area: 2 249.48 m^2
Drag coefficient: 0.8 *
Cross-sectional area: 225 m^2 *
Mass: 137 673 112.5252 kg **
* Drag coefficient and cross-sectional area are based on the assumption that the ship is falling nearly nose-first toward the ground. Any potential lift thrust based on the aerodynamic design of the ship has been ruled negligible.
** Mass is calculated based on a durasteel density estimation of high-end stainless steel (~8030 kg/m^3) with neutronium deposits (about 1 part per trillion, adding a density of 400,000 kg/m^3). This accounts for the outer hull only (interior bulkheads are treated, for better or worse, as negligible), which is presumed to be approximately 15 cm thick. The remaining volume of the ship (roughly calculated using the exterior dimensions--hence why treating interior bulkheads as negligible seems okay) is attributed to breathable air, here given a density of 1.225 kg/m^3.
Consider that, at the initial altitude (604 158 m), gravity was approximately 83% of its surface value, and that acceleration increased over time (at a rate of about 0.000014 m/s^3 and 0.000014 m/s^4, by my calculations). Simple plug-and-play of the values means that a vessel of that cross-sectional area and mass with that drag coefficient has a terminal velocity of 3 354.24 m/s, which it will reach after 326.1018 seconds, accounting for polynomial acceleration over time. At that point, the vessel will be at an altitude of 70 480.0755 m, which will take it (at terminal velocity) only 21.0122 seconds to traverse.
All that said, it's quite rough, but given the source material, it seemed close enough. Plus, it makes the story sound better. Of course a droid in his position would know all of that! And it would take him a few seconds to calculate, instead of a few hours. (Of course, I had to refresh my calculus as part of the deal, too. It's been a while.)
Drongar (based on data here)
Radius: 6 259 000 m
Surface Gravity: 11.76798 m/s^2 (1.2g)
Mass: 6.90774081 x 10^24 kg
Vessel (based on data here)
Total surface area: 2 249.48 m^2
Drag coefficient: 0.8 *
Cross-sectional area: 225 m^2 *
Mass: 137 673 112.5252 kg **
* Drag coefficient and cross-sectional area are based on the assumption that the ship is falling nearly nose-first toward the ground. Any potential lift thrust based on the aerodynamic design of the ship has been ruled negligible.
** Mass is calculated based on a durasteel density estimation of high-end stainless steel (~8030 kg/m^3) with neutronium deposits (about 1 part per trillion, adding a density of 400,000 kg/m^3). This accounts for the outer hull only (interior bulkheads are treated, for better or worse, as negligible), which is presumed to be approximately 15 cm thick. The remaining volume of the ship (roughly calculated using the exterior dimensions--hence why treating interior bulkheads as negligible seems okay) is attributed to breathable air, here given a density of 1.225 kg/m^3.
Consider that, at the initial altitude (604 158 m), gravity was approximately 83% of its surface value, and that acceleration increased over time (at a rate of about 0.000014 m/s^3 and 0.000014 m/s^4, by my calculations). Simple plug-and-play of the values means that a vessel of that cross-sectional area and mass with that drag coefficient has a terminal velocity of 3 354.24 m/s, which it will reach after 326.1018 seconds, accounting for polynomial acceleration over time. At that point, the vessel will be at an altitude of 70 480.0755 m, which will take it (at terminal velocity) only 21.0122 seconds to traverse.
All that said, it's quite rough, but given the source material, it seemed close enough. Plus, it makes the story sound better. Of course a droid in his position would know all of that! And it would take him a few seconds to calculate, instead of a few hours. (Of course, I had to refresh my calculus as part of the deal, too. It's been a while.)