Enterprise Mission 00: "From Dauntless to Enterprise"

Mission 05 (Dauntless) StarDate 20504.04-20601.24 (Hromi/StarBase 343)

Mission Summary: “Time – The Unreliable Constant”

Full details of all events can be found in the mission logs that follow:

Intro to mission

A Star Fleet medical supply ship, the USS Alba Varden, went missing a few days ago. No reports from her had indicated anything untoward until a distress beacon started transmitting twelve hours ago providing only her location near the Hromi cluster, close to the Klingon border and about 21 light years from our present location. Long-range scans are difficult due to the proximity to the cluster. Our orders are simple, go out there, find out what happened, make any rescue and recovery that is possible, and report back. Of course things are never that simple ….

We stopped off on the way at the new StarBase 343 (under construction) to collect several new shuttles and stores from the Engineering Facility constructing the new base there, and also undertake some crew exchanges. Due to illness, Cdr Rylus had to be placed in stasis and so CTO Cdr K’Etana is now the FO.

Events @ SB 343

It was whilst we were at SB343 that we witnessed the unrelenting power of a black hole. Following very severe gravimetric interference we suddenly detected a large and expanding gravity well followed by a rapidly expanding singularity. Using our engines at high power to prevent our destruction, we managed to snatch a few smaller craft out of the gravitation pull to safety but several other ships were not as lucky. Light Cruiser USS Denab in for an engine refit was lost along with 35 of the 47 lifepods launched. As the ship crossed the 'event horizon' of the anomaly, it exploded sending a level 2 shock wave across the region. The Base was another victim - though we did lock onto the command module the stresses caused our tractors to fail. Released of the StarBase we were accelerated well beyond the safe sub-light relativistic limit and experienced suffered some damage. They were then hit by a massive shock wave emanating from the grossly enlarged black hole further damaging the ship. As sensors came back on line we got a confusing picture of local space – there were no other ships detected in the region, and nothing on any of the COMM channels—not even the normal 'background noise' that indicated any communication traffic of any source within sensor range. Sensors did reveal however that the 'anomaly' was gone, all spatial objects seemed normal other than a few of the stars seeming slightly off their normal positions and a short distance away was the Hromi Cluster. Further details were unavailable, as none of the Star Fleet subspace relay and sensor stations within range were detected, presumably as a result of the anomaly.

A welcome @ Hromi Cluster

Following repairs we started towards the Hromi cluster at Warp 9, continuing with the other repairs enroute. We were still concerned about lack of federation comm traffic, federation beacons, and the slight misplacement of local star patterns and scheduled a re-calibration (& re-alignment if appropriate) of our comms and sensor systems. Then we detected the distress signal from our missing medical freighter. Enroute towards the signal's point of origin the sensors picked up signs of a strange anomaly field, tears in the fabric of space were forming on a regular frequency of about 8 seconds. It was a virtual minefield of spatial anomalies emitting tachyons of high intensity but due to the size of it and the risk to the survivors, we opted to go through it. We could still scan beyond the field revealing something beyond but no wreckage could be detected, leaving the exact whereabouts of the Alba Varden unknown. However the distress signal was confirmed coming from the edge of the Gamma Hromi star system, just at the edge of the Hromi Cluster—on the opposite side of this 'field' of anomalies. Use of our active sensors appears to trigger a reaction from the anomalies, and after an abortive attempt using probes we used shuttles to steer the battle cruiser through, and headed for the source of the signal – Hromi IV.

As we got closer we started to pick up indications of a debris field though of insufficient mass to be our freighter, and on our comms all we could hear was static, of a similar format to an anti-time anomaly discovered by Captain Picard in the Devron system over 30 years ago believed to be emanating from the 7th plant. We then also discovered a chronoton-composed beam from Hromi VII that intersected Hromi IV where the debris field ends. Staying clear of the beam we continue our approach and detect another strange effect - it appears that everything that beam hits on the Hromi IV surface changes. According to our readings it's as though it's renewing the planet in some way. For instance, passing over what appeared to be a forest which had burnt several years ago there was now a thriving swamp in that very location. As Dauntless made another orbit around the world, our course had to be corrected slightly as the chronoton beam changed angle. Additional information was obtained by another probe until it intersected the beam and disappeared completely.

Full sensor sweeps were conducted, and with no sign of the ship or any wreckage the ship headed towards Hromi VII. As we entered orbit and neared the source point of the interference, sensors identified debris consistent with a small starship, however through the interference in the atmosphere it was hard to make out anything further. There was a massive electrical storm in the area and sensors just couldn't seem to penetrate it until we diverted more power to the sensors, applied several innovation sensor calibrations and took the ship into a lower orbit. We discovered a power source down there, from where the chronoton beam seemed to be emanating from. In addition the mass readings indicated what appeared to be a small starship—probably of the scout class. Armament information was unavailable as was the exact status of the ship, but the rough image of the hull showed a shape which was totally alien. It was impossible to tell anything more detailed without penetrating the storm. Following advice that it was inadvisable to trust the transporters we sent an away team to the surface in shuttles.

We initially lost contact with the shuttles are they headed to the surface, but recalibration of the deflector dish to attempt to clear a comm path to the away team appearred to work. Cdr K'Etana managed to get a comms message through, informing us that Commander Dega has just been caught by some kind of temporal stasis field from the wreckage. We were also informed that there is no Tetra radiation whatsoever in the surrounding atmosphere. According to the away team science officers this means the place is full of chronoton particles.

After ascertaining that there was a good probability that another deflector dish process might give us transporter facility I agreed with the FO to send down further away team members. We succeed but there were unexpected side effects; the transport went as planned though a lot slower than expected and suddenly explosions rocked the Dauntless due to major power overloads originating at Transporter Room one, spreading throughout the ship. As the warp core breached and matter/antimatter fuel explosions started, the chronoton beam from the planet intersected the doomed starship and she disappeared in a huge explosion surrounded the Dauntless and it winked out of existence, to leave behind only an ever expanding highly energetic cloud of supercharged particles and stellar gases.

Adventures of the Away Team I

Following a huge explosion in the upper atmosphere resulted in a deluge of acid rain and as the away team took cover, they found themselves enveloped in stasis bubbles similar to what captured Cdr Dega. We they woke up they found themselves in unknown bodies belonging to a race called the Az'SharrAhn'Ti. Though their personalities remained intact so did that of the previous occupants. In some the new persona was dominant, in others their own took control, and in the remainder a mental battle ensued. The mission of this Az'SharrAhn'Ti vessel commanded by the persona Captain Naa Va’Reece, formerly Cdr Mike Wong, was to destroy the crystalline entity, though whether this was the same one known to the Federation was not clear. Whilst some of the away team were dedicated in their new mission, others fought back, attempting to sabotage the vessel and her mission to try and bring the nightmare to an end.

As most crew went about their duty those affected found themselves scattered all over the ship in different positions. In engineering, upon discovering that he was still Ltjg Halycon but trapped in an alien body, Halycon went about trying to sabotage a projector generator. On the bridge the alien FO, aka Ryan, was left in charge as the Captain and CSO, who were coincidentally mates, discussed the strange goings-on in the ready room only to be interrupted by two armed crewmembers. They demanded to know what had happened to them and the away team. With weapons pointed at each other the situation quickly deteriorated. A mutiny took hold. There was a firefight, the CSO and Captain were seriously injured and the two crewmembers, Reid and Vol escaped to sickbay only to be apprehended there. Still en route to the crystalline entity the ship was in crisis; with its Captain in surgery the FO took command. And the two perpetrators waited in sickbay for their reckoning with the Captain.

Second Chance for the Dauntless

In the following sentence, the word ‘next’ is wrong in this context because it implies that this event followed the previous one, but there is no word in the English language that can possibly explain what is now happening … and yet it happened.

The next thing the Dauntless crew felt was a shaking sensation, although there was no apparent cause. Following a detailed scan of their patrol area along the Klingon border, there were no indications of a shock front in the vicinity that could have caused the disturbances we had just felt, but they were surprised when they detected a record about the apparent destruction of Star Base 343 a little over three days travel away, a fact verified by the ship's log as well as various other anomalies, as well as the disappearance of 14 members of the ship's crew. With no recollection that the destruction of Star Base 343 having been previously reported, and no explanation of the reasons for the disappearance of almost the entire senior staff a detailed search of the records was made. They discovered that the missing crew members formed part of an away team transported down to a planet Gamma Hromi IV just a few minutes earlier, a planet five days' travel [40 LY] beyond the position of the reportedly-destroyed Star Base 343, a total of eight days at warp 9.5. With the Klingon border quiet at this time and after conferring with the local Sector Commander, Commodore Owen on Star Base 157, Dauntless made best possible speed to StarBase 343’s last position.

On arrival at the intact SB343 the ship evoked dark ship status - no communications in or out, the sensor cloak active and all active sensors and navigational systems powered down. Sensors offered no evidence of a recent explosion or other untoward events. On a hunch Cmdr Thrawn ordered a hardcopy of the destruction record made and in reviewing the report discovered that the original report had been lodged by the Dauntless six hours into the future, giving a complete record of the black hole, the destruction and the presence of chronoton particles, the host of the time quanta. This latter point raised the possibility that they were facing an effect and causal time event, i.e. the effect predated the cause giving rise to the dilemma – interfere and possibly effect the future by attempting to save lives and the Base by aiding the future Dauntless if the anomaly does materialise or whether to not interfere. The decision was made - the ship will do everything it could to help without making our presence known to the StarBase or the other Dauntless – that would cause too many questions. The reports security signature confirms the report, albeit in the reality outside the hull not yet written, it was in fact genuine.

The Dauntless in dark mode observed the other Dauntless (in the report) arrive and start commencing crew transfers. When the scheduled anomaly started to appear however, its position was not as expected; altered by the presence of the dark Dauntless casting its gravitational signature and overlapping that of the StarBase. The Dark Dauntless changed cause and was detected by the Star Base which dispatched the further Dauntless to investigate. In an attempt to avoid the two ships meeting, for fear of the consequences of time-interaction, the Dark Dauntless send a unique code word to the future Dauntless. Both ships slowed to rendezvous but following a rapid shift of the anomaly due to the approaching mass shadow of the future Dauntless, both ships and the StarBase lost power, and the ships were by then travelling on a collision course desperately trying every means to abandon ship. The resulting collision and explosion enveloped the StarBase as well, destroying it in its own explosion. All that was left was a massive debris field of materials and bodies in a huge gaseous bubbling cloud of energy, with a smokey strand being pulled into the black hole. They were all gone ….. all dead … the black hole anomaly had won again.

