Chapter 2 - The Bushan-Re

Fleet Intelligence Personal Log 

I remember the punchline of an old joke: With ki'ithmates like these, who needs enemies. While I
don't remember the joke itself, it still holds true. 

Kiith Manaan asked for our assistance on a search and rescue mission. The last word the Bushan-Re
sent was of a power-plant failure. We had reports of Turanic Raider ships operating in this region,
so all pilots were put on combat alert. 

Recon craft started on a spiral path outward from the Kuun-Lan, with two Recons traveling on
opposing vectors on an X/Z-vector to increase our effective sensor bubble. The third Recon traveled
on a Y/Z-vector in case the Bushan Re had drifted significantly from its last reported path. Mining
craft and the Mining Processor Hard Luck started to a nearby patch of asteroids, escorted by Tooth
and Fang Acolyte squadrons. 

Actually, their official designation is still Alpha and Beta Squadrons, but I had a word with the
Squadron leaders. They agreed with me that it would be a morale boost to have more... combatoriented code-names. While Tactical might insist on calling them by generic squadron names,
Colonel Sareni cannot force the squadrons to use the names among themselves. 

We did have one small problem facing us. The Somtaaw has never had reason to build their own
salvage or repair corvettes. Repairs would be done in the hanger bay of the Kuun-Lan itself, and the
Somtaaw have not had occasion to salvage enemy ships. In addition, the Kuun-Lan does not have
sufficient docking space for corvettes; part of the incentive behind the ACV program was the fact
the ACVs could be converted back into easily-stored fighters when docking. 

It was decided that we would need to build an Engineering Module and modify the Worker ships
for Repair and Salvage duty. (To be honest, I found the idea rather innovative. One of Karan Sjet's
greatest difficulties was keeping track of multiple ships. While having specialty ships was easier for
engineering and repair purposes, it would strain resources. Multi-speciality ships allows us to use
fewer ships for more purposes. And while the ships will not be quite as effective for each role as a
specialty ship, the benefits outweigh the disadvantages.) 

The Kuun-Lan had to jettison the upper ore canister to make room for the Module. Fortunately, the
Kuun-Lan (and its sister ship, the Faal-Corum) are modular in design. Any section from the Hanger
to the Engines to even the lower decks of the ship can be jettisoned. The upper ore canister was
destroyed to keep it out of the hands of the Turanic Raiders, and work on the Engineering Module
began. 

Sensors soon detected fast moving meteor belts in the region. The first belt of meteors was a threat
to the Kuun-Lan, and we had to move position. After a brief discussion, we decided that our fighters
should have no problem maneuvering through them. The problem posed by the meteors was if the
Bushan-Re drifted into one of them it could be easily destroyed. 

The mining ships soon attracted trouble of their own with the attention of two flights of Turanic
Bandit-class fighters (consisting of five fighters for each flight). Recon-045 reported contact with
a third flight of Bandits and retreated toward the Kuun-Lan. Tooth and Fang Squadrons promptly
engaged the Raiders as ACVs. 

While the hybrid corvettes were slower and less maneuverable than the Bandits, the Raiders
concentrated their initial fire on the Workers. This gave the ACVs the edge in the fight, allowing
them to escape with minimal damage. (ACV Tooth-01 did need to return to the Kuun-Lan for
repairs, but this was more a precaution against future Raider attacks than a critical need.) 

The Tough Luck also proved quite apt at protecting the Workers. For a bunch of miners, they're good
shots. I'll make warriors of them yet. To be honest, the Processors the Somtaaw designed are much
better craft than the Resource Controllers we used 15 years ago. (I argued for over a month during
our journey to Hiigara that the Controllers needed mass drivers to assist in defending our own
mining ships; however, I was overruled in the belief that if we armed those ships, they'd become
military targets. While they were ignored by Turanic and Taiidani fighters, they were easy prey for
bombers that the fighters were escorting.) 

A second wave of Bandits joined the first in chasing the Recon, and we ordered her back to the
Kuun-Lan. The Raiders were soon met by a wave of mass driver fire from the Command ship. We
suffered minor damage fighting the Raiders. In addition, Recon-045 was lost when she approached
too close to the combat; the Raiders seem to take a perverse joy in destroying our Recon craft.
Luckily, Lt. Saena survived, and was recovered by a Rescue & Recovery shuttle when the battle had
ended. 

