Breen biotechnology in a Breen Refrigeration Suit

Published in the Kropasar Journal of Applied Biotechnology

Author: Lt. L.B. Pierce CMO CSO USS Ballista

Stardate: 49490

Abstract
A Breen refrigeration suit was found to have self-repairing properties. Analysis showed that the suit was constructed of densely packed crystalline nanocellulose attached to flexible sections that contained a type of cyanobacteria that produced more nanocellulose when stimulated by light and carbon dioxide.

The tensile strength of each strand of nanocellulose was so high that this material could be used for space vessels.

Introduction
The Breen race has been something of a mystery to xenobiologists for some time now. Nobody has ever seen a Breen body without their characteristic suits on. Their technology often seems to be organic in nature but nobody has been close enough to confirm this.

After a combat situation a Breen casualty was brought in to the med bay of the USS Ballista. The refrigeration suit had been significantly damaged by an edged weapon and appeared to be empty. On closer examination the suit had a residue of ammonia and gelatine suggesting that once the suit had begun to warm up the body inside had sublimed.

Due to various circumstances the refrigeration suit was left in the medbay under a variety of lights for approximately 8 hours during which it seemed to repair itself. This paper shows an analysis of the structure of the suit.

Methods
A heavy duty UV laser scalpel was used to cut a sample of the suit and prepare it for analysis.

A light micrograph and electron resonance imager was used to examine the sample. The sample was then put in an atmosphere of pure carbon dioxide and irradiated with a broad spectrum lamp to stimulate further self-repair.

Tensile strength, conductivity and hardness of the suit’s plating were tested using a universal testing machine, tricorder and a Schmidt hammer.

Results
The external appearance of the suit shell appeared, superficially, to be hard plates of a ceramic substance joined with flexible sections. The full suit after it had mostly repaired itself is shown in figure 1.

Breen suit

Figure 1: Full Breen refrigeration suit after almost full self-repair.

After a section of the plates had been removed with a laser scalpel the electron resonance imager showed a densely packed structure of crystalline nanocellulose microfibrils which are shown in figure 2.

nanocellulose3

Figure 2: Nanocellulose structure of Breen suit plating.

The flexible jointed areas of the suit contained strands of a type of cyanobacteria lying inert in a resin or gel substance. An image of the cyanobacteria can be seen in figure 3.

bluegreenalgae1

Figure 3: Flexible section of Breen refrigeration suit under electron resonance imaging showing strands of cyanobacteria lying dormant in a resinous material.

The cyanobacteria seemed similar in structure to blue-green algae with some subtle differences in genetic structure.

Once the suit was damaged and the cyanobacteria were flooded with light and CO2 the bacteria started to produce more crystalline nanocellulose. The nanocellulose was automatically distributed in layers by distribution channels in the underside of the plating.

Tests showed that the substance was electrically conductive with a tensile strength 8 times that of steel and a hardness similar to ceramic.

Discussion
This fascinating material could represent a leap forward in material science. A material that repairs itself, conducts electricity, stronger than steel and harder than ceramic yet light enough to be used in a suit of armour. It is highly likely that Breen ship hulls and perhaps even internal ship structures are created in this method.

The only drawback that this material has is its vulnerability to other microorganisms. Several earth based bacteria can consume cellulose at a rapacious rate. As the Breen are highly militarised, such bacteria could be part of a defence strategy if the Breen ever turn their attention to the Federation.

Advertisements

Ep15: Department Heads meeting

Secure internal memo

From:
Commander Babylon H.Reed, Executive Officer, USS Axanar

To:
All Command Crew and Heads of Department, USS Axanar

Date:
49657.19

Re: Command & Heads of Department Meeting

All,

Please be advised that a Heads of Department meeting has been scheduled for 49661.88 in the conference room. During this meeting, please be prepared to report on and discuss your department’s functional readiness as well as any other departmental matters that may be tables by the Captain and Command Crew.