Adventures of the Away Team II

The situation on the alien ship however was incredibly tense. Though the away team were small in numbers against a crew of 500 they had managed to secure high positions for ourselves, but there were now rumours and worry spreading through the rest of the alien crew. All of the injured, including the CO had been released from sickbay, and the CO had taken charge again of the Bridge and they were in pursuit of the Crystalline Entity.

As soon as they dropped out of warp the ship went to the equivalent of red alert. The entity was several thousand kilometres away, hovering by a green populated planet and as the ship approached, the entity suddenly dived for the planets atmosphere. In a rage the CO followed at full sublight speed. Not able to fire their weapons in the atmosphere without damaging the planet's ecology fatally he ordered the ship to ram the entity. With the deck plating shuddering as the ship was starting to feel the strain of the friction in the upper atmosphere, Dr Wong managed to reassert his control and ordered them to change course. The Helm hesitated at the change in orders and then complied, but at that moment bridge consoles, sabotaged by some members of the away team who were fighting their alien persona, exploded. The ship tumbled through the atmosphere with power and control lost to the bridge and they fell from the sky, brief glimpses of hills and rocky outcrops flickering on the viewscreen, their power source - a black hole singularity destabilising. As the ship continued to fall there was a sudden rise in its altitude, a vortex of some sort was opening behind it, caused by engine operation in the atmosphere. Though apparently set to swallow up the entity, the ship, and then the whole planet, the engineers shifted the position of vortex and it swallowing up the crystalline entity, and then popped out of existence. The resulting shockwave from the vortex closing levelled a nearby city, looking like the shock wave from a huge weapons explosion, and then threw the ship tumbling across the atmosphere toward a less inhabited region. The ship skipped off the top of a mountain, creating a huge gash in its underside. The Xandr’ made its impact in a deep lake somewhere on the Northern Hemisphere and sank fast, her crew desperately trying to escape their watery coffin.

Third Chance for the Dauntless

And then … impossibly …. the Dauntless found themselves on yet another timeline but this time with one StarBase, one Dauntless and just their mission plans – to find their missing away team. Following the completion of crew transfers and stores replenishment, they departed StarBase 343. Detecting a Star Fleet Distress Beacon which appeared to be coming from one of their own shuttlecraft originating from orbit of Gamma Hromi IV. Analysis of the distress beacon identified it had been broadcasting for about 24 hours.

As the Dauntless drew closer to Hromi IV, the scans began to get more detailed [though still impaired] results. Heavy ionisation in the planet's atmosphere was creating a massive handicap to the sensors, and there was little chance of sending communications or transporters through it. Scans were however able to locate the missing crewmembers, in a built up area surrounded by hundreds of thousands of alien lifeforms. In order to make contact with the Away Team I dispatched our duty security chief in a shuttle down to the surface.

Then the scans indicated severe electrical storms were covering most of the planet’s surface. The scans then detected something more startling - the planet was undergoing amazing and rapid environmental changes right in front of us. The cities and the wildlife were all disappearing, and the air composition was changing from oxygen to carbon dioxide. Indications were also received that would point to some kind of temporal phenomenon at work. According to these readings the entire world revert to a Class K world within minutes, transforming before Dauntless' eyes. What was once a Class M environment, with a clear atmosphere, cities, and a thriving ecosystem had, in the past few minutes transformed into what was now a world that was inhospitable and uninhabited.

Return of the Away Team

The Away Team members woke up to find themselves lying in a sickbay, in their own bodies and apparently completely healed; the damage done from the harsh surface of Gamma Hromi IV was gone, although there was one crewmember, Nathan Halycon, who seemed badly affected by it. They were not alone – Aliens in similar bodies to which they had occupied appeared to be worshipping them as heroes.

Cdr K’Etana managed to establish that they had been expecting us for thousands of years, and in fact, they regarded them especially Mike Wong as their saviours. They were the descendants of the aliens we had inhabited. When Mike had decided to spare the ship and thus caused it to crash into the planet Gamma Hromi IV the crew was stranded. Stranded and with no way home they settled down and built a life for themselves there. Their descendants now enjoyed a small civilisation, with cities and towns and culture, The Away team were invited to stay for a ceremony on ‘their’ descendants behalf, but it was only after secretly checking that their Federation shuttle craft was spaceworthy that they agreed. On the very short trip to the arena that was to host the ceremony, it was clear that the planets surface had changed drastically. No longer was there an inhospitable atmosphere and rocky ground, in its place were lush green grass and native plants and snow capped mountains and hills in the distance. It was pleasantly warm. Once they arrived and took our seats at the very front, they realised that they were on a huge stage facing a crowd of tens of thousands of aliens. The alien leader gave a short speech and welcomed each of us to then give a speech of our own. Some went well, the aliens went wild when Mike stepped up...and Kathy’s was very diplomatic. Following the speeches were done an amazing display of fireworks were set off, and through it appeared the shuttle piloted by Chief Carson Smith from the Dauntless.

The alien leader realised it was time for us to leave and approached the FO and gave her a memory chip, adding with a strange tone as if he knew something was going to happen "On this you will find a file of our complete history. Please ensure that our memory lives on..." . Moments later the mountains in the background began to fade, the crowd began to diminish...the leader standing before them seemed to swirl in and out of existence, and then acid rain began to fall. The world was reverting back to the way we had first found it. Sprinting for the shuttles, dodging the shrapnel from exploding rocks and burns from the acid they made it to the shuttles and then back to the Dauntless.

A debriefing was arranged and it was clear from what was said that there were still major gaps in our understanding and that it would be left to the Temporal Experts to stitch the story together. The science vessel enroute to starbase 343 would also be rescheduled to undertake a survey when it had completed its duties there.

It was also clear from what was said that several of the new officers had suffered personality so the Counsellors services would be in great demand. Before that could be completed however one of the Away Team managed to seriously injury Dr Wong, Major Sexton, LCdr Thomas. At the same time the person was identified as Halycon, he was in the process of attacking Cmdr Thrawn in his quarters. It was clear that the alien persona had reasserted control, and as the assassin removed a large knife and gloated over the fact of his evil deeds, a strange expression come over the officer. A look of puzzlement …. almost bewilderment as an internal battle was fought and won… the ferocity in his eyes had suddenly gone .. and then he thrust the knife into his own stomach and then stammered “Lieutenant…Junior Grade…Nathan Halycon reporting in sir…” before falling to the floor.

Docking at StarBase Alpha all the wounded were transferred to the Base Hospital for specialist treatment and shore leave was granted to the crew … with some interesting results

Mission Summary Hkomi Ends/…]

Captain's Logs

Cmdr Thrawn

Stardate 20504.04

Stardate 20504.05 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #01 - events up to 5 April 2005]

We didn’t even get time to return to StarBase 157 following the end of our previous mission before I received new orders from SB157 Commander, Commodore Owens.

Apparently a Star Fleet cargo ship, the USS Alba Varden, went missing a few days ago. No reports from her had indicated anything untoward until a distress beacon started transmitting twelve hours ago. It's a typical automated beacon with limited data, but has served to provide a location for the stricken vessel. The Alba Varden was transporting medical supplies, and was near the Hromi cluster, which is rather close to the Klingon border, about 21 light years from our present location. The beacon is coming from the edge of the cluster itself where interference makes any detailed long-range scans difficult. Our orders are simple, go out there, find out what happened, make any rescue and recovery that is possible, and report back. Now I have just received an update. I was going to pull a updated data feed from StarBase 24 but we have been ordered to travel via StarBase 343 at best speed where we will be collecting several new shuttles and stores from the Engineering Facility constructing the new base there. We will also be picking up some new crew members and Commander Havek will be transferring to a ship there for transport back to StarBase 157 where we will meet up with him when we return.

Calling a Department Heads meeting together, I have outlined our mission profile, informed them of Cdr Haveks temporary departure as well as our ex-security chief LCdr Caer’s promotion to Commander and FO of the Drake, whilst awaiting us at StarBase Alpha. Various DHs have been asked to obtain as much information of the ship, her cargo, her mission, and the locality we are approaching so we can be as ready as possible for what we may find. Presently we do not know whether the close proximity to the Klingon border is relevant.

Following the meeting, Cdr Samantha Rylus (FO) looked decidedly unwell, and on enquiring further I summoned CMO Dr Wong. On investigation we established she had what looked like white and yellow pin prick size pustules where the cuff and collar elastic had pressed into the skin. Samantha then added that she had started feeling very hot and itchy about thirty minutes previously, but she had felt clammy since the recent viral agent outbreak a few days ago. Following an initial opinion that Commander Rylus was reacting to a side effect either from the initial virus or our responsive measures, causing her immunity system to be overly stimulated to the extent that her body has become aggressive, like a very bad allergic reaction. He added that he would take her to sickbay and carry out more tests as he was worried that this was showing symptoms similar to a contagious reaction. Further tests showed that her body organs have been severely weakened to the extent that we probably will be unable to overly stimulate their recovery, but for a definitive prognosis we still need to run some tests. As a precaution to avoid further deterioration over what is clearly a long term recovery period, she has been put into stasis.

Accordingly I have formally relieved Cdr Rylus of her responsibilities as First Officer and appointed Cdr K’Etana in her place.

Additionally Lt Dregs has been promoted to Assistant CMO.

Log ends/..

Stardate 20504.19

Stardate 20504.19 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #02 - events up to 19 April 2005]

This log finds the majority of the crew in good spirits following a get-together in 10Forward courtesy of Lt Dregs who has been made ACMO.

