TO: 38th/Command | SUBJ: Review of Nebula-Class Starship USS Shackleton

[Derenzis_]

Stardate 96084.4 Security Level 1 - Open TO 38th/Command CC CAPT A. Derenzis FROM RADM A. Rebal SUBJ Review of Nebula-Class Starship USS Shackleton

Officers,

As you may be aware, the ADSB is tasked with reviewing older starship classes still in service in order to determine whether it is time to retire said class. We are currently in the process of reviewing the Nebula Class, first introduced in 2353, as there are now fewer than thirty such starships of this class still in service and the roles that class filled have been largely taken over by the Sutherland Class.

Our records show that the newest Nebula Class starship, U.S.S. Shackleton, NCC-93844, is currently serving with the 38th Fleet. We request that you recall the Shackleton to DS-13 as soon as is convenient, so that a qualified inspection team may examine the ship and make its recommendation to this committee. The inspection team has departed Earth Spacedock and can be expected to arrive at DS-13 by Stardate 96098.1.

We understand that DS-13 possesses drydock facilities; please insure that a berth is cleared for the Shackleton's inspection. We ask that you, the drydock staff, and the captain and crew of the Shackleton do everything possible to assist the inspection team so that this review may be completed efficiently and with minimal disruption for all involved.

Thank you in advance for your cooperation.

//SIGNED//
RADM Aarun Rebal,
Chairman / Nebula Review Committee, Advanced Starship Design Bureau

[Konieczko]

Stardate 96086.5 Security Level 1 - Open TO RADM A. Rebal CC 38th/Command; CAPT A. Derenzis FROM RADM. Konieczko, D. SUBJ RE: Review of Nebula-Class Starship USS Shackleton

Admiral,

I understand your desire to do your job, but I have my own to do mine. As the Shackleton has not encountered any engineering faults of note, I have no obligation or desire to recall the vessel prior to the completion of it's patrol. Doing so could potentially leave a gap in our patrol routes and compromise the security of our quadrant.

Luckily however, the Shackleton is returning from it's patrol and is expected back today. We will elongate the hold time here at DS13 to allow your inspection team the appropriate amount of time. It is however a vital part of this command and inspections should be done quickly and effectively.


//SIGNED//
Rear Admiral Dmitri Konieczko
Commanding Officer
38th Fleet 'Argo'

[Konieczko]

Stardate 96087.3 Security Level 1 - Open TO RADM A. Rebal CC -- FROM RADM. Konieczko, D. SUBJ RE: Review of Nebula-Class Starship USS Shackleton

Admiral,

I would like to speak to you via subnet video at your earliest convenience.

//SIGNED//
Rear Admiral Dmitri Konieczko
Commanding Officer
38th Fleet 'Argo'

[Derenzis_]

Stardate 96090.1 Security Level 1 - Open TO RADM D. Konieczko CC CAPT A. Derenzis FROM LCDR K. Pierce SUBJ Apology and Clarification

Dear Sir,

First off, I apologize for my behaviour last night. I have no real excuse, but I do wish to make amends, and start over.

The inspection of the Shackleton is one of several we are performing on Nebula classes still in service. As Admiral Rebal has surely mentioned, these inspections will influence the committee's decision on whether to keep the Nebula in service or phase them out.

Now the Shackleton is an anomaly; having been designed to 25th century specifications instead of having been upgraded through gradual refits. Our task will be to determine how well this fusion of 25th century technology and a 24th century spaceframe has held up. We will be performing Level 1 diagnostics on all systems as well as reviewing all repairs and maintenance work performed on the Shackleton since its launch. This should give us enough data to project its performance over time and determine its viability.

If our studies demonstrate that the Nebula class is still viable, then the Shackleton and other Nebulas will be returned to service until the ASDB chooses to re-examine the issue; likely in ten years time. If, however, our studies show the Nebula class is no longer viable, then the ships currently in service will be decommissioned at the end of their current refit cycle. For the Shackleton, this would be in one year's time, at Stardate 97087.1.