Any pre-reading that you would like to submit prior to this meeting should be forwarded to me for collation and distribution no later than 1500 hours today. Please note that there will be no presentations at this meeting. Any pre-reading that is submitted will be for discussion and decision making purposes only.

If you have not already, please make yourselves familiar with all staff capabilities within your department. Personnel files have been made available to you, and I’m sure Counsellor Rymon will be happy to be of assistance if required

I am sure that I do not need to emphasise that, as we are headed in to a hostile area of space, combat readiness will be an important factor for all Starfleet staff on board this vessel. As such, I have allocated one Holodeck for the exclusive use of Security, Marines and Flight staff, who will in turn have the responsibility to contribute towards improving battle readiness of those in traditionally non-combatant positions. Scheduling shall work on a rotation. Further information regarding this initiative will be discussed during the meeting.

I am certain that it goes without saying, please be punctual, late comers will not be admitted.

Commander Babylon H.Reed, Executive Officer, USS Axanar.


Secure internal memo

From:
Lt. Pierce

To:
Commander Reed

Here are the topics I want discussed at the meeting.

As you know I am standing in for the Chief Science Officer at the moment so I will be raising issues for that department as well, however, with a ship this size covering both departments is non-trivial. I will be extremely glad to brief the new Chief Science Officer as soon as they arrive and hope that day will come soon.

  • Issues for meeting
  • Science officer issues
  • Iconian ruins in Zeta Caeli system on planets Aurquar and Zeta Caeli I
  • Atypical readings from planetary surface on Huda I in the Huda system
  • Anomalous sub space readings from surface of Mu Doradus II in the Mu Doradus system
  • Large metallic object in ice of Sigma Circini III
  • Quarantine facility and radiation readings on Vega Chandra I
  • Volcanic activity on zeta reticuli II
  • Breen

Chief Medical Officer issues:

  • check ups for all staff
  • Stress testing for flight crew, command crew and marines
  • Combat training for medical personnel

General issues:

  • a lot of new faces, need to have some kind of group activity so we can recognise each other for security purposes

From:
T/SO Bin’Tar

To:
Captain Lombardo, Commander Reed, Major Curtis

Title:
Naming Recommendation

Further to the discussion of the Black Ops team being put together, can I recommend an Andorian animal for naming purposes. The Grimmdarr is small stealthy flying rodent on Andor about 30cms long. It’s main means of attack is to glide from tree to tree holding onto the tree with claws on the ends of it’s wings,looking for a target with it’s big eyes which have great range and excellant night vision.

It then goes about quietly sneaking up on it’s pray, which is normally ground based, and silently drops from the tree on the back of the neck of it’s victim. A dark grey in colour when relaxed the Grimmdarr can change colour like the Earth Chameleon, to suit it’s environment.

T/SO Lt Bin’tar

End Communication


From:
Major (Brevet) Curtis, CO, 8th TFW.

To: 
Cpt. Lombardo, XO Reed, TO Bin’Tar

At the risk of sounding a little parochially Australian… TacO, you’re describing a Drop Bear.

I’m not asking any of my people to join a unit called Drop Bear, and I assure you that’s what they’ll call it. At least, that’s what I’ll call it, and that’s pretty much the same thing.

CAG out.

Ep15: Medical Preparations

USS Axanar medical preparations

 

[Secure Internal Communication]

From:
CMO LB Pierce USS Axanar

To:
All Medical Personnel USS Axanar.

I’ve managed to speak to you all individually by now and I’m looking forward to working with such a talented staff.

As the transferred staff from the dearly departed USS Ballista will tell you, I like to do my homework and I expect my staff to do their homework too.

Each member of the medical staff must be familiar with all of the medical facilities aboard the Axanar. To this end I will be rotating staff members through different shifts in different areas before deciding on permanent shifts. I will be personally conducting assessments of performance and anyone who falls below a standard of excellence will undergo further training.

Permanent assignation will be based on my observation of your performance. I understand that many medical personnel will have particular areas of expertise and preferences, I am already aware of the former, feel free to inform me of the latter. I may consider it in my decision.