To recap recent events, Dauntless arrived at the StarBase 343 without incident to find the area a hub of activity. A lot of the main body modules have already been coupled together and seam welded, and there is a lot of outfitting already in progress even though the station is clearly not structurally completed yet. Albeit not completed, one of the new deep space sensor systems had already been fitted, and given this bases location with regards the Klingon Empire is probably already in use – this will hopefully provide us with a lot of updated information regarding the Hromi cluster and the nearby Klingon regions.

Whilst downloading the latest intelligence and sensor data, quite a few of the crew headed for 10Forward and the Entertainment decks facilities. Whilst there I discussed with Major Ryan and Lt Thomas the developments on the joint marine & security team training project - an attempt to foster a new understanding between the two groups with a cross fertilisation of weapons usage and tactics – and I understand they are planning a series of training holodeck exercises.

It was as expected an opportunity to say a few words to the senior officers, to announce various promotions in rank and changes in responsibility; • Cdr Rylus’s replacement by Cdr K’etana as FO due to illness [and formally denying that this was anything to do with K’etana’s diplomatic skills as CTO and her well known navigation skills, and the fact that I was running out of shuttles for her to fly :)] • LCdr Wongs promotion to Second Officer, • our ex-COS LCdr Caers promotion to Commander and FO of the USS Drake, and • her subsequent replacement being Lieutenant Thomas.

We also welcomed several new members of the crew transferred from the StarBase under constructions – Midshipmen Halycon and Farseer – and said goodbye to our Chief Science Officer Cdr Havek who is returning to StarBase 157 on temporary reassignment.

It was also that time when I was pleased to announce the further promotion of Lieutenant Dregs to Chief Medical Officer of the Copernicus, a Galactic Science Vessel, tinged of course with sadness at the loss of such a promising, professional, quick thinking doctor

With the exception of a brief tête-à-tête between a drunken marine and major Ryan, resulting in the offender being thrown in the Brig for future sentencing by myself, the party was a great success.

Once the transfers have all been completed and the intelligence downloaded we will be departing for the Hromi Cluster, approximately 11 Light years away, to continue our search for the missing medical freighter.

Log ends/..

Supplemental:-

What I and several others didn’t realise at that time was the appearance of a young girl in the corner, dancing by herself to the music which was playing. Apparently human, she was about 6–7 years old, with strawberry hair pulled into pigtails and held up with white bows, bright blue (almost glowing) eyes and a fair complexion with freckles all over her face. She was wearing a pink sundress and white shoes, and laughing to herself as she danced. Sounds suspiciously like someone we encountered on our last major mission but left over a hundred light years away on the other side of the Klingon empire.

Log ends/..

Stardate 20504.27

Stardate 20504.27 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #03 - events up to 27 April 2005]

I believe I started the last log entry by saying that the majority of the crew were in good spirits – how things have changed – now we are coming to terms with the potential loss of thousands of lives and the new StarBase which was under construction..

To recap what has happened.

It started with approximately a two minute period during which an unexpected and very severe gravimetric interference was apparent across several hundred thousand kilometres. Everything in the area was being shaken violently and several of the ships and construction equipment in the area were reporting minor damage and some small injuries. Shortly afterwards we suddenly detected a large and expanding gravity well forming, approximately 12,500 kilometres off our port stern, exerting a force of 30,000,000 kilograms per square metre of pull on the ship, requiring 12% engines just be remain stationary. Increasing to quarter impulse momentarily allowed us motion away from it , but the even at that force we were soon loosing ground again. Then we detected a singularity forming starting off at ~ 1 metre and rapidly expanding.

It soon claimed its first victim; a construction shuttle was sucked in and disappeared when they reached the anomaly perimeter. Putting some distance between the anomaly and ourselves we managed to snatch a few smaller craft out of the gravitation pull to safety. Unfortunately several other ships were not as lucky - Light Cruiser USS Denab in for an engine refit was lost along with 35 of the 47 lifepods launched. As the ship crossed the 'event horizon' of the anomaly, now measuring 82,000 km in diameter, it exploded sending a level 2 shock wave across the region. Following a general evacuation order from the StarBase and a plea for any help that could be offered, we commenced tractoring shuttles and transporting personnel to safety. One shuttle moving in haste collided with our ship and was heavily damaged. The StarBase, which was at that time now 140,000 km from the Dauntless and therefore outside transporter range, was slowly still moving toward the anomaly and escape craft were launching from it rapidly. Sensors indicated that the number of people aboard was still over 1,000. It was shaking and trembling as it's small engines tried to pull away, but it was obvious the act was futile.

Science were able to analyse the anomaly and reported that it closely matched what was known as a 'black hole', with the exception that it had appeared from nothingness and was growing—and black holes normally did not exhibit chronometric readings. The analysis of the chronometric readings indicated that time was being compressed along with space, at a quantum level, at the center of the anomaly. As best they could tell based on the computer models, the anomaly was compressing the spatial and temporal nature of the objects entering it, and then they would disappear to another space/time …. that is if they were not being destroyed by the compression. It also appeared that the greater the energy and mass signature of the object being absorbed, the greater the pull of the gravity well, and the more the anomaly would grow. This meant that when the station was absorbed, the anomaly would likely expand dramatically in a very short time. Guesswork implies that the anomaly will probably stop growing, or nearly stop growing, once every bit of solid matter or energy within it's reach has been 'absorbed'. As for the temporal flow from the inside, it was hard to tell, but indications were that objects were being sucked into the past as they shrunk...

While Mid. Halycon and Dr Wong established a forward triage and collection point in 10Forward, I was left with a decision to make - panels and sections were being pulled off the incomplete structure into the anomaly and as an engineer it was quite clear that the structure and those still alive aboard it were mere seconds from death … unless we did something. Accordingly we headed on a parabolic course initially towards the centre of the anomaly with our path taking us close to the StarBase - any movement towards the anomaly, even at 89 degrees to it, will mean that the gravity well works in our favour by adding gravitation energy to the output of our own engines and allowing us to build up more speed than we would be able to do under our own power. We will be safe providing we stay within the limitations of our structural integrity fields and shield capacities, and of course – and most importantly - we should be safe until we reach the ‘effective event horizon’ of the black hole as it relates to our ship. This event horizon, the point beyond which there will be nothing we can do to escape, varies depending upon our engine status, the load we will be carrying or tractoring, and the effect of material entering the anomaly and the way it distorts the space time continuum. Several of these are variable and not under our control so of course we won’t be going anywhere near that point. However it will enable us to tractor additional vessels to safety and allow us to lock onto the StarBase Command module and maybe, just maybe, pull her to safety along with all those residing within. Although we cannot save everyone, we will do our best to save as many as we can.

Log ends/..

Stardate 20505.09

Stardate 20505.09 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #04 - events up to 9 May 2005]

Early results were good; smaller shuttles were helped to escape the anomaly. As the main tractor projectors locked onto the huge construction, we could physically feel the shudder running through the Dauntless as the ship struggled to pull the structure against the gravitation pull of the black hole. Fleeting radiation alarms sounded whilst shield harmonics re-synchronised with the widely fluctuating radiation fields of the hole; high density particle and electromagnetic fields almost competing with the immense gamma strength. However, whether as a result of a random fluctuation in the relative gravity of the area or due to an over-taxed component, the tractors failed. Released of the increasing burden of the StarBase as it approached the anomaly we were accelerated well beyond the safe sub-light relativistic limit and with all the stresses the ship was experienced suffered some damage in the process until compensated by the deck artificial gravity feedback systems. Estimating that the StarBase would enter the anomaly event horizon in 25.7 seconds, and that based on previous observations the anomaly would expand very rapidly, it was clear we needed to depart the area with those we had saved. Reinforcing the structural integrity field generators we carried out a microwarp jump of five seconds

We watched as the StarBase appeared to be strangely twisted and folded apart at the event horizon and then suddenly the ship made its micro-jump, obscuring our view of the final event. We calculated the micro-warp jump to last long enough to deposit the ship safely distant from the enlarged black hole, whilst not pushing ourr luck regarding the stresses the ship would experience attempting such a jump in a highly fluctuating local gravitational field. In the final analysis it didn’t seem to matter. As the ship dropped back to real space we appeared to be hit by a massive shock wave emanating from the grossly enlarged black hole; a shock wave that must have matched or slightly exceeded our warp jump. There was no time for a warning. Easily overwhelming our inertial dampers the ship was brutally shoved to one side, the ship spinning out of control as the thrustors tried to compensate, further adding to the stresses on the hull superstructure. With the engineering damage control schematic showing hull fabrication joint sensors registering stresses above their alarm settings, and wide spread power failures occurring as power tapping relays isolated unstable EPS conduits we would have our work cut out to get back to working order. In addition both warp cores tripped out and the main power conduit plasma flows fluctuated but fortunately the fusion generators remained onload, stabilising the power situation and ensuring shield generators remained functional, thereby preventing extremely unpleasant radiation doses being accumulated.

Reports are now coming in from various parts of the ship.

There were no other ships detected in the region, and nothing on any of the COMM channels—not even the normal 'background noise' that indicated communication traffic. Put simply... • it appeared Dauntless was the only thing emitting any artificial signals within sensor range. • Sensors did reveal however that the 'anomaly' was gone, and that other than a few of the stars seeming slightly off their normal positions, all spatial objects seemed normal. • numerous reports from crew members who had been caught unawares and had suffered a variety of medical injuries, myself included to the lower abdomen area • A strange report of a little girl in ten forward who was a hologram, but who apparently stated I would be wanting her help – I have asked for more investigation into what a little girl could do ….. \i{unless it is annie for some reason half the quadrant from where she should be} • A short distance away was the Hromi Cluster, and the other stars which were nearby seemed to be there. Further details were unavailable, as none of the Star Fleet subspace relay and sensor stations within range were detected.

Although the information from the sensors and comms were not what we would have expected, they were explainable. It was theoretically possible that the appearance and resolution of the anomaly could have done some short term damage to the local fabric of space such that systems didn’t work as intended.

However our priority is repairing this ship. In the meantime we can wonder about this anomaly – a natural occurrence or a new weapon? Either way with its immense power we need to obtain some answers …. And quickly

Log ends/..

Stardate 20505.29

Stardate 20505.29 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #05 - events up to 29 May 2005]

