Welcome to Star Trek Simulation Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Sign in to follow this  
Followers 0
Tom Servo

Incident Report

To> LT CMDR WILL MARX

From> ENS TOM SERVO

cc> CMDR LO'AMI; LT SAM SEMA'J

 

Subject> EXPLOSION IN STELLAR CARTOGRAPHY (ENCRYPTED)

SD Reference> 50709.19

 

I have compiled a report concerning the explosion in stellar cartography

(the exact panel/conduit could not be readily determined, however it

appears to be either SC163/38 or SC163/39), and attached is the evidence

supporting my findings and conclusions.

 

Based on engineering logs obtained from the computer (appendix A), it

appears that in addition to the analysis and subsequent repairs done by

Ensigns Slartibartfast and Beeblebrox for the damage done during recent

missions, Ensign Gigglethorp was assigned to complete a routine check

and make any necessary repairs two weeks prior to the explosion. No

further access to the conduits in question were recorded. After looking

into the history and service record of all three Ensigns (appendix :D,

there appears to be no reason to suspect them of any wrongdoing, or

sabotage.

 

Internal sensor logs (appendix C) were also reviewed, and provided the

most valuable information. It appears that during Captain Dacotah's

encounter with Baran, that there was a surge in the EM spectrum at

872.587MHz at the exact times when Baran appeared and disappeared. In

reviewing the internal sensor logs, for the three days prior to Baran's

appearance, there was one unexplained burst at that frequency, though

not quite as powerful as those that correlate to Baran's unexpected

visits. No activity was found from the time that Baran's last visit

until I obtained the sensor logs. Although this information, does not

implicate Baran, nor does it confirm that Baran was the source of these

surges, it does seem to point strongly towards him. Furthermore, if this

is linked to the method that Baran transports onto and off of the ship,

it does not shed any light as to the technology being used.

 

Damage control teams sent to repair stellar cartography were not

instructed that this was an abnormal occurrence and that there would be

an investigation launched to determine its cause therefore, minimal

readings were obtained by them, and no more than were necessary to

conduct the repairs. Scans by these teams are compiled into appendix D.

Information collected revealed no known explosive residue, or unknown

components. Supplies used to repair the damaged area are consistent with

those found in the damaged conduits. Engineering logs did not provide

any additional information.

 

Medical scans on Commander Lo'Ami and Lieutenant Nouvelle (appendix E

and F) provided no information on what triggered the explosion or what

it was composed of. It only showed that the explosion was more of a

energy shock than a heat driven one, as there was less burning, and more

blunt force trauma.

 

At this time it is impossible to determine an exact source of the

explosive material, what it was composed of, or how it was placed in

stellar cartography. It should be noted as well, that based on the

passive scanning pattern of the Romulan ship in the vicinity at the time

of the explosion, an explanation as to how they were able to transport

the Commander and Lieutenant at the exact moment could not be

determined. Although pure conjecture, it would appear that Baran and the

Romulan's were both involved in some way with the explosion and

subsequent abduction of Commander Lo'Ami.

 

I would also further recommend that revisions to the process in which

repair teams conduct themselves at locations that might be subject to

investigation be changed to ensure that a maximum amount of information

is obtained in the repair process. Security teams should also be

notified and dispatched at the same time as the damage control teams to

provide a proper level of containment at the scene, this would of

course, be at the discretion of the Chief of Security or their designate.

 

This incident is now no longer under active investigation, but still

open, and will be made available to an Board of Inquiry if necessary. No

fault has been established, and no cause has been determined.

 

Investigated and reported by: Ens. Tom Servo

Assigned by: Lt Cmdr. William Marx, Chief of Security

Incident reference number: 947-8766C-94/1

 

END OF REPORT

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0