The following communication is classified level Sigma, any unauthorized access is punishable under The Order's Toledo Security Act of 804 A.S of the Black Squadron charter.
The special directive was received by Mission Commission and forwarded to the only available unit in range with adequate equipment to undertake the operation. O.C.V. Svizra, testing fleet-wide prototype of Faster Than Light device independent of jumphole network. Secrecy and minimal radio contact was maintained through the mission, limiting exposure of vital intelligence slipping to unauthorized hands and crew. The only personnel fully or partially aware of mission details, besides Admiralty Board and people directly authorized by Adm. Golanski, are listed as follows.
⧫ C.O. CPT N. Herrera (BF5-036-434)
⧫ X.O. CDR V. Sanford (BF2-399-155)
⧫ COMM LT S. Savidge (BF3-009-513)
⧫ NAV LT K. Takenaka (BF8-575-727)
⧫ FTLOPS Agent H. Leitzke (WW9-342-788)
⧫ GUNN LT D. Silva (BF8-412-839)
⧫ SENS ENS G. Deniaud (BF2-602-122)
Asset list
⧫ O.C.V. Svizra - Osiris-class
⧫ CITRUS ALPHA - Satsuma-class, friendly
⧫ HIKARI 2 - GC The Sisterhood fighter, based of Satsuma
⧫ HANA 1 though 3 - GC The Sisterhood escort fighter element, friendly
⧫ AMARIRISU - GC The Sisterhood armored transport, friendly O.C.V. Svizra entered Chugoku at 12th May 826 A.S. 2100 SMT / 1000 AMT from direction of Tohoku under guise of heavy armed patrol. To keep appearances, Svizra had not utilized its onboard cloaking device and instead complied with Blood Dragon directives. Unopposed, Svirza proceeded to cruise to coordinates D-2 and held position.
O.C.V. Svizra aboard complement of snubcraft consisted of two X-Shuttles reserved for S&R, MEDEVAC and transfer of qualified engineer personnel. 30th Tactical Squadron “Dawn Breakers” was on standby. CPT Herrera decided against deploying any element of 30th as to minimize exposure to confidential intelligence. Assessment was well calculated: possibility of enemy assault deep within allied space was minimal. Chugoku space did not experienced either KNF or AOI raiding parties that day.
Mission was straightforward. Locate and intercept objective marked as CITRUS ALPHA, name chosen to not alert Blood Dragons to existence and most importantly presence of this warship. Certain fluctuations in Kusari political climate on the side of the revolutionary forces caused The Sisterhood to panic and request assistance of The Order to jump the ship to safety. Due to urgent nature of request, Adm Golanski used executive powers to approve an immediate rescue operation. Rather than use towing tugs or a Bison-class transport with sufficient materials to move CITRUS ALPHA under its own power, it was agreed to deploy hyperspatial FTL device.
CPT Herrera executed mission parameters to the letter, linking up with HANA wing and converging closer to Mito docks. First contact was made at 2234 SMT / 1134 AMT with HIKARI 2. Stranded and able to move only on partial impulse speed, crew of CITRUS ALPHA sought to look for help at Mito as it allegedly was part of their original plan. HIKARI 2’s mission was overridden by HANA 1 and newly arrived AMARIRISU docked with CITRUS ALPHA to deliver technicians and parts to the warship. Emergency protocol was initiated to land every available asset and commence hyperspace jump to OMICRON EPSILON.
Blood Dragons are unaware of our involvement and failed to locate CITRUS ALPHA. Proximity of Mito leads Intelligence to suggest that Blood Dragons may had scrambled interceptors in attempt to find CITRUS ALPHA. It is no doubt they had detected surge resulting from exit vector of GC jump. The Order departure was however not noted and search parties had been cancelled.
Official Order story dictated by Wedjat is as follows: O.C.V. Svizra was reprioritized elsewhere to safeguard Order convoy and engaged its cloaking device to depart Chugoku unnoticed.
Wedjat operation is approved and scheduled at 14th May to re-emerge Svizra to the world at large in Tohoku to support the official story. Wedjat armored transport codenamed ABADDON 2 and 4 will be used as decoy and subsequently withdrawn to Epsilon under guard. 30th Dawn Breakers will escort ABADDON to Fort Carthage and return to Svizra. Cargo manifest of ABADDON will be forged and scrambled under decoy commodity.
⧫ Carthage
⧫ Omicron Epsilon
⧫ 15/05/826
⧫ FROM: COL C. Blair
⧫ SUBJECT: Damage assessment
Start of report
The following communication is classified level Sigma, any unauthorized access is punishable under The Order's Toledo Security Act of 804 A.S of the Black Squadron charter.
Following report is for the eyes of The Order Overwatch General Assembly’s eyes.
On the 14th May 826 A.S. at 0013 hour a warship designated as “Shiragiku” had entered Carthage’s security perimeter. As standard procedures pertaining heavily damaged capital ships, four shuttles carrying Order marines and engineers had boarded “Shiragiku” to secure the vessel for emergency mooring. Three tug boats were assigned to dock “Shiragiku” in assigned position when at the same time marines were operating its limited in capacity main engine and maneuvering drives. Mooring procedure was completed with a seal by 0058 hour.
There are no casualties or injured requiring immediate medical attention aboard. Non-essential GC and The Order personnel were evacuated. The Sisterhood, a curious sight to behold on Carthage of all places, were accommodated in right wing, deck 14. Marines detachment secured frontal airlocks, primary elevator, internal hangar and bridge. Due to fact that we do not possess blueprints or even layout of Satsuma-class battleship, damage control teams could not enter beyond aforementioned sections. Instead, we deployed drones to map and investigate other decks for damage and booby traps.
15th May 1200, Wedjat operatives took GC crew for a questioning. GC commanding officers complied fully and entered “Shiragiku” with Damage Control teams at 1500 to assess fully the extend of damage to the vessel’s hull.
Initial damage assessment
⧫ Powerplant
Primary energy plant has been breached, engineering and cooling decks had been contaminated by radioactive elements from reactor core 3. Traces of decaying isotopes of U - uranium, Pu- Plutonium, Sr - strontium and Cs - Caesium had been found across entire level too dangerous for unprotected human to enter. In first order, decontamination of entire engine and reactor block has been scheduled as a priority. Fortunately, majority of elements with extreme half life had been vented into the vacuum of space. Reactor 4 and 2 had safely disengaged and are dead cold - resetting is possible. Reactor 1 continues to operate despite partial degradation however provides only fraction of power that a warship will require to enter operational combat status.
⧫ Energy Grid
Energy grid is well preserved despite damage of infrastructure near Reactor Core 3. Capacitors of warships energy-based weapons operate at nominal rate, however recharging is severely hampered by ship’s power plant only providing approximately 18 to 20 percentage of total output at current maximum load.
⧫ Weapon subsystems
Weapon systems are nearly intact. Despite limited power output, entirety of the ship’s primary, secondary and tertiary artillery and turrets are fully operational. It is estimated that providing main reactor will be replaced, the vessel’s offensive armament can be brought to operational status. Those are pre-Nomad war models, dating approximately 750 A.S. during a wave of Kusari’s massive rearmament refit and expansion program in 8th century.
⧫ Structure
Structural integrity of the ship is remarkably in excellent state. Armor plating and main structure have suffered major breach only in close proximity to reactor 3. Catastrophic decompression noted in Engineering. Limited incidents of isolated decompressed sub-sections in deck 25th through 27th.
⧫ Auxilary subsystems
Life support is fully operational after emergency power has been brought online. Databanks and shipboard mainframe appear intact but under a security lockdown. Shield is fairly competent experimental yet outdated system from about 805 A.S. currently offline due to power shortages.
⧫ Drives
Propulsion is limited to approximately 80 percent of impulse. GC crew that operated the vessel prior could not push Satsuma to accelerate any faster. System used is standard fusion engine, propelling H-Fuel in its gas form as means of propulsion. It is in workable condition, however its effectiveness was reduced to balance out minor damage of leftmost exhaust.
There is one problem, Admiral. Satsuma according to previous intelligence dossier dating 810 A.S. concerning the ship’s defensive and offensive capabilities should be able to accept standard sized dock just like an Osiris. We did not broke the news to GC yet, however we will have to remove two dragon-shaped ornaments embedded into sides of Satsuma… at least for duration of its stay. According to survey of our teams already on site, these ornaments do not house any important or even a tertiary sub-system of importance. They are just extreme extravagance on behalf of the Imperial House of Kusari with no practical application whatsoever.