Sufficient repairs to get us underway towards the Hromi cluster were completed fairly quickly and we started towards our destination at Warp 9, continuing with the other repairs enroute.

An anomaly regarding the aft hull macroscopic structure had been unearthed by Engineering and CCPO Kryteski attempted to compensate to a great extent by thermally annealing the hull using the ablative armour as a reflective jacket to raise temperatures using ships hull systems. Results are encouraging, though the reasons behind the anomaly are unknown at this stage. Science section are investigating.

Major Ryan has completed his investigation into the altercation between himself and a marine in 10Forward during the party at StarBase 353.

Medical reports that apart from a few isolated cases, most crew & SB353 survivors are medically cured, though psychologically it may take some more time for several persons.

Tactical and Comms remain concerned (as do I) about lack of federation comm traffic, federation beacons, and the slight misplacement of local star patterns. Once we arrive at Hromi we will undertake a re-calibration (& re-alignment if appropriate) of our comms and sensor systems. Engineering report they can find nothing wrong with relevant ships systems at present, but are still investigating

Log Ends/..

Supplemental

Supplemental:-

Bridge has detected the distress signal from our missing medical freighter. We are closing to investigate.

Stardate 20506.06

Stardate 20506.06 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #06 - events up to 6 June 2005]

Enroute towards the signal's point of origin the sensors picked up signs of a strange anomaly field, tears in the fabric of space were forming, and then disappearing. It was a virtual minefield of spatial anomalies. Readings were difficult to get, due to the transient nature of the anomalies. What was clear is that it would take days to traverse around this field, time any survivors might not have – we would have to try and go through.

Each anomaly was perfectly hexagonal, 36 meters to a side. They would 'grow' out of a central point over a period of .223 seconds, remain there as some sort of 'hole' in space-time for exactly 7.62 seconds and then fade back down into that point. They appeared to appear and disappear as 'waves' across the region. The "field" of them appeared to be nearly a light year across, although due to their nature exact sensor readings were difficult to obtain. The readings on the anomalies indicated that they were emitting a high amount of tachyons but sensors looked 'through' them as though looking through some sort of 'window'. There appeared to be something beyond but no wreckage could be detected leaving the exact whereabouts of the Alba Varden unknown; however the distress signal was coming from the edge of the Gamma Hromi star system, just at the edge of the Hromi Cluster—on the opposite side of this 'field' of anomalies.

Use of our active sensors appears to trigger a reaction from the anomalies, causing a series of small space-time fissures to open within the field. Our need to pass through the field without use of the ship’s active sensors meant that we had to explore other means to determine our safest course. The FO tried launching 2 probes to chart a potential course, but remote navigation of them proved too difficult - they travelled 'over' the field, taking various readings but then the first probe went a bit too close to one of the anomalies and was instantly pulled into it, disappearing to an indeterminable place. The other registered a massive burst in trans-spatial distortion when the probe went in—but only for a brief second. The data returned by the probe indicated that it was possible to traverse this field, but each move would have to be timed perfectly, as the 'fissures' opened and closed. Whilst the computer could technically do it, there was clearly an advantage to using 'instinct' on plotting, as the computer couldn't account for anything unexpected happening.

Two shuttles ahead of the ship were launched to chart our course and apart from a few close-calls all seemed to be going very well. Sensors were operating on passives only, and shields had to be kept offline, else the energy generated would create more anomalies. The ship was about 80% of the way through when another 'ripple' or 'wave' was noticed to go through the field, this time extinguishing several of the anomalies. Then as suddenly as they had appeared almost all of the anomalies seemed to disappear leaving only a handful of them around, and dead ahead was a distress Star Fleet issue beacon. This was mysteriously still the only extraneous Star Fleet signal picked up in days and though weak was clearly coming from the Gamma Hromi star system, dead ahead; if our sensors could be trusted in this volatile area, it was coming from somewhere in the vicinity of the fourth planet of the ternary star system.

Commander K'Etana was about to recall the shuttles when a rumble went through the whole ship, as though something had shaken it. It was subtle, and didn't appear to do any damage, but accompanying it was a wave of light that seemed to momentarily emanate from every solid object aboard. And then all seemed normal again, with one exception - the distress beacon was no longer transmitting. With only our passive sensors to rely on indications are that some sort of transdimensional energy wave passed through us, high in photonic energy. The shuttles appear to be unaffected, and our systems appear to be normal, and so the recover of the shuttles proceeded.

Safe from any other discernible anomalies we are heading for Gamma Hormi 4 at full impulse. We are undertaking a full sensor survey for the missing freighter. As a precaution I have also brought the ship to yellow alert and raise shields; I don’t want to be caught out if that’s what happened to our missing ship]

Log Ends/..

Stardate 20506.19

Stardate 20506.19 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #07 - events up to 19 June 2005]

We have moved into the gamma Hromi system and have started to detect what appears to be a debris field near Gamma Hromi 4 comprising duranium and other materials spread over a wide area – whether this is our missing freighter I cannot say at this time as there doesn’t appear to be sufficient debris mass. On our comm channels all we hear is static.

The static is somewhat of a mystery. Its characteristics appear to be similar to that detected once before, over 30 years ago, in the Devron system when (then) Captain Picard reported an anti-time anomaly threatening history. Only limited details are available from our database as we can’t get a link to Star Fleet central data network, ut from what we know the anomaly was only overcome by use of anti-tachyon beams in 3 time zones. Whether our static is associated with the same thing is unknown, but it is believed to be emanating from the 7th plant. We then also discovered a chronoton-composed beam from Hromi 7 that intersects Hromi 4 where the debris field ends.

Staying clear of the beam we continue our approach. Another strange effect has been detected - it appears that everything that beam hits on the Hromi 4 surface changes. According to our readings it's as though it's renewing the planet in some way. For instance, it just passed over what appeared to be a forest which had burnt several years ago. Now there is a thriving swamp in that very location. Further analysis shows last areas of Hromi 4 must have been touched by the beam and that the beam focus slowly looses cohesion as it travels. As Dauntless made another orbit around the world, course had to be corrected slightly as the chronoton beam changed angle and started pointing off into space; analysis indicates that in 21 minutes it will intersect over 20% of the stars diameter.

Additional information was obtained by another probe until it intersected the beam and disappeared completely. Almost coincidentally a alarm was received on the bridge indicating all our torpedo stock was missing – physical stock taking has confirmed this event.

We have continued to manoeuvre towards the area the missing freighter was last known to be. Full sensor sweeps have been conducted, and there was no sign of the ship or any wreckage.

We are now heading towards Hromi 7 to see what we can find there. LCdr Wong as Second Officer has taken over the comm whilst Cdr K’Etana sorts out a problem in security. Apparently Lt Darkfang and a few others have been involved in an altercation that needs resolving personally.

Log ends/..

Stardate 20507.01

Stardate 20507.01 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #08 - events up to 1 July 2005]

As we entered orbit above the planet Gamma Hromi 7 and neared the source point of the interference, sensors identified debris consistent with a small starship, however through the interference in the atmosphere it was hard to make out anything further. There was a massive electrical storm in the area and sensors just couldn't seem to penetrate it.

A check of the previous few days logs has revealed that there are discrepancies – items of equipment have been going missing – not one or two items but complete types and stores worth. In addition our CEO reports that she believes we have experienced some sort of temporal shift most likely caused by the chronoton beam.

Diverting power to the sensors, applying several innovation sensor calibrations and taking the ship into a lower orbit has revealed that there is a power source down there, and it was where the chronoton beam seemed to be emanating from. The source itself seemed to be generating enough power to power a small starship. In addition the mass readings indicated what appeared to be a small starship—probably of the scout class, although smaller than a Federation scout. Armament information was unavailable, as was the exact status of the ship, but the rough image of the hull showed a shape which was unfamiliar—something totally alien. It was impossible to tell anything more detailed without penetrating the storm.

We have returned to standard orbit. Following advice that it was inadvisable to trust the transporters we will be sending an away team to the surface in shuttles. Although withdrawal from the area to make contact with Star Fleet command has crossed my mind, I feel sure that our comms blackout, missing stores and apparent temporal shift is all associated with the crashed vessel. And if that’s where the answers lay, then that is where we will have to go.

Log ends/..

Stardate 20507.17

Stardate 20507.17 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #09 - events up to 17 July 2005]

Computer records

Discrepancies are continuing to be discovered between our memories and computer records. The latest point in question concerns the marines. Major Ryan has come to me to announce that he believed that the ship’s complement of marines used to number 3 companies … almost 300 men, yet now he has found out that there are only 14 including officers. In addition they are only armed with handheld phasers, yet he claims that we used to carry heavy weaponry, including ground based I must admit that my recollection was that we had a large marine contingent and we had weaponry matching his description yet the ships logs [even my own] do not tally with my memory. The more I try to think about it, the more difficult I am finding it to reconcile the difference, if such a difference even exists.

In a previous log entry a few days ago I vaguely remember reporting that there was a discrepancy between our torpedo computer stock and our actual stock. I can remember the conversations at the time yet there is no mention of this in the logs as they stand now. Ditto with the belief that we were a fully armed battle cruiser – we are logged as a search & rescue ship which in times of war could quite readily be staffed up to perform that duty.

What would really trouble me is if this was just an isolated incident but there is a general consensus that things are progressing as they should be …. that there is nothing wrong. Different people have slightly different memories but that is what always happens. In the absence of evidence to the contrary I can only assume that things are as they should be.

Replicator Malfunction – no water shortage here

There are apparently problems with our replicators. As well as my own ready room one dumping litres of water onto the floor, we have apparently had to jettison a cargo bay full of water (approximating 100,000 litres) into space presumably created from our industrial sized replicators, and we have just flooded the bridge floor when someone opened the doors to the observation room. Remedial measures are in place and engineering are investigating.

Away Team

The shuttles taking our away team to the planets surface has now departed. Though a mission which is particularly hazardous, it is one nonetheless that we must attempt in order to bring some sanity to what we are observing. Along with Cdr K’Etana, we have dispatched Lieutenant’s Auroris and Thomas, Major Ryan, Lieutenant Commander Dega and Ensign Kerithrion and Midshipman Alexandre, both newly arrived in science but based on their specialities ideal members of the team. For medical Lt Talis has accompanied the team, as LCdr Wong is currently commanding the bridge, gaining valuable information and skills during this mission that he needs for future progression.

