History Headscratchers / ReturnOfTheJedi

25th Jan '16 9:22:42 AM Cleric_Quarion
Is there an issue? Send a Message
* So, does it bother anyone else that the Empire's defeat hinged on the Empires inability to guard a door for a couple hours? The battle would have been more or less an Imperial Curb Stomp to the Alliance if the shield had stayed up and at one point, the rebels on the moon had all pretty much been captured by "A Legion of the Emperors Finest Troops". Somehow, however, the stormtroopers are incredibly distracted by teddy bears with stone age tech jumping out of the woods that they forget that their number one priority is to keep the shield generator from getting blown up. Instead, they run around acting like complete idiots chasing the ewoks for an hour, more then enough time for Han and Chewy to get inside the bunker and blow it up. The imperials had ONE JOB and failed miserably at it. What makes this even worse.....there's no particular reason there needed to have forests that close to the bunker, when it would have been easy enough to clear the trees around it and set up defense in depth and fortification to prevent an ewok from getting within a mile of the bunker without becoming flash fried by pre-sighted imperial laser cannons. You know, stuff that any competent military leader on earth could do facing armies with similar tech, let alone teddy bears with rocks and spears.
to:
* So, does it bother anyone else that the Empire's defeat hinged on the Empires Empire's inability to guard a door for a couple hours? The battle would have been more or less an Imperial Curb Stomp to the Alliance if the shield had stayed up and at one point, the rebels on the moon had all pretty much been captured by "A Legion of the Emperors Finest Troops". Somehow, however, the stormtroopers are incredibly distracted by teddy bears with stone age tech jumping out of the woods that they forget that their number one priority is to keep the shield generator from getting blown up. Instead, they run around acting like complete idiots chasing the ewoks for an hour, more then enough time for Han and Chewy to get inside the bunker and blow it up. The imperials Imperials had ONE JOB and failed miserably at it. What makes this even worse.....there's no particular reason there needed to have forests that close to the bunker, when it would have been easy enough to clear the trees around it and set up defense in depth and fortification to prevent an ewok from getting within a mile of the bunker without becoming flash fried by pre-sighted imperial laser cannons. You know, stuff that any competent military leader on earth could do facing armies with similar tech, let alone teddy bears with rocks and spears. **You're right, the base did have one job - being an attractive target to the Rebel Alliance so that they would be lured into a trap. If the base had been set up to be utterly impregnable, then the Rebels would've taken one look and had nothing more to do with the place. Also, you have a much better chance of preventing your base from being destroyed if you actively repel attackers while leaving their captured comrades still in custody of your allies.
25th Jan '16 8:12:10 AM Cleric_Quarion
Is there an issue? Send a Message
18th Jan '16 8:09:49 AM MrDeath
Is there an issue? Send a Message
* The Alliance's plan for the attack on the second Death Star was that the "cruisers [would] create a perimeter, while the fighters fly into the superstructure and attempt to knock out the main reactor." Why would the cruisers create a perimeter? Were they worried that the Death Star would escape? Remember, they thought that the Imperial fleet was scattered throughout the galaxy looking for them, so they were not expecting to need to fight the Imperial fleet. So apparently the plan was to have all these Rebel capital ships just floating there while the fighters flew into the superstructure and did all the work. What for? As far as I can tell, the Rebel capital ships were only present at the battle to be targets for the Death Star.
to:
* The Alliance's plan for the attack on the second Death Star was that the "cruisers [would] create a perimeter, while the fighters fly into the superstructure and attempt to knock out the main reactor." Why would the cruisers create a perimeter? Were they worried that the Death Star would escape? Remember, they thought that the Imperial fleet was scattered throughout the galaxy looking for them, so they were not expecting to need to fight the Imperial fleet. So apparently the plan was to have all these Rebel capital ships just floating there while the fighters flew into the superstructure and did all the work. What for? As far as I can tell, the Rebel capital ships were only present at the battle to be targets for the Death Star.Star. ** There's no way for them to stop the Death Star from sending out a distress signal once it's under attack. Therefore, even if they're scattered all over the galaxy, the odd Star Destroyer can still pop in and try to assist. The Rebel fleet is there to hold those ships off if they show up.
17th Jan '16 8:48:17 AM Oddstar6
Is there an issue? Send a Message
Added DiffLines:
**** Boy, I bet Han [[spoiler:wishes he had listened to his wife on that one]]..
17th Jan '16 7:48:34 AM Oddstar6
Is there an issue? Send a Message
* The TIE Interceptor that gets eaten by the explosion of the Death Star II during the ''Millennium Falcon''[='s=] escape is apparently faster than the ''Falcon'' (as per the EU) but can't outmaneuver it so it has to follow it out. [[WhyDontYaJustShootHim It didn't occur to the pilot to just take out the]] ''Falcon'' and clear its own escape? It's not like they were friends. This seems more like FridgeLogic but just to be safe I'll call it a Headscratcher.
to:
\n** What Luke is saying, in effect, is that, if what Vader has said is true, then his father is dead, but only if. If Vader can change, then Anakin still lives. To put it another way, Luke, Vader, and Palpatine are fighting a psychological war, and everything that each one says and does from the moment that Luke confronts his father in the Imperial base on Endor has to be seen as a maneuver in that war. * The TIE Interceptor that gets eaten by the explosion of the Death Star II during the ''Millennium Falcon''[='s=] escape is apparently faster than the ''Falcon'' (as per the EU) but can't outmaneuver it so it has to follow it out. [[WhyDontYaJustShootHim It didn't occur to the pilot to just take out the]] ''Falcon'' and clear its own escape? It's not like they were friends. This seems more like FridgeLogic but just to be safe I'll call it a Headscratcher.Headscratcher. ** I am sure the TIE pilot wanted very badly to do just that and probably tried, but the Falcon has deflector shields that the Interceptor's guns could not have penetrated in time. * The Alliance's plan for the attack on the second Death Star was that the "cruisers [would] create a perimeter, while the fighters fly into the superstructure and attempt to knock out the main reactor." Why would the cruisers create a perimeter? Were they worried that the Death Star would escape? Remember, they thought that the Imperial fleet was scattered throughout the galaxy looking for them, so they were not expecting to need to fight the Imperial fleet. So apparently the plan was to have all these Rebel capital ships just floating there while the fighters flew into the superstructure and did all the work. What for? As far as I can tell, the Rebel capital ships were only present at the battle to be targets for the Death Star.
17th Jan '16 7:16:08 AM Oddstar6
Is there an issue? Send a Message
to:
** You also have to remember that Leia has been tortured multiple times, first when she was tortured repeatedly while a prisoner on the first Death Star, and then again while a prisoner in Cloud City--the film shows us Han's torture, but Leia was also brought back to the cell shortly after Han was, and says to him "why are they doing this to ''us''?" (emphasis added)--and seems not to be particularly traumatized by that either. Also, shortly after the destruction of Alderaan, and the murder of her whole homeworld, she was comforting Luke about the death of a man he had known well for a matter of days, maybe. You just have to accept that she is a very tough, very resilient person who can keep going after events that would leave most people psychologically crippled.
2nd Jan '16 11:34:59 AM trumpetmarietta
Is there an issue? Send a Message
** Why would he care, even if he did? Boba wouldn't have made any connection between Lando and the Rebels, as he left long before that connection was made (publicly). Sure, he might have recognized him as one of the guys shooting at Slave 1 as it left Bespin (can't recall if Lando was even in that scene, and if he wasn't, that makes the point), and been a little miffed, but that was business. Fett is a businessman, first and foremost. But again, why would he care? Jabba has already paid him (not even Jabba would withhold payment from that one...), so it is no longer his problem. He could potentially double-dip Jabba, as once Han has escaped, a capable (and now proven) bounty hunter will have to be hired to track him down again...
to:
** Why would he care, even if he did? Boba wouldn't have made any connection between Lando and the Rebels, as he left long before that connection was made (publicly). Sure, he might have recognized him as one of the guys shooting at Slave 1 ''Slave I'' as it left Bespin (can't recall if Lando was even in that scene, and if he wasn't, that makes the point), and been a little miffed, but that was business. Fett is a businessman, first and foremost. But again, why would he care? Jabba has already paid him (not even Jabba would withhold payment from that one...), so it is no longer his problem. He could potentially double-dip Jabba, as once Han has escaped, a capable (and now proven) bounty hunter will have to be hired to track him down again...
2nd Jan '16 11:32:20 AM trumpetmarietta
Is there an issue? Send a Message
to:
** Based on ''[[Film/TheForceAwakens Episode VII]]'', yes, he does.
2nd Jan '16 10:54:31 AM trumpetmarietta
Is there an issue? Send a Message
corrected misspelling of "Tyderium"
*** Actually, it is the apparent ''absence'' of ships in the area that should have raised suspicions! Think about it: the Death Star is gigantic megastructure. Yet, there is no indication that the Empire is strip-mining Endor for the raw materials to build it. So where are the materials coming from? A steady stream of freighters should have been coming and going from the system in order to support the project and deliver materials. Yet, when Tyderium arrives it is the ''only'' ship in line awaiting clearance through the deflector shield. That would imply that local space had been cleared of all traffic ''deliberately''! The Emperor could not "oversee the final stages of the construction" if construction ground to a halt because supply ships were no longer being allowed into the system!
to:
*** Actually, it is the apparent ''absence'' of ships in the area that should have raised suspicions! Think about it: the Death Star is gigantic megastructure. Yet, there is no indication that the Empire is strip-mining Endor for the raw materials to build it. So where are the materials coming from? A steady stream of freighters should have been coming and going from the system in order to support the project and deliver materials. Yet, when Tyderium ''Tyderium'' arrives it is the ''only'' ship in line awaiting clearance through the deflector shield. That would imply that local space had been cleared of all traffic ''deliberately''! The Emperor could not "oversee the final stages of the construction" if construction ground to a halt because supply ships were no longer being allowed into the system!
2nd Jan '16 10:51:44 AM trumpetmarietta
Is there an issue? Send a Message
* Shouldn't the presence of the Executor have tipped the Tydirium crew off that the Empire was waiting for them? It was only the biggest, most powerful thing in the Imperial fleet that could still get away with being called a ship, and it's being there doesn't put any crimp in their plans? ** Pay attention to the briefing. One of the reasons they give for why this is the perfect time to strike is because they ''know'' the Emperor himself is going to be there. And the Executor is the Emperor's flagship. Of ''course'' it's going to be there. *** Eh, the Executor's nothing special. (And it's ''Vader's'' flagship, not the Emperor's.) "There're a lot of command ships." Yes, General Solo, there are.
to:
* Shouldn't the presence of the Executor ''Executor'' have tipped the Tydirium ''Tydirium'' crew off that the Empire was waiting for them? It was only the biggest, most powerful thing in the Imperial fleet that could still get away with being called a ship, and it's being there doesn't put any crimp in their plans? ** Pay attention to the briefing. One of the reasons they give for why this is the perfect time to strike is because they ''know'' the Emperor himself is going to be there. And the Executor ''Executor'' is the Emperor's flagship. Of ''course'' it's going to be there. *** Eh, the Executor's ''Executor''[='=]s nothing special. (And it's ''Vader's'' ''Vader''[='=]s flagship, not the Emperor's.) "There're a lot of command ships." Yes, General Solo, there are.

****** Not at all; I'm just saying it's weird that the Rebels didn't even consider that it might be a trap, given the Empire's track record of deception, and that they considered the Executor and it's accompanying squadron, plus a nigh-impenetrable energy shield, "relatively unguarded." ****** Perhaps the Rebels believed that, for even a secret project, the Executor and its escorts would be considered sufficient protection by Imperial Command. After all, Imperial doctrine says that even a single Star Destroyer is enough to subject an entire star system. Also, at this time, there were four other Super Star Destroyers in active service. ****** It's not like the Rebels only sent a couple of squadrons on this one like they did at Yavin. They mustered together what was, until the Emperor sprung his trap, the largest fleet of ships we had seen in the entire series. The plan was to jump in, send in Lando's team to dive into the Death Star's core before the Imperials could react to the shield being down, and then wail on the Executor and her escorts. The plan was for the whole op to be done and them on the way out before reinforcements could arrive, assuming that the Imperials based their strategy around the assumption that any attacking force would be delayed by the shield.
to:
****** Not at all; I'm just saying it's weird that the Rebels didn't even consider that it might be a trap, given the Empire's track record of deception, and that they considered the Executor ''Executor'' and it's accompanying squadron, plus a nigh-impenetrable energy shield, "relatively unguarded." ****** Perhaps the Rebels believed that, for even a secret project, the Executor ''Executor'' and its escorts would be considered sufficient protection by Imperial Command. After all, Imperial doctrine says that even a single Star Destroyer is enough to subject an entire star system. Also, at this time, there were four other Super Star Destroyers in active service. ****** It's not like the Rebels only sent a couple of squadrons on this one like they did at Yavin. They mustered together what was, until the Emperor sprung his trap, the largest fleet of ships we had seen in the entire series. The plan was to jump in, send in Lando's team to dive into the Death Star's core before the Imperials could react to the shield being down, and then wail on the Executor ''Executor'' and her escorts. The plan was for the whole op to be done and them on the way out before reinforcements could arrive, assuming that the Imperials based their strategy around the assumption that any attacking force would be delayed by the shield.

** Oh, right. Vader ''did'' figure out Luke was onboard that shuttle, even without using this tactic. And yet the shuttle was ''still allowed to land'', instead of just being tractored into the ''Executor's'' hangar bay. Look, if you want the Death Star blown up ''that'' bad, Anakin, just get in your TIE fighter and go do it yourself.
to:
** Oh, right. Vader ''did'' figure out Luke was onboard that shuttle, even without using this tactic. And yet the shuttle was ''still allowed to land'', instead of just being tractored into the ''Executor's'' ''Executor''[='=]s hangar bay. Look, if you want the Death Star blown up ''that'' bad, Anakin, just get in your TIE fighter and go do it yourself.

*** It IS possible the the commando team was able to send transmissions from the shuttle, but not from anywhere near the shield generator itself for fear of interception. In fact, consider that in order for Han's scheme to work at all someone must have had to take the shuttle Tydirium and actually deliver some supplies to the base on the moon after dropping the commandos some distance away - otherwise it would be obvious after just a few hours that the Executor had cleared a shuttle that had never arrived, and the alarm would be raised. This skeleton shuttle crew would then have been able to return and deliver the message that the plan had worked so far, but perhaps the commandos themselves didn't have the equipment to send a signal after insertion (I can't recall - is Tydirium ever shown on Endor after the insertion?). Knowing this, Palpatine would have needed to allow them to insert safely, with the plan to curb stomp them when they got to the actual generator. What doesn't make much sense is keeping that part of the plan secret from Piett, since he could have accidentally scrubbed the plan by being more suspicious about the old code.
to:
*** It IS possible the the commando team was able to send transmissions from the shuttle, but not from anywhere near the shield generator itself for fear of interception. In fact, consider that in order for Han's scheme to work at all someone must have had to take the shuttle Tydirium ''Tydirium'' and actually deliver some supplies to the base on the moon after dropping the commandos some distance away - otherwise it would be obvious after just a few hours that the Executor ''Executor'' had cleared a shuttle that had never arrived, and the alarm would be raised. This skeleton shuttle crew would then have been able to return and deliver the message that the plan had worked so far, but perhaps the commandos themselves didn't have the equipment to send a signal after insertion (I can't recall - is Tydirium recall—is ''Tydirium'' ever shown on Endor after the insertion?). Knowing this, Palpatine would have needed to allow them to insert safely, with the plan to curb stomp them when they got to the actual generator. What doesn't make much sense is keeping that part of the plan secret from Piett, since he could have accidentally scrubbed the plan by being more suspicious about the old code.

*** Whether or not the shuttle actually has an interstellar transmitter (the EU makes it plain that interstellar transmitters are large enough that only capital ships have them, but ok, fine, that's the EU), its not really relevant. Between the Executor itself and the Death Star, the Imperials can easily jam any transmission that one shuttle could make, a billion times over. So, wait until you know what shuttle it is, then suddenly light off all your active jammers before the Rebels can even know anything is wrong, tractor the shuttle, and board it. Don't turn the jammers off until after the shuttle has been taken apart and everybody on it was stunned. Easy peesy. The Rebel fleet is hardly going to detect that somebody used a broad-spectrum jammer in the Endor system from outside the Endor system -- indeed, the Imperials were using some type of jamming field ''in canon'', and Lando doesn't notice it until after the Rebel fleet's all in the Endor system and he's wondering why the Falcon's sensors aren't working.
to:
*** Whether or not the shuttle actually has an interstellar transmitter (the EU makes it plain that interstellar transmitters are large enough that only capital ships have them, but ok, fine, that's the EU), its not really relevant. Between the Executor ''Executor'' itself and the Death Star, the Imperials can easily jam any transmission that one shuttle could make, a billion times over. So, wait until you know what shuttle it is, then suddenly light off all your active jammers before the Rebels can even know anything is wrong, tractor the shuttle, and board it. Don't turn the jammers off until after the shuttle has been taken apart and everybody on it was stunned. Easy peesy. The Rebel fleet is hardly going to detect that somebody used a broad-spectrum jammer in the Endor system from outside the Endor system -- indeed, the Imperials were using some type of jamming field ''in canon'', and Lando doesn't notice it until after the Rebel fleet's all in the Endor system and he's wondering why the Falcon's sensors aren't working.

*** The 'simple explanation' does cover why no special code for the Rebels, but it still doesn't address the idiocy of allowing them to land on Endor at all. Vader knew the shuttle was full of Rebels before it even finished the password sequence; he has no reason except a firm clutching of the IdiotBall to ''not'' order that it be tractored into the Executor's hangar bay immediately. The Rebel sabotage team had no "we must make this check-in or else the fleet doesn't come" in canon, nor could it be credibly expected to have. (see points above re: fear of interception and possibility of jamming). Additionally, the Emperor's ''entire plan'' relied on the assumption that the Rebels would have only the information about Endor that the Emperor chose to deliberately leak to them and that the Rebel fleet would jump in blind; if Palpatine wasn't confident he had that information monopoly, he wouldn't have tried his trap in the first place. Further evidence lies in the behavior of the Rebel fleet once it ''does'' arrive at Endor -- at no point does either Lando or Admiral Ackbar actually make any attempt to call the ground team on the radio, not even to ask them 'Do you still have any chance to lower the shield any time soon, or should we all be running away now?'. Lando's only method of knowing whether or not Han and his team are still in action is using the ''Falcon's'' sensors to check if the shield is still up or not. It is shown that the Rebel ground team had no way of contacting the Rebel fleet even at as short a range as 'within the Endor system', which casts huge huge doubt on the notion they had a way of contacting the Rebel fleet over the interstellar distance between Endor and the Fleet's original muster point.
to:
*** The 'simple explanation' does cover why no special code for the Rebels, but it still doesn't address the idiocy of allowing them to land on Endor at all. Vader knew the shuttle was full of Rebels before it even finished the password sequence; he has no reason except a firm clutching of the IdiotBall to ''not'' order that it be tractored into the Executor's ''Executor'''s hangar bay immediately. The Rebel sabotage team had no "we must make this check-in or else the fleet doesn't come" in canon, nor could it be credibly expected to have. (see points above re: fear of interception and possibility of jamming). Additionally, the Emperor's ''entire plan'' relied on the assumption that the Rebels would have only the information about Endor that the Emperor chose to deliberately leak to them and that the Rebel fleet would jump in blind; if Palpatine wasn't confident he had that information monopoly, he wouldn't have tried his trap in the first place. Further evidence lies in the behavior of the Rebel fleet once it ''does'' arrive at Endor -- at no point does either Lando or Admiral Ackbar actually make any attempt to call the ground team on the radio, not even to ask them 'Do you still have any chance to lower the shield any time soon, or should we all be running away now?'. Lando's only method of knowing whether or not Han and his team are still in action is using the ''Falcon's'' sensors to check if the shield is still up or not. It is shown that the Rebel ground team had no way of contacting the Rebel fleet even at as short a range as 'within the Endor system', which casts huge huge doubt on the notion they had a way of contacting the Rebel fleet over the interstellar distance between Endor and the Fleet's original muster point.

* So the reason that the rebel fleet's desperate frontal assault on the Executor worked because [[AchievementsInIgnorance no one had ever thought to actually fight a Star Destroyer head-on]]? I mean, sure, the rebels don't exactly have the resources to toss around to go on balls-to-the-wall assaults, but what, did everyone else just give up when they saw a Star Destroyer? "Welp, Star Destroyer's here. Everyone pack up, we're surrendering."
to:
* So the reason that the rebel fleet's desperate frontal assault on the Executor ''Executor'' worked because [[AchievementsInIgnorance no one had ever thought to actually fight a Star Destroyer head-on]]? I mean, sure, the rebels don't exactly have the resources to toss around to go on balls-to-the-wall assaults, but what, did everyone else just give up when they saw a Star Destroyer? "Welp, Star Destroyer's here. Everyone pack up, we're surrendering."

** It's not that they hadn't tried before; go look at the scene in question. Once they discover the Death Star is operational Lando proposes Akbar to go engage the Executor at point blank range. Akbar retorts that "they won't last long against a Super Star Destroyer at that range" not that they CANT win the engagement. Akbar also doesn't state that their ships are weak, as the spectator can infer from the visuals that they CAN take on normal Star Destroyers at point blank.
to:
** It's not that they hadn't tried before; go look at the scene in question. Once they discover the Death Star is operational Lando proposes Akbar to go engage the Executor ''Executor'' at point blank range. Akbar retorts that "they won't last long against a Super Star Destroyer at that range" not that they CANT win the engagement. Akbar also doesn't state that their ships are weak, as the spectator can infer from the visuals that they CAN take on normal Star Destroyers at point blank.

*** And they DID last longer with this strategy and were even able to disable the Executor's shield generator; they downed it on a lucky shot since they had a ship accidentally crash INSIDE the command deck. ** The Executor isn't a Star Destroyer. It's a ''Super'' Star Destroyer; it's more than 10 times the size of the regular Star Destroyers, ''and'' it's the Emperor's flagship. So, yes, when they saw it on the battlefield, it was shorthand for "you are so fucked right now."
to:
*** And they DID last longer with this strategy and were even able to disable the Executor's ''Executor'''s shield generator; they downed it on a lucky shot since they had a ship accidentally crash INSIDE the command deck. ** The Executor ''Executor'' isn't a Star Destroyer. It's a ''Super'' Star Destroyer; it's more than 10 times the size of the regular Star Destroyers, ''and'' it's the Emperor's flagship. So, yes, when they saw it on the battlefield, it was shorthand for "you are so fucked right now."

** It may have worked because it was a completely suicidal attack - the Rebels probably incurred more losses in the process of taking out the Executor than any admiral would consider an acceptable trade in a normal battle. The Battle of Endor was simply too desperate for retreat or surrender, and it probably also involved a larger enemy force than any Super Star Destroyer had ever faced. *** Although I'd say taking out the Executor meant that the battle was an acceptable trade. That thing is worth a half-dozen of any other ship type out there fighting.
to:
** It may have worked because it was a completely suicidal attack - the Rebels probably incurred more losses in the process of taking out the Executor ''Executor'' than any admiral would consider an acceptable trade in a normal battle. The Battle of Endor was simply too desperate for retreat or surrender, and it probably also involved a larger enemy force than any Super Star Destroyer had ever faced. *** Although I'd say taking out the Executor ''Executor'' meant that the battle was an acceptable trade. That thing is worth a half-dozen of any other ship type out there fighting.

* So, shuttle Tydirium is "bringing parts and equipment" to the Endor moon. The Emperor and Vader know what's up, and let it pass. Piett suspects there's something off, but heeds Vader's command. But the rest of the Imperial crew has no idea why that shuttle, instead of landing in the nice, elevated, designated landing platform, suddenly veered off course and landed in the middle of a forest, and was never heard from again. Sure, anyone who brought this up would be told not to worry about it, but wouldn't the Rebels themselves realize the myriad issues with this plan?
to:
* So, shuttle Tydirium ''Tydirium'' is "bringing parts and equipment" technical crew" to the Endor moon.forest moon of Endor. The Emperor and Vader know what's up, and let it pass. Piett suspects there's something off, but heeds Vader's command. But the rest of the Imperial crew has no idea why that shuttle, instead of landing in the nice, elevated, designated landing platform, suddenly veered off course and landed in the middle of a forest, and was never heard from again. Sure, anyone who brought this up would be told not to worry about it, but wouldn't the Rebels themselves realize the myriad issues with this plan?

** Callous and wasteful of human life.. sure. Callous and wasteful of an expensive spaceship, probably not. Besides it's a top secret project, any random crash is going to be investigated in case it wasn't an accident. Also as mentioned in the Star Wars headscratcher archives, the military does not watch everything that closely. The Executor let them pass, and would expect to get a call from the base if the shuttle never arrived but since the shuttle isn't expected by the shield generator in the first place, there would be no reason to call it in.
to:
** Callous and wasteful of human life.. sure. Callous and wasteful of an expensive spaceship, probably not. Besides it's a top secret project, any random crash is going to be investigated in case it wasn't an accident. Also as mentioned in the Star Wars headscratcher archives, the military does not watch everything that closely. The Executor ''Executor'' let them pass, and would expect to get a call from the base if the shuttle never arrived but since the shuttle isn't expected by the shield generator in the first place, there would be no reason to call it in.

** The most common theory (and a common explanation in the EU) is that the Death Star was putting out a strong artificial gravitational field in order to keep the Rebel Fleet from escaping into hyperspace. When the Executor's bridge was taken out, the ship (which was fairly close to the Death Star) got caught in its massive gravity well and pulled in before any backup controls could take hold.
to:
** The most common theory (and a common explanation in the EU) is that the Death Star was putting out a strong artificial gravitational field in order to keep the Rebel Fleet from escaping into hyperspace. When the Executor's ''Executor'''s bridge was taken out, the ship (which was fairly close to the Death Star) got caught in its massive gravity well and pulled in before any backup controls could take hold.

** Another possibility is that the Executor was in the middle of a maneuver that involved turning in that direction, and the pilot was killed before he could complete the maneuver and turn back away from the Death Star. A third possibility is that the pilot yanked on the controls in any old direction in order to try to shift the ship so that Arvel Crynyd's A-wing wouldn't crash into the bridge and kill them all.
to:
** Another possibility is that the Executor ''Executor'' was in the middle of a maneuver that involved turning in that direction, and the pilot was killed before he could complete the maneuver and turn back away from the Death Star. A third possibility is that the pilot yanked on the controls in any old direction in order to try to shift the ship so that Arvel Crynyd's A-wing wouldn't crash into the bridge and kill them all.

** Fact is the rebels did not know a huge fleet was behind the corner waiting for them. Every 'fact' the Bothan net provided was leaked on purpose by the Emperor. Rebels thought the Death Star was -relatively- poorly defended (the Executor being there was no mystery though) because the shield generator made a fleet unnecessary. If they really came in and attempted to destroy the generator through brute force, the Empire would have had enough time to respond to the attack with other ships in the area. Instead they tried to blow up the generator, drop in, blow the thing and get out before a serious response showed up, which is the usual Rebel hit-and-run MO. Also they had to move quickly because the intel they received indicated that DS weaponry was not yet functional. Must give credit to the Emperor for a really well set-up trap, too bad he screwed it all up by giving fancy orders to his fleet (troops losing to a bunch of Ewoks wasn't exactly his fault though).
to:
** Fact is the rebels did not know a huge fleet was behind the corner waiting for them. Every 'fact' the Bothan net provided was leaked on purpose by the Emperor. Rebels thought the Death Star was -relatively- poorly defended (the Executor ''Executor'' being there was no mystery though) because the shield generator made a fleet unnecessary. If they really came in and attempted to destroy the generator through brute force, the Empire would have had enough time to respond to the attack with other ships in the area. Instead they tried to blow up the generator, drop in, blow the thing and get out before a serious response showed up, which is the usual Rebel hit-and-run MO. Also they had to move quickly because the intel they received indicated that DS weaponry was not yet functional. Must give credit to the Emperor for a really well set-up trap, too bad he screwed it all up by giving fancy orders to his fleet (troops losing to a bunch of Ewoks wasn't exactly his fault though).

* The Super Star Destroyer Executor loses its shields, and moments later an A-Wing crashes into the bridge. After this, the huge, gigantic, MASSIVE ship crashes directly into the Death Star, killing all on board. You're telling me that on a ship that size, there are NO redundant control systems? No damage control teams? No engineering section to say "Holy crap, we just lost the main bridge," and take control of the ship? That's just poor design.
to:
* The Super Star Destroyer Executor ''Executor'' loses its shields, and moments later an A-Wing crashes into the bridge. After this, the huge, gigantic, MASSIVE ship crashes directly into the Death Star, killing all on board. You're telling me that on a ship that size, there are NO redundant control systems? No damage control teams? No engineering section to say "Holy crap, we just lost the main bridge," and take control of the ship? That's just poor design.

**** "Concentrate all fire on that Super Star Destroyer!" Yeah, I'm fairly certain that was a contributing factor to Executor's destruction. *** All the pointless little changes Lucas made to the Special Editions, and he never bothered to improve the destruction of the Executor, which is one of the most underwhelming explosions of a 19 km long starship crashing into an artificial dwarf planet I've ever seen. Then again, both Death Star explosions and the Alderaan explosion are equally lacking. They are too "sparkly"; just adding a Praxis ring isn't a substitute for throwing solid-looking debris in all directions.
to:
**** "Concentrate all fire on that Super Star Destroyer!" Yeah, I'm fairly certain that was a contributing factor to Executor's ''Executor'''s destruction. *** All the pointless little changes Lucas made to the Special Editions, and he never bothered to improve the destruction of the Executor, ''Executor'', which is one of the most underwhelming explosions of a 19 km long starship crashing into an artificial dwarf planet I've ever seen. Then again, both Death Star explosions and the Alderaan explosion are equally lacking. They are too "sparkly"; just adding a Praxis ring isn't a substitute for throwing solid-looking debris in all directions.

***** Except that if you converted something as massive as ''Executor'' directly into energy the out put would briefly exceed that of an average star. The rebels wouldn't have needed to hit the reactor, ''Executor's'' destruction should have destroyed the Death Star. But then, technically the Death Star's destruction should have destroyed Endor.
to:
***** Except that if you converted something as massive as ''Executor'' directly into energy the out put would briefly exceed that of an average star. The rebels wouldn't have needed to hit the reactor, ''Executor's'' ''Executor''[='=]s destruction should have destroyed the Death Star. But then, technically the Death Star's destruction should have destroyed Endor.
This list shows the last 10 events of 246. Show all.