Should our inspections determine that a ship is dangerously unfit, we will recommend to the fleet command that ship is linked to for immediate decommission, and a reassignment of the captain and crew to a new vessel. Now there are some science vessels currently in the final stages of construction at the fleetyards, and I am certain that Captain Derenzis can be given one of those vessels in compensation in the unlikely event we find the Shackleton to be dangerously unfit. However, let me stress that this is a last resort option, and I am certain that a vessel still only a year old can clear this hurdle easily.

The rest of my team will be arriving on the stardate mentioned in the Admiral's communique. Among them will be my assistants, Lieutenant Hird Negan, systems engineer from the Beta Anteres Shpyards, and Lieutenant Veriv, structural engineer from the 40 Eridani A Starfleet Construction Yards. Both were selected by Admiral Rebal himself to be part of this team. They will be available to answer more detailed questions about this inspection as well as to field any concerns the crew of the Shackleton as well as the DS-13 dry-dock may have as the inspections progress.

Again, my apologies for my unfortunate behavior on our first meeting, and I hope we can work more smoothly together going forward.

//SIGNED//
LCDR Kayden Pierce,
Team Lead / Nebula Inspection Team Gamma

[Derenzis_]

Stardate 96126.2 Security Level 2 - Confidential TO RADM D. Konieczko CC 38th/Command; CAPT B. Ailes; LCDR H'ajah FROM CAPT A. Derenzis SUBJ U.S.S. Shackleton Evacuation

Admiral,

It is my sad duty to report that the Shackleton is currently evacuated. A full report is forthcoming, but in brief: on Stardate 96125.9, we started experiencing a sudden overload of our EPS grid resulting in multiple explosions on several decks. 30 crewmembers were wounded, 4 have been killed. My chief engineer has completed a total power-down of the ship and damage control teams from both the Shackleton and DS-13 have put out the plasma fires, so there is no further danger; but for the present, the Shackleton is not spaceworthy.

Some of my bridge crew have suggested the possibility of sabotage. I have detailed Commander Akaela to head up an investigation on our end; but I will defer to your judgement on how to proceed further.

I expect you will have questions. I am at your disposal, sir.

//SIGNED//
CAPT Alyx J. Derenzis
Commanding Officer / U.S.S. Shackleton

[Konieczko]

Stardate 96127.3 Security Level 2 - Confidentia TO CAPT A. Derenzis CC <38th/Command> FROM RADM. Konieczko, D. SUBJ RE: U.S.S. Shackleton Evacuation

Acknowledged.

//SIGNED//
Rear Admiral Dmitri Konieczko
Commanding Officer
38th Fleet 'Argo'

[Master_Dex]

Stardate 96125.8 Security Level 2: Confidential TO LCDR H'ajah; LCDR Fozka, Throk CC CAPT Ailes, Beylara FROM CMDR Akaela, Tala SUBJ. Assistance on Investigation RE: Shackleton incident

Greetings, as you are all by now aware, the Shackleton experiences some severe malfunctions and has been evacuated. If you need details please see my report attached Here.

There is a suspicion of potential sabotage, perhaps by one or more members of the ASDB inspection team, however we cannot confirm this as of yet. I was hoping to enlist your help in investigating this.

I know LCDR H'ajah will be quite busy coordinating efforts to repair the ship, which I am grateful for of course, but if you can spare anyone from the Computer Services Branch, and likewise LCDR Fozka if you know anyone who can help, I have a copy of a program the inspectors tried to install on the ship earlier in the week. Our chief engineer had it removed due to security vulnerabilities but I am unsure if it did some damage before it was removed. This is what I wanted to learn, with your help.

Let me know if these tasks are possible. I would greatly appreciate it. Further I am having LT Thurston follow up a different angle to this investigation, he should be contacting Operations department shortly about that as well.

//SIGNED//
Commander Tala Akaela
Executive Officer, U.S.S. Shackleton

[Sam]

Stardate 96125.8 Security Level 2 - Confidential TO CMDR A. Mandra CC ~~ FROM LCDR T. Fozka SUBJ FW: Assistance on Investigation RE: Shackleton incident

Commander Mandra,