Just after the shuttle left for the planet we lost her on sensors and all communications as soon as she broke through the upper atmosphere and entered a region of high levels of electrical interference. Though it wasn’t unexpected, if they run into any trouble we won’t be able to help them, or even know of their status. Our best guess on the cause is some high ionisation levels in the region of the atmosphere she passed through, and so we are going to try something – using the deflector dish and neutralise the area of high ionisation concentration. We reconfigured the systems and have just made contact – I am awaiting a status report from Cdr K’Etana at the moment.

log ends /..

Supplmental

Personnel log – Supplemental

Recently I have been experiencing pain in my lower abdomen. Though initially suspected to be a muscle sprain, my recent biosigns have indicated an increased heart and respiratory rate, and coupled with my recent use of pain medications sent up a red flag in the medical monitoring system, alerting the doctor. He has now informed me that I have an infection in the area of the prostate gland and whilst this could explain the pain, there is also an abnormal growth of tissue in the area that does not appear at this time to be particularly dangerous. I think he referred to it as BPH: Benign Prostatic Hypertrophy, the relatively harmless enlargement of the gland. As long as the infection responds to treatment the process may reverse itself spontaneously… sometimes the growth can be permanent, so long as it causes no discomfort or physiological problems with certain bodily functions, it's something to watch. We will be investigating further in the near future.

In the meantime he has given me a portable enhanced medical scanner which has also been programmed to dampen pain impulses. It has lessened to a certain extent the discomfort significantly and allows him to discreetly monitor the abnormal tissue from sickbay.

log ends /…

Stardate 20507.31

Stardate 20507.31 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #10 - events up to 31 July 2005]

Water, water, everywhere!!

Investigations by Commander Wong and the Engineering department appear to have determined that a recent change to the replicator molecular bonding subroutines approximately 63 hours ago maybe have had the obvious side effect we are now seeing. Whether this is a crude attempt at sabotage or an inadvertent occurrence will have to wait until the backup codes are compared to the current ones. All we can do now is mop up on the three decks affected.

Away Team

Our experiment with the deflector dish to attempt to clear a comm path to the away team appears to have worked, though the storm is re-coalescing quickly.

Commander K'Etana managed to get a comms message through, informing us that Commander Dega has just been caught by some kind of temporal stasis field from the wreckage. They are trying to get her out now. We were also informed that there is no Tetra radiation whatsoever in the surrounding atmosphere. According to the away team science officers this means the place is full of chronoton particles.

After ascertaining that there was a good probability that another deflector dish process might give us transporter facility I agreed with the FO to send down further away team members including Ried, Vol, Sexton, Rogue, Wong and Hendil. We would be bringing Auroris back to the ship in exchange. With that number of away team members, the large shuttle they have will suffice to get them all back, and as hendil is our best shuttle pilot it makes sense to exchange him for auroris.

Following the deflector dish process, things were indeed satisfactory for transportation. However it would appear that there has been an unexpected side effects. The transport went as planned though a lot slower than expected, and now explosions are rocking the Dauntless due to major power overloads originating at Transporter Room one.

Further details in my next log entry

/log ends…..

Stardate 20508.31

Stardate 20508.31 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #14 - events up to 31 August 2005]

[Recorded in the split-second before a huge explosion decimated the ship and everything within 10,000 kilometers, including a piece of the upper atmosphere of the planet Gamma Hromi IV.]

Voice of Commodore Thrawn:

“Explosions are working their way throughout the ship and towards the Bridge, no doubt killing my crew from either shock, asphyxiation as the hull breaches, or from trauma as the structures fail. We have made attempts to jettison both the primary and secondary warp cores which were exhibiting massive pressure increases within the pressure vessel but the attempt has failed, as has venting the cores.

We are breaking up ….. the end is close. What has caused this is not …………………”

The Dauntless started to break up into pieces, every weld failing simultaneously, and the chronoton beam from the planet then intersected the doomed starship just as every containment field on the antimatter bottles failed. As the warp core breach began, and matter/antimatter fuel explosions started, the ship disappeared. Viewed from space a huge explosion surrounded the Dauntless and it winked out of existence, to leave behind only an ever expanding highly energetic cloud of supercharged particles and stellar gases.

Stardate 20509.18

Stardate 20509.18 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #15 - events up to 18 September 2005]

As I think back the first thing I and the rest of the crew remember, without any warning, was feeling a shaking sensation and a dull pain throughout our bodies. There was no apparent reason as to what caused the problem. Ordering the ship to come to a complete halt with the shields raised, we undertook a detailed short range scan. There were no indications of a shock front in the vicinity that could have caused the disturbances we had just felt, but we were surprised when it was reported that we could detect the apparent destruction of Star Base 343 a little over three days travel away, a fact verified by the ship's log as well as various other anomalies. We have also discovered that 10 members of the ship's crew were apparently missing including the First officer, Marco, Chief Medical Officer, chief engineer, chief of security officer, and various other ranks.

With no recollection that the destruction of Star Base 343 had been previously reported, and no explanation of the reasons for the disappearance of almost my entire senior staff, I have ordered the ship to general quarters 4 status, whilst we searched the ship and the records. We then discovered that the missing crew members formed part of an away team transported down to a planet Gamma Hromi IV just a few minutes earlier. The only problem being that this planet was five days' travel [over 40 lightyears from the Hromi Cluster] beyond the position of the destroyed Star Base 343, a total of eight days at warp 9.5

Fortunately with the Klingon border quiet at this time and after conferring with the local Sector Commander, Commodore Owen on Star Base 157, I have ordered the Dauntless to turn about and make best possible speed to StarBase 343’s last position.

On arrival at SB343 we were hailed by an automated system and which we ignored, instead invoking Garellian Protocol 3 – making this vessel silent, no communications in or out. We also raised the sensor cloak and powered down all active sensors and navigational systems.

Sensors offered no evidence of a recent explosion or other untoward events. On a hunch I have had a hardcopy of the destruction record made and in reviewing the report a startling fact has emerged – we have discovered that the original report had been lodged by the Dauntless six hours into the future. The reports security signature confirms the report, albeit in the reality outside the hull not yet written, is in fact genuine.

We have positioned the Dauntless on the far side of the Base, effectively putting us in the blind spot from where the future Dauntless will drop out of warp in a little over one hours time. And then, in a little under 6 hours time, the StarBase we can now see will be destroyed along with hundreds of federation personnel and several ships when a black hole type anomaly will suddenly appear out of nowhere. The report shows that the ‘future’ Dauntless will attempt to save as many ships and lives as possible and yet we will loose the StarBase. The report also describes the presence of chronoton particles, the host of the time quanta. This latter point is the reason for my concern as it means in all probability we are facing an effect and causal time event, i.e. the effect predated the cause. Now the dilemna – interfere and possibly effect the future by attempting to save lives and the Base by aiding the future Dauntless if the anomaly does materialise or whether to not interfere. There is no question in my mind that this ship will do everything we can to help without making our presence known to the StarBase or the other dauntless – that would cause too many questions.

I am currently exploring options using the report, the attached data and our holographic display. Somehow there must be an acceptable way out from this conundrum.

Log ends./

Stardate 20510.07

Stardate 20510.07 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #17 - events up to 7 October 2005]

Official Log The Dauntless had just arrived from a tour of the Klingon Border, following the discovery of 10 missing crewmembers who had just transported down to a planet 5 days away at warp 9; presumably the result of a strange but understandable time paradox which annoyingly does occur from time to time.

We are commencing crew transfers and stores replenishment before heading off to Hromi to search for a lost federation ship and our missing crewmembers.

I have just discussed with the CO of the StarBase a delay to a test of the new Prototype gravitational sensor/emitter until a science vessel can be despatched to investigate the surrounding region of space. Although there is no definitive proof, I am convinced that the Base could be at great risk – where this belief originates is somewhat of a mystery and yet I feel sure I have come across a similar region of space before. The CO has concurred and the test has been delayed.

Departure is in one hour.

Official Log ends

Stardate 20510.07 [Addendum Ultra Secret] USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #17A - events up to 7 October 2005]

Classified Ultra Secret = Eyes only – Fleet Comm 1; COSFEC; o/c SFSI;

Addendum to Official Log 20510.07

Whilst the aforementioned log is an accurate log as far as the current knowledge of the crew is concerned, I have in my possession several hardcopy logs from the Dauntless and the StarBase that I appear to have ordered created in a different timeline leading up the our current situation, and for which I have no knowledge of requesting. This is the source of the information that led to the test delay. If anyone can determine the ‘’actual’’ timeline I would appreciate it. Details are as follows:

Apparently we had information that in timeline approximately 1 hours ahead of our own, the ‘future’ dauntless would be positioned at the StarBase taking on crew and supplies. We had positioned our Dauntless on the far side of the Base, effectively putting us in the blind spot from where the future Dauntless would drop out of warp in a little over one hours time. And then, in a little under 6 hours time, the StarBase would be destroyed along with hundreds of federation personnel and several ships when a black hole type anomaly would suddenly appear out of nowhere. The hardcopy reports show that the ‘future’ Dauntless will attempt to save as many ships and lives as possible and yet we will loose the StarBase. The report also describes the presence of chronoton particles, the host of the time quanta. This latter point means in all probability we are facing an effect and causal time event, i.e. the effect predated the cause. Now the dilemma – interfere and possibly effect the future by attempting to save lives and the Base by aiding the future Dauntless if the anomaly does materialise or whether to not interfere.

The future Dauntless duly arrived but its approach velocity and the positioning of the anomaly were not as expected. Analysis showed that a large density field gradient centred on our Dauntless was interacting with the gravitational well formed by the StarBase, and where they intersected corresponded to the new position of the anomaly. The timeline was being altered by our presence and this was apparently confirmed as the computer copy (now non-existent) of our hardcopy was being rewritten in our database. In an attempt to relocate the anomaly away from the StarBase our Dauntless changed course.