Homework also includes getting to know your coworkers, I want every member of the Axanar medical staff to be on a first name basis with each other. To facilitate this I will be conducting a series of seminars on the species and possible challenges of the Rolor sector that I will be calling on some of you to present at. I expect you all to attend these seminars unless you are working.

Make sure you have a working knowledge of the anatomy of every race aboard the Axanar as well as those races residing in or around the Rolor sector including Cardassian, Bajoran and Tzenkethi anatomy. The Rolor sector also abuts the Breen sector, while little is known about them I expect you to know what little there is including my recent research which I will forward to you. The Rolor sector is isolated, if a medical situation occurs help will be a long way away. We will be the first and last line of medical assistance in any situation involving the Axanar so we absolutely must know what we’re doing.

Lastly, I was horrified to note that many of you have let your combat training slip. This is unacceptable in any member of Starfleet, especially a member of my medical staff, so I will be liaising with XO Commander Reed and Security Officer Lt. Bin’tar to devise a remedial training program for everyone to attend.

[End Secure Internal Communication]

Ep15: USS Axanar security measures

Preliminary Analysis for USS Axanar (SECURE PROTOCOLS ENGAGED)

 

From:
Lieutenant SG Louise B. Pierce, Chief Medical Officer, USS Axanar

To:
Captain Jake Lombardo, Commanding Officer, USS Axanar
Commander Babylon H. Reed, Executive Officer, USS Axanar
Lieutenant SG Annabelle Archer, Chief Engineering Officer, USS Axanar
Lieutenant JG Bin’tar, Chief Tactical Officer. USS Axanar

Given the escalation in the Dominion conflict I think it might be advisable to install low level, wide beam polaron emitters at key areas of the ship including the transporter room to safe guard against Changeling infiltration. Even if no Changeling ever attempts to board the Axanar the peace of mind it will give the crew will make it worth the effort.

As the Rolor sector abuts Breen space I should let you know that I have developed a biological weapon against Breen materials which is perfectly safe for most materials used in Starfleet vessels. Basically it’s two types of anaerobic bacteria combined, one that voraciously eats the particular material that Breen appear to use in their armour and another that consumes the byproducts of the first bacteria and turns it into electricity. They should function together to eat holes in any Breen ship hull or armour as well as fry any circuitry inside. I have some ideas about deployment but would need to confer with Bin’tar and Archer to work out specifics.

Lastly, my new medical staff is woefully incompetent in self defence. Commander Reed and Lt. Bin’tar, can I ask you to work with me on a remedial training schedule for my soft bodied staff members?

[End Secure Internal Communication]


 

From: 
Captain Jake Lombardo, Commanding Officer, USS Axanar

To:
Lieutenant SG Louise B. Pierce, Chief Medical Officer, USS Axanar

For your information, Doctor, I’ve attached my preliminary tactical analysis.


 

From:
Lieutenant JG Bin’tar, Chief Tactical Officer. USS Axanar

To:
Captain Jake Lombardo, Commanding Officer, USS Axanar
Commander Babylon H. Reed, Executive Officer, USS Axanar
Lieutenant SG Annabelle Archer, Chief Engineering Officer, USS Axanar
Lieutenant SG Louise B. Pierce, Chief Medical Officer, USS Axanar

Commander Reed and Lt LB Pierce, please find attached the schedule for your staff to conduct assessment, and appropriate combat training for your review and approval.

This training schedule will include assessment and training in:

  • General fitness
  • General combat skills: Weapons and hand-to-hand techniques; Identifying weapon signitures, Audio visual identifiers, and damage markers (type of damage expected on hardware and physical forms); Smart engaging techniques to reduce localised threats (use of force fields and air locks)
  • Identifying personal stealth technologies under combat pressure
  • Impromptu barricades – Modified to maximise combat first aid
  • Hidden weapon systems of known races and basic techniques to assess and reduce possible threats.
  • Engaging/Avoiding boarding parties – modified to suit Medical staff involvement
  • Defensive knowledge: Including fighting withdrawals, supporting combat participants, and medical support requirements outside of regular medical support.
  • Communications. Calling for support. Protocols and procedures.
  • Finally, ALL evacuation protocols.