Please view the forwarded message, and give assistance as you can. Feel free to delegate work if you can, but please, make this a priority.

Strength and Valour

//SIGNED//
Lieutenant Commander Throk Fozka
Science Department Chief, Deep Space 13

[Sophist]

Stardate 96128.5 Security Level 2 - Confidential TO CMDR Akaela, Tala CC CAPT Ailes, Beylara; LCDR Sakkhet FROM LCDR H’ajah SUBJ Re: Assistance on Investigation RE: Shackleton incident

THE SHIPYARD TEAM HAS FINISHED IMAGING THE SHACKLETON'S COMPUTER CORE. THIS IMAGE CAN BE USED BY MY COMPUTER SERVICES MINIONS TO SIMULATE CONDITIONS WITHIN THE CORE AT THE TIME OF SHUTDOWN, WITHIN A SAFELY ISOLATED VIRTUAL MACHINE. I HAVE BEEN WORKING WITH THE SHACKLETON ENGINEERS INCLUDING MOSSIC, SON OF BUHES, WHO CLAIMS TO HAVE PREVIOUSLY VIRTUALIZED A SIMULATED PROGRAM INSTALLATION WHICH DEMONSTRATES HOW ACCESS PROTOCOLS CAN BE CIRCUMVENTED. I WILL INFORM YOU OF MY TEAM'S FINDINGS AS SOON AS THEY ARE AVAILABLE.

//SIGNED//
tuq cargh qaStaHvIS ghIm h'ajah, shal puqbe'
Lt. Cmdr. H'ajah, daughter of Shal, of House Cargh in exile
Chief Engineer, Engineering Dept., Deep Space 13

[Omar_]

Security Level 2 - Confidential TO LCDR Sakkhet CC CAPT Derenzis; CMDR Akaela; FROM LT Thurston, James A. SUBJ USS Shackleton Incident/Request for Resourcing

LCDR Sakkhet;

By now I'm sure your hands are quite full with various emails and requests regarding the recent incident aboard the Shackleton. As I am sure you are by now aware, there is something of an internal investigation going on, not to mention the potential for this investigation to become escalated to higher levels of command. I'll try to be brief and make my request simple.

I am requesting the following assets/resources in order to complete a task relating to that investigation under CMDR Akaela's authority. I'll be happy to answer any questions regarding these requests, and for further verification, I am confident CMDR Akaela will be helpful as well.

• Holodeck reservation for length of time necessary to complete the exploration of a theory. This holodeck will need to be on a network completely removed from DS13 networks and associated systems in order to ensure a potentially harmful program is kept contained.
• Support from Operations personnel, or others as needed, regarding software construct, editing, and evaluation. I have some very limited abilities in programming, but this is more a hobby than anything else, and very limited in scope - specifically, I am proficient with holodeck programming, and a basic understanding of the more rudimentary computer languages, but that is very literally the limit of my knowledge.

My plan is simple - construct a simulation of the Shackleton as completely and accurately as possible in the holodeck; secure that network from all other DS13 systems to prevent contamination in case the program in question is harmful; run the simulation with the program installed on the virtual ship's computer in order to see what it's intent is. This may, of course, take considerable amounts of time in order to determine what will happen. Lastly, I will need all of this recorded, in both transcript - text, log, etc. - as well as pertinent audio and visual records. I would prefer that these recordings be kept separate from the holodeck system, and, of course, those files available only to CAPT Derenzis, CMDR Akaela, myself, and any others that are duly recognized by the Shackleton command team as having a need to know.

//SIGNED//
Thurston, James A.
Lieutenant
Conn Officer, USS Shackleton
//ATTACHMENT// -none-

[Sophist]

Stardate 96132.7 Security Level 2 - Confidential TO CMDR Akaela, Tala CC CAPT Ailes, Beylara; LCDR Sakkhet FROM LCDR H’ajah SUBJ Re: Assistance on Investigation RE: Shackleton incident