Unfortunately it would appear that the Base had detected the anomaly and our Dauntless (travelling under sensor cloak), using its new gravimetric detector/projector system designed to detect cloaked ships at system distances. The ‘future’ Dauntless changed course to intercept and in an attempt to avoid the two ships meeting, for fear of the consequences of time-interaction, our dauntless send a unique code word to the future Dauntless. Both ships slowed to rendezvous but following a rapid shift of the anomaly due to the approaching mass shadow of the future Dauntless, both ships and the StarBase lost power, and the ships were by then travelling on a collision course desperately trying every means to abandon ship.

The two saucers met, one of them catching the other just under the rim and forcing itself into the body of the other saucer, hull plates, structural stanchions and crewmembers being flung out into space. People on the StarBase would have watched as one saucer buried itself into the other, causing the hull skins to ripple and break apart, killing the collective 4000 crew. Whilst this was happening the two main engineering hulls were dancing a strange ballet together, their respective nacelles interlocking and causing the hulls to violently change spin and direction, and causing them to smash into the underbelly of the saucers. The lower saucer broke apart clearly showing the deck plates within and what looked like sand grains flowed from the gash only to quickly change direction into the black hole.

There was a massive explosion from one and then the other hull as the antimatter systems, weaponry and super hot systems literally atomised the area, consuming all matter in an ever larger inferno of energy. The saucers and hulls were consumed in the hellish fire and the boundary of the explosion front expanded, enveloping the lifepods, crew in EVA suits, fighters and everything local, the energy and materials then being sucked into the distorting black hole anomaly. The StarBase then suddenly lurched, its own hull plates, bulkheads and support girders flexing in the widely changing gravitational field, taking on impossible shapes and angles. Windows shattered, compartments ruptured, decks were ripped off, sending the crew members unluckily enough to be present into the vacuum of space, and to be eaten by the black hole. Then the stress became too much for the Bases’ shutdown but still pressurised warp core and a rupture formed on the main reaction vessel. The resulting explosion of pressure and energy ripped through the engineering decks, antimatter stores and crews quarters, eating up the Base from within, feeding on the atmosphere and causing a catastrophic explosion that ripped the Base apart.

All that was left was a massive debris field of materials and bodies in a huge gaseous bubbling cloud of energy, with a smokey strand being pulled into the black hole. They were all gone ….. all dead … the black hole anomaly had won again.

And then … impossibly …. we found ourselves as we are now ….. on yet another timeline but this time with one StarBase, one Dauntless and just our mission plans.

Addendum Log Ends….

Stardate 20510.13

Stardate 20510.13 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #18 - events up to 13 October 2005]

Following the completion of crew transfers and stores replenishment, we have departed StarBase 343. As the ship jumped to warp speed, there was a fluctuation in power flow to the M/A containment control subsystem. Although appearing minor, until it was repaired maximum achievable warp would be warp 4. Repairs would take a few hours so even doing that would still save us 32 days travel.

After putting Engineering to work, our comms officer detected a Star Fleet Distress Beacon which appears to be coming from one of our own shuttlecraft originating from orbit of Gamma Hromi IV, sir. Unfortunately that wasn’t all... we were also detecting wreckage in orbit but couldn’t determine anything further from this distance.

Once repairs were completed we restarted our journey at maximum warp.

Log ends./

Stardate 20510.27

Stardate 20510.27 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #19 - events up to 27 October 2005]

As the Dauntless drew closer to Hromi IV, our scans began to get more detailed [though still impaired] results. Heavy ionisation in the planet's atmosphere was creating a massive handicap to the sensors, and there was little chance of sending communications or transporters through it. Scans were able to locate the missing crewmembers, in a built up area surrounded by hundreds of thousands of alien lifeforms. In the same area, varying sizes of energy bursts were erupting at random intervals. There was also a lot of other activity that suggested the energy bursts were being directed. Other than this, there was little else the sensors could pick up.

In order to make contact with the Away Team I dispatched our duty security chief in a shuttle down to the surface.

Analysis of the distress buoy has commenced to attempt to determine anything such as how long it has been sounding, would the away team know it was operational etc.. Additionally in conjunction with our communications section we have started checking the whole communications suite of frequencies and modulation – anything that might penetrate the disturbance.

After welcoming one of our new crew members to the bridge staff – Midshipman Daque –[following not part of log but reproduced for information ….and receiving some updated Ship Intelligence concerning events on our last mission ] additional scan results were obtained.

The orbital beacon had apparently been out there for about a day, and was registered to one of Dauntless' very own shuttles. It was a standard distress beacon.

Scans indicated that the Dauntless was in orbit of a Class K world, with a very inhospitable atmosphere. Some type of severe electrical storms were covering most of the surface, with the result that between them and certain elements in the atmosphere, scans of the surface were all but impossible. The space surrounding the world and Dauntless were part of the Hromi Cluster, a grouping of four stars and dense nebula gasses. The scans then detected something more startling - the planet was undergoing amazing and rapid environmental changes right in front of us. The cities and the wildlife were all disappearing, and the air composition was changing from oxygen to carbon dioxide. Indications were also received that would point to some kind of temporal phenomenon at work. According to these readings the entire world revert to a Class K world within minutes. Noteworthy as far as the planet was concerned is that the atmosphere and surface features appeared to be transforming before Dauntless' eyes. What was once a Class M environment, with a clear atmosphere, cities, and a thriving ecosystem had, in the past few minutes transformed into what was now a world that was inhospitable and uninhabited.

And one where the surface could still not be scanned at any level of detail, so we are denied any information of the status of our Away Team and shuttles.

Log Ends …../.

Stardate 20511.15

Stardate 20511.15 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #21 - events up to 15 November 2005]

The away team have arrived safely back onboard, and not a moment too soon. The environmental catastrophe that has somehow struck the planet is complete - what was once a Class M environment, with a clear atmosphere, cities, and a thriving ecosystem had, in the past few minutes transformed into what was now a world that was inhospitable and uninhabited.

After conducting a local sensor scan there is no sign whatsoever of any Star Fleet distress beacon from the missing freighter, and longer range scans have no identified no hint of debris from the ship or cargo. Given what has happened here and at the StarBase 343 I have taken the decision to return home. There is every probability given the time effects we have experienced that the freighter will never be found, and I believe that there is a clear and present danger to the Dauntless staying here. It would be better for a science research vessel to stop off here after completing their work at SB343 to try and understand what has happened. As a result we are currently heading home to SBA.

I have called the Away Team together for a debriefing to try and understand what happened to both parties – the team and the ship. It was also an opportunity to hear from those for which this was their first time on an away mission. It was clear from what was said that there are still major gaps in our understanding and we may well have to leave it to the Temporal Experts to stitch the story together. It is also clear from what was said that several of the new officers suffered personality or responsibility clashes and so we’ll arrange some team building sessions, starting with Away Team Medical Basics which appears to be a root cause of one disagreement.

Apart from that, the only things of note were an intermittent fault in the replicator material database that causes carrots to be produced every time someone asks for something, much to the amusement of the officers who as you can imagine allowed their intellect to take second place to their humour.

And the final piece de la resistance was a faulty operation in Engineering that caused the ship wide fire suppression system to suddenly activate and coat everyone and everything in a fine blue powder. It didn’t make things better when just at that moment a comms message came through from the SB343 commander about a package awaiting us there. We have therefore diverted course slightly to collect it.

The meeting has just broken up, and everyone is now heading off to clean themselves up.

Log Ends …../.

Stardate 20511.30

Stardate 20511.30 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #22 - events up to 30 November 2005]

[Caution : Some of this information has only recently become available and may not have been known at the time]

First the good news.

Commander Rylus has been released from medical stasis and is starting to recover from what was her life threatening illness. Medical staff are somewhat confused as to the recovery and are investigating whilst making the patient comfortable. As of yet she doesn’t know she has been replaced as First Officer by Commander K’Etana.

Commander Dega is currently with security detailing the results of her investigation into some sabotage aboard the Dauntless relating to a previous mission where some vital debris recovered from a Klingon ship was transported through our shields onto a renegade Klingon battle ship. The evidence left behind implicated Cdr Dega as the traitor. Discussions are continuing.

Now the bad news.

During an exercise involving the medical section and a simulated mass casualty drill that resulted in the sickbay becoming unattended, Dr Wong was conducting an exam of a crewmember when he was viscously attacked and left for dead. The assailant (now know later as an alien personality [Shaava] controlling the body of Lt. Halycon) used his security knowledge to falsify the security logs to implicate an innocent Klingon security ensign who had previously been seen by Dr Wong. Fortunately the FO discovered Dr Wong fairly quickly and managed to alert the exercising medical crew, and the full resources of the medical staff are now in use to try and stabilise Dr Wong’s serious condition.

Hidden to some extent by the his injuries, unbeknown to us Dr Wong’s subconscious has somehow communicated with his guardian spirit in the subconscious plane of existence in the form of Dauntless ex-security chief Telsia Shikozu, and they are discussing various subjects …. probably including the weather in Dreamland.

Log ends/..

Stardate 20512.15

Stardate 20512.15 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #23 - events up to 15 December 2005]

[Caution : Some of this information has only recently become available and may not have been known at the time]

First the good news.

Commander Rylus has continued to make a good recovery and although confined to her sick bed, is regaining full use of her faculties. Any contributions of oranges or grapes greatly received.

Commander Dega is continuing to help security with their enquires (as they say in quaint English towns and cities).

Now the strange (and somewhat disturbing) news.

The FO & Security staff have arrested the assumed perpetrator of the attack on Dr Wong, a Klingon Security Ensign D’Targh D’Shar, whilst he was taking a bubble bath. I have impressed upon those concerned to fully corroborate the evidence as something doesn’t sound right - it is totally out of character for a Klingon to remain where he can be captured after such an attack, and although I am a firm believer in allowing people to do whatever they want in the privacy of their own cabin I have to say that a Klingon taking a bubble bath does stretch that policy a long way (LOL)

Now the very strange news.

