info Overview
Name - What is the name of Pulse Detonation Engine Mishap?

Pulse Detonation Engine Mishap

 
Summary - In short, what happens in Pulse Detonation Engine Mishap?
gesture Action
What caused this? - What previous events led to Pulse Detonation Engine Mishap?

Following an argument over the cutting of funding to Devellion Dayt FTL engine program following revelations he is using the Turner 12c research facility, Dev uses ANBIS to remotely prepare the Pulse Detonation Engine Test Vehicle before the GRU seizes the facility.

ANBIS delays the GRU long enough for he and Dev to get to the facility and prepare to lauch. They plan on taking the vehicle to Turner 12, where the hostile environment will impair the GRU.

Task Landager detects the lauch activity and manages to intercept the PDETV in high orbit. Task's forces are able to cut off Dev's escape, while unable to damage the larger vessel, they are able to prevent SFTL burn until reinforcements arrive.

With ANBIS controlling the PDETV's weapons and systems, he keeps Task's force at distance. ANBIS detects incoming GRU forces, and Dev realises they cannot outrun their pursuers. Dev tells ANBIS to plot a course using the PDE to the furthest system where they can get back using SFTL.

ANBIS begins activating the PDE, which distrupts Tasks navigation instruments. They figure out the PDE is activating, and Task calls off the attack hastily to prevent his forces from being caught in the wake. He keeps his forces within sensor range of the PDETV to make sure Dev does not escape using SFTL.

The PDE activates, and from Tasks perspective, fails catastrophicly. The sector where the PDETV was was not in visual range. When the engine activated, it created a massive bright light and sent hyperfast particles out like shrapnel, which damaged Tasks forces. The area remains luminous for several seconds as the matter dissipates. Afterwhich, nothing remains of the PDETV, and Dev is assumed dead. The PDE project is shelved until an answer for the mishap can be found.

The PDE activates, and from Dev's perspective, nothing happens. ANBIS had controlled the PSETV expertly, but the PDE worked too well. It had lauched them with a velocity great enough to exit the galaxity as their vector was towards radial out. ANBIS used the PDE to alter their course before shutting it down to use gravity assists to slow their velocity

 
Description - What happens in Pulse Detonation Engine Mishap?
Results - At the end of Pulse Detonation Engine Mishap, what has changed?

Devellion Dayt and ANBIS are believed dead, and the GRU shutters PDE research as being unviable.

 
edit Notes
Notes

In 6 API, Dayt discovers that his subordinates were suddenly all furloughed and that his project had been put on an indefinate hold. Anbis guesses that either the GRU thinks they are bluffing about the blackmail, or know that the release of the data would not be as deveastating as it once was.

GRU security lock down the ship and force Dayt and Anbis to return home, despite Anbis' suggestion that take direct action.

Anbis covertly asks Dayt if he is planning on offering Task an exit again. Dayt signals that he is. Anbis states that Task already made his choice once, and if Dayt thinks that Task would change his mind now. Dayt considers the possiblity of leaving Task and Exek behind.

Over dinner, Dayt and Anbis makes their move, spiking Task's drink with a dose of the knockout drug they had helped develop. Dayt and Anbis argue over wether to bring Task and Exek or not. Dayt argues they could just throw him in a locked room on the ship until they were clear. Anbis argued that Task had already decided to stay, and that bringing them along could jepardise their future survival.

They end up decideding to send Exek to bed and tell him that he didn't have school in the morning, and to not bother Task since he was very tired. They blindfold and gag Task and handcuff him to his bed, and damage the door to the room.

Dayt an Anbis then head back to the Mystic Trench. Anbis disables part of the perimeter security and the two sneak back onto the ship. Anbis sends radio traffic to make it seem like the GRU is confiscating the ship, trying to keep scrutiny off of the ship's launch activity. The ship's refueling takes a long time. After sunrise the following day, the first alarms begin to sound 10 minutes prior to launch. Hasty GRU attempts to access the ship were thwarted by the Mystic Trench's ignition sequence.

Task wakes up and escapes from his bondage just in time to watch the Mystic Trench lift off. Task rushes to the nearby spaceport and scrambles all available ships. He boards a corvette that lifts off in pursuit.

As the Mystic Trench ascends it orbit, the small patrol craft stationed around Baron 3b catch up and begin attacking. Anbis activates the Mystic Trench's automated weapon systems, which catches the pursuers off guard. Long range attacks manage to damage some of the Mystic Trench's engines, slowing their ascent. Anbis detects a task force of GRU ships in nearby system scramble to assist the force of Baron 3, consisting of several battleships and heavy cruisers. Anbis relises that the Mystic Trench's reduced speed means the task force will arrive before they can attempt a SFTL burn.

Realising he is trapped, Dayt hot mics his radio and begins the procedure for PDE activation.

The launch sequence has a few issues, but Dayt manually overrides them. Before commencing ignition, Dayt tells Tasks that he almost brough him and Exek, and hoped that he made the right decision.

Upon ignition, the Mystic Trench is engulfed in a massive cloud of burning space material, and vanishes from view.

 
Character chevron_right Notes link mentioned Pulse Detonation Engine Mishap


This scene was created by GRUsturmovik on Notebook.ai.

See more from GRUsturmovik
Create your own universe