THE FOOLS IN THE ADMIRALTY HAVE EXPELLED MY SHIPYARD MINIONS AND RESTRICTED ACCESS TO THE SHACKLETON. OUR WORK IN IDENTIFYING THE CAUSE OF THE MALFUNCTION WILL BE DELAYED BY THIS MEDDLING, BUT NOT HALTED. HERE ARE OUR INITIAL FINDINGS:

• PRIOR TO OUR BANISHMENT, THE LEVEL 1 DIAGNOSTIC OF THE SHACKLETON EPDN HAD UNCOVERED NO HARDWARE FAULTS WHATSOEVER. ALL EPS CONDUITS, REGULATORS AND ASSORTED FLOW ASSEMBLIES APPEAR TO HAVE BEEN OPERATING WITHIN TOLERANCES. THE CAUSE OF THE OVERLOADS WAS SIMPLY THAT OVERCHARGED PLASMA WAS BEING ROUTED THROUGH NETWORK SEGMENTS WHICH WERE NOT RATED FOR SUCH HIGH ENERGY THROUGHPUT.
  
  
• THIS PATHING FAILURE SHOULD NOT BE POSSIBLE WHEN THE SHIP'S ENERGY DISTRIBUTION LOAD BALANCING SUBROUTINES ARE WORKING CORRECTLY. HOWEVER, IN OUR ANALYSIS OF THE COMPUTER CORE IMAGE, WE HAVE DISCOVERED THAT NEARLY ALL OF THE DIAGNOSTIC MONITORING PROGRAMS HAVE BEEN TAMPERED WITH. THESE MODIFICATIONS APPEAR TO HAMPER OR COMPLETELY DISABLE THE PROGRAMS' ABILITY TO SENSE THRESHOLD TRANSGRESSIONS. IN SHORT, THE SHIP COULD NO LONGER RELIABLY DETECT THE OPERATIONAL STATE OR LIMITATIONS OF THE HARDWARE.
  
  
• ALL OF THE MODIFIED DIAGNOSTIC PROGRAMS SHARE A COMMON FEATURE: RELIANCE ON A RUNTIME LIBRARY MODULE WHICH IS NOT PART OF THE SHACKLETON'S OPERATING SYSTEM. THE OWNERSHIP OF THIS MODULE IS OBSCURED; ACCORDING TO TRACE RECORDS, IT APPEARS TO HAVE BEEN INSTALLED FROM WITHIN A SEPARATE CHROOT WITHIN THE SHACKLETON COMPUTER CORE. THIS SEPARATE VOLUME HAS SINCE BEEN UNMOUNTED AND DESTROYED.
  
  
• IN CONSULTATION WITH THE SHACKLETON ENGINEERS, I HAVE LEARNED THAT A PROGRAM SUPPLIED BY LT. CMDR. PIERCE, WHICH WAS THE SUBJECT OF MUCH CONTENTION, WAS DESIGNED TO SET UP JUST SUCH A CHROOT WORKSPACE FOR HIS TEAM. AS THEY WERE THE ONLY OFFICERS WITH ACCESS TO THIS WORKSPACE, IT APPEARS THAT ONE OF THE INSPECTORS WAS RESPONSIBLE FOR DAMAGING THE SHIP'S DIAGNOSTIC SOFTWARE.
  
  
• BEFORE THE INSPECTORS' CHROOT WORKSPACE WAS DELETED FROM THE SHACKLETON CORE, AN EXTERNAL BACKUP OF ITS DATA WAS MADE PER STANDARD PROCEDURE. WHEN WE GAIN ACCESS TO THIS DATA, WE SHOULD BE ABLE TO IDENTIFY WHICH MEMBER OR MEMBERS OF THE INSPECTION TEAM WERE RESPONSIBLE FOR THIS FOULD SABOTAGE. WE ARE CURRENTLY WORKING TO BREAK THE ENCRYPTION ON THIS BACKUP VOLUME, BUT WE COULD AVOID THE NEED IF A MEMBER OF THE INSPECTION TEAM WOULD LEND US THEIR CREDENTIALS.
  
  
• AT THIS TIME ALL WORK ABOARD THE SHACKLETON IS HALTED; THE LEVEL 1 DIAGNOSTIC REMAINS INCOMPLETE AND REPAIR WORK ON THE DAMAGED SECTIONS HAS YET TO BEGIN. ONLY COMPUTER CORE SIMULATION ANALYSIS PROCEEDS, AS THAT CAN BE CONDUCTED OFF THE SHIP. WHILE THE CAUSE OF THE DISASTER MIGHT SOON BE CLEAR, WE WILL BE UNABLE TO ASSESS THE EXTENT OF THE SHIP'S TROUBLES UNTIL THE BRASS LIFTS THE LOCKDOWN AND ALLOWS US TO GET ON WITH OUR WORK.