LCdr Hendil has apprehended what can only be described as “a wee man”, a sentient being presumably from Gamma Hromi IV who must have decided to undertake some exploration of our ship. It apparently roams the ship leaving no sign except for a faint chocolate odour and occasionally (if we are very lucky !!) sometimes even a chocolate deposit …. Which was unfortunate for LCdr Hendil who got splattered when he caught the wee beastie. Unfortunately the visitor who is believed harmless managed to escape and is somewhere now in the depths of the ship somewhere. We are trying to find it but as our internal sensors appear unable to find him it may take some time!!!.

Now the bad news.

Engineering officer Ried has sustained a nasty eye injury whilst undertaking some maintenance work. After some skilful eye surgery he is now recovering in sickbay.

Dr Wong has undergone the first of many surgical procedures to try and stabilise his condition. Indications are still erratic as to whether he will be saved but I know the medical staff are giving it their top priority. Unbeknown to us in the world of his subconscious Dr Wong and Telsia Shikozu are still conversing about their life pathways and recapping on past events. Although it is probably contributing to the erratic bio-signs, at least it is keeping him alive.

Finally the carnage apparently continues unabated. Shaava/Halycon had joined Major Sexton in 10F and after a few drinks went back to his quarters**, where Shaava then attacked Sexton with a knife. He then left the dying Major and reported for duty. Once there, in discussions with LCdr Thomas in his office he proceeded to catch him unawares and attacked the security chief.