Five minutes after the battle ended, construction crews reported that the Engineering Module was
completed. Cyrogenics reported that the Engineering crew who were to man the Module had
awakened from stasis, and after an additional 10 minutes testing the systems in the Module, the
Engineering crew began research on how to modify our Workers with repair technology. It was also
decided to modify the Processor; the Engineers felt it could have four repair modules, two situated
on each side of the Processor. 

We fought off four further attacks from Turanic fighters. I calculated their approach vector and
found that most of the Raider fighters had come from one specific region; it was likely a Turanic
Carrier was out there, reinforcing the fighters. I suggested to Colonel Sareni that it was unlikely the
Bushan-Re was along our positive Z vector. The Raiders appeared to be searching for something;
it was likely they were hoping to capture the Bushan-Re and use the ship in their own fleet (or
ransom it and the crew back to Hiigara). 

After focusing our sensors along the negative Z vector, Tactical reported that faint comm echos had
been detected along an X/-Z vector. Recons 048 and 062 went to the region to investigate.
Unfortunately, Recon-049 was intercepted by another flight of Bandits and was destroyed. The pilot
survived, and Tooth Squadron unlinked into Acolytes. Half of the Acolytes escorted two R/R
shuttles to the site, while the remainder stayed with the mining ships along with Fang Squadron. 

Engineering soon reported that Repair specs had been complete. The modifications were easy
enough to be made in the field, and soon the Tough Luck begin building repair modules. The
Workers continued to harvest the patch of asteroids they had found while engineers on the Workers
started putting together a repair module; it was believed that with the proper components together,
that Engineers could install the package in under a minute. The Workers need to be powered down
in order to install the Repair module. Engineering started researching how to upgrade the Workers
to perform salvage duties as well. 

10 minutes after reaching the region with the comm echos, Recon-062 detected the Bushan-Re. She
had suffered serious damage, and had several fires burning around the engines and on the lower
deck. We were able to tight-beam a message to the Destroyer, and learned that they had been able
to evacuate the damaged sections; only five fatalities were reported, though over half of the crew
had suffered injuries. The Recons took up holding positions around the Bushan-Re while waiting
for backup. 

The Processor Tough Luck immediately started toward the Bushan-Re with Fang Squadron, while
Fang Squadron stayed with the Workers, who shut down and immediately started upgrading with
the Repair module. The Kuun-Lan and the Spirit Quest also started moving toward the stricken
Destroyer. After finishing their upgrades, the Workers immediately set course for the Bushan-Re
as well; with their higher speed, they soon overtook the Tough Luck. 

We reached the Bushan-Re without further incident and began repairs on her. We also successfully
recovered Lt. Marlie without incident, and Tooth Squadron relinked into ACV mode. After 10
minutes, sensors detected four Hiigaran Support Frigates emerge from hyperspace. They indicated
they wished to assist us in repairing the Bushan-Re and started toward our position. 

Tooth Squadron diverted course to protect the Frigates from any Turanic fighters in the area. I soon
received a tightband communique from Captain Kensar Soban, who was assisting the Somtaaw
pilots as a squadron leader. (Kensar was one of the Soban who was revived from the Sleeper tubes
en route to Hiigara when his cyropod started to fail. I hired him to help train the Somtaaw's fighter
training program.) 

Kensar told me that the Frigates were giving off an ion trail, like that from fighters and corvettes.
While one Frigate might have a drive malfunction that could cause this, for four to have the same
problem was a matter of curiousity. The four Frigates showed up on both sensors and visual scans
(looking at the ships through the cockpit), but I let Kensar know privately to keep the squadrons on
alert. Kensar also alerted the Captain of the Spirit Quest to position his ship in position to push the
Frigates away in case there were problems. 

The frigates approached to under a kilometer before they stopped. At that point, Fleet Command
noted that the Frigates were not transmitting any kiith recognition codes. As we started trying to
visually identify the Frigates, sensors went wild. The ships appeared to twist and change shape
before our eyes, reforming into four Thief-class Raider corvettes. 

Having been alerted by Captain Kensar, our ships immediately started firing on the corvettes. The
Bushan-Re also immediately fired with its Ion Cannons; I later learned that Captain Kensar had
tight-beamed a message to Captain S'tarl Manaan, warning him to be ready for a trap. (Captain
Kensar has not informed either Tactical or Fleet Command of my involvement in this; Colonel
Sareni was displeased with his failure to inform her of the situation, but accepted his reason that he
was worried the ships would detect his message. 