//SIGNED//
tuq cargh qaStaHvIS ghIm h'ajah, shal puqbe'
Lt. Cmdr. H'ajah, daughter of Shal, of House Cargh in exile
Chief Engineer, Engineering Dept., Deep Space 13

[Master_Dex]

Stardate 96136.4 Security Level 2: Confidential TO LT Thurston, James; LT Mercer, Olivia; LTJG Khet, Mossic CC CAPT Derenzis, Alyx; CAPT Quint, Emery FROM CMDR Akaela, Tala SUBJ. CIR Assignment

Hello everyone, I apologize for the delay.

By authority of Captain Derenzis, I am officially assigning you all to the Critical Incident Review team for the Shackleton, which can allow you to continue your investigations as before.

Keep us in the loop on what you are doing please, some of you already have tasks so I'll leave it at that.

I expect us to figure this out. So let's not waste any time.

//SIGNED//
Commander Tala Akaela
Executive Officer, U.S.S. Shackleton

[Derenzis_]

Stardate 96147.4 Security Level 2 - Confidential TO RADM A. Rebal CC <38th/Command> FROM LCDR K. Pierce SUBJ Final Report

Dear sirs,

Below you will find my team's final report on the Shackleton. In summary, it is my sad duty to report that the Shackleton is manifestly UNSAFE. The recent EPS explosions which killed four crew are but the most visible indication of the sorry state of this vessel. I must recommend that the Shackleton be decommissioned and scrapped immediately.

Further, in the course of our review, I have uncovered clear evidence of gross negligence on the part of the Shackleton's chief engineer, the Tlith known as Lieutenant Voyrays. The Lieutenant has consisently falsified repair and maintenance logs from the beginning of his service aboard this ship, as an attempt to cover up his incompetence. It may even be possible that he will use the antagonism between my team and the Shackleton crew - an antagonism which stems fully from my most unfortunate behaviour on the day of my arrival, and for which I accept full responsibility - to shift the blame for this recent disaster to members of my team. I must recommend he be detained and submitted to court martial at once.

While I am loathe to accuse a Starship Captain, I suspect that Captain Derenzis may have had knowledge of LT Voyrays' deception, and recommend she be questioned.

We are preparing to depart for our next assignment, and should begin our review of the U.S.S. Phoenix on Stardate 96161.0.

//SIGNED//
LCDR Kayden Pierce,
Team Lead / Nebula Inspection Team Gamma
//ATTACHMENT// shackleton-final-report.doc

---

Stardate 96147.4 Security Level 2 - Confidential TO CAPT E. Quint CC FROM LCDR K. Pierce SUBJ Retrieval of Vital Equipment

Captain Quint,

My team and I are preparing to depart for our next assignment. However, during the chaos of the evacuation from the Shackleton, certain pieces of vital equipment, containing sensitive ASDB files, were left behind on the ship. Your office has instituted a lockdown of the Shackleton,, preventing us from recovering our equipment. Since our schedule can brook no delay, I request that you allow us to board the Shackleton so that we can recover our equipment before the next ship for Celes sector is due to leave.

If you are concerned about security, I am willing to board the Shackleton alone, while the rest of my team remains aboard the starbase.

//SIGNED//
LCDR Kayden Pierce,
Team Lead / Nebula Inspection Team Gamma

[Valore]

Security Level 2 - Confidential TO RADM Rebal, A. CC RADM Konieczko, D.; <38th/Command> FROM LT Valore, S. SUBJ RE: Final Report