Assessment will be in conjunction with the Marine units.

Training will be conducted in various parts of the ship and the Holodeck (where appropriate for low level training only), and I would advise supervisors to introduce their teams to unknown staff in these areas when appropriate. A close team is a hard fighting team.

I understand this seems like a large list to deal with, but we all agree that in dire combat situations, the Medical teams place themselves in the front lines. To maximise survival possabilities and to provide confidence in individual team members, it is recommended that that all Medical team members have a skill level graded at 3-6.

Please feel free to add or delete where appropriate and provide feedback to any modifications.

T/SO Lt Bin’tar

End message.


 

Bin’tar,

Perfect.

Medical personnel will be eagerly participating with smiles on their faces if they know what’s good for them.

LB

Ep15: Tactical Analysis Discussion

Preliminary Analysis for USS Axanar (SECURE PROTOCOLS ENGAGED)

 
From: 
Captain Jake Lombardo, Commanding Officer, USS Axanar

To:
Major (Brevet) Sheila Curtis, Flight Operations Squadron Commanding Officer, 8th Tactical Fighter Squadron
Commander Babylon H. Reed, Executive Officer, USS Axanar
Lieutenant SG Annabelle Archer, Chief Engineering Officer, USS Axanar
Lieutenant JG Bin’tar, Chief Tactical Officer. USS Axanar

CC: 
Tacfleet Operational Command.

This communication is preliminary tactical analysis of the Akira Class, specifically the USS Axanar. This not meant as a definitive and comprehensive analysis of the operational capacity of the Akira Class starship, but as a starting point for considering future strategic and tactical possibilities for the USS Axanar as we get to know the kind of ship we’re working with and how they relate to the unique mission parameters required of the Axanar in this sector of space.

As we discovered during our tenure on the USS Ballista, one of the greatest assets our team has is our capacity to think creatively to enhance the capabilities of our ship, in effect, maximising our force potential. The Akira Class is an impressive ship with resources far in excess of our former ship, but that mustn’t mean that we should just rely on its base capacity alone. We must continue to innovate and nurse our creativity to make her one of the best ships in the fleet. We are essentially alone out here, with no real idea what odds we’ll be up against in the future. I think it is definitely in our interests to remember that uncertainty and attempt to maximise all the resources at our disposal.

With that in mind, it’s worth considering the tactical configuration of the USS Axanar. Like all Akira Class ships, it has an impressive array of torpedo launchers and an equally impressive complement of torpedoes.However, for reasons I’m still yet to understand, there are no aft-facing tube launchers.I believe the philosophy behind this was to project maximum force forward (and a little to the side). In fleet-sized engagements, this sort of configuration is appropriate as formations of starships can be configured to cover the weapon blind spots of other ship within that formation.

However, because we are a lone ship patrolling a vast sector of space, we do not have that luxury. Fortunately, we have a very extensive collection of fighter craft embarked on the ship, which will be extremely useful to cover our particular blind spot. As a result, significant battle drills and manoeuvres  will need to be conducted to improve our coordination with smaller craft, particularly when it comes to screening the Axanar from attacks at the rear. As Starfleet reports of Dominion activity has made abundantly clear, the potential for kamikaze attacks from smaller spacecraft is a risk we must be prepared for.

Considering our successes with the USS Ballista, it is worth further developing our torpedo and probe technologies to enhance our capabilities in intelligence gathering, subterfuge, and force projection. To that end, I’d like to recommend the development of an extensible plug-in architecture for our torpedoes and probes. The idea of implementing this technical system would be to speed the implementation of our tactical improvements. If we think of something, I want to be able to implement those changes as quickly as possible.

As always, I will require an intensely detailed astrophysical map of our sector. As always, we need to know our terrain. Fortunately, with the Axanar, we have a dedicated stellar cartography system, which should enhance our capabilities in this area. This “terrain” analysis is a vital part of our tactical preparation, and should be considered a priority.

