Location: Z'ha'dum : Start Date: 3200.001

Enemy Strength - Mobile: Viking craft equivalent to approximately 6 ESBs. Approx. 3 ESBs
worth of these appear to be new builds and may not yet be operational, however we must
assume that they are fully functional.

Enemy Strength - Static: The base on Za'Ha'Dum III is defended by approximately 90-100
planetary defence batteries. Additionally, there are 8 large orbital fortresses, each of ESB
size.

Friendly Force composition:

CHF-1 broken down into task forces as follows:

TF-A - The Anvil - composition: 3 CAI, 2 CVI, 2 SVI, 3 EVI, 3 CLI, 3 DDI, 2 ALSI -
CF = 101 [to the enemy this will appear as 12 'big' burns, 3 medium, & 3 small];

TF-B - The Hammer: 4 BBI, 4 CAI, 5 CVI, 5 SVI, 1 AVI, 3 DDI - CF = 204;

TF-C: Auxiliary Ships - 1 SSI, 5 ALSI, 2 TPTI, 10 LSSI, 2 C5, 4 DDI, 2 MDI;

The Plan
(with gratitude to MSN admiral Sho-sho Hines):

1) TF-A enters normal space and burns towards the enemy base, on a standard intercept
course, but at 0.8g;

2) When the enemy sends out an intercept fleet, then assuming TF-A + TF-B is adequate to
successfully engage the enemy intercept forces, then: TF-A will switch to a pre-set evasion
course, still at 0.8g and TF-B will enter the system on a SWIFT course, timed to intercept the
enemy as the enemy intercepts TF-A [See appendix for a discussion of the SWIFT course for
this plan];

3) If the enemy responds with such a force that TF-A + TF-B is NOT adequate to
successfully engage the enemy intercept forces, then: TF-A will flee the system at full
acceleration and TF-B will remain, unrevealed, outside the M25;

4) TF-A will have a 'cut off' point after which it turns and burns to leave the system even if
the enemy has not moved to intercept it. This point will be the last point at which it is able to
successfully achieve step (3).

Operational Priorities: In order:

1) To avoid excessive losses to CHF, unless resulting in much larger losses to the enemy;

2) To gain space superiority in the Z'ha'dum system by engaging and destroying the
maximum number of mobile enemy units;

3) To maximise damage done to the enemy base - eg. by launching mass driving attacks;

The above proposed SWIFT intercept will be more complex than the one used at
PEROXIDE. However, I do see it as achievable if we plan carefully and the enemy is
predictable. What I see happening is: TF-A will follow a rigidly predetermined trajectory
inward, then once the enemy intercept is detected it flips over and starts trying to flee along
another pre-chosen course. The only variable here is WHEN the flip occurs. This effectively
results in a series of possible trajectories for A. Next, we will have to assume a starting
position for the enemy and what acceleration it will use to intercept TF-A - We can assume
they start at their base and will use 1g accel as they always have done to date. This gives us
a series of intercept points and velocities - which one of the series we actually use still only
being dependent on WHEN the enemy starts to intercept (if our assumptions hold). Thus the
speed of TF-B required to perform the intercept will vary with time as A moves into the
system. B will therefore be positioned a few hours travel by HSD outside the M25,
accelerating/deccelerating to keep its speed at that required by our modelled intercept points.
This should be far enough away that their burns will not be detected in system. Once A
signals that it is being intercepted and that it is beginning to evade, B, already at the correct
speed, will jump to the required point on the M25 with the correct orientation (remember
your officer cadet Physics classes - HSD transitions only conserve energy not momentum,
thus outside the M25 we can turn BBI's on the proverbial old Earth dyme) and begins its
intercept run. This SHOULD work IF the enemy re-acts as we predict and sends the right
amount of ships in the intercept force.