I realize that I need to be given an official standing within the Kuun-Lan. Just being the Oracle's
consort (a phrase that still makes me want to laugh) is not suitable in a military environment. And
while the Kuun-Lan is not a military vessel, there is a chain of command, and I need to be placed
within it. Otherwise we risk dividing the crew when some turn to me for advice. 

Five additional flights of Turanic Raider craft were detected when the Thief Corvettes showed
themselves. This included a flight of six Brigand-class Missiles corvettes, as well as several flights
of Bandits, each lead by an additional Brigand corvette. These were all on an intercept course with
the Bushan-Re and the remaining vessels. Our Recon fighters immediately fled the battleground;
the Somtaaw have noticed that the Raiders seem to take a perverse pleasure at destroying our Recon
fighters. 

The Spirit Quest rammed the first Thief corvette, destroying it, while the Bushan-Re focused
firepower on a second corvette. In a matter of 20 seconds, the remaining Thiefs were destroyed, and
we were able to shift our focus to the incoming fighters and corvettes. Before they closed to attack,
Recon-062 reported the presence of the Turanic Raider Carrier. The ship remained outside of the
Kuun-Lan's sensors, and seemed to be there primarily to reinforce the fighters and corvettes
attacking the Bushan-Re. 

With our presence, it seemed unlikely the Raiders would be able to capture the Destroyer, and the
Raider Captain must have come to the same conclusion. The next wave of fighters was sent after
our Recon craft, chasing them away from the Carrier. 

I realized the Raiders were trying to hide their next actions from us. At the time, I believed they
intended on attacking us directly with the Carrier, and try to drive us from the Bushan-Re. I soon
realized I was mistaken. Fortunately, I did have time to inform Captain Sjaar of my suspicions.
When I approached, I overheard this communique between Fleet Command and the Bushan-Re: 

Fleet Command: We're picking up a dual signal on the emergency channel. Attention Bushan-Re!
Did you send out a distress beacon? 

Bushan-Re: Negative, Kuun-Lan. We've been picking up that signal since we drifted into the region.
It must be some kind of derelict. 

Recon-062 soon reported contact with the derelict. 

Tactical: Source of anomalous signal located. It may be of some value. Recommend sending a
Worker in to investigate and retrieve source of signal. 

Engineering reported that they had finished preliminary research on modifying the Workers to
perform Salvage duties. While they were still working on the VOP (Viral Override Protocols),
magnetic grapplers had been designed to allow the Workers to tow small ships without engine assist
from the captured vessel. As we were looking at a derelict vessel, and likely something small
enough to not be picked up by the Kuun-Lan's sensor array, it was felt that the magnetic grapplers
would be sufficient. Workers 152 and 146 were taken off repair-duty and started work on increasing
the efficiency of existing magnetic grapplers used to dock the Workers within the Kuun-Lan. 

Within two minutes, the upgrades were complete and Worker-152 started toward the derelict.

Worker-146 was put on escort duty to repair 152 in case of Turanic attack, or to assist in towing if
the derelict was too massive to be moved with just one Worker. Tooth Squadron and the Spirit
Quest were also put on escort duty. This proved fortunate as soon Tactical detected Turanic Raiders
on an intercept course. 

Tactical: Picking up Turanic Raider comm transmissions. They must be after the derelict as well.
Engage and destroy. 

The Tough Luck and remaining Workers reported that exterior repairs to the Bushan-Re were
complete. Weapon systems were also on-line, as was their hyperdrive engine. Captain Sjaar decided
to ask the Bushan-Re for assistance against the Raiders. 

Fleet Command: Attention Bushan-Re. Was wondering if you might be able to help out? 

Bushan-Re: Sorry Kuun-Lan. We barely have Nav restored to the point that we can hyperspace.
Besides, even a mining Kiith should be able to handle a few pirates. Thanks for the help. Bushan-Re
out. 

The Bushan-Re then activated hyperdrive engines and fled back to Hiigara. 

I suppose I can understand the Bushan-Re's position. They were still damaged, with many injured
crewmembers. But their final comment could be considered insulting. Captain Sjaar's reason for
asking for assistance was to minimize the chance of losses on our side. Even after 15 years, with
new technologies to assist us, we are not a numerous people. Every life lost is a life we could not
afford to lose. If we of Hiigara do not stand together... then we risk losing to the Taiidani
Imperialists in a war of attrition; a war they are much better suited to fight than we are. 