As with the Ballista, I would like to ensure that the ship is ready in case of boarding actions, but also be quite prepared to conduct those sort of operations ourselves should we need to. Although we have a dedicated Marine contingent, as well as our own security detail, I still feel it is necessary to keep the entire ship at basic level of combat readiness for hand-to-hand and internal ship firefights. The Klingons and the Jem’Hadar are well known for their hand-to-hand fighting prowess, and we must be prepared to face concerted offensive on the ship should we be boarded. Please ensure that tactical drills are run to maximise the ships internal combat readiness.

Finally, while the Axanar’s presence in this sector is designed to be a projection of Federation force in this are of space, I believe that one of our main goals in the coming months, along with our primary mission, will be to gather as much intelligence as possible in the region. If the opportunity arises to gather data on the Dominion or the Klingons, then must seek to take the opportunities wherever possible, with all the resources at our disposal. Likewise, we should try to gather intelligence of any other Federation threats that may arise. Once again, our ability to conduct these sort of intelligence operations (if possible) will be a force multiplier for not only ourselves, but for the entire Federation.

I believe we are in for dark times ahead and we need to be prepared. Nevertheless, we should also be cognisant of ship morale. We mustn’t overstretch the crew as the esprit de corps will suffer. Balance is always necessary, but we have a difficult time before us.

Best of luck to us all.

This concludes this preliminary report.


 

Subject: Addendum to preliminary tactical report (SECURE PROTOCOLS ENGAGED)

From:
Captain Jake Lombardo, Commanding Officer, USS Axanar

To:
Major (Brevet) Sheila Curtis, Flight Operations Squadron Commanding Officer, 8th Tactical Fighter Squadron
Commander Babylon H. Reed, Executive Officer, USS Axanar
Lieutenant SG Annabelle Archer, Chief Engineering Officer, USS Axanar
Lieutenant JG Bin’tar, Chief Tactical Officer. USS Axanar
Lieutenant SG Louise Brooks Pierce, Chief Medical Officer, USS Axanar

Further to the preliminary tactical report, I’ve considered other potential tactical opportunities provided by our new ship, in particular our embarked vessel complement. At this stage, our embarked vessels comprise of the following:

12x Peregrine class medium fighters
2x Danube class runabouts
6x Type 7 shuttles
6x Type 6 shuttles
6x Type 15 shuttlepods
6x Workbees
2x Pelican class dropships

Of particular note are the Peregrine fighters and the runabouts. It’s clear that some form of combat air patrol (CAP) will be necessary to ensure ship security while the Axanar is under impulse power within a star system. Any sort of CAP will be ineffective at higher warp speeds (anything above Warp 4) as the Axanar has a much higher warp speed than those embarked vessels.

For general impulse power operations within a system, a wing of four to six fighters will be necessary to maintain normal operational status. The purpose of this small complement will be to provide cover for the Axanar, but also provide co-ordinated sensor enhancement of the Axanar’s sensors, whether that be by tying into the Axanar’s main sensor array, or via probes linked to the Axanar. The hope is that this flight of fighters will be able to cover us from any nasty little surprises, particularly in sensor blind spots that aren’t covered by the Axanar’s sensors.

Further to that, it would be useful to outfit one of the Danube Class Runabouts with an advanced sensor array that could be deployed as a portable sensor platform. When deployed within a star system at impulse speeds, this runabout would operate as an airborne early warning, control and sensor (AWACS) platform for the Axanar. When utilised in this capacity, an escort patrol of four fighters should accompany the AWACS vessel, while a four-fighter CAP covers the Axanar. The AWACS’s operational capacity would be further enhanced by the implementation of our probe network system. As always, development of highly robust and secure communications equipment for these sort of operations are incredibly important. Please ensure these are implemented.

Please note that the AWACS system with fighter escort could be utilised for low-warp-speed operations.