• • [disclaimer: in order to pre-empt representations from the lawyers of Sexton and Halycon I am honoured to state for the record that this was just a coincidence as their quarters were on the same deck.

Log ends/..

Stardate 20512.31

Stardate 20512.31 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #24 - events up to 31 December 2005]

[Caution : Some of this information has only recently become available and may not have been known at the time]

First the good news.

The Security section have indicated that they are satisfied that Cdr Dega did not have anything to do with the sabotage on the Dauntless during our last mission, and that she was being framed by a crewman Jacques who left the ship shortly after the problems. Whilst Star Fleet security will be following up the case I can’t help thinking that he will have long since disappeared.

Dr Wongs condition has been stabilised and he will be transferred to StarBase Hospital upon our arrival; prognosis is satisfactory but it is early days.

Now the bad news

Following enquiries by Major Ryan about the location of Major Sexton, the computer detected that Sexton was unconscious, severe haemorrhaging and chest injuries. He was promptly transported to sickbay and attempts started to stabilise him.

LCdr Thomas’s body has been discovered laying in a pool of his own blood in his office within the security section. The FO and security are organising a search for Shaava[Halycon] and whom is now the prime suspect behind all the recent attacks. The fact that at the time of the latest attack the arrested Klingon was being held in the brig supports his claims of innocence and he has been released back into the protective surroundings of his scented bubble bath.

After leaving Thomas, Shaava made his way up to deck 3 where the senior officers have their apartments. Whilst I was entering my quarters I was rugby tackled into the room and attacked. Although fighting back it was clear that in the true sense of the word Halycon was acting as if possessed. As the assassin removed a large knife and gloated over the fact of his evil deeds, a strange expression come over the officer. A look of puzzlement …. almost bewilderment … the ferocity in his eyes had suddenly gone .. and then he thrust the knife into his own stomach. Unable to move all I could do was stare at the him and then he stammered “Lieutenant…Junior Grade…Nathan Halycon reporting in sir…” before started to slowly fall to the floor in front of him. “Sorry for being so…late. It appears that the mission…has stayed with me…and left me with a powerful foe. I’m…sorry…”. Smiling one last time he fell to his knees, pulling free the bloody knife and collapsed on the floor unmoving, a stream of blood emanating from under his body..

At that moment Yeoman Rand entered the room and summoned security and the medical personnel. Halycon was transported to sickbay for emergency surgery. Halycon will also be transferred along with the rest of our wounded to StarBase Hospital upon our arrival.

Giving Halycon the benefit of any doubt, I can only guess that whatever possessed Halycon and made him carry out the attacks was finally defeated by Halycon’s own life force. Hopefully when we get to StarBase, someone will be able to unravel what actually happened.

Log ends /…

Supplemental

[Supplemental Log

Dauntless has now docked at StarBase Alpha. Our wounded have all been transferred to the Base Hospital for specialist treatment and we can only hope they all recover. Shore leave has been granted to the crew.

Log ends/….]

Stardate 20601.21

Stardate 20601.24 USS Dauntless Ships Log, Commodore Thrawn commanding. [Hromi Cluster mission – Log #25 - events up to 24 January 2006]

I must have been mad.

The short period of shore leave has turned out to be most memorable for the Dauntless senior officers, for all the wrong reasons.

From what I can ascertain it started in the StarBase ‘Drunken Tribble’, where Cdr K’Etana and several officers were eating. SBA Security decided to temporarily close the place due to the drunken behaviour of some of its patrons, not a wise think to do with Fleet officers in there after a long mission away. Due to a clash of personalities between the SBA Security Ensign and K’Etana, the sober but obviously annoyed FO ends up in the Brig along with several others.

Whilst they are cooling their heels, Cdr Wong was released from SBA Sickbay after his near death experience and in a somewhat confused state carries out a jail break single handed. K’Etana and Wong then proceed to a promenade café where they partake on some beverages, whereupon they are spotted by SBA security and other Dauntless officers. The reportably heavy handed re-arrest of the two then prompted a fracas between security and dauntless officers, which resulted in a significant number of my senior officers all being locked up.

Thankfully combined the good patience and pragmatism of the SBA security chief Cdr Grant, myself and the Cdr managed to unravel the sequence of events. Accepting that there are faults on all sides and no real damage was done, the officers were released into my custody for punishment.

Mission Log Hkomi Ends/…]

Stardate 20603.17

Stardate 20603.17 USS Dauntless Ships Log, Commodore Thrawn commanding. [follows Hromi Cluster mission – Log #26 – 3 March 2006]

This is my last log entry for the Dauntless, a ship I can truly call my own. After taking command of her shortly after the outbreak of the Romulan War, we have been in many battles and missions since that date and we, myself and the entire crew have done her proud in our exploits.

Fighting the war took a tremendous amount of courage and hard work for everyone, but this was surpassed by the last battle – the arrival of the Borg, the search for allies in fluidic space, and the eventual return to Earth with our new allies, and the remnants of the Federation and adjoining empires to defeat and eradicate the Borg once and for all from our galaxy (as far as we know). In the upheaval that followed when the Federation started to fragment at the edges, we visited our once far flung allies and confirmed our support for them, whether they remained with the UFOP or as important trading partners. We also had our share of policing and exploration missions, one of most importance to me was the time in conjunction with elements of the 1st Fleet when we liberated a planet conquered by an Orion Pirate Clan and returned her to her rightful owners.

And now we close a chapter headed the Dauntless and open a new one, one I did not expect and one I am very proud to undertake.

In the presence of a very distinguished company of my friends and colleagues including Ambassador Picard (Retired) and Admiral Riker (Retired), former COs of previous incarnations of this ships namesake, I was formally handed command of the Federation’s newest Heavy Carrier USS Enterprise CV-07 by Admiral Nekitaroma COSFEC.

Now, one more the name Enterprise is associated with an active Federation Starship to continue the missions of all ships of that name. And she’s mine.

Log Ends //

Cdr K'Etana

Stardate 20508.02

Stardate 20508.02 USS Dauntless Away Team Log, Commander K'Etana commanding. [Hromi Cluster mission – Log #11 - events up to 2 August 2005]

Having conferred with the CO a number of away team reinforcements arrived who seemed very confused and in pain after the beam-in.

Meanwhile I was having a conversation of sorts with the MarCO (the contents of which I will have to discus with the Commodore) and the atmosphere exploded around us. The storm broke, sending down acid rain which reacted with magnesium in the rocks (a fact we were only informed of as the rain started!).

Our EVA suits were being burned and ripped to shreds by the rocky shrapnel so I gave the order to find cover in the wreckage.

On the way we spotted a suit face-down in the dust, we thought it could have been Kathy Obuszewski the CEO who had been earlier caught in a stasis bubble, but we never had the chance to find out, as each member of the away team was enveloped in "bubbles" of their own.

In hindsight it might have been a bad idea to seek cover in the wreckage.

We woke up to find there was something very different and wrong..our bodies were not our own….

Stardate 20508.18

Stardate 20508.18 USS Dauntless Away Team Log, Commander K'Etana commanding. [Hromi Cluster mission – Log #12 - events up to 18 August 2005]

The crew woke up to find themselves incarcerated in bodies of the Az'SharrAhn'Ti, an alien race. It was a strange experience. Our personalities or consciousness remained, but so too did our previous occupants memories survive, so things were..confused. The aliens we inhabited were tall, had skin that changed colour and walked around with no clothes apart from a sash around their chest. They also had four eyes, this was probably their most disorientating feature at first.

Some of us found the reality of the situation take hold - we simply acted the way our bodies’ previous occupants would have, just going about our duties and forgetting who we really were. Others did not forget whom they really were, in fact their confusion and panic led to a mutiny.

I found myself trapped in the body of Shan'Ul'Thrren the CSO. At first I was very aware of my identity but an hour or so into it I only had a vague recollection of who I really was.

The mission of this Az'SharrAhn'Ti vessel, the K'Zaarrr, commanded by Captain Naa Va’Reece, a.k.a. Commander Mike Wong, was to destroy the crystalline entity. At this point we still did not know where in time we were, if this was the crystalline entity mentioned in a previous mission of the Enterprise D or another one altogether. All we knew was our Captain would stop at nothing to destroy the entity and his crew would follow him without question.

As most crew went about their duty those affected by us found ourselves scattered all over the ship in different positions. In engineering, upon discovering that he was still Ltjg Halycon but trapped in Junior Tactical Crewmember Shaava'Edarreaf's body, Halycon went about trying to sabotage a projector generator.

Meanwhile the two religious officers, Sexton and Hendil went about their normal duties; trying to heal an injured crewmember by some serious chanting.

On the bridge, the FO, Ryan, was left in charge as the Captain and CSO, who were coincidentally mates, discussed the strange goings-on in the ready room, only to be interrupted by two armed crewmembers. They demanded to know what had happened to them and the away team.

With weapons pointed at each other the situation quickly deteriorated. A mutiny took hold. There was a firefight, the CSO and Captain were seriously injured and the two crewmembers, Reid and Vol escaped to sickbay only to be apprehended there.

Still en route to the crystalline entity the ship was in crisis; with its Captain in surgery the FO took command. And the two perpetrators waited in sickbay for their reckoning with the Captain..

/log ends…..

Stardate 20508.31

Stardate 20508.31 USS Dauntless Away Team Log, Commander K'Etana commanding. [Hromi Cluster mission – Log #13 - events up to 31 August 2005]

With Reid and Vol escorted to security Captain NaaVa'Rcece/Wong and the CSO ShanUl'Thrren/myself recovered in sickbay. Some of the crew were now fully aware that we were indeed two people trapped in the same body; I tried to investigate the reason for this - maybe we had passed through an anomaly or something - but I could find nothing. All records indicated nothing out of the ordinary had happened for weeks aboard the alien ship, and our bio signs told us we had always been this way.

Meanwhile in engineering the crew worked overtime trying to ready the ship for battle with the crystalline entity. With ten minutes to intercept they double-checked the new configuration of the weapon frequencies as suggested by TrraVa’Dece/Vol.

At the same time, minutes after being escorted to security and "interrogated" by the COS, Reid and Vol attempted a breakout with their new accomplice Lt Thomas.

/log ends…..

Stardate 20509.22

Stardate 20509.22 USS Dauntless Away Team Log, Commander K'Etana commanding. [Hromi Cluster mission – Log #16 - events up to 22 September 2005]

As things were falling apart - literally - on the Dauntless it wasn't much different on the Xandr’.

All of the injured, including myself and the Captain had been released from sickbay. Our injuries hadn't completely healed, but given a few days we would be fine. That is, apart from the Captain having to get used to a prosthetic leg device.

The next few hours of our mission would prove to be the most challenging yet.

The one thing that struck me, walking through the corridors was the sheer tension in the air. The crew went about their business without a word, their faces taught and worried.

The fact of the matter was those of us on the away team still numbered only about fourteen or so, and we were on a ship with a crew compliment of almost five hundred. For some strange reason we had managed to secure high positions for ourselves, but there were now rumours and worry spreading through the rest of the alien crew. Had they known exactly what was happening, that fourteen of their most senior staff were now experiencing dual personalities I'm certain they would have joined Vol and Reid in their earlier mutiny.

Be that as it may they didn't have much time to think about such things as minutes later we were found ourselves approaching the crystalline entity. Our mission’s first, and only, objective.

On the bridge a plan had been formulated. Drawing on previous experience from their former lives as Star Fleet officers, someone had remembered how the crystalline entity had been communicated with and ultimately destroyed. So with their weapons now modified to emit a harmonic frequency they were prepared to face the entity.

As soon as they dropped out of warp the ship went to the equivalent of red alert. The entity was several thousand kilometres away, hovering by a green populated planet.

As the Captain ordered the ship to approach, the entity suddenly dived for the planets atmosphere. In a rage Captain NaaVa'Rrece followed, full sublight speed ahead. He was now faced with a dilemma - they could not fire their weapons in the atmosphere without damaging the planet's ecology fatally. So if they fired they would very likely destroy all life on the world. And if they didn't fire, the entity would do the same.

Coming to a decision, it was truly the only one NaaVa'Rrece could make, he shouted "ramming course!". His bridge crew followed him without question.

At this moment in time I found myself stepping into the piron (turbolift) on my way to the bridge. The deck plating was shuddering; the ship was starting to feel the strain of the friction in the upper atmosphere.

On the bridge, inside the mind of Captain NaaVa'Rrece, Mike Wong’s personality broke to the surface. In a split second he ordered them to change course, going against everything Captain NaaVa'Rrece had ever thought or did over the past four months.

After a moments hesitation the helmsman complied. The ship began its course change. We were now level with the atmosphere, only needing another few degrees of an upward turn to make our escape when all consoles on the bridge blew up in rapid succession.

Nathan Halycons and Xavier Thomas's earlier handiwork (sabotage) had finally made its appearance. At the worst possible moment.

The ship tumbled through the atmosphere, with power and control lost to the bridge all they could do was watch in horror as they fell from the sky, brief glimpses of hills and rocky outcrops flickering on the viewscreen.

As we fell things started to go further downhill in engineering. The warp core, a black hole, was destabilising.

As the ship continued to fall there was a sudden rise in its altitude, a vortex of some sort was opening behind it. The vortex was caused by the engines being engaged in the atmosphere—it was set to swallow up the entity, the ship, and then the whole planet.

But PaarnaVrak, the assistant Engineer, had his timing well. Even as Gaar/Thomas watched, the vortex shifted, swallowing up the crystalline entity, and then popped out of existence. The resulting shockwave from the vortex closing levelled the nearby city, looking like the shockwave from a huge weapons explosion, and then threw the ship tumbling across the atmosphere toward a less inhabited region.

The ship skipped off the top of a mountain, creating a huge gash in its underside. They hurtled toward water.

The Xandr’ made its impact in a deep lake somewhere on the northern hemisphere.

We sank fast, water rushed through the holes now scattered over the ships hull from various explosions and damage from the vortex.

When crew came to, those that could after the impact discovered life support was offline. And so were all sensors and communications, both internal and external. Main power was down, and the main computer was offline.

The black hole warp core was destabilising. It was wobbling and expanding slightly in its chamber. Lucky for us, our chief engineer/security man Gaar/Thomas knew what to do. He conntected a high-powered phase emmitter to the../

K'Etana paused, trying to remember what Thomas had told her. She wanted to get the details right as she was sure Thrawn would want to know exactly what had happened..

/...To the core containment chamber. With the ships hull creaking and water leaking in Gaar/Thomas hurried about his work. He had the emitter ready within minutes with the help of his engineering team. Unlike the Dauntless there was no core ejection system for this ship.

Gaar/Thomas fired the beam.

It took all of the ships power to do so. There was a bright flash from inside the core, and the room filled with a blinding white light. And then everything plunged into darkness. He had succeeded.

Now all there was left to do for everyone was to escape. Easier said than done. Many of the crew were injured, and with no power whatsoever and life support gone the ship had essentially shut down. Doors weren't working, turbolifts had stopped.

Some managed to escape using the escape pods, most of those in sickbay escaped, but others were simply trapped in areas scattered around the ship. I found myself trapped in a corridor leading to the bridge that was quickly filling up with a river of cold water. As that was happening those on the bridge were searching for the bridge ejection controls...

Log ends./

Stardate 20510.31

Stardate 20510.31 USS Dauntless Away Team Log, Commander K'Etana commanding. [Hromi Cluster mission – Log #20 - events up to 31 October 2005]

We had escaped. As soon as we hit the surface of the water there was a flash of light..this noise..

And then, we were somewhere else.

The away team woke up to find themselves lying flat out staring up at a blue light ceiling. We were in a sickbay. And we weren't Az'SharrAhn'Ti anymore. Not only had we been somehow returned to our own bodies but they had been completely healed; the damage done from the harsh surface of Gamma Hromi IV was gone. Although there was one crewmember, Nathan Halycon, who seemed badly affected by it.

We soon realised there were others in the room. Aliens. Very similar to those who we had only moments (a very relative term) ago inhabited.

It appeared they were worshipping us. After some staring back and forth I eventually struck up a conversation with the one who was their leader.

He explained that they had been expecting us for thousands of years. And in fact, they regarded us, and especially Mike Wong as their saviours. They were the descendants of the aliens we had inhabited. When Mike/Naa'Va'Rcece had decided to spare the ship and thus caused it to crash into the planet Gamma Hromi IV the crew was stranded. Stranded and with no way home they settled down and built a life for themselves there. Their descendants now enjoyed a small civilisation, with cities and towns and culture...

After some time talking he invited the away team to stay for a ceremony on our/his descendants behalf. As this was a First Contact situation of sorts I agreed, but sent people to check on the shuttle. Fortunately it was ok and had somehow survived the trip through time without so much as a scratch.

It was a very short trip to the arena that was to host the ceremony. The planets surface had changed drastically. No longer was there an inhospitable atmosphere and rocky ground, in its place were lush green grass and native plants and snow capped mountains and hills in the distance. It was pleasantly warm.

Once we arrived we took our seats at the very front. The arena was vast. The seats were on a high stage facing a crowd of tens of thousands of aliens. The alien leader gave a short speech and needless to say we were not expecting it when he asked each of us to then give a speech of our own...

Some went well, the aliens went wild when Mike stepped up...and Kathy’s was very diplomatic, while others did not./

K'Etana paused, the horrible memory of the start of her speech where she couldn't think of what to say...and then Patrick Sextons speech..

“Wow…I could sure as hell go for some Jellybeans…Ladies and Gents, you were great…Those of you that might have known my good friend, he was…Great…Thanks.” followed by an awkward grin.

She shook her head and laughed.

/After the speeches were done an amazing display of fireworks were set off, and through it appeared the shuttle piloted by Chief Carson Smith. He navigated his way down to the surface and came up to meet us.

The alien leader realised it was time for us to leave and approached me.

At this moment Nathan Halycon was standing beside me...there's something different..odd..about him since he has returned to his own body..not sure if this is meant to go in a log..

As I was saying, the alien leader approached. He held out a memory chip for me to take, his exact words were;

"On this you will find a file of our complete history. Please ensure that our memory lives on..."

He knew what was about to happen.

Moments later the mountains in the background began to fade, the crowd began to diminish...the leader standing before me seemed to swirl in and out of existence, and then acid rain began to fall.

The world was reverting back to the way we had first found it.

We sprinted for the shuttles, already getting hit by shrapnel from exploding rocks and burns from the acid.

We made it back in one piece, mostly. Mail Vol incurred the only serious injury. His face is a mess.

I'm recording this log as we travel back to the Dauntless, it's a smooth ride, Hendil is piloting.

How or why all of this happened I don't know, perhaps speaking to the Commodore and examining the chip the leader gave us will shed some light on things.

Log Ends./