Right. Think of it as the ship (or Mir or whatever) is
already falling when in orbit, just that the planet is "sliding out" from under it at the same rate of the fall. Hence, orbit.
Exactly. The downward pull is already as strong as it's going to get. It's how fast you're moving forward that determines whether you loop around the planet entirely or spiral in to collide with it.
On the other hand, the movie is consistent with Star Trek physics. In The Naked Time, when Reilly turned the engines off, the ship's orbit started to decay. Similarly, in Court Martial, the orbit was affected. These instances at least featured a slow decay, which in itself is realistic.
Well, actually the decay should probably have taken weeks in those cases, and it wouldn't have happened at all unless the ship had been in a low enough orbit to be impinging on the outer fringes of the atmosphere, creating drag.
In Star Trek III, it was portrayed more like the effect of an airplane running out of fuel while in flight.
Actually this is another thing fiction routinely misrepresents: airplanes that run out of fuel in flight can glide safely for hundreds of miles and dozens of minutes, if they're high enough. They don't just plummet to the ground, because they're aerodynamic. If the engines go out, sure, they start to decelerate and descend, but the glide ratio is high enough that, for a fast-moving jet at high altitude, there should be plenty of time to find a safe place to land. The laws of aerodynamics don't stop working just because the engines do. (This is why so many plane-crash scenes in movies and TV these days involve something happening that causes the pilot to push forward on the control throttle, thereby angling the plane downward faster than if it were simply gliding.)
As I am on my phone I won't respond in great detail, but in regards to Mir, that too was not a good example as that too was a controlled deorbit. It was controlled to ensure as much of the station burned up and secondly it was controlled to ensure any remaining debris wouldn't land in any populated areas.
I'm sorry, but you're getting it backward. A controlled deorbit is a
deliberate deceleration to cause the vehicle to descend toward the planet. Mir was already in a decaying orbit, but it was caused to decay
faster so that its re-entry trajectory could be controlled and it could be ditched safely. An explosion in space, something not designed to decelerate the ship, would probably not cause it to fall out of orbit
at all. And if it did, the deceleration would probably be far less, because it was entirely accidental, and thus it should take much
longer to deorbit.
Realistically, the debris of the
Enterprise should've just hung there in a diffuse cloud orbiting the planet and gradually spread out into a debris ring. That's what usually happens when satellites break up in orbit. Any decay of the debris should've occurred over weeks or months.
And yet this claims that:
Reentry into Earth's atmosphere (100 km/60 mi AMSL) of the 15-year-old space station occurred at 05:44 UTC near Nadi, Fiji. Major destruction of the station began around 05:52 UTC and most of the unburned fragments fell into the South Pacific Ocean around 06:00 UTC.
Which is 8 mins from reentry to breaking up + another 8 mins for when the debris smacked into the ocean.
Far from being over an hour.
You misread my post. It was over an hour from the
final deorbit burn -- the thrusting manuever that turned its orbital trajectory into a descent trajectory -- to the moment of impact. The final deorbit burn occurred at 05:08 UT. It took over half an hour to descend from its orbital altitude to the altitude where it began re-entering the atmosphere, which is where you're starting the clock. Final impact was at 06:04 UT. (Okay, that's slightly under an hour, but deorbit is still a very different thing from re-entry.)
The other factor is that we're not talking about the same thing happening to the Enterprise as it wasn't slowly thrusted into the atmosphere, it was blown up and propelled into the atmosphere.
Speed of orbit is irrelevant if you have enough force to change the direction of that travel.
Again, the point is that the force has to be directed in the right way. It has to be directed
backward, not down. You're talking about "propelling" a ship toward the planet, but that's gravity's job. The velocity of the ship is working against the pull of gravity, moving the ship forward fast enough that it overshoots the planet surface. As I said, pushing the ship toward the planet will just change the angle and eccentricity of its orbit, make it more cometary. The way to descend from orbit is to
slow down and let gravity take over.
Hypothetically if the Enterprise and Bird of Prey were stationary, which is also plausible, then they may have been not in orbit at the time in the first place and just outside of main gravitational pull but when the Enterprise self destruct, again, the force of the blast most likely was enough to propel it into the gravitational pull and thus, what we see in the movie.
That's not how it works. There's no "edge" to the gravitational influence of a planet -- it extends infinitely outward, decreasing by the inverse square law. If you're ten times as far away, you'll only feel 1/100 the attraction, but it will still be pulling you in, just more slowly. That's why you need to move laterally in order to stay in orbit. You can't avoid being pulled inward by gravity -- all you can do is move forward fast enough to overshoot the surface and loop back on your own path. The only way to maintain a "hover" over a given spot is by applying continuous thrust, a so-called forced orbit. In that case, if your engines gave out, then you would start to descend.
So yes, it is hypothetically possible that the ship could've been in a powered hover and the loss of power caused it to descend. But it is
also hypothetically possible that it behaved the way I'm proposing. All I'm saying is that it's a possibility. The fact that other possibilities exist does not exclude the one I'm suggesting. There's room for multiple options.