Recon-062 soon reported five Thief corvettes on an intercept course with the derelict and Worker152. Fang Squadron was dispatched to assist Tooth Squadron. We soon detected multiple bogeys
as several more flights of Bandits with Brigand Missile corvettes leading them in. This is when the
wisdom of the ACV program was proven; the Brigands started a missile volley against Tooth
Squadron which would have decimated a fighter squadron. Tooth Squadron took heavy damage, but
was able to destroy the Brigands. Fang Squadron focused on the Bandits. 

Worker-152 was attacked several times, but soon docked with the Kuun-Lan. Unfortunately, at that
time we received a distress signal from Recons 048 and 062. Recon-048 had just been destroyed
(though Lt. Jeslai has ejected and was still alive). Recon-062 had taken damage and Capt. Yebail
felt she would have to eject soon. Her last report was that several Raider ships were docking with
the Carrier; it seemed likely that the Turanic Raiders were pulling out, having lost their chance at
the derelict. 

Tooth Squadron docked with the Kuun-Lan to undergo repairs, while Fang Squadron escorted three
R/R shuttles to the last reported location of the lost Recon fighters. Worker-146 also successfully
retrieved one of the derelict Thief corvettes; Engineering was told to start work on duplicating the
Turanic holographic technology after they finished the VOP programs and finished the Salvage
routines for the Workers. 

Colonel Sareni also informed us that the derelict appeared to be a message pod of some type, but
with a completely alien technology. It seemed likely to predate the initial conquest of Hiigara by the
Taiidani, though we would need to run further tests to determine the actual age of the pod. 

The message within the pod also defied translation, though linguists were continuing to work on it.
A message was sent to the Somtaaw High Council for advice on what to do next. (My personal
feeling was to contact Kiiths Sjet and Kalaal and work on translating the message before dissecting
the pod, but I decided to practice some tact and mentioned it to Jaana instead. She seemed...
distracted, however. She... well, it's hard to describe. I've been married for 15 years, and I've only
seen her look like this a few times before; it was as if she was scared, but when I asked her, she
denied it. Jaana said she'd mention my advice if a chance rose where it would not be taken the
wrong way, but I suspect she's going to forget. I wish I knew what was eating at her....) 

We resumed mining the remaining harvestable asteroids in the region while the R/R shuttles
recovered our lost Recon pilots. Fang Squadron reported contact with one Bandit flight, but
destroyed them with no losses. 

Finally, we received word back from the Somtaaw High Command: 

Fleet Command: Honored Greetings, Somtaaw Kiith-Sa. Did you receive our data regarding the
anomalous artifact? 

Somtaaw Kiith-Sa: We have. Our researchers agree the signal and design matches nothing currently
used by known Galactic races. Where is the pod now? 

Fleet Command: We have brought it aboard now and are securing it in the main Hangar bay. What
should we do with it? We're just a mining vessel. We are not equipped to study anything like this.

Somtaaw Kiith-Sa: We are transmitting design specs so that your manufacturing unit can construct
a science module.

Fleet Command: Excuse me Kiith-Sa, but would it not be easier to seek help from another Kiith?
We are still within hailing range of the Naabal Command Carrier. Surely they would have the staff
to-

Somtaaw Kiith-Sa: NO! A find like this could lead to alien technology that surpasses anything used
by the other Kiith. Somtaaw needs this advantage. 

We have a science vessel, the Clee-San, studying stellar phenomena in the Coruc-tel system. They
have been ordered to meet with you at these coordinates and transfer over a research team with
analysis equipment. This matter must be kept within Kiith Somtaaw. Is this clear? 

Fleet Command: Yes, Kiith-Sa. Very Clear. Kuun-Lan out. 

We are preparing to hyperspace to the Coruc-tel system now to meet with the Clee-San. I have a bad
feeling about this... I still think this should be handled with Kiith Sjet and Kalaal... but I cannot
mention this now. I am barely trusted as it is. If I state my opinion... then I wonder if even being the
consort of the Oracle would be enough to save me. At the very least I'd find myself in the brig until
Somtaaw has finished dissecting the pod. 

Also... I don't know. Something just doesn't feel right. Jaana is... that alien artifact appears, and
Jaana starts acting odd, like she's waiting for something to happen. I have to be with her. She needs
me. 

I look back at this paragraph and the cynic in me snorts. I'm starting to sound like my wife now.
Sheesh. Still, I suppose someone has to keep her out of trouble. Well, more trouble.