When at Yellow Alert while at impulse within a star system, the ideal would be to have 8 to12 fighters providing a CAP for the Axanar. This will, of course, be dependent on the tactical situation. If an escalation of readiness is required, but not necessarily an escalation of tension, then it might be prudent to keep the non-patrolling fighters on standby during Yellow Alert while within a star system. As a result, it will be necessary to be clear about the Yellow Alert status for the fighter crews when Yellow Alert is initiated for the Axanar.

When at full Red Alert while at impulse within a star system, all fighters that are available should be used to provide a CAP for the Axanar.

Further to combat operations, it would be incredibly useful to modify our remaining Danube Class Runabout as a special weapons platform. As we progress and attempt to develop force-multiplying technologies to enhance our combat capabilities, the creation of weapon systems that can be deployed from a mobile platform separate from the Axanar will great improve our combat flexibility. While I baulk at using the term ‘bomber’, this is perhaps the most accurate term to describe what the functional role of this modified Runabout would be. As Dr Pierce has already indicated, we are developing all types of specific counter-measures for dealing with enemies known and unknown, and as has been seen with our success with modified torpedoes, the ability to deliver that kind of payload in a portable, hard-to-detect package has many advantages. During combat operations, this “bomber” would require an escort patrol of fighters (much like the AWACS), so a four-fighter complement should be attached to this vessel while conducting those sort of operations.

Finally, we come to one of the most unusual, but I think important, tactical ideas I have for the Axanar. We are afforded the luxury of an excellent complement of marines, shuttle craft, and fighter craft, as well as having a “special operations” expert on board. I think it would be worth considering the development of a cross-trained fighter/marine complement that could be utilised for co-ordinated intelligence gathering and infiltration, particularly in areas of space in which we know very little. This special force could be used in a sabotage capacity if necessary (depending on operational considerations), but the primary role for this group would be infiltration and intelligence. This group should be no more than a dozen people, they should be very able to pilot any type of craft, and have the necessary personal combat and infiltration skills to fulfil the role to a high standard. This type of work will be extremely dangerous, so only volunteers will be allowed to apply for these positions. While the use of fighter craft for this role would be ideal, our comparatively small complement for fighters makes this less than viable for most operations. Depending on the type of operation, and if the resources are there, fighter craft may be made available. However, it may be more prudent to modify and disguise a number of our Type 6 shuttles (two, perhaps three) for these operations. Ideally, the Type 6 shuttles to be used will be modified with enhanced secure long-range communications capability, be given a longer operational range, and also have a reasonable self-defence capacity. Modifications to the appearance of these modified Type 6 shuttles must be made, but they must be easily reversible. Ideally, a system should be developed that will allow these modified shuttles to be made to look like any type of small vessel (Cardassian, Klingon, Breen, Tzenkethi, etc.) easily and quickly.

This concludes this tactical report addendum.


 

Preliminary Analysis for USS Axanar (SECURE PROTOCOLS ENGAGED)

From:
Flight Captain (brevet Major) Sheila Curtis, Commanding Officer, 8th Tactical Fighter Squadron

To:
Captain Jake Lombardo, Commanding Officer, USS Axanar
Commander Babylon H. Reed, Executive Officer, USS Axanar
Lieutenant SG Annabelle Archer, Chief Engineering Officer, USS Axanar
Lieutenant JG Bin’tar, Chief Tactical Officer. USS Axanar
Lieutenant SG Louise Brooks Pierce, Chief Medical Officer, USS Axanar

Sirs, Ma’ams, glad to be a part of the team. I feel this is a good opportunity to introduce you to Black Sheep squadron.

We operate in standard, two-fighter Wings, two of which make up a Flight, and these three Flights make up our squadron. Our Peregrines are Mk Is, single-seater, space-superiority models – three Type IV phaser mounts, dual Micro-torp launchers. Good armour, good shields, turns on a strip of latinum.

