Commonly used in the droid manufacturing industry, the T-44 power-shunt was a bomb produced by Baktoid Armor Workshop during the waning days of the Republic. In 22 BBY, a set of T-44 power-shunts were planted in the airspeeder of Gran Senator Aks Moe during a state visit to the planet Aargau. The bomb detonated while the airspeeder was traveling along an expressway on Aargau, killing the Moe and three of his companions. It remained unknown following Moe's assassination who exactly had placed the power-shunts inside the airspeeder, but many believed that the attack was linked to the Confederacy of Independent Systems.


The T-44 power-shunt was a bomb produced by Baktoid Armor Workshop, a subsidiary of Baktoid Industries, during the last years of the Galactic Republic. T-44 power-shunts were commonly utilized in the droid manufacturing industry, but were also used as weapons against other beings. A set of T-44 power-shunts were sufficiently powerful enough to obliterate an entire airspeeder and a large portion of the area around it. The bomb could also be equipped with a rare protein based triggering mechanism that could target a specific individual's DNA and detonate when said individual was in close proximity to the power-shunt.


In 22 BBY, during the Separatist Crisis, a set of T-44 power-shunts were placed in the airspeeder of Aks Moe—a Gran Senator and member of the Senate Loyalist Committee—during a state visit to the banking world Aargau. Moe, a pair of Dug servants, and a traveling companion of Moe's boarded the airspeeder during the visit to journey to the Commodities Exchange Cathedral in the city of New Escrow. However, as the airspeeder merged onto an expressway, the power-shunts triggered, overloading the speeder's power plant, and causing the speeder to explode and kill everyone inside.


Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.