That automation system was also probably improvised in the field by Scotty, who would have designed the system without expectation of it having to cope with anything more challenging than getting from point to point, and which was attempting to run a ship that was never properly repaired after being mangled in combat. It's entirely possible that the automation system was itself relying on backup systems to function, with no redundancies left to switch to after taking damage.Ahriman238 wrote:Didn't the automation freeze the first time they tried to do something more complicated then fly to point B, then completly overload the first time they took damage?Romulan Republic wrote:As an example of this, consider the original Enterprise in The Search for Spock. The standard crew was something like 400, right? But Kirk and company were able to fly it, even badly damaged, with only a crew of five.
The Enterprise-D, by contrast, is clearly designed to be highly automatic. We've seen Picard and Data fly the ship solo before, with Data even flying it solo while locking out the ship's systems from the rest of the crew. My guess is that you could probably program the Enterprise computer to operate sans crew in friendly space for awhile; fly here, pick up cargo, fly there, do a sensor scan, etc. Of course, you'd eventually need to have someone perform maintenance on the ship, and it wouldn't really be the best use of the then-most advanced starship in Starfleet, but it could be done.