CAP operations are not a problem, but I would be concerned about pilot and hardware fatigue, not to mention give the deck crew a hard time turning around any maintenance, by having two many birds out at once. I prefer not to run my people for more than six hours at a time in the cockpit, so I’d feel more comfortable dropping the CAP to a single Wing – that gives us much greater endurance across the board – for standard operations. That means we can maintain two in the air, two hot for launch, and two re-arming, and six in maintenance.

Of course, for alert situations, we’ll step up. Ideal would be four birds flying, four on the ready line, and four arming/refitting. We can crunch that for a full scramble as needed.

As always though, happy to spitball other mission plans, but my prime concern is making sure my people can maintain peak performance.

An AWACS setup is a good idea – we’ve flown with converted Nebula class ships for larger fleet operations before, and having that kind of command and control node is handy. Akiras are designed for that, but I’m guessing we’ll be sending out patrols on long distance flights, and those Danubes are perfect. I can even have some of my deck crew work with your Engineering types to get a sensor package rated and ready to run.

Finally, I think I can winnow out a few multi-skilled individuals from my squadron that might fit your idea, but if you’re taking them out of my crew rotation, I’ll need to rework my roster. That said, if you’re thinking of something more ad-hoc, I’m sure we can manage. I understand your XO’s reserved a Holodeck for training, so let me know if any of your people need a flight refresher.

Happy to help, Cap.

Mj. Curtis.


 

To:
Flight Captain (brevet Major) Sheila Curtis, Commanding Officer, 8th Tactical Fighter Squadron

CC:
Commander Babylon H. Reed, Executive Officer, USS Axanar
Lieutenant SG Annabelle Archer, Chief Engineering Officer, USS Axanar
Lieutenant JG Bin’tar, Chief Tactical Officer. USS Axanar
Lieutenant SG Louise Brooks Pierce, Chief Medical Officer, USS Axanar
Lieutenant Commander Ariana Rymon, Chief Counsellor, USS Axanar

Many thanks for your input regarding my preliminary tactical analysis.

When it comes to fighter operations, I’m very much in uncharted territory, so I’m always happy to get the best advice possible. Your plan to keep standard CAP operations during non-alert status to a single two-fighter wing sounds like the way to go. All officers, see to it that the necessary arrangements are made to incorporate this CAP operational system within our command and control structure.

For Yellow Alert status, as you’ve suggested, the single flight (2 x two-fighter wings) of four fighters should be in the “air”, with one flight on the deck, and the remaining flight rearming and refitting.

The AWACS system should help with our ability to operate independently in this sector of space. Any expertise you can provide our Engineering team for putting together the appropriate sensor package for the Danube Class Runabout would be most appreciated.

With regards to the need for multi-skilled individuals, please liaise with the XO and Chief Tactical Officer (CTO) so that you can co-ordinate your efforts to compile a suitable list of candidates for the (as yet unnamed) infiltration and intelligence unit. They will draw suitable candidates from our Marine contingent and the Axanar’s own Security contingent. Once a final list has been compiled, please ensure that Lieutenant Commander Ariana Rymon, the Chief Counsellor, is provided with the list. It will be necessary for the Counsellor to review the psych profiles of each of the candidates and interview those applicants that manage to pass her assessment of their profiles. Once the final candidates have been compiled and interviewed, the final selection will take place, in consultation with myself, the XO, the CTO, the Chief Flight Officer (CFO), and the Counsellor. When the successful candidates have been determined, they will be passed through to the CMO for final physical assessment. Once we’ve established the unit’s composition, then we can start worrying about training. I hope you understand my reasoning.

With regards to training, we’ll get into a more in-depth discussion at a later date, but the key areas for this unit will be a high level of competence in the following areas:

Flight operations (for a wide variety of spacecraft)
Hand-to-hand combat
Small-arms and long-arms combat
Demolitions
Infiltration and subterfuge
Advanced intelligence gathering (this will require suitable engineering and science knowledge)

Clearly, this isn’t going to be a quick ad-hoc sort of unit, but I think it’ll be one worth investing in over the coming months.

Once again, thank you for your invaluable help in getting my head around Flight Operations, Major.

Best regards.