Rear Admiral Rebal,

This office has received Lieutenant Commander Pierce's report. It will be processed accordingly within 3-5 business days. Please be advised that the severity of the positional, logistical, and diplomatic contextual theaters that the 38th Fleet finds itself in leaves the applicability of mothball or an imposition of equal or greater of such a status presently untenable. It would behoove the fleet, Starfleet, and the Federation for the contextual matter to remain relegated to the status quo while discretionary elements continue to ascertain the crux of the epistemological matter - all of which is also under independent review by this office.

The emergent facts of the matter leave the proper acquisition of diagnostics of both methodological and epistemological venues unfulfilled with regards to the subject matter. As a result, verification of such vital matters by any independent team or panel to affirm Lieutenant Pierce's report remains impossible.

Thank you for your time. A conclusion shall be dispatched when ready.

//SIGNED//
Lieutenant S. Valore
Administrative Yeoman
Office of Rear Admiral Konieczko

[Quint]

Stardate 96149.5 Security Level 2 - Confidential TO LCDR K. Pierce CC RADM Konieczko, D; RADM A. Rebal; CIR Team FROM CAPT Quint, E. SUBJ Re: Retrieval of Vital Equipment

LCDR Kayden Pierce,

You and your team are going to have to make arrangements to be late to your next assignment. As you and your team were aboard the Shackleton, you will be making yourselves available to the Critical Incident Review's panel. As your equipment is aboard it is also currently considered evidence along with the rest of the ship. This process is moving as quickly as it can and will certainly be done quicker with your cooperation. Especially since you presented your 'expert' option of what occurred in your review.:

"Further, in the course of our review, I have uncovered clear evidence of gross negligence on the part of the Shackleton's chief engineer, the Tlith known as Lieutenant Voyrays. The Lieutenant has consisently falsified repair and maintenance logs from the beginning of his service aboard this ship, as an attempt to cover up his incompetence. It may even be possible that he will use the antagonism between my team and the Shackleton crew - an antagonism which stems fully from my most unfortunate behaviour on the day of my arrival, and for which I accept full responsibility - to shift the blame for this recent disaster to members of my team. I must recommend he be detained and submitted to court martial at once."

I think your data will prove interesting reading material for the CIR, and feel they would benafit from being able to ask a few questions. Furthermore, as the incident in question resulted in four deaths, and a number of injuries the conclusion of the CIR takes priority over all other activities unless an emergency is in place. I am sure that Rear Admiral Rebal can give you the exact section of regulations to read up on if you'd rather not hear it from me.

Get comfortable Mr Pierce, and please enjoy your stay on DS 13

//SIGNED//
Emery Quint
Captain, Fleet Executive Officer
38'th Fleet 'Argo'

[Master_Dex]

Stardate 96150.4 Security Level 2: Confidential TO LCDR Nim, Vera; <38th/Security> CC CAPT Quint, Emery; LCDR Thorne, Yvette; LT Mercer, Olivia; LT Thurston, James; LTJG Khet, Mossic FROM CMDR Akaela, Tala SUBJ. Watch notice

Lt. Commander Nim, I am writing you in relation to the Shackleton Critical Incident Review.

We cannot fully reveal details of this review as of this writing, but due to evidence gathering and our ongoing investigation, I want to request of you and your department to keep a close watch on the individual known as Lieutenant Commander Pierce. He is part of the ASDB team originally sent to investigate the Shackleton and is temporarily staying on DS13.

We are not at this moment accusing him of anything nor do I ask you to apprehend him, but we worry that he should be kept an eye on in case he tries to leave the station. He already has been ordered to stay by Captain Quint due to the Review anyway so hopefully you will not have to worry. This need will likely last until the end of this Incident Review which will hopefully conclude within the week.

Thank you for any help you can provide.

//SIGNED//
Commander Tala Akaela
Executive Officer, U.S.S. Shackleton

[Derenzis_]

Stardate 96157.8 Security Level 2 - Confidential TO <Nebula Inspection Team Gamma/All> CC <38th/Command> FROM RADM A. Rebal SUBJ Change in Assignment

ALLCON:

Effective this stardate, I am relieving Team Gamma of its duties until further notice. I expect each and every member to cooperate with the Critical Incident Review currently underway. Until that review is complete, your next scheduled inspections will be picked up by the other teams currently in the field.

Also, effective immediately, LCDR Pierce is placed on administrative leave until further notice. LT Hird Negan will be interim team lead until this matter is settled to the satisfaction both of this office and of the Command of the 38th Fleet.

Speaking on behalf of the Advanced Starship Design Bureau, I apologize for the mess this incident has become.

//SIGNED//
RADM Aarun Rebal,
Chairman / Nebula Review Committee, Advanced Starship Design Bureau

---

Stardate 96157.9 Security Level 2 - Confidential TO LCDR K. Pierce CC FROM RADM A. Rebal SUBJ What Happened?

Lieutenant Commander Pierce,

I go away for a few days leave and come back to an administrative mess. What the hell happened out there?

As your new status should indicate, neither I nor the rest of the committee are pleased with your performance. I gave you one job, Kayden: review the Nebula classes on your list and report back with the results. This isn't a hard task, as your review of the U.S.S. Sutherland demonstrated.

Your combative attitude - about which we have discussed at length - only pales in comparison to your attempt to flee the site of an investigation in progress, while hiding behind duty. Think of the impression of the ASDB you're giving to the people of the 38th. The crew of the Shackleton especially, who had to bury four of their number from this incident.

When I interviewed you, you showed a level of professionalism I admired. I expect you to spend your administrative leave finding that professionalism again, and sticking to it this time.

Oh, and no, you cannot use your current leave status to duck out of the CIR's questions.

Don't make me come out there.

//SIGNED//
RADM Aarun Rebal,
Chairman / Nebula Review Committee, Advanced Starship Design Bureau

[Sophist]

Stardate 96158.9 Security Level 2 - Confidential TO CMDR Akaela, Tala CC CAPT Quint, Emery FROM LCDR Nim, Vera SUBJ Re: Watch notice

Unfortunately, the thanks are a little premature. I can't help you without disclosure of the evidence you have against Lt. Cmdr. Pierce. We don't put Federation citizens under surveillance and/or travel restriction without due process. I'm afraid I can't just take your word on this.

In the mean time, if your suspect is a flight risk and you need to put him on a leash, I suggest you pass that up to Capt. Quint to work out with Capt. Ailes. Until this is a criminal matter, my hands are tied. When you're ready to share, we'll be here. Hopefully Pierce will be too.

//SIGNED//
LCDR Vera Nim
Chief of Security, Deep Space 13

[Valore]

Security Level 3 - Restricted TO LCDR Nim, V. CC RADM Konieczko, D.; <38th/Command> FROM LT Valore, S. SUBJ Request for Investigation

Lieutenant Commander Nim,

Following an independent investigation by the DS13 engineering department with the sanction of Rear Admiral Konieczko's office, sabotage by the inspection team send by Rear Admiral Rebal has been discovered. See the attached file.

The Office of Rear Admiral Konieczko requests, in light of this evidence, that all members of RADM Rebal's inspection team be detained and a criminal investigation by DS13 Security be launched. It would also be beneficial if they were separated so they could not coordinate to establish a unified story.

The office thanks you for your cooperation. Any questions may be answered by a reply to this communique.

//SIGNED//
Lieutenant S. Valore
Administrative Yeoman
Office of Rear Admiral Konieczko
//ATTACHMENT// Fnl.xxp

[Valore]

Security Level 2 - Confidential TO RADM Konieczko, D. CC LCDR Nim, V.; <38th/Command> FROM LT Valore, S. SUBJ Conference Result

Sir,

The conference regarding the Shackleton and LCDR Pierce has concluded. He fully confessed to sabotaging the Shackleton in front of me and all others assembled. With the matter concluded, I would propose that the lockdown on the Shackleton be ended and repairs recontinue.

I serve at your pleasure.

//SIGNED//
Lieutenant S. Valore
Administrative Yeoman
Office of Rear Admiral Konieczko