This was a busy month in the Frontier. The sathar probe into the Theseus system is intercepted and destroyed by the militia. The lost K’aken-Kar assault scout finally finds its way home and Spacefleet starts to get serious about locating the sathar routes into the Frontier and their starship construction centers. The UPF suffers a major blow to its production capabilities as saboteurs nearly completely destroy the Hentz (Araks) starship construction center. Finally, the HSS History’s Hope misjumps into an unplanned system and makes what might be a major yazirian cultural discovery.
Date (FY)
Events
62.038
Five fighters are completed at the CDC shipyards (Triad, Cassidine) and work begins on five more. Three of the fighters are immediately assigned to fill out FFC Squadron Eta while the other two are placed in storage.
62.039
The Second Battle of Theseus. The Theseus militia intercepts SFB-J2 and destroys, only suffering minimal damage.
62.040
– Jump calculations complete, the HSS History’s Hope begins the final accelerations and alignment for their next jump.
– Deceleration complete, SBF-A2 begins accelerating for the return jump to OFS203.
62.041
– Deceleration complete and with still no sign of sathar presence in the OFS020 system, PG Probe Alpha begins acceleration for a return jump to the Fromeltar system.
– The militia ships arrive back at Minotaur (Theseus) after the battle with the sathar and the damaged assault scout is immediately moved into the shipyard for repairs, bumping out a HS 5 ship undergoing maintenance.
– SG Alpha jumps into the Prenglar system. A ship carrying the new fighter pilot graduates boosts to meet up with carrier as work begins on calculations for the jump to Athor.
– A heavy cruiser is completed at SCC#5 (OFS19) and joins SBF-E2. The battle group, consisting of 2 C, 1 FF, 1 DD, 1 LC, & 2 HC depart for SCC#4 (OFS111).
– Three assault scouts are completed at the PGC shipyards (Gran Quivera, Prenglar) and join TF Prenglar. The shipyard space is released by Spacefleet back for pubic ship maintenance work.
62.042
The HSS History’s Hope successfully jumps into the new system which they are designation YS13. They begin deceleration an jump calculations for the return trip to YS12.
62.043
SBF-A2 is detected in the outer reaches of the Gruna Garu system but is too far away to be identified and just recorded as an unidentified vessel. Due to the on-going conflict, it is reported immediately to Spacefleet.
62.044
Two fighters completed at the Minotaur (Theseus) shipyards and join those manned by the militia under the direction of FFC Squadron Epsilon.
62.045
– After 13 days, the astrogator on the K’aken-Kar assault scout establishes that they are in FS33, the original destination for their first misjump. They begin work on calculations to jump back to their home system.
– SBF-A2 slips into the void but misjumps, overshooting its target and ending up in OFS198.
– Given the reports from the Gruna Garu system of unidentified vessels in the outer system, Spacefleet orders SG Alpha to deliver the fighters waiting at Hentz (Araks) to the Gruna Garu system.
62.046
– PG Probe Alpha slips into the Void but misjumps and doesn’t end up in the Fromeltar system. However, their comm systems light up almost immediately and they realize they have overshot their target and ended up in the Dramune system. They immediately begin decelerating and plotting a return jump to Fromeltar.
– SBF-A2 determines its location and begins plotting a jump back to OFS203.A light cruiser is completed at sathar SCC#4 (OFS111)
62.047
Starfleet puts out a Frontier-wide announcement looking for high level astrogators to participate in a high-paying, adventurous, but possibly dangerous classified project.
62.048
With CNE Group’s infrastructure rollout on Groth (Fromeltar) plagued by constant sabotage, the consortium brings in a large MercCo contingent as additional security and several investigative teams.
62.049
Despite the vagueness of the advertisement, Starfleet’s call for high level astrogators garners dozens of applicants in just two days. Screening of applicants begins immediately.
62.050
Three more pilots complete the accelerated training at Gollwin Academy. They are temporarily assigned to fighters at the Academy and start training with TF Prenglar while awaiting permanent assignment.
62.051
– The HSS History’s Hope misjumps and instead of ending up in YS12 are in an unknown system which they designate YS14. They begin immediately working on finding their position.
– The K’aken-Kar militia assault scout begins accelerating for the jump back to its home system.
– Four fighters are completed at the Hentz (Araks) shipyard and FFC Squadron Beta takes control of them and the other four fighters currently manned by the militia in preparation for the arrive of SG Alpha in a few days.
– Two fighters are completed at the Minotaur (Theseus) shipyards and join the partial squadron manned by the militia under the command of FFC Squadron Epsilon.
– SG Alpha jumps into the Araks system and begins deceleration towards Hentz to pick up the fighter stored there.
62.052
Sathar agents succeed in sabotaging the Hentz (Araks) starship construction center almost completely destroying it. Pieces of the SCC rain down on the planet. All ships in the center, including 4 civilian vessels, 2 assault scouts, & 4 fighters are destroyed. It will be years before the facility is back to full capacity.
62.053
In wake of the near total loss of the Hentz (Araks) SCC, Star Law launches an investigation into the Family of One’s management of the facility and their security measures. Security is tightened at all other SCCs.
62.054
– Sathar fleet TG1 jumps into the OFS138 system containing sathar SCC#3. It is joined by the frigate and heavy cruiser there and continues on toward OFS020.
– A destroyer is completed at sathar SCC#10 (OFS174).
– A HS:5 ship completes maintenance at the Minotaur (Theseus) SCC and the militia uses the space to begin construction of another frigate.
62.055
– After a full assessment of the damage to the Hentz (Araks) SCC, it is determined that existing center is effectively a total loss (98% damaged) and the decision is made to build a completely new structure. The limited capacity of the surviving center is dedicated to that work.
– SG Alpha arrives at the Hentz station and the eight pilots take control of their fighters and begin loading them onto the assault carrier for transport to Gruna Garu.
62.056
– The K’aken-Kar militia assault scout successfully jumps back into the K’aken-Kar system and begins decelerating toward home. All data from its travel are immediately transmitted to Spacefleet.
– With the fighters loaded, SG Alpha departs for Gruna Garu.
– The crew of the HSS History’s Hope detects a faint, intermittent radio signal emanating from somewhere in the YS14 system. While the astrogators continue to work on locating their position, other crew work on finding the source of the signal and understanding it.
62.057
– SBF-E2 arrives at SCC#4 (OFS111). The AC, LC, and 8 fighters are attached to the battle fleet and preparations are made for them to join TG1 in OFS020.
– An assault scout is completed at the PGC shipyards (Gran Quivera, Prenglar) and joins TF Prenglar.
62.058
– A heavy cruiser is completed at sathar SCC#10 (OFS174). Together with the destroyer completed four days earlier, they are designated TG2, and immediately departs for SCC#1 (OFS203).
– Three assault scouts are completed at the CDC shipyards (Triad, Cassidine). Designated Shuttle Group Beta, they depart immediately for Prenglar.
– Five fighters are completed at the PGC shipyards (Gran Quivera, Prenglar) and are transferred to Gollwin Academy.
62.059
PG Probe Alpha arrives back at Terledrom (Fromeltar). Two high level astrogators from TF Cassidine are transferred to the ships of PG Probe Alpha and it sets out once again to OFS020 to try to chart the jump back.
62.060
– SBF-A2 successfully arrives back at sathar SCC#1 (OFS203).
– The astrogators on the HSS History’s Hope identify their location as a system 9 light years from YS12 and begin plotting a jump back to the YS12 system.
– A Spacefleet destroyer is completed at the Minotaur (Theseus) shipyards. It departs to joint PG Vigilant in the K’sta-Kar system.
62.061
– With the screening of the initial astrogator candidates complete, Spacefleet organizes three new patrol groups, Probe Beta, Gamma, & Delta, each consisting of two assault scouts (drawn from TF Prenglar) with a level six astrogator on board.
– After a final briefing, the newly formed patrol groups are dispatched to try to discover the jump routes the sathar are using to enter the Frontier.
62.062
With more resources available now that their position has been determined, the crew of the HSS History’s Hope localizes the source of the mysterious signal to a planet in the inter system. It appears to be a FM radio signal and work begins on decoding it.
62.063
Security for CNE Group on Groth capture saboteurs attempting to disrupt their infrastructure rollout. As suspected the saboteurs were hired by the Groth Energy Corporation.
62.064
PG Probe Alpha jumps into the OFS020 system and immediately begins deceleration and jump calculations for the return to Fromeltar.
62.065
– Jump calculations complete, the HSS History’s Hope begins acceleration for the jump back to YS12.
– SBF-E2 departs sathar SCC#4 (OFS111) for a jump into the OFS020 system to join up with TG1.
– SG Alpha arrives at Hargut (Gruna Garu) delivering the fighters from Hentz which are formed into FFC Squadron Theta. The assault carrier departs to return to Prenglar.
62.066
– The crew of the HSS History’s Hope finally have a breakthrough on the signals from the inner system of YS14. To their surprise, it is a garbled mayday message in a very old Yazirian dialect.
– The old yazirian mayday identifies the ship as the Yazirian Ark Ship (YAS) Royal Cloud. The HSS History’s Hope immediately aborts the jump back to YS12 and starts heading to the inner system.
62.067
– Now 500 days since hatching, the Eorna young are still growing and thriving. The problems seem to have been all with the rogue Eorna and a new batch of eggs are prepared for hatching and plans begin to accelerate the population growth program.
– An assault scout is complete at the Outer Reach (Dramune) shipyard and departs for Morgaine’s World (Prenglar) to join TF Prenglar.
– All attempts at communication with the YAS Royal Cloud by the crew of the HSS History’s Hope receive no response.
62.068
– SG Beta arrives at Gollwin Academy and joins up with TF Prenglar, replacing several of the assault scouts that departed as part of the new patrol groups.
– The replacement destroyer for the Inner Reach (Dramune) militia is completed at the Outer Reach shipyards and departs across the system to Inner Reach. Outer Reach begins construction of a destroyer for themselves.
– Five more fighters and an assault scout are completed at the CDC (Cassidine, Triad) shipyards. The fighters are temporarily attached to FCC Squadron Eta while the assault scouts depart to join PG Vigilant.
This month both sides of the conflict are probing for new routes into enemy space with the Sathar looking for routes to Theseus and Gruna Garu and the UPF probing outward from Fromeltar. The lost militia scout begins to find its way home and the HSS History’s Hope continues its journey.
Both sides continue to build up their forces and the Sathar start a major reshuffling of their ships in preparation for a major change in tactics. The sathar continue with sabotage efforts around the Frontier. This month also sees the events of SF4: Mission to Alcazzar play out.
Date (FY)
Events
62.008
– The militia assault scout coming from Theseus arrives back at Pale station. The crew is debriefed, and the ship immediately begins duties.
– SG Alpha arrives at Gollwin Academy to pick up a shipment of fighters to be delivered to K’sta-Kar.
– Five fighters are completed at the Triad (Cassidine) SCC and work begins on five more.
62.009
After loading 8 fighters at Gollwin Academy, SG Alpha departs for K’sta-Kar.
62.010
– PG Liberty does not detect the return of SBF-J2 until they are nearly back to Snowball being tipped off my some of their Mhemne contacts. They radio the news of the fleet’s return back to Spacefleet.
– Construction is competed at the Minotaur (Theseus) shipyard of a HS: 7 civilian freighter. This is the first civilian ship competed since the beginning of the conflict. It was started before the conflict began.
62.011
– Arriving back at Snowball (Liberty) SBF-J2 spends a day replenishing supplies before heading back out of the system to complete charting the route to Theseus.
– Eight Academy pilots arrive at Theseus and take control of the waiting fighters. They form FFC Squadron Epsilon.
62.012
Jump calculations for the next leg complete, the HSS History’s Hope begins accelerating toward Void speed.
62.013
An assault scout is completed in the PGC (Gran Quivera, Prenglar) shipyards and joins TF Prenglar. Work begins on another assault scout.
62.014
– Two UPF assault scouts are completed at the CDC (Triad, Cassidine) shipyards. They are designated Patrol Group Probe Alpha and depart for the Fromeltar system to explore outward an attempt to find the sathar route into that system. Work begins on two more assault scouts.
– Two fighters are completed at the Minotaur (Theseus) station. One rounds out FFC Squadron Epsilon bringing it up to full strength and the other is manned by the militia supporting the FFC. Work begins on two more fighters.
– The CDC team arrives on Alcazzar. Within minutes of their landing, their transport, the Nightrunner, is attacked and forced to flee the system, stranding them on the planet. (SF4)
62.015
– After securing the CDC compound on Alcazzar, the strike team realizes that their only option for off-world communication will be at the Streel compound about 120 km away. As they prepare to depart, they are attacked by an aircar with Streel markings. (SF4)
– A UPF light cruiser, part of Task Force Meteor, is completed at the CDC shipyards (Triad, Cassidine). It departs immediately to join up with TF Cassidine in the Fromeltar system. Work is started on another light cruiser.
– After a day of travel over rugged terrain, and several encounters with the mega-fauna of Alcazzar, the CDC set up camp for the night. (SF4)
62.016
– As the CDC team sets out to continue its journey to the Streel compound, they are attacked by a large armed force of Streel vehicles. After an intense battle, the Streel forces are destroyed but the CDC team is down to a single vehicle. (SF4)
– The HSS History’s Hope successfully make the jump into the system they are now designating YS12. They begin deceleration and start calculations for the return jump to YS11.
– Entering the forest east of the Streel compound, the CDC explorer is bombarded by fruit pits from unseen assailants for a few seconds before the bombardment ends with chittering echoing through the forest. (SF4)
– A few hours after the fruit pit bombardment, the CDC team’s path is blocked by six individuals that they recognize as members of the planet’s sentient species. Recognizing the opportunity for allies against Streel, the team attempts to communicated with the natives. (SF4)
62.017
– Having established friendly relations with the natives of Alcazzar, the CDC team works with the natives to plan an attack on the Streel compound where over a hundred of the natives are being held and used as slave labor. (SF4)
– After nearly 70 days, the astrogator on the K’aken-Kar militia assault scout finally determines the ship’s location and discovers that they are well outside the Frontier. They begin plotting a jump to OFS167 to start the trek home.
62.018
An unauthorized aircar attempts to approach Spacefleet headquarters on Morgaine’s World. Refusing to divert, it is engaged and shot down but detonates upon impact causing considerable damage and several civilian casualties. The driver is incinerated in the blast.
62.019
With jump calculations about halfway done, the crew of the K’aken-Kar militia assault scout begin accelerating toward jump speed for the jump to OFS167, 5 light years away.
62.020
– After 3 days of planning and resting, the CDC team, together with the Alcazzar natives, launch an attack on the Streel mining compound. (SF4)
– The attacking CDC team manages to fuse the reactor of the Streel compound and get a message to the Nightrunner to pick them up back at the CDC compound in ten days. (SF4)
– Nine more pilots graduate from the accelerated training program. Eight depart for Triad (Cassidine) while the remaining pilot joins Task Force Prenglar.
62.021
– Deceleration into YS12 complete, the HSS History’s Hope begins accelerating for it’s jump back to YS11 while jump calculation continue.
– Four fighters are completed at the Hentz (Araks) shipyards. They are temporarily crewed by militia pilots under the supervision of PG Tranquility. Work begins on four more.
– Two fighters are completed at the Minotaur (Theseus) shipyards and work begins on two more.
62.022
A cutter is completed at sathar SCC#5 (OFS19)
62.023
An attempt is made to sabotage the starship construction center at Rupert’s Hole (Cassidine) but is thwarted by security personnel. The saboteur, a human, kills himself before he can be captured.
62.024
– SBF-J2 arrives in the Padda system and begins working on jump calculations to chart a route to the Theseus system.
– The K’aken-Kar militia assault scout successfully jumps into the OFS167 system. As the engineers start working on their engine overhauls, the astrogator gets to work plotting a jump to the neutron star in OFS166.
– A frigate is completed at sathar SCC#10 (OFS174)
62.025
SG Alpha arrives at K’sta-Kar delivering 8 fighters which become Frontier Fighter Corps Squadron Zeta. The crew is given 2 days of R&R before heading out for the Araks system. The assault scout joins PG Vigilant.
62.026
The HSS History’s Hope successfully jumps back to YS11 and begins deceleration and starts calculations for the jump back to YS12.
62.027
– PG Probe Alpha arrives at Terledrom (Fromeltar) and confers with leader from TF Cassidine and the local militia about the sathar incursion into the system. They decide to attempt to chart the route through the nebula to the double star system OFS020 a 6 light year jump.
– With their jump calculations nearly complete, the K’aken-Kar militia assault scout begins acceleration for the jump to OFS166.
62.028
– Jump calculations complete, sathar SBF-J2 begins accelerating for the jump into the Theseus system.
– A destroyer is completed at sathar SCC#1 (OFS203).
– Deciding to try a different tactic, the sathar begin a major fleet reshuffling. The ships (1 F, 1 FF, 1 HC, & 1 AC) at SCC#10 (OFS228), designated TG1 depart for SCC#3 (OFS138).
– Five fighters are completed at the PGC shipyards (Gran Quivera, Prenglar) and are transferred to Gollwin Academy while work begins on five more.
62.029
The 8 FFC pilots arrive at Cassidine and take command of the fighters stored there forming FFC Squadron Eta.
62.030
– The Nightrunner arrives back at Alcazzar and retrieves the CDC team. They slip out of the system avoiding Streel forces and return to Triad (Cassidine). (SF4)
– With assistance from the TF Cassidine astrogators, PG Probe Alpha completes jump calculations and begins accelerating for a jump to the OFS020 system.
62.031
SBF-A2 (1 LC) departs SSC#1 (OFS203) to attempt to chart a route to Gruna Garu.
62.032
The K’aken-Kar militia assault scouts misjumps once again and ends up in another unknown star system (FS33). They begin working on finding their location.
62.033
SBF-J2 successfully jumps into the Theseus system. It begins deceleration to turn around and jump back to the Padda system.
62.034
Eight more pilots graduate from the accelerated fighter training program at Gollwin Academy. They are to join SG Alpha as it passes through the system in 10 days to take control of the new fighters at Hentz (Araks).
62.035
– The HSS History’s Hope jumps back into the YS12 system and begins calculations for the next jump, a small star system 8 light years away. They remain near jump speed as the next system is in nearly a direct line to their current line of travel.
– PG Probe Alpha successfully jumps into the OFS020 system. They remain near jump speed and monitor the system for sathar presence while work begins on engine overhauls and calculations for the return jump to Fromeltar.
– A heavy cruiser is completed at sathar SCC#3 (OFS138).
62.036
– SBF-J2 is detected by a patrol of two assault scouts of the Theseus militia and detects them in return. It immediately begins altering its flight path to attempt to avoid an engagement.
– Loath to engage the light cruiser of SBF-J2 by themselves, the two Theseus assault scouts radio for backup and begin to trail the sathar ship. The rest of the militia immediately boosts to attempt to intercept the sathar.
– SBF-A2 successfully jumps into the Gruna Garu system. It begins deceleration out of the system plane to attempt to avoid detection while it plots the return jump.
62.037
After 2 days of no sathar detection, PG Probe Alpha begins deceleration in preparation for the return jump to Fromeltar.
A sathar light cruiser, detected three days ago by a pair of patrolling militia assault scouts, was engaged today by the full force of the Minotaur militia after a long, high-g boost to intercept the alien vessel. A thirty minute battle ended with the complete destruction of the sathar ship while only one of the militia assault scouts sustained some minor hull damage.
An anonymous source has confirmed that Spacefleet has assets in systems beyond Theseus that alerted the militia to the possibility of the sathar vessel arriving in system. Our thanks go out to those brave souls risking their lives to watch the sathar movements.
Victoria Sorensen, StarPlay News
Background
After the failed attempt by the frigate to chart the course into the Theseus system, the sathar dispatch a light cruiser (the remains of SBF-J2) to attempt to complete the route. Detected after three days of deceleration by two patrolling militia assault scouts, the light cruiser attempts to evade and jump out of the system before it can be attacked.
Unsure of their ability to take on the light cruiser by themselves, the two militia assault scouts report in and begin to trail the light cruiser while the rest of the militia ships begin a high-g boost in an attempt to intercept the light cruiser before it can jump out of the system. After three days of grueling pursuit, the militia ships overtake the light cruiser and engage.
Order of Battle
Minotaur Militia
4 Assault Scouts
1 Frigate
1 Destroyer
Sathar
1 light cruiser
The Battle
Setup
The militia are the attackers in this fight and will move first. The militia deploy in three groups: the destroyer and frigate together in the middle to take the light cruiser on directly while the assault scouts deploy into two pairs on the wings to make strafing attacks with their assault rockets. They start a speed 20.
Out gunned, the light cruiser plans to focus on the smaller faster ships in an attempt to disable the militia ships enough to escape. The light cruiser also starts at speed 20.
Initial setup for this battle. Click for full sized image.
Turn 1
The assault scouts accelerate to speed 25 while the destroyer accelerates to 23 and the frigate only accelerates to 22 allowing the destroyer to catch up to it. The sathar light cruiser accelerates to speed 23 and veers to starboard to go after the upper flight of assault scouts. All ships are out of range this round.
The ships start to close. Click for full size image
Turn 2
The militia ships continue to accelerate and close on the light cruiser from multiple directions with the assault scouts accelerating to a speed of 30 and the capital ships accelerating to a speed of 26. The light cruiser fires all of its beam weapons at the lead assault scout in the upper group. It only hits with the electron battery but induces a fire on the small ship.
The militia ships fire everything they have except their rocket batteries as they are out of range. The light cruiser fires two ICMs at each of the incoming torpedoes both of which are intercepted by the ICMs. The gunners on the destroyer are having a bad day with none of their weapons connecting. The frigate scores hits with both its laser cannon and battery knocking out the cruiser’s proton battery and slightly damaging its hull (6%). The four assault scouts only connect with one of their laser batteries damaging the cruiser’s hull (10%) but three of the assault rockets slam home knocking out 20% of the cruisers hull integrity, it’s electron battery, and a third of it’s engine capability.
Unable to bring its disruptor cannon to bear, the sathar light cruiser pulls a turn to port, accelerates to a speed of 25, and fires broadside at the militia ships. It fires a torpedo at the frigate, a rocket battery at one assault scout, and its laser battery at the other assault scout. Defensively, the militia ships fire their energy weapons again with the destroyer and frigate also firing rocket batteries at the cruiser.
Both militia rocket batteries connect damaging the hull (22%) and its combat controls systems. The frigate hits with its laser cannon knocking out the cruiser’s disruptor cannon while the destroyer with its two batteries, damaging the hull (10%) and knocking out the electron screen. The assault scouts connect with two of their laser batteries taking out the torpedo launcher and scratching the hull (1 HP). The cruiser misses with all of its weapons.
First shots exchanged. Click for full sized image.
Turn 3
The militia ships continue to pursue the carrier with the capital ships slowing to speed 23 and the assault scouts slowing to speed 25. They continue to stay outside of rocket battery range which limits the heavily damaged cruiser to just its laser battery. The fire on the assault scout knocks out its laser battery. The cruiser fires at the scout with the fire hitting it but only slightly damaging the hull (1 HP).
Once again the militia ships fire all their energy weapons and the scouts fire their assault rockets. Given the damaged state of the cruiser, the capital ships elect not to fire torpedoes. With no torpedoes incoming, the cruiser elects to fire an ICM at each of the assault rockets but it doesn’t make any difference as three of the AR impact the cruiser while one goes off course. The militia ships also hit with one laser cannon and two laser batteries. The assault rockets take out the cruisers stasis screen and ICM launcher while the laser cannon takes out the laser batteries take out 13% of the cruises hull (leaving it with only 4% hull integrity and damage its navigation control system.
The navigation control damage causes the cruiser to pull to starboard. Amazingly, the heavily damaged cruiser holds together through the turn but is then obliterated by the laser fire from the militia ships before it has a chance to get a shot off.
Final positions when the sathar light cruiser is destroyed. Click for full size image.
Final repairs
The scout manages to get the fire out immediately but its hull damage will require a day in the shipyard to repair.
Lessons Learned
The sathar cruiser really didn’t have a chance in this one against the full militia roster. Its only real hope was to get lucky and damage the engines on several of the ships to allow it to even the odds a bit and get away but that didn’t happen. Unfortunately, it was detected in the system while it was still decelerating to jump back out which greatly increased the chance that the militia, with their faster ships, could catch it. Had it been detected outbound, it would have either gotten away or, if the militia decided to press their luck, only had to engage to the two assault scouts.
This post takes us into Frontier Year 62. Things are relatively quiet with no major incursions by the sathar although they begin to step up sabotage attempts. The UPF continues to build up the Frontier Fighter Corps while replacing the ships lost in battle. The sathar are also working on replacing battle losses and commit additional resources to the war effort. They also continue to probe for new routes into the Frontier.
The HSS History’s Hope suffers a serious malfunction but recovers and continues on it’s way. This installment also sees the beginning of the events in the final module not already included, SF4: Mission to Alcazzar.
Date (FY)
Events
61.382
– SBF-J1 arrives back at SSC#10 (OFS228). The heavy cruiser under construction is moved out of the shipyard to make room for the damaged cruiser from the battle fleet.
– Work is completed on a UPF assault scout at the PGC shipyards (Gran Quivera, Prenglar) and it joins TF Prenglar at Morgaine’s World. Construction begins on another UPF assault scout.
61.383
SBF-J2 successfully jumps into the Waller Nexus system. It remains near void speed as the astrogators begin calculating the 7 light year jump to the Padda system.
61.384
– The HSS History’s Hope successfully jumps into the YS11 system. However, just minutes after the jump is completed and confirmed, a short circuit causes a fire to break out onboard. The fire is put out but not before it severely damages the hull reducing it to only 25% integrity.
– With its serious hull damage, the HSS History’s Hope begins to drift while the crew attempts repairs. After an hour an a half, the hull is patched and the ship resumes deceleration while the crew cleans up the ship. They begin calculations for the return jump to YS08.
– SG Alpha jumps into the Dramune system. It remains near jump speed and begin calculations for a jump to Fromeltar.
– Two UPF assault scouts are completed at the Hentz (Araks) shipyards. Their crews, having arrived with the FFC pilots take command of the ships immediately. They are given orders to remain in the Araks system for now and together with the FFC fighters are designated PG Tranquility. Work begins on two more assault scouts.
– A UPF fighter and assault scout, as well as the replacement assault scout for the Pale militia is completed at the Terledrom (Fromeltar) shipyards. The UPF battleship is moved into the shipyard for repairs and work begins on two more fighters.
– The second Pale assault scout is completed in the Minotaur (Theseus) shipyards and work begins on another assault scout for Spacefleet. The Pale assault scouts both depart immediately on high-speed transits to their home system.
61.385
The third assault scout for the Pale militia is completed at the CDC shipyards (Triad, Cassidine). With the new classified route linking Cassidine and Truane’s star the ship will be home after a single jump instead of the usual three. Spacefleet begins work on another assault scout
61.386
– After four days of work the damaged heavy cruiser emerges from sathar SCC#10 (OFS228) fully repaired and work resumes on the partially completed heavy cruiser that was moved out to make room.
– The assault scout from Dramune arrives and joins TF Cassidine.
61.387
Two assault scouts, replacements for the Zik-kit (Kizk-Kar) militia, emerge from the CDC shipyards (Triad, Cassidine) and begin a high-speed transit to their home system where they will join up with SF Meteor. Spacefleet begins work on a new destroyer.
61.388
SG Alpha jumps into the Fromeltar system and begins decelerating toward Terledrom to deliver the ships to Task Force Cassidine.
61.389
– Deceleration and jump calculations, along with as much damage clean-up as possible complete, the HSS History’s Hope begins accelerating for the return jump to YS08.
– Another group of 8 pilots graduate in the accelerated program at Gollwin Academy. They immediately depart for the Theseus system to take command of the fighters waiting there.
61.390
Calculations complete, SBF-J2 slips into the Void and successfully jumps to the Padda system. With the next jump being Theseus, they begin decelerating and work on calculations for a return jump to the Waller Nexus system.
61.391
– Four more fighters are completed at the Hentz (Araks) shipyards and their pilots take command of them, filling out FFC Squadron Beta.
– Two more fighters are competed at the Minotaur (Theseus) shipyards. They are crewed by militia pilots until the pilots en route from Gollwin Academy arrive.
61.392
– SG Alpha arrives at Terledrom (Fromeltar). Three of the fighters are transferred to TF Cassidine, while the other 8 are formed into FFC Squadron Gamma.
– A light cruiser is completed at Sathar SCC#5 (OFS19).
61.393
– After 40 days of operation, the CDC compound on Alcazzar (Rhianna), which had been producing at levels even higher than the previous season, suddenly goes silent. (SF4)
– SF Alpha departs for Prenglar to pick up more fighters.
61.394
– The HSS History’s Hope successfully jumps back to the YS08 system, completely mapping that route. Despite the recent fire, the crew decides to press on toward their target and begin decelerating and working on calculations for the jump back to YS11.
– The Pale militia assault scout arriving from Cassidine docks at Pale station. The crew is debriefed and the ship begins duties immediately.
– The UPF Battleship of TF Cassidine emerges from the Terledrom (Fromeltar) shipyards fully repaired. Work begins on 2 destroyers, a frigate and an assault scout.
61.395
Deceleration and calculations complete, SBF-J2 beings to accelerate for the jump back to the Waller Nexus system.
61.396
A UPF assault scout is completed at the Gran Quivera (Prenglar) shipyard and joins TF Prenglar. Work begins on another assault scout.
61.397
After months of negotiations, many energy suppliers on Terledrom (Fromeltar) and Inner Reach (Dramune) agree to join the Consolidated Nebula Energy Group. CNE begins major infrastructure rollouts on Groth (Terledrom).
61.398
Five fighters are completed in the PGC shipyards (Gran Quivera, Prenglar) and transferred to Gollwin Academy. Work begins on five more.
61.399
Successfully jumping in the Waller Nexus system, the sathar have fully plotted the jump route between Waller Nexus and Padda. SBF-J2 remains near jump speed and works on the jump back to the Liberty system.
61.400
Seven more pilots graduate in the accelerated cadet class at Gollwin Academy. They take command of fighters at the Academy, and together with the surviving fighter assigned to TF Prenglar form FFC Squadron Delta base out Morgaine’s World (Prenglar).
62.001
A strike team is assembled by CDC on Triad (Cassidine) and briefed on the Alcazzar project. They depart immediately for the Rhianna system to investigate. (SF4)
62.002
An attempt to sabotage the Inner Reach militia destroyer under construction at the Outer Reach (Dramune) shipyards is thwarted due to a last-minute tip off to the shipyard management. Star Law is called in to investigate.
62.003
– HSS History’s Hope successfully jumps back in YS11. They begin decelerating and begin work on jump calculations for the next leg of their journey, a 9 light year jump.
– The militia assault scout coming from Fromeltar arrives back at Pale station. The crew is debriefed the ship immediately resumes duties.
62.004
The sabotage attempt on the Inner Reach destroyer is quickly traced to agents tied to criminal organizations based on Outer Reach. However, the exact organization responsible is still unknown.
62.005
A frigate is completed at Sathar SCC#3 (OFS138)
62.006
– SBF-J2 successfully jumps back in the Liberty system completely charting the route between Liberty and Waller Nexus. They begin decelerating back toward Snowball.
– The Zik-Kit militia assault scouts arrive at their home station. After a day of debriefing, they begin patrol duties with SF Meteor.
– Sathar commit a portion of the production capacity of Sathar SCC#6 (OFS117) to the war effort and start ramping up production of frigates and destroyers at that center.
62.007
An inside source provides a tip to Star Law indicating that Malthar Enterprises, thought to be mostly destroyed after the events known as the “Dramune Run,” are connected with the recent sabotage attempt of the Inner Reach destroyer.
This post is only a bit over a year late. These are the events that I posted to twitter back in February of 2021 just before I stopped blogging. I’m finally getting them online. I also plan on resuming the daily Twitter posts of the events. starting on day FY61.382. If you want to get the daily updates, follow the @StarFrontiers account on twitter or the #SFTimeline hashtag. If you want to review everything that has happened, or are new to this series of posts, you can grab the PDF file linked at the bottom of the post that contains every entry in the timeline since I started it. Its up to 81 pages so there’s a bit of reading there.
Also, depending on how things go generating the timeline, I might start posting events using the GST calendar of the Frontier. Which means you’ll get 36 Frontier days worth of events every 30 Earth days as the GST calendar only has 20 hours per day instead of our 24. We’ll see if that actually pans out.
The events in this post include the two battles I posted the detail of early last year which are linked in their appropriate entries. With the conclusion of the Battle of Liberty, the war cools down for a while. The sathar are currently out of ships at the moment although they have dozens under construction. Both sides are now maneuvering to reposition and rebuild forces. Otherwise, not much happening in this post outside of the war events.
Date (FY)
Events
61.357
– Ten more pilots complete their fast-tracked certifications for the Frontier Fighter Corps. They immediately depart for Hentz (Araks).
– SBF-J2 (Liberty system) begin calculations for a jump to the Waller Nexus system.Spacefleet holds the space in anticipation of more ships finishing and beginning construction on a new battleship.
61.358
– Second Battle of Ken’zah-Kit (K’aken-Kar) – After nearly 2.5 hours of fighting TF Cassidine defeats SBF-J1 losing only a single fighter while the sathar only have a fighter and heavy cruiser surviving. Most of the UPF ships have damage requiring a shipyard to repair.
– The surviving sathar heavy cruiser and fighter from SBF-J1 accelerate for a jump to the K’sta-Kar system.
– The damaged UPF destroyer completes repairs in the Streel shipyards (Pale, Truane’s Star) and the ship that was moved out to make room resumes construction (it will be done in 23 days).
– SBF-E2 jumps into the Zebulon system. It remains at high speed and begins calculations for jump to Kazak.
– A HS:8 ship completes maintenance in the PGC shipyards (Gran Quivera, Prenglar). Spacefleet moves a couple of small ships in for maintenance to coordinate their completion with more ships finishing and beginning construction on a new battleship.
61.359
– Calculations for the jump back to YS07 complete, the HSS History’s Hope begins accelerating for the jump while the astrogators get a day of rest before double checking the figures on the way out.
– Sathar TG-1 jumps into the OFS136 system where SCC#3 is located as they continue on their journey to SCC#4 (OFS111)
– The battleship Admiral Dooltan and accompanying minelayer arrive at Zit-kit (Kisk-Kar) and join up with PG Meteor. With the addition of the battleship and minelayer, the fleet is now designated Task Force Meteor.
– After spending a day rearming, Task Force Cassidine splits up with the undamaged heavy and light cruiser, now designated Patrol Group Vigilant, departing in pursuit of the sathar heavy cruiser which is headed toward K’tsa-Kar.
– The main force of TF Cassidine, all needing time in a shipyard to fully repair, begin accelerating for a jump to the Kizk-Kar system and then on to Fromeltar. The Terledrom (Fromeltar) shipyard is notified that they will arrive on FY61.375 and begins making preparations to receive them.
– The Clarion (White Light) militia, at the request of Spacefleet, depart for a jump to K’sta-Kar to join up with PG Vigilant and patrol that system. The saurians send 3 of their 6 Battle Rays to assist.
61.360
– Calculations complete, SBF-J2 (LC & FF) begin accelerating from the Liberty system for a jump to the Waller Nexus system. PG Liberty detects the departure almost immediately and subspace radio the intel back to Spacefleet.
– Stationing 8 of the fighters at Fortress Pale as the first official squadron of the Frontier Fighter Corps, the second assault carrier currently with Strike Force Nova is designated as Shuttle Group Alpha and departs back to Triad (Cassidine) to start moving more fighters around the Frontier.
61.361
– PG Liberty are authorized to engage the outbound SBF-J2 if conditions are favorable. Several Mhemne Belter ships offer to assist although their outdated engines mean that they will only be able to make a single pass at the sathar vessels. The ships all boost for intercept.
– Four fighters are completed at the Hentz (Araks) shipyard. They are put into storage awaiting the arrival of the Spacefleet pilots. Construction beings on four more fighters.
– Two fighters are completed at the Minotaur (Theseus) shipyards for the Frontier Fighter Corps but are currently manned by the militia. Construction begins on two more fighters.
61.362
– SBF-E2 jumps into the Kazak system and begins calculations for a jump to OFS019 and SCC#5.
– Battle of Liberty – PG Liberty, augmented by Mhemne ships, engage the sathar in the outer system. The fight does not go well for the UPF who lose their frigate and an assault scout although they do manage to destroy the sathar frigate.
– After fighting the UPF in the Liberty system, the surviving sathar light cruiser of SBF-J2 continues on its course to jump to the Waller Nexus system.
61.363
– CDC staff arrive back on Alcazzar (Rhianna) in anticipation of the new mining season. (SF4)
– SBF-J1 jumps into the K’sta-Kar system. They remain at speed and begin calculations for a jump to FS33.
61.364
– The HSS History’s Hope successfully jumps back into the YS07 jump completely charting that route. They begin decelerating to turn around and jump back to YS08 to continue their journey forward.
– PG Vigilant and the Clarion militia both jump into the K’sta-Kar system from opposite directions. Keeping an eye on the retreating SBF-J1, they start deceleration toward Kwadl-Kit.
– TF Cassidine jumps into the Kizk-Kar system and begin calculations for the jump to Fromeltar. They transmit details of their recent battles to TF Meteor to share their experiences.
61.365
– SBF-E2 jumps back into the OFS019 system and begins decelerating toward SCC#5.
– SBF-J2 enters the Void and like the frigate before it, misjumps, this time ending up in the OFS196 system.
– Enough space has cleared in the CDC shipyard (Triad, Cassidine) to allow Spacefleet to begin construction on another battleship to replace one of the two lost in the Second Battle of New Pale.
61.366
– SBF-J1 jumps into the FS33 system and begins calculations for a jump to OFS166.
– Eight more fighters are completed at the PGC shipyards (Gran Quivera, Prenglar) and shuttled to Gollwin Academy. Spacefleet delays the start of construction of more fighters as production of the ships is outpacing training of pilots and they want to use the space for construction of another battleship.
61.367
– As OFS196 is a system in the sathar charts, being on the route to OFS203 and SCC#1, SBF-J2 determines it position after just two days. It decides to take the known route back to Liberty and try again.
– Enough space opens up in the PGC shipyards (Gran Quivera, Prenglar) for Spacefleet to begin construction on the second battleship to replace the second one lost in the Second Battle of New Pale.
61.368
– The HSS History’s Hope arrives in the inner system of YS07 where they will rest for a day before they begin accelerating for the jump back to YS08.
– Task Force Cassidine jumps into the Fromeltar system and begins a slow deceleration toward Terledrom and the shipyard there. They radio ahead that they are a few days early.
– Spacefleet resumes fighter construction in the PGC shipyards (Gran Quivera, Prenglar) but only producing five at a time instead of eight. The other 3 HS worth of space is dedicated to constructing an assault scout. Additionally, 3 more assault scouts are started in the CDC shipyards (Triad, Cassidine).
61.369
– PG Vigilant and the Clarion militia, together with the saurian battle rays, arrive in orbit around Kwadl-Kit (K’sta-Kar). They set up a patrol schedule to watch for new sathar threats.
– SBF-J1 jumps into the OFS166 system and begins calculations for a jump to OFS167.
– SG Alpha arrives back at the CDC shipyards (Triad, Cassidine). The fighters in storage are transferred to the carrier while they await the arrival of their pilots, scheduled to graduate from Gollwin Academy tomorrow.
61.370
– SBF-E2 arrives back at SSC#5 (OFS019). The heavy cruiser under construction is moved out of the shipyard to make room for the damaged one to receive the necessary repairs.
– Nine more pilots graduate in the accelerated cadet class at Gollwin Academy. They immediately depart to take command of the fighters currently sitting in storage at Triad (Cassidine).
61.371
SBF-J1 jumps into the OFS167 system and begins calculations for a jump to OFS169.
61.372
An attempt to explode a bomb at the Council of Worlds building while the council is in session is foiled by Star Law agents and local law enforcement. Unfortunately, none of the perpetrators survived. An investigation is launched immediately to track down the origin of the plot.
61.373
TF Cassidine arrives in orbit around Terledrom. There is currently 6 HS of open space in the shipyard and the heavily damaged frigate and fighter are moved in for repairs.
61.374
– The HSS History’s Hope jumps back to the YS08 system. They begin decelerating and working on the jump calculations for the next system, a binary system 5 ly away.
– SBF-J1 jumps into the OFS169 system and begins calculations for a jump to the OFS170 system.
– The K’aken-Kar militia assault scout, also in OFS169, happens to detect the heavy cruiser just hours after it jumps into the system. Realizing they are in sathar controlled space, the ship goes into as stealthy a mode as possible to avoid detection as they monitor the sathar vessel.
– SBF-J2 jumps back into the Liberty system.
– The TF Cassidine fighter in the Terledrom (Fromeltar) shipyard competes its repairs. The space is held in reserve for the larger ships needing repairs.
61.375
– Princess Leotia’s 35th birthday. Major celebrations are held all over Clarion (White Light) in commemoration of her coming of age. While her father had planned to step down and hand the government over to her during the ceremonies, this has been delayed due to the ongoing sathar conflict.
– SBF-J1 jumps into the OFS170 system and begins calculations for the final leg of their jump back to SSC#10 in the OFS228 system.
– PG Liberty detects the returning light cruiser and radios its presence back to Spacefleet.
– The damaged sathar heavy cruiser at SCC#5 (OFS019) completes repairs and construction is resumed on the new heavy cruiser.
61.376
Three UPF fighters are completed at the Terledrom (Fromeltar) shipyards. They are transferred to Task Force Cassidine. The shipyard space is held in reserve to fit the larger ships needing repair.
61.377
– SBF-J1 jumps back into the OFS228 system and begins decelerating toward SSC#10
– An assault scout is completed in the Outer Reach (Dramune) shipyards. It sets off immediately for the Fromeltar system to join TF Cassidine. Construction begins on a new assault scout.
61.378
– SBF-J2 arrives back in orbit around Snowball. After rearming, it sets off once again to try to jump to the Waller Nexus system.
– Calculations complete, the HSS History’s Hope begins accelerating to the next system on their route, which they designate as YS11.
– A UPF assault scout is completed at the CDC shipyards (Triad, Cassidine). This is the first of the replacement ships larger that a fighter to come out of the shipyards since the conflict began. 5 fighters are also completed and work begins on another AS and 5 fighters. The completed ships join SG Alpha.
– The first damaged frigate from TF Cassidine emerges from the shipyard at Terledrom (Fromeltar) fully repaired. The other frigate enters and work begins on it.
61.379
– The Frontier Fighter Corps pilots arrive at Hentz (Araks) to take command of their fighters there. There is some initial tension between the UPF and militia forces as the latter do not want to turn over control of the ships.
– The Spacefleet pilots arrive at Triad (Cassidine). They are immediately transferred to the carrier in SG Alpha where their ships are awaiting them. SG Alpha departs immediately for a jump to Dramune and then on to Fromeltar where the fighters are to be delivered.
– The Yazira Dome completes its second year of operation. With the on-going sathar conflict, travel has been curtailed and off-world yazirian visitors diminished but the Dome is still wildly popular with on-planet visitors.
– Detecting SBF-J2 outbound once again, PG Liberty sends a subspace message informing Spacefleet and continues to monitor the sathar ship.
– Calculations complete and checked, the HSS History’s Hope begins accelerating for the jump to the next system on their route, designated YS11.
61.380
– Sathar TG-1 arrives at SCC#4 (OFS111), joining the other ships there.
– After several back-and-forth communications, including a threat by Spacefleet to dispatch TF Prenglar to the Araks system to eliminate or take control of the militia, the Hentz militia turns over control of the Frontier Fighter Corps fighters to the UPF crews.
– The second damaged frigate from TF Cassidine completes repairs at the Terledrom (Fromeltar) shipyards. A new UPF assault scout, along with an assault scout for the local militia are also completed. This frees up enough space that TF Cassidine’s assault carrier can move in for repairs.
61.381
TF Cassidine’s assault carrier completes repairs at the Terledrom (Fromeltar) shipyards. There is not enough free space to move the battleship in, but that space will free up in three days. With 30% of the shipyard empty, the work crews can each get a full day off to rest over the next few days.
Engaged sathar forces outbound from Snowball. Lucky hit by sathar torpedo detonated magazine on UPFS Singing River (frigate) during initial engagement. Mhemne forces, together with assault scouts (UPFS Dirk and Heron) destroyed sathar frigate but UPFS Dirk lost maneuvering and pursued by sathar light cruiser. Damage to engines resulted in light cruiser overtaking and destroying UPFS Dirk. UPFS Heron remains on station in system.
*** FLASH FLASH FLASH ***
Spacefleet Signal Traffic
Background
With the loss of the single frigate comprising Exploration Group 1, the sathar decide to go with a stronger reconnaissance force and dispatch SBF-J2 (a light cruiser and frigate) to explore the route to Theseus.
Detected departing Snowball by PG Liberty, Spacefleet authorizes them to attack the sathar vessels on their way out of the system. The Mhemne offer some of their ships to help. Although limited in technology compared to the UPF and sathar vessels, the Mhemne ships will be able to make at least a single pass at the sathar vessels.
Three days out from the planet, the UPF and Mhemne forces intercept the sathar vessels.
Order of Battle
The Mhemne ships only posses limited chemical drives compared to the atomic drives of the sathar and UPF vessels and required significant help to boost up to the required speed. For the purposes of this battle they all have 25 HP, 2 ADF, 2 MR, and a laser battery. In addition, they can only use a total of 8 MR and/or ADF before their fuel supply is exhausted.
UPF
2 Assault Scouts
1 Frigate
3 Mhemne vessels
Sathar
1 Frigate
1 Light Cruiser
The Battle
Setup
The UPF are the attackers in this scenario. The sathar ships are flying in formation moving at speed 15 entering from the right of the battle area.
The three UPF ships are in a formation with the three Mhemne ships flying together nearby. They are also moving at speed 15. The plan is for the Mhemne to make a single pass at the sathar vessels firing at the frigate and then continue on while the UPF continue to engage and hopefully destroy the sathar.
Initial positions. Click for full size image.
Turn 1
The UPF and Mhemne forces drift forward maintaining their speed of 15. Perceiving the UPF forces to be the bigger threat, the sathar maneuver to take the UPF ships on head-on while also maintaining their speed of 15. No shots fires as the combatants are all out of range.
Initial maneuvering. Click for full size image.
Turn 2
Seeing that the sathar are tracking them, and hoping to draw them into the firing range of the Mhemne, the UPF forces pull up parallel the Mhemne course and accelerate to speed 19. They turn to face the oncoming sathar vessels in the hope that that will cause the sathar ships to fly up near the Mhemne vessels.
The UPF plan works (maybe too well) and the sathar accelerate to speed 16 and maneuver so that they don’t come into the forward firing arc of the frigate’s laser cannon and move into rocket battery range. However, that brings them within 20,000 km of the Mhemne ships.
Defensively, the UPF and Mhemne all focus their fire on the sathar frigate. Two of the Mhemne ships hit lightly damaging the frigates hull (5%) and knocking out its laser cannon. The UPF forces all miss.
Offensively, the sathar ships fire their energy weapons at the assault scouts and rocket weapons at the frigate. They miss the lead assault scout but the light cruiser its the second assault scout with its disruptor cannon damaging its navigation control system. They do much better against the frigate hitting it with a rocket battery and a torpedo that slips through the ICM screen destroying the UPF vessel.
Positions after initial engagement. Click for full size image.
Turn 3
With the UPF frigate destroyed right off the bat, the UPF forces are now seriously out gunned. The assault scout, its navigation controls system damaged, turns to port and accelerates to maximum to try to get away. It doesn’t have a perfect shot but fires its assault rocket at the sathar frigate. The other assault scout loops around and fires on the frigate from behind before heading off away from the sathar vessels at maximum acceleration. The Mhemne ships continue to drift away reserving their limited maneuvering in case they need it later.
Ignoring the Mhemne ships, the sathar vessels fire all their energy weapons at the two assault scouts. The lead assault scout is hit by a laser and electron battery as well as the light cruiser’s disruptor cannon seriously damaging its hull (60%) and crippling its damage control systems. The second assault scout is hit by a proton battery damaging its hull (47%).
The Mhemne ships fire at the frigate as they pass hitting with 2 laser batteries damaging the sathar vessels hull (33%). The assault scouts both fire everything at the frigate as well hitting with 1 laser battery and 2 assault rockets knocking out the frigates maneuvering (with the laser battery) before destroying it with the assault rockets.
The sathar light cruiser accelerates to chase after the assault scout directly ahead, ignoring the other ships. The assault scout fires its laser battery in defense but misses. The light cruiser fires its energy weapons at the assault scout hitting with its electron and proton batteries damaging the assault scout’s engines and knocking out its maneuvering capability.
Repair Turn 1
Neither of the assault scouts are able to effect any repairs. No other ships are currently damaged.
Positions after the first half hour. Click for full size image.
Turn 4
The UPF assault scout and Mhemne ships continue to drift away from the sathar ship. The assault scout being chased, lacking any maneuvering maxes out its acceleration as it tries to escape the pursing light cruiser.
The light cruiser hits the assault scout with its proton battery knocking out half of the assault scout’s acceleration capability. The assault scout misses the light cruiser. The light cruiser continues to accelerate as it chases the assault scout and maneuvers to come directly astern of the smaller ship. It drops a bit behind this turn but with the assault scout’s engines mostly disabled, it will close on it soon enough. It gets some extreme range shots with its energy weapons but misses.
It’s a tail chase now. The other ships are far enough away that they get away safely and we are just tracking the sathar vessel and its target. Click for full image.
Turn 5
Using what acceleration it has, the assault scout continues to speed up as it tries to get away. The LC hits it with its disruptor cannon igniting a fire. It returns fire with its laser battery but misses. The assault scout’s initial speed advantage temporarily takes it out of range of the light cruiser’s weapons.
To avoid having to draw long trails, and since relative velocity is all that really matters, I’ve adjusted the displayed speeds down. Click for full-size image.
Turn 6
The gap between the ships widen but the light cruiser’s greater acceleration will start closing it once again soon.
Repair Turn 2
Again the assault scouts fail to repair any systems.
Positions of the two ships still engaged after an hour. Click for full size image.
Turn 7
The light cruiser matches the assault scouts’ speed and will begin to overtake it on the next turn. (I forgot to save an image but it was just more of the same.)
Turn 8
The light cruiser starts to close the gap and is just out of range of its electron and proton battery weapons.
The gap between the ships start to close. Click for full size image.
Turn 9
The light cruiser closes to within 90,000 km. The assault scout fires on the cruiser with its laser battery but misses. The light cruiser fires with its energy weapons and hits with its proton battery destroying the small UPF ship.
And the fight is over after an hour and a half. Click for full size image.
Final Repairs
It takes another 8 hours but the damaged UPF assault scout manages to repair its damage control system (7 hours) and its hull (another hour).
Lessons Learned
That didn’t go at all like the UPF planned. They did manage to destroy the sathar frigate but expected their frigate to survive a bit longer. Poor shooting by the UPF and great shooting by the sathar on the first round definitely tipped things in favor of the sathar.
The Mhemne acquitted themselves well hitting with 4 of their 6 shots. Had the frigate survived the first round they might have tried to loop back around for a second pass but the quick destruction of the frigate put survival ahead of damaging the sathar.
The second assault scout almost got away but the long range hit by the light cruiser’s distruptor cannon that knocked out its engines, combined with its failed repair rolls, spelled eventual doom for that ship as it was seriously outgunned by the light cruiser.
The sathar finally won a battle but unfortunately for them it was just a minor one on the periphery of the battle.
After nearly two and half hours of fighting, Task Force Cassidine defeated the invading sathar forces destroying all but a heavy cruiser and fighter which are currently departing the system. The ships of the task force are almost all heavily damaged but only a single fighter was lost in the battle, the pilot of which ejected safely and has been recovered.
Rak’tal-ka, StarPlay News
Okay, I thought the Second Battle of Kwadl-Kit was a long one, this one went even longer. Sorry about the delay in getting it out but it took a while to play out. Task Force Cassidine just seems to like these long, spread-out battles. The map is going to really shift around this time as this fight involves a long chase and at one point it’s happening on two different maps as the battle spreads out. I hope you enjoy the narration. I also think this might now be the longest blog post yet.
Background
Fresh from the battle with the other sathar force in the K’tsa-Kar system, Task Force Cassidine is ready to face this new sathar threat. While the presence of the militia assault scout that recently disappeared trying to probe the source of the sathar fleets would have been helpful, it would not have made a lot of difference in the fight.
After the recently losses in the K’tsa-Kar and Truane’s Star systems, SBF-J1, crewed by veterans of the campaign against the saurians, look to turn the tide and chalk up a victory for the sathar forces. The fleets are fairly evenly matched with the UPF forces leaning more toward the larger ships with the loss of their assault scouts and half of their fighters in the previous engagement.
Order of Battle
This is probably the most evenly matched battle, in terms of hull points and capabilities, of any fight yet in the war. Looking at hull points, the UPF are coming into this with a total of 435 HP of ship compared to the sathar’s 441. Three of the UPF ships are slightly damaged: one fighter only has 5 of 8 HP, a frigate is at 29 of 40, and the battleship has a damaged stasis screen. Those were all battle damage that couldn’t be repaired in space after their recent battle in the K’sta-Kar system. It will be interesting to see how this one plays out.
Spacefleet (Task Force Cassidine)
3 Fighters
2 Frigates
1 Light Cruiser
1 Assault Carrier
1 Heavy Cruiser
1 Battleship
Sathar
7 Fighters
1 Frigate
1 Destroyer
2 Light Cruisers
1 Assault Carrier
1 Heavy Cruiser
The Battle
Setup
The UPF elect to battle near the planet although with no station left to defend, they start far back from the planet at a moderate speed of 15 for all ships, including the fighters. The two frigates form a battle group and the light cruiser and the battleship team up. Those two groups form the center of the battle line. The heavy cruiser escorts the assault carrier toward the bottom of the battle area while the three fighters form a flight near the top. They deploy four of the six seeker missiles available on the side of the planet the sathar will be approaching from. The heavy cruiser and battleship each retain one seeker missile in their magazines for deployment during the fight.
Like the UPF, the sathar come in at only a moderate speed to try to gauge the other side’s tactics and responses before committing. They too are only moving at speed 15 but are split up to go wide around the planet. The sathar heavy cruiser and assault carrier, escorted by a destroyer come in opposite their UPF counterparts with a flight of three fighters just off their wing. The light cruisers, escorted by a frigate, come in opposite the UPF fighters, with a flight of four fighters off their wing.
Initial positions of the ships. The seeker missiles are not shown. Click for full sized image.
Turn 1
The sathar capital ships maintain their speed and advance on the UPF forces. The fighters accelerate to speed 20 and fly farther out on the wings of the formation.
The UPF ships converge toward the lower group of sathar capital ships. The heavy cruiser and assault carrier continue to advance at speed 15. The light cruiser and battleship accelerate to speed 17, the frigates to speed 19, the fighters to speed 20.
No shots are fired this round as the two forces remain out of range.
Positions after the first turn of maneuvering. Also the seeker missiles are shown on this one for reference. Unfortunately, the file was partially corrupted and the bottom of the map was cut off but the three sathar fighters just mirrored the maneuver of the fighters at the top of the map. Click for full size image.
Turn 2
The sathar all begin accelerating toward the UPF. The group centered around the heavy cruiser accelerates to speed 17 and flies straight at their UPF counterpart while their wing of fighters accelerates to 25 and makes a pass at the same group. All the sathar ships fire at the UPF assault carrier. The upper battle group accelerates to speed 18 and turns down toward the UPF forces while the upper flight of fighters accelerates to speed 25 and sets up for an attack run next turn as they are too far away to engage this round.
Defensive, the UPF ships all focus on the flight of three lower fighters with the UPF heavy cruiser taking a long-range shot with its disruptor cannon at the sathar destroyer. They don’t do too well and of the 17 shots fired at the three fighters, only one connects with each ship, knocking the hull integrity down by half on one, inducing a navigation control hit on a second, and knocking out the maneuvering on the third. The disruptor cannon shot at the destroyer also misses.
Offensively, the sathar fare a bit better. Two of the assault rockets hit the assault carrier knocking out half its engine capability and reducing its hull integrity by 17%. The sathar destroyer hits with its laser cannon further reducing the hull integrity of the UPF assault carrier by another 19%. The heavy cruiser’s distruptor cannon knocks out the assault carrier’s masking screen launcher.
The larger UPF capital ships maintain their speeds and converge on the sathar battle group. The heavy cruiser and assault carrier fly right over the group turning up toward the planet at the end of their move. The battleship and light cruiser maneuver down to take point blank shots at the sathar as well. The frigates accelerate to speed 20 and come just in range of their rocket batteries while the fighters accelerate to speed 25 and make an assault rocket pass from below.
Defensively, the sathar ships continue to fire at the assault carrier with their energy weapons while they fire their three rocket batteries at the lead frigate. The frigate is hit by two of the rocket batteries reducing its hull integrity by 28% and knocking out a third of its maneuvering capability.
The assault carrier is hammered by the sathar’s weapons being hit by 2 electron, 2 laser, and one proton battery as wall as a laser and disruptor cannon. All told the damage knocks out all of the UPF assault carrier’s weapons, starts a fire, damages its combat control system, induces a navigation control failure, and reduces its hull integrity by another 13%.
Offensively the UPF focus on the sathar assault carrier and heavy cruiser with the frigates and fighters firing at the assault carrier and the other ships firing on the heavy cruiser.
Only one of the fighters hit the assault carrier but it scores a critical hull hit dropping the carrier’s hull integrity by 40%. The frigates combine to hit with a laser battery, laser cannon and rocket battery knocking out the carriers engines and further reducing its hull integrity by 7%.
The sathar heavy cruiser fares even worse being hit by a barrage of weapons from the UPF battleship, light cruiser and heavy cruiser. All told it is hit by all 3 distruptor cannons, 2 rocket batteries, 3 laser batteries, two proton batteries, and an electron battery. The damage knocks out the sathar heavy cruiser’s engines and maneuvering, ICM launcher, laser battery, proton screen and stasis screen, cuts it damage control ability in half, and starts a fire. Surprisingly, the weapons did little hull damage only reducing the ship’s hull integrity by 25%.
Positions and course after the first shots were fired. Click for full size image.
Turn 3
The sathar fighter and heavy cruiser, both with no MR, fly straight ahead (to the left). The fighter slows down to speed 20 while the heavy cruiser, with no ADF either, just stays at speed 17. The fighter with the navigation control hit slows to speed 20 and spins to port flying up toward the planet while the remaining fighter from the lower group accelerates to speed 20 and goes after the pair of UPF frigates. The other fighters also speed up to 30 hexes/turn and go after the frigates as well, both fighter groups looping around the planet.
The sathar assault carrier, with its navigation control hit, pull to starboard and with no ADF, flies up away from the main battle. The sathar destroyer loops around to go after the UPF frigates as well and the light cruisers and frigate decelerate back to 15 and light up for a shot at the UPF battleship. The fire on the UPF assault carrier damages its hull (5%).
Defensively, the UPF frigates fire their laser batteries at the fighters and rocket batteries at the destroyer while the other UPF ships concentrate all their fire on the lead sathar light cruiser.
The UPF frigates miss the fighters completely but hit the destroyer with two rocket batteries seriously damaging it and deducing its hull integrity by 72%. The other ships hit the sathar light cruiser with 2 laser, 2 rocket, 1 electron, and 1 proton battery knocking out its ICM launcher, engines, and stasis screen, starting a fire and reducing its hull integrity by 16%.
Offensively, the sathar fighters hit the lead UPF frigate with and assault rocket reducing its hull integrity by 43% and the second one with an assault rocket as well reducing its already damaged hull (from the previous battle) by 38%. The destroyer also hits the second UPF frigate with its electron battery and laser cannon knocking out the frigates engines.
The sathar frigate and light cruisers hammer the UPF battleship hitting it with 2 disruptor cannons, 2 proton batteries, 1 electron battery, and 2 torpedoes that slip through the battleship’s ICM screen. The weapons short circuit the battleship’s defensive system, reduce its maneuvering ability by half, knock out its proton battery and reduce its hull integrity by 66%.
The two UPF frigates, now heavily damaged, drift on their current course firing at the destroyer as they leave. The assault carrier also drifts but its navigation control hit causes it to pull to port. Despite its weakened hull, it holds together. The battleship also drifts away from the fight firing all its weapons at the damaged light cruiser.
The UPF heavy cruiser turns parallel to the course of the assault carrier but lines up for a direct shot with its disruptor cannon at the sathar destroyer. It fires its rocket battery and torpedo at the undamaged light cruiser and uses its energy batteries to fire on the sathar fighters. The light cruiser follows a similar path and firing at the same targets. The fighters loop up around the planet and come up behind the sathar frigate firing their assault rockets at it.
The fire on the sathar light cruiser and sathar heavy cruiser damages both ships’ hulls reducing their integrity by 13% and 11% respectively.
Defensively, the sathar ships continue to fire at the battleship, hoping to destroy it before it can fly out of range. The sathar assault carrier makes a long range attack at its UPF counterpart with its proton battery but misses. The sathar destroyer fires at the lead UPF frigate hitting with its electron and rocket batteries knocking out the frigate’s masking screen launcher and damaging its combat control system.
The battleship manages to get off lightly and is only hit by 2 distruptor cannons and a laser battery cutting its damage control capability in half and reducing its hull integrity by another 14%.
Offensively, the UPF battleships hits the lead sathar destroyer with its laser and 2 electron batteries and slips a torpedo through the cruiser’s ICM screen destroying it and scoring the first kill of the battle. The UPF heavy cruiser manages to get its torpedo through the other light cruiser’s ICM screen cutting the sathar ship’s maneuvering in half but otherwise missing.
The UPF fighters hit the sathar frigate with all three assault rockets destroying it completely. The sathar destroyer is hit by disruptor canons from the UPF light and heavy cruiser, as well as a laser battery and two rocket batteries from the frigates. The frigates also manage to get a torpedo through the destroyer’s ICM screen. The combined damage from the UPF weapons obliterates the sathar ship. The sathar fighters get away with only minor damage: one loses 60% of its engine capability, one has its damage control capabilities cut in half, and the third loses 38% of its hull integrity.
Repair Turn
As the ships work on repairs, the lead UPF frigate finds that it’s hull is too damaged to repair in space and must find a way to a shipyard with only 30% of its hull intact. The other frigate manages to repair a bit of its hull restoring 10% of its integrity. The UPF assault carrier puts out the on-board fire while the battleship repairs 3% of its hull.
The two sathar fighters with hull damage find that they need a shipyard to repair their hull as well with their hull integrity sitting at 62% and 50% respectively. The sathar assault carrier restores 11% of its hull integrity while the heavy cruiser gets its fire under control.
Courses and positions after a half hour of combat and repairs. Things are starting to scatter as ships are damaged and lose maneuvering capability and control or are too damaged to risk maneuvering. Ships moving off the map will have a yellow number by them showing how many hexes off the map they are. Click for full size image.
Turn 4
The flight of four sathar fighters all go after the UPF assault carrier hoping to finish it off. They loop around to make a direct assault and then fly off to chase after the UPF frigates. The lone fighter, after firing its last assault rocket at the heavy cruiser loops around and starts heading for its carrier to dock and rearm. The fighter with the navigation control damage loops to port and fires one of its assault rockets at a UPF fighter as it passes by. The remaining fighter, with no maneuvering, along with the sathar heavy cruiser in the same condition, continue to drift away from the fight. The sathar assault carrier, with its navigation control damage, pulls to starboard and passes distantly in front of the UPF cruisers and assault carrier. The remaining sathar light cruiser turns to go after the battleship hoping to finish it off.
Defensively, the UPF cruisers fire at the sathar fighters hoping to take them out before they can fire their assault rockets. The battleship fires at the light cruiser pursuing it and the frigates get a couple of distant shots at the sathar fighters.
The sathar light cruiser is hit by one of the battleship’s laser batteries and both electron batteries which score a critical hull hit (integrity reduced by 26%), knock out its ICM launcher, and damage its navigation control systems. Four of the five sathar fighters are hit by the UPF ships knocking the hull integrity down to half on one, destroying a second and damaging the assault rocket launcher on the other two (including the lone fighter going after the heavy cruiser).
Offensively, the two fighters with working assault rocket launchers firing at the assault carrier both miss while the sathar fighter with the navigation hit firing at the UPF fighter hits with its assault rocket destroying the UPF fighter, the first (and as it will turn out, only) UPF ship destroyed in the fight. The battleship is hit by the sathar light cruiser’s electron battery, proton battery, and distruptor cannon knocking out its proton screen, damaging its combat control system, and reducing its hull integrity by another 12% (only 11% remaining).
The two UPF frigates continue to drift and fire long distance shots at the fighters. The battleship drifts away from the light cruiser firing at it as it goes. The two UPF fighters loop around and take a run at the sathar light cruiser firing their last assault rockets. The UPF assault carrier pulls to starboard and runs parallel to its sathar counterpart while the UPF light and heavy cruisers maneuver directly onto the sathar assault carrier’s tail and take point blank shots with all their weapons.
Defensively, the sathar light cruiser fires at the battleship and the sathar assault carrier fires at the UPF light cruiser. The UPF light cruiser is hit by a rocket battery reducing its hull integrity by 17% while the battleship is hit by an electron battery knocking out its ICM launcher.
Offensively, the sathar light cruiser is hit by one of the battleship’s laser batteries knocking out its proton battery and by both assault rockets from the fighters which damage its combat control system and knock its hull integrity down by 20%. The lead UPF frigate manages to score a long range laser battery shot on the lead sathar fighter knocking out its assault rocket launcher. The UPF cruisers hit the sathar assault carrier with a distruptor cannon and a laser, electron, and rocket battery knocking out the carriers maneuvering, laser battery, and masking screen launcher and damaging its combat control system.
Maneuvering and positions after forty minutes of battle. The UPF are stating to score kills and the ships are really starting to scatter. Click for full size image.
Turn 5
The group of three sathar fighters sets off after the two UPF frigates, the lone fighter, with its assault rocket launcher disabled, and realizing that the assault carrier is probably not going to survive the battle, attempts to ram the UPF light cruiser. The sathar light cruiser pulls to port and slows down, firing at the two UPF fighters. The other ships just continue to drift away with the assault carrier firing at the UPF light cruiser as it drifts.
Defensively, the UPF frigates fire at the remaining fighter with a working assault rocket launcher but miss. The UPF light cruiser fires at the oncoming fighter and destroys it before it can ram the larger ship. The UPF heavy cruiser hits the sathar assault carrier with its laser and rocket battery and reduces its hull integrity by another 36%.
Offensive, the sathar fighter misses the UPF frigate with its assault rocket while the sathar light cruiser hits one of the UPF fighters damaging its combat control system. The sathar assault carrier hits the UPF light cruiser with its proton and rocket battery short circuiting the cruiser’s defensive systems and reducing its hull integrity by 20%.
The UPF assault carrier’s loss of navigation control pulls it to starboard and the fighters, out of assault rockets, start heading back to the carrier to rearm. The heavy and light cruiser stay on the tail of the sathar assault carrier while the frigates and battleship continue to drift.
Defensively, the sathar assault carrier continues to fire on the UPF light cruiser hitting with its rocket battery for another 16% hull reduction on the cruiser. All other ships are out of range.
Offensively the UPF frigates fire at the pursuing fighters but miss. The UPF cruiser open fire on the sathar assault carrier and hit with 3 laser batteries, 2 proton batteries, an electron battery, a disruptor cannon, and two torpedoes completely destroying the sathar carrier.
This is the ships off the top of the main map (UPF cruisers and frigates, sathar assault carrier and fighters). The bottom row of hexes on this map exactly correspond to the top row of hexes on the main map (below). Click for full size image.Main battle map after turn 5. Things continue to spread out. Click for full size image.
Turn 6
With their carrier destroyed and being either out of weapons or their weapon system disabled, the three sathar fighters attempt to ram the UPF frigates. The sathar light cruiser pulls to starboard and accelerates back to speed 16, the lone fighter near the planet pulls to port with its navigation damage and the other two ships continue to drift away.
Defensively, the frigates fire everything they can at the incoming fighters hitting two with their laser batteries, the lead fighter for 75% of its hull and the second for a navigation hit but not enough to destroy them before they ram. Two fighters slam into the lead frigate and despite its damaged hull fail to destroy it only taking out 20% of the remaining 30% hull integrity. The third fighter hits the second frigate for a measly 5% of its hull integrity.
The UPF frigates and battleship continue to drift, the assault carrier pulls to port and the fighters continue to close on the carrier to rearm. The heavy and light cruiser start accelerating and turn to head after the sathar light cruiser. No shots are fired as everyone is out of range.
Repair Turn 2
The lead UPF frigate repairs the damage caused by the two ramming sathar fighters but can repair its hull no further. The other frigate repairs 12% of its hull integrity while the light cruiser repairs 3% of its. The assault carrier gets its navigation control system fixed as well as repairing 8% of its hull. The battleship repairs 5% of its hull and brings is damage control system fully back on-line.
The sathar light cruiser repairs its navigation control system while the heavy cruiser discovers that a shipyard will be required to bring its damage control system back fully on-line.
The upper map after an hour of fighting. The second blue line by the assault carrier should have fighters at the end of it but I forgot to move the tokens. Click for full size image.The main battle map after an hour. The poor sathar fighter can’t get is navigation system under control and is stuck near the planet. Click for full size image.
Turn 7
With its navigation control system repaired, the sathar light cruiser sets off at max acceleration to attempt to intercept the UPF battleship and finish it off. The damaged fighter comes to a stop near the planet as the pilot continues to work on its navigation control issues.
The UPF cruisers continue in pursuit of the sathar light cruiser while the assault carrier, its hull and navigation control fixed, starts to turn around and head back toward the planet. The two surviving fighters pull alongside the carrier and start docking procedures.
We’ve now shifted the map to track the sathar light cruiser pursing the battleship and the UPF cruisers pursing it. The other ships are effectively out of the battle. The planet is some 200,000 km off the left side of this map. Click for full size image.
Turn 8
The chase continues. The sathar light cruiser continues to close on the battleship but the UPF light cruiser, which had a slight speed advantage on the sathar light cruiser, continues to close on it as well as it starts to outdistance the older heavy cruiser that has a lower acceleration. The two UPF fighters dock with the assault carrier.
The gaps between the ships are narrowing. Click for full size image.
Turn 9
Since relative speed are all that matter, I’ve adjusted the speeds shown on the maps down so that the battleship is stopped and the other three ships have been scaled accordingly.
The chase continues as the light cruisers close on their targets. The UPF heavy cruiser is as close as it is going to get to the sathar ship unless the sathar vessel’s engines are damaged as the greater acceleration of the sathar light cruiser has allowed it to match speeds with the heavy cruiser. The UPF fighters are rearmed.
Repair Turn 3
The lead UPF frigate repairs some of its maneuvering while the other frigate repairs 10% of its hull. The UPF light cruiser also repairs 10% of its hull while the assault carrier brings its laser and proton battery back on-line. The battleship, expecting to have to defend against torpedoes from the the sathar light cruiser, gets its ICM launcher working again and repairs another 5% of its hull.
The lone sathar fighter repairs some of its maneuvering capability and starts to maneuver to meet up with the heavy cruiser. The sathar light cruiser repairs 13% of its hull while the heavy cruiser restores half of its engine capability and begins accelerating to out of the system.
The ships have almost come in range of the battleship. Speeds have been adjusted so that they are relative to the battleship being at rest. Click for full size image.
Turn 10
The sathar light cruiser continues to close on the battleship and the UPF light cruiser continues to close on the sathar light cruiser. The two UPF fighters, rearmed, launch from the assault carrier and go after the lone sathar fighter near the planet.
The heavy cruiser is now starting to fall behind. Click for full size image.
Turn 11
The UPF light cruiser continues to close the gap but it is looking like the sathar ship will get to the battleship before the UPF light cruiser can intercept it. The battleship, at relative rest to the other ships, rotates to face the direction it expects the sathar vessel to come from in order to bring its disruptor cannon to bear.
It’s taken nearly an hour, but the sathar light cruiser is nearly in range of the battleship with the UPF light cruiser in hot pursuit and gaining. Click for full size image.
Turn 12
Realizing it cannot quite get into torpedo range this round, the sathar light cruiser remains at its current speed staying at extreme range for the battleship’s defenses although this will also allow the UPF light cruiser a chance to close as well.
Defensively the battleships fires all of its energy weapons at the sathar vessel but they all go wide although one of the electron batteries would have hit except for the battleship’s damaged combat control system. The sathar light cruiser returns fire but also misses.
The UPF light cruiser and heavy cruiser close in on the sathar vessel but the heavy cruiser is still well out of range. The sathar ship fires once again at the battleship this time hitting with its distruptor cannon shorting out the battleships defenses and ICMs. The battleship and light cruiser return fire. The battleship connects with a LB damaging the sathar light cruiser’s hull (11%). The UPF light cruiser is still too far away and its shots go wide.
The UPF fighters hit the sathar fighter with one of their assault rockets knocking out it’s assault rocket launcher.
Repair Turn 4
The lead UPF frigate repairs its combat control system and is now as functional as it can be without getting to a shipyard to repair its heavily damaged hull. The other frigate restores more of its engine capability. The UPF light cruiser repairs 13% of its hull while the assault carrier also gets a minor hull repair restoring 1%. The battleship focuses all of its repairs on its hull, hoping to survive the oncoming attack and restores 13% of its hull integrity.
The sathar fighter under attack by the UPF fighters finally fixes its navigation control system while the other fighter restores some of its maneuverability. The UPF light cruiser fixes its combat control system and brings its proton battery back on-line in preparation for attacking the UPF Battleship.
Shots are fired as the ships once more come in range. Click for full size image.
Turn 13
The sathar light cruiser makes a pass on the battleship firing everything it can at the larger vessel and using its maximum acceleration. The lone sathar fighter, its navigation control issues solved, begins accelerating away from the planet, hoping to surviving the next two rounds of assault rocket fire from the two UPF fighters.
Defensively, the battleship and light cruiser try to take out the sathar light cruiser before it can inflict any more damage on the battleship. The UPF light cruiser, at nearly maximum range misses, while the battleship connects with 2 laser batteries, a proton battery, and its disruptor cannon slightly damaging the cruiser’s hull (8%), knocking out its laser battery and engines, and inducing a malfunction in its navigation control system.
The sathar light cruiser returns fire with all of its function weapons but in the excitement of the moment, the gunner all miss and the battleship escapes unscathed.
The UPF light cruiser closes to torpedo range on the sathar vessel and opens fire with everything it can. The heavy cruiser continues to close and the battleship fires a long range salvo at the now retreating sathar light cruiser. The fighters again fire at the lone sathar fighter, this time hitting it with one of their assault rockets and destroying it.
Defensively the sathar light cruiser now focuses on its pursuer and fires at the UPF light cruiser hitting with both its electron and proton battery inducing a fire and damaging the light cruiser’s damage control system.
Returning fire at the sathar light cruiser, the battleship misses and the UPF light cruiser hits with its laser, electron, and proton batteries damaging the ship’s hull (14%), knocking out its rocket battery, and damaging its combat control system.
The sathar light cruiser gets its shot and fails. It probably should have stayed closer to the battleship to get one more try. Click for full size image.
Turn 14
The sathar light cruiser pulls to port and holds together. The fire on the UPF light cruiser knocks out its laser battery.
Defensively, the battleship and light cruiser fire on the sathar ship. The battleship hits with an electron and proton battery starting a fire and knocking out its stasis screen. The light cruiser hits with its proton battery and disruptor cannon knocking out the sathar ship’s disruptor cannon and electron screen.
The sathar light cruiser fires at the UPF light cruiser but misses.
The UPF light cruiser continues to tail the sathar vessel closing to rocket battery range while the heavy cruiser starts catching up with the other ships. The fire on the sathar light cruiser damages its hull (6%)
The sathar light cruiser fires on the approaching UPF light cruiser hitting with its electron and proton battery damaging its hull (4%) and knockign out a third of its engine capability.
The UPF light cruiser hits the sathar ship with its electron and rocket batteries destroying it and ending the battle.
Final moves of the fight. Click for full size image.
Turn 15
The fire on UPF light cruiser damages its navigation control system.
Repair Turn 5
The UPF light cruiser gets its fire under control, the assault carrier repairs its rocket battery but discovers that any more repair of its engines will require a shipyard, and the battleship repairs another 11% of its hull.
The sathar heavy cruiser fully repairs its engines.
Final repairs
Battle repairs of the UPF ships continue over the next four and a half hours as the ships return to orbit around Ken’zah-Kit. In the end, the second UPF frigate can only get its hull up to 65% integrity, and the battleship can only get its hull up to 58%.
The lone sathar fighter meets up with the heavy cruiser and is attached to the hull of the larger vessel where it will remain until they get back to a shipyard. It’s maneuvering is fully repaired as the ships accelerate out of the ship. The heavy cruiser gets all of its systems repaired over the next four hours expect its hull which it is only able to restore to 81% outside a shipyard.
Lessons Learned
The sathar just can’t seem to catch a break and finish off the UPF ships. I though the light cruiser was going to finish off the battleship but rolled over 80 for every single attack so it missed completely. The battleship only had about 26 HP at that point. (On a whim I rerolled all the attacks and the second time it hit with a PB and RB, the latter did double damage and destroyed the battleship. But alas, that wasn’t the actual roll.) The same with the ramming of the frigates. I thought for sure the UPF frigate hit by two fighters was going to be destroyed, it only had 12 HP left but then I just rolled 8 on 2d10 for the hull damaged sustained. And it wouldn’t have done any good for the third one to hit it as I only rolled a measly 2 HP damage for that ship as well. There were several other times where I expected the sathar to get better hits but the dice were just against them. The UPF had bad spells as well but it didn’t seem to be at those critical, ship-finishing moments.
I considered having the light cruiser ram the battleship but the odds were in the favor of the battleship avoiding the ramming attempt and if it failed, the sathar ship would have been at point blank range for both the battleship and the oncoming UPF light cruiser so it didn’t try. Although it probably should have stayed a bit closer to the battleship as it ended its movement. But I really didn’t expect it to completely miss. This does have me thinking a bit about the ramming rules, however, so there may be a blog post about that when I have time to think on it some more.
The UPF are pretty beat up with the two cruisers and a fighter as the only ships not needing to go to a shipyard for repairs, but they only lost a single fighter. The sathar on the other hand lost everything expect a fighter and a heavy cruiser. Task Force Cassidine has now destroyed two major sathar fleets while only losing 3 assault scouts and 4 fighters.
There is one more battle coming up (in the Liberty system) and then things are going to quite down a bit as the sathar just don’t have very many ships surviving at the moment. They are done to just 9 fighters, 1 cutter, 2 frigates, 1 destroyer 2 light cruisers, 2 heavy cruisers, and two assault carriers but they are spread out all over the Frontier and the starship construction centers (and two are in the battle coming up in the Liberty system and may not survive). Its going to take some time to get them all together and build a few more ships.
This is only a week later than I had planned. I’ve gotten behind on updating the timeline entries and am still trying to catch up. I’ve had some big battles to play through and I just haven’t had the time to do so. There will be another battle coming in a few days as soon as I get it played out.
The timeline this month, like last, focuses almost exclusively on the maneuvering, battles, and logistics of the Second Sathar War. There are a few entries on the HSS History’s Hope but that is really the only not war related thread I’m tracking right now. This month saw a couple of battles. There was originally going to be one more but the UPF withdrew seeing as they faced almost certain destruction.
This month also sees the fast-track completion of pilots in the current class in the Gollwin Academy to service as pilots for all the new fighters coming out of the starship construction centers for the newly formed Frontier Fighter Corps. This is a process that will continue of the next several months until all the pilots are graduated or the class completes their current training.
There might be a bit of other, non-war stuff next month but not much. The next two posts after this one will be battle reports that I’ll get up as soon as I can. Depending on how those play out, there might not be much in the way of ships left to fight for a while so things will probably quiet down.
Date (FY)
Events
61.326
– Sathar SCC#4 (OFS111) completes 5 fighters.
– The K’aken-Kar assault scout jumps into its home system and begins decelerating toward Ken’zah-Kit.
– RG One settles into orbit around Zik-kit and joins up with the rest of PG Meteor already in orbit.
61.327
SG Alpha jumps into the Fromeltar system and begins calculations for the jump to the Kizk-Kar system. The pilot of the recently completed fighter takes on extra life support and begins boosting to join SG Alpha as it transits the system.
61.328
– SBF-J1 arrives at SCC#3 (OFS138). After a rapid reprovisioning, during which orders are issued to all existing sathar vessels, SBF-J1 departs the SCC and begins accelerating for a jump to the OFS137 system.
– Sathar EG-1 jumps out of the Liberty system but does not end up in the Waller Nexus system as expected. Rather it overshoots and arrives in the Padda (FS11) system instead. The astrogators begin working out where they are at.
61.329
– SBF-J3 jumps into the OFS168 system and begins calculations for a jump to the OFS167 system.
– SBF-E3 arrives at Stenmar (Kazak) and merges with SBF-E2.
– The fighter in the Fromeltar system joins up with RG Alpha as it crosses the system for its jump to Kizk-Kar.
61.330
– The HSS History’s Hope makes the jump and ends up in a binary system but it is not the two stars of YS07. While the engineers start to work on the engine overhauls, the astrogators try to figure out where they are.
– The lone K’aken-Kar militia assault scout arrives back in its home system and the crew stands down for some leave but remain on alert for rapid recall if needed.
61.331
– SG Alpha jumps into the Kizk-Kar system and begins deceleration toward Zik-Kit and PG Meteor.
– SBF-J3 jumps into the OFS167 system and begins calculations for a jump to OFS166.
– 2 UPF fighters are completed at both the Minotaur (Theseus) and Hentz (Arak) SCC and 2 more go into production in each location. The fighters are temporarily manned by the local militias until UPF pilots and be dispatched to the system.
61.332
Realizing that they need pilots for all the new fighters being produced, the current cadets at Gollwin academy are polled for volunteers for the Frontier Fighter Corps. Those that volunteer are put on a fast completion track to get their Pilot and Rocket Weapons certifications.
61.333
– SBF-J1 jumps into the OFS137 system and begins calculations for a jump to the OFS136 system.
– SBF-J3 jumps into the OFS166 system and begins calculations for the jump to FS33 to join up with SBF-B2.
– 11 UPF fighters are completed at the CDC shipyards (Triad, Cassidine). With no pilots ready, they are put into storage and Spacefleet temporarily gives the space over for commercial ship maintenance.
61.334
– A fighter and assault carrier are completed at SCC#10 (OFS174). Instead of starting another AC and fighter, construction begins on 2 destroyers and a frigate.
– The new sathar assault carrier at SCC#10 (OFS174) collects the 3 fighters in the system and begins a transit to SCC#4 (OFS111). The ships are designated Transit Group (TG) 1.
– Astrogators aboard the HSS History’s Hope work out their position and discover that they went nearly twice as far as they intended. The system is designated YS09 and they decide to take two smaller jumps to get back to YS07 to reduce the chance of error. They begin working on jump calculations for an 8 ly jump to the next system.
– 3 more fighters are completed at the Hentz (Araks) SCC for the Frontier Fighter Corps, 2 more go into production, the other slot being given over to commercial ship maintenance for now.
61.335
Initial calculations complete, the HSS History’s Hope begins accelerating for a jump to the first system on their way back to YS07, another binary system 8 lightyears away.
61.336
– SBF-J1 jumps into the OFS136 system and begins calculations for a jump to the FS56 system.
– SG Alpha arrives at Zit-Kit (Kizk-Kar). The fighters are stationed on the planet’s surface while the assault carrier begins preparations for a trip back to Prenglar to pick up more fighters.
– SBF-J3 jumps into the FS33 system and begins decelerating to join up with SBF-B2.
– 8 fighters are complete for the Frontier Fighter Corps at the PGC shipyard (Gran Quivera, Prenglar). They are shuttled over to Gollwin academy to serve as trainers for the accelerated pilot classes. Construction begins on 8 more.
61.337
– The astrogators in sathar EG-1 are able to localize their position. Being only a single jump from Theseus, they begin calculating a jump to that system first.
– SBF-E2 leaves orbit around Stenmar (Kazak) and begins accelerating for a jump to the Zebulon system and Strike Force Nova.
– SBF-B2 leaves orbit in the inner FS33 system and begins accelerating for a jump to the K’sta-Kar and Task Force Cassidine. SBF-J3 changes course to meet them enroute.
61.338
– After another 100 days of exploiting their secret jump route between Truane’s Star and Cassidine, Obar Enterprises has grossed another 1.47 million credits. In the year since charting the route they have grossed over 6.8 million and paid off the loan on their new freighter. Given the current crisis, they turn over the details of the jump route to Spacefleet.
– Initial jump calculations complete, sathar EG-1 starts accelerating for a jump to the Theseus system.
61.339
– SBF-J1 jumps into the FS56 system and begins calculations for a jump to the Kizk-Kar system.
– SBF-J3 meets up with SBF-B2 enroute to K’sta-Kar and merges into that battle group.
– Another UPF fighter is completed at the Hentz (Araks) shipyard. The extra capacity in the shipyard will be used for the next six days to accelerate construction on two of the other fighters to get all four fighters on the same schedule.
61.340
– The HSS History’s Hope successfully jumps into their target system which they designate YS10. They immediately begin working on engine overhauls and calculations for the 6 ly jump to return to YS07.
– The initial group of more advanced students at the Gollwin Academy (Morgaine’s World, Prenglar) complete their fast-track certification for the Frontier Fighter Corps. The ten of them are dispatched to Triad to take command of some of the fighters there.
61.341
SG Alpha jumps back into the Fromeltar system and begins calculations for a jump to Dramune.
61.342
– SBF-J1 jumps into the Kisk-Kar system and begins decelerating to engage PG Meteor.
– SBF-E2 jumps into the Zebulon system and begins decelerating to engage Strike Force Nova.
– SBF-B2 jumps into the K’sta-Kar system and begins decelerating to engage Task Force Cassidine.
– The sathar battle fleets are detected within hours of their arrival in their respective systems and alerts go out across the Frontier. Spacefleet is out gunned in nearly every case but is determined to stop the worms.
– Sathar EG-1 jumps into the Theseus system. They immediately begin decelerating to stay in the outer system and begin working on calculations for a jump back to the Padda system.
61.343
– Construction of the Spacefleet battleship, Admiral Dooltan, at the Pan Galactic starship construction center orbiting Gran Quivera (Prenglar) complete. With the new sathar offensive, Spacefleet starts construction of a light cruiser, frigate, and assault scout.
– 2 assault scouts of the Theseus militia detect the sathar frigate of EG-1 and immediately begin boosting to intercept the ship. An alert goes out and the other ships of the militia boost to intercept as well although they will be two days behind.
– Suspecting FS33 to be the origin of the sathar fleets jumping into the K’sta-Kar system, the K’aken-Kar militia assault scout starts working on calculations to chart a jump route to that system.
61.344
– Construction of the Spacefleet battleship, the Admiral R’kazk’tar, at the Cassidine Development Corporation starship construction center orbiting Triad (Cassidine) completed. The crew takes command of the ship and begins a short shakedown cruise in the system as they await the arrival of the fighter pilots and SG Alpha.
– With the completion of the Admiral R’kazk’tar, Spacefleet uses the space in the shipyard to begin construction of two destroyers and two assault scouts.
– With plans to send the Admiral R’kazk’tar to Truane’s Star, the Admiral Dooltan is ordered to the Fromeltar system and then on to Kisk-Kar to take command of Task Force Meteor if the patrol group survives the coming attack.
– Detecting the incoming militia assault scouts, sathar EG-1 change their deceleration profile to try to avoid the ships while they change direction for the return jump to Padda.
– Realizing that they have an opportunity to exploit the new jump route provided by Obar Enterprises, Spacefleet HQ orders Strike Force Nova and supporting militia ships to fall back to the Truane’s Star system and expect reinforcements.
61.345
– The HSS History’s Hope successfully jumps back into the YS07 system. They begin working on engine overhauls and calculations for a jump to return to YS08.
– SG Alpha jumps into the Dramune system and begins calculations for a jump to the Cassidine system.
– SBF-E2, detecting the departure of SF Nova, vector to follow them to the Truane’s Star system.
61.346
– Unable to avoid intercept by the 2 Theseus assault scouts, the sathar frigate turns to engage them. They transmit all their jump data back to SBF-J2 before engaging.
– Battle of Theseus – In a short, 20-minute battle, the sathar frigate managed to damage one of the assault scouts before being destroyed by a single volley of assault rockets and laser batteries from the 2 militia ships. The damaged assault scout heads to Minotaur for repairs.
– Calculations complete, the K’aken-Kar assault scout begins accelerating for a jump to FS33.
– Three more fighters for the Frontier Fighter Corp are completed in Theseus. Construction begins on 3 more.
61.347
– Second Battle of Kwadl-Kit – Though outgunned by the sathar, Task Force Cassidine put up an amazing defense and over the course of 1.5 hours completely destroys the sathar fleet. While almost no ship goes unscathed, they only lose 3 fighters and 3 assault scouts.
– SG Alpha jumps into the Cassidine system and begins vectoring for a jump to the Truane’s Star system using coordinates provided by battleship Admiral R’kazk’tar.
– After a detailed assessment of the strength of SFB-J1, PG Meteor and Spacefleet command decided that they cannot hold the Kizk-Kar system and the jump capable ships start accelerating for a jump to the Fromeltar system. The fighters go into hiding on the planet’s surface.
– Seeing PG Meteor departing, the sathar forces vector to intercept but the acceleration of the UPF ships is such that only the smaller sathar vessels could intercept which would give the advantage to Spacefleet. After a few hours of pursuit, they reverse course and settle into orbit once again around Zit-Kit.
61.348
– Sathar SCC#1 (OFS203) completes construction of a light cruiser.
– Arriving back at Minotaur (Theseus), the damaged militia assault scout is immediately put into the shipyard. A HS:7 ship under construction is moved out to make room.
– 5 fighters are completed at the CDC shipyards (Triad, Cassidine). Work begins on five more. These fighters are put in storage until crews can be obtained for them.
61.349
– SF Nova and its supporting militia ships jump into the Truane’s Star system and begin decelerating toward Pale.
– The group of 10 FFC pilots arrive at Triad (Cassidine) and take command of their fighters. They immediately take on extra life support and begin a high-g boost, together with the battleship Admiral R’kazk’tar, to join SG Alpha.
– After a day rearming, Task Force Cassidine begins acceleration for a jump to the K’aken-Kar system and then on to Kizk-Kar to engage the sathar forces there.
– The Theseus militia assault scout completes its repairs and the HS:7 ship is moved back in to resume work.
– The battleship Admiral Dooltan jumps into the Cassidine system, it remains at high speed to transit to Dramune.
61.350
– Joining up with SG Alpha, the fighters are quickly taken aboard the carrier and stowed for jump. The battleship, assault carrier, and fighters are designated Task Force Relief and prepare for level 2 risk jump to the Truane’s Star system.
– SBF-E2 jumps into the Truane’s Star system and begins decelerating toward New Pale. SF Nova and the local militia begin maneuvering to intercept.
– SBF-J1 departs orbit around Zit-Kit (Kisk-Kar) and begins accelerating for a jump to the K’aken-Kar system to intercept TF Cassidine.
– Detecting the departure of SBF-J1, PG Meteor puts its jump on hold and drifts in the outer system to observe.
– The UPF minelayer, currently in the Fromeltar system, begins accelerating for a jump to the Kisk-Kar system. It will join up with the Admiral Dooltan as it transits the Fromeltar system before making the jump.
61.351
– TF Relief jumps into the Truane’s Star system and begins a hard deceleration toward New Pale.
– The K’aken-Kar militia assault scout misjumps and instead of reaching FS33 ends up in an unknown star system (OFS169). They begin working on determining their location.
– With a HS:12 ship completing maintenance in the CDC (Triad, Cassidine) shipyards, Spacefleet starts work on 3 new assault scouts to replace those lost by Task Force Cassidine. The remaining space is used for civilian ship maintenance.
– The battleship Admiral Dooltan jumps into the Fromeltar system. It begins vectoring and performing jump calculations to take it to Kisk-Kar.
61.352
– The HSS History’s Hope makes the return jump to YS08 and begin decelerating toward the inner system as they once again overhaul engines and try to plot the route back to YS07.
– Seeing that SBF-J1 seems to be committed to jumping out of the Kisk-Kar system, PG Meteor changes course and starts to decelerate back toward Zit-Kit.
– A fighter is completed at the PGC shipyards (Gran Quivera, Prenglar). It is transferred to Gollwin Academy (Morgaine’s World, Prenglar) for use in training the accelerated cadets.
– Detecting TF Relief, the sathar reassess their position and despite being out gunned nearly two to one, press on toward New Pale and the UPF forces.
61.353
– Strike Force Nova and the Truane’s Star militia ships arrive back at the armed station orbiting New Pale (Truane’s Star). Just hours later, they are joined by TF Relief. The incoming sathar ships are only a day away.
– The UPF minelayer in the Fromeltar system joins up with the Admiral Dooltan and then continue on their way to the Kisk-Kar system to join with PG Meteor.
61.354
– Second Battle of New Pale – The UPF destroy or drive off most of SBF-E2 but both battleships, including the newly constructed Admiral R’kazk’tar, are destroyed in the fighting.
– The fleeing sathar ships accelerate for a jump back to the Zebulon system.
– The UPF destroyer damaged in the Second Battle of New Pale heads to the starship construction center on Pale for repairs.
– TF Cassidine jumps into the K’aken-Kar system. Alerted that SBF-J1 is headed their way, they begin decelerating toward the inner system instead of continuing on the Kisk-Kar.
– Another UPF fighter is completed at the Terledrom (Fromeltar) shipyard. It is temporarily manned by militia forces until Spacefleet can get fighter pilots to the system.
61.355
– SBF-J1 jumps into the K’aken-Kar system and begins decelerating to intercept TF Cassidine.
– The UPF battleship and minelayer jump into the Kisk-Kar system and start decelerating toward Zit-kit.
– The damaged UPF destroyer arrives at the Streel shipyard (Pale, Truane’s Star). A HS:6 ship under construction but nearly complete is temporarily moved out to provide priority access for the Spacefleet vessel.
61.356
– PG Meteor arrives back in orbit around Zit-Kit (Kisk-Kar).
– A HS:5 ships complete maintenance in the CDC shipyard (Triad, Cassidine). Spacefleet holds the space in anticipation of more ships finishing and beginning construction on a new battleship.
In a short, high-speed battle around New Pale today, the invading sathar forces were destroyed or driven off by the militia and the augmented Strike Force Nova.
The victory was not with out cost, however, as both UPF battleships were destroyed in the fighting, along with one of the UPF fighters. While the sathar losses were much higher, we mourn the loss of the crews of those ships
Goolar Nadd, New Pale News
Background
With the arrival of Task Force Relief (battleship, assault carrier, and 10 fighters) and its merger with Strike Force Nova, the UPF and Truane’s Star militia outgun the invading sathar fleet nearly two to one. Despite these odds, the sathar continue on to engage the UPF forces although they aim for New Pale instead of Pale to avoid the UPF Fortress at that world.
Order of Battle
Pale Militia
Armed Station
1 Assault Scout
1 Frigate
Strike Force Nova
17 Fighters
3 Assault Scouts
3 Frigates
1 Destroyer
3 Light Cruisers
2 Assault Carriers
2 Battleships
Sathar
8 Fighters
1 Cutter
2 Frigates
2 Destroyers
1 Light Cruiser
1 Assault Carrier
2 Heavy Cruisers
The Battle
Setup
Expecting the sathar to make a run at the station as they have in other systems (and in the battle here over a month ago), the UPF position the battleships on either side of the planet, one supported by a destroyer and the other a light cruiser. Out from the battleships is a pair of frigates on each side with a pair of assault scouts out and slightly back from the frigates. There are two wings of fighters beyond and a bit back from each pair of assault scouts. The assault carriers, each escorted by a light cruiser, are far back from the planet. The capital ships and assault scouts are all moving at speed 15, the assault scouts are at speed 20, and the fighters are at speed 30. The eight seeker missiles from the two battleships are arrayed in an arc around the planet.
The sathar, recognizing that they are not going to win this fight, are planning a high speed pass hoping to take out the UPF battleships and assault carriers and then escaping the system. They line up in two groups directly opposite the battleships. The upper group is comprised of a heavy and light cruiser, a destroyer, and a frigate while the lower group is composed of a heavy cruiser, the assault carrier and cutter, and a destroyer and frigate. The fighters are divided into two flights of four, one on each wing. All of the sathar vessels come in much faster than the UPF expected and are moving at speed 35.
Positions of ships and seeker missiles at the beginning of the battle. The two main groups of sathar ships are represented by a single marker with the actual ships displayed at the top and bottom of the map. Click for full size image.
Turn 1
The sathar capital ships accelerate to speed 37 and fly straight at and past the UPF battleships. The fighters accelerate to speed 40 turning in to fire at the battleships as well.
Defensively the assault scouts and frigates fire their laser batteries at the fighters and the frigates fire their rocket batteries at their sathar counterparts in each group. The battleship and destroyer in the upper group, along with the station, fire at the sathar destroyer, while the battleship and light cruiser in the lower group fire at the assault carrier.
The defensive fire at the sathar fighters is fairly ineffective, slightly damaging the engines on three fighters and knocking the hull integrity down to 38% on two others. However, none are destroyed and all are able to fire their assault rockets at the battleships.
The sathar frigate in the upper group is hit by a rocket battery knocking out 30% of its hull while the sathar frigate in the lower group is hit by two rocket batteries knocking out its laser battery and slightly damaging its maneuvering.
The destroyer in the upper group is pummeled by the UPF destroyer and battleship being hit with 2 laser batteries, 3 electron batteries, a proton battery, a rocket battery and the cannons from both ships. In the end, it has it defenses knocked off-line, its electron battery and engines knocked out, a hit to its combat controls system, its hull integrity reduced by 68%, and a fire breaks out on-board.
The assault carrier in the lower group doesn’t fare much better. It is hit by 2 laser batteries, an electron battery, 2 proton batteries, a disruptor cannon and a rocket battery. It loses its laser battery and 65% of its hull integrity.
The sathar unload all of their weapons at the battleship they fly over with the battleships firing 3 ICMs at each incoming torpedo.
The Admiral Clinton (upper battleship) is hammered. All 4 assault rockets from the fighters hit knocking out its engines and maneuvering capability and reducing its hull integrity by 22%. The sathar frigate hits it with its laser cannon knocking out the battleship’s disruptor cannon. The sathar destroyer hits with its laser cannon, rocket battery, and a torpedo that slipped through the ICM screen knocking out the battleship’s torpedo and ICM launchers and knocking the hull integrity down another 16%. The sathar light cruiser lands a series of hull hits with its disruptor cannon and electron and rocket batteries reducing the battleships hull by another 28%. Finally, the sathar heavy cruiser hits with its laser, electron, and proton batteries as well as its disruptor cannon knocking out the battleship’s proton screen, damaging its combat control system and reduces its hull integrity by another 28%. In the end, the Admiral Clinton has only 6% of its hull integrity left.
The sathar is the lower group were not as effective firing on the new UPF battleship, the Admiral R’kazk’tar. Only one of the four assault rockets connect knocking out the battleship’s disruptor cannon while the cutter misses completely. The sathar frigate hits with everything but its torpedo knocking out the battleship’s torpedo and ICM launcher and knocking half of its engines off-line. The sathar destroyer hits will everything expect its torpedo inducing an on-board fire and knocking out 35% of the battleship’s hull integrity. The sathar assault carrier scores a minor (<2%) hull hit with its laser battery while the sathar heavy cruiser only hits with it’s laser battery and disruptor cannon cutting the battleship’s maneuvering in half and knocking the hull integrity down another 13%.
Each sathar heavy cruiser deploys a single seeker missile, about 40,000 km behind their final positions where they expect the UPF to end the movement to fire their torpedoes at maximum range.
The maneuvering on this turn was so complicated, that I almost did a sathar movement map and a UPF movement one but in the end I left them on the same map. It’s a bit confusing but so was the maneuvering.
The seriously wounded battleship drifts away from the fight and two frigates join it as escorts. The other battleship, its MR reduced by half, turns and uses the gravity of New Pale to gain an extra turn. The other ships also loop around the planet, accelerating as much as possible to come around and bring all their weapons to bear on the various sathar vessels. The fighters split their fire between the heavy cruiser and frigate in the upper group, and the heavy cruiser and assault carrier in the lower group, assisted by the assault scouts firing on the heavy cruisers as well. The other ships focus their fire on the smaller more maneuverable ships. The assault carriers and their escorts accelerate and cross the sathar battle line hoping to get out of the maneuvering arc of the larger ships. They fire what weapons they can at the sathar fighters. The fire on the sathar destroyer knocks out its laser cannon.
Defensively, the upper flight of sathar ships focus their particle battery weapons at the damaged battleship, hoping to finish it off but they all miss. They use their laser batteries defensively against the fighters destroying one, nearly destroying another, lightly damaging the engines on a third. They fire their rocket batteries at the light cruiser but they all miss.
In the lower group of sathar ships, all the beam weapons are focused on the fighters but only one hits damaging the fighter’s combat control system while the rocket batteries are fired at the UPF destroyer but they all miss as well.
The upper UPF assault carrier connected with its laser and proton battery destroying one fighter and knocking out the assault rocket launcher on the other. The lower assault carrier hits with it’s proton battery and almost takes out a figher but it manages to hold togheter. The carrier’s light cruiser escort hits the same fighter with its laser battery, damaging the fighter’s engines, and a different fighter with it’s proton battery damaging its maneuverability.
The sathar heavy cruiser in the upper group is hit by 5 assault rockets and a laser battery from the fighters and assault scouts which damage its combat control system, short circuits its defenses, and reduces its hull integrity by 98% nearly destroying it.
The sathar heavy cruiser in the lower group gets away fairly unscathed as it is only hit by 3 assault rockets from the fighters and assault scouts knocking out its ICM launcher and maneuvering and reducing its hull integrity by 16%.
The sathar frigate in the upper group is hit by 2 assault rockets from the fighters as well as an electron batter, disruptor cannon, and torpedo from the light cruiser which knock out its defenses before the torpedo destroyers the ship.
The final fighter flight hits the upper sathar assault carrier with four assault rockets destroying it. while the sathar destroyer is destroyed by its UPF counterpart which hit with its laser and rocket batteries as well as torpedo that got through the ICM screen.
The sathar frigate in the lower group is hit by its UPF counterpart with a laser battery that damages its maneuvering and a torpedo that slips through the ICM screen but only manages to take out the frigate’s laser battery.
Maneuvering and final positions after the first ten minutes of battle. Click for full size image.
Turn 2
With the assault carrier destroyed, the sathar fighters are stranded and so continue the attack on the battleships. The flight that lost a fighter loops around to go after the heavily wounded battleship (Admiral Clinton) while the other group goes after the less damaged one. The heavily damaged heavy cruiser just drifts away from the battle while the light cruiser from the upper group turns to make a pass at the less damaged battleship (Admiral R’kazk’tar) as it accelerates away from the battle. The lower group, minus the destroyed assault carrier, just accelerate straight away from the battle at the heavy cruiser’s max acceleration (it has 0 MR), staying in formation. They fire on the UPF destroyer as they fly away. The fire on the Admiral R’kazk’tar induces a navigation control hit.
The sathar also activate the two seeker missiles they deployed the previous round. Unfortunately for the sathar, the UPF did not react as expected and the only ships nearby are the assault scouts. Each seeker missile goes after one of the assault scouts but they both miss.
Defensively, the battleships fire at the incoming fighters as do the assault scouts and the frigates escorting the heavily damaged battleship. They are assisted by the station and the lower assault carrier and it’s escort. Together the UPF ships manage to destroy two of the three fighters headed for the Admiral Clinton and two of the four headed for the Admiral R’kazk’tar, inducing a fire on a third.
The upper light cruiser and assault carrier fire at the light cruiser as it passes. It is hit by 2 laser, an electron, and 2 rocket batteries damaging its combat control system and engines, knocking out its ICM launcher and reducing its hull integrity by 23%.
The lone light cruiser fires at the drifting heavy cruiser connecting with a rocket battery and its disruptor cannon destroying the heavily damaged sathar vessel.
Finally, the group of frigates and destroyer focus their fire on the fleeing heavy cruiser from the lower group connecting with 3 laser batteries, a rocket battery and a laser cannon damaging the heavy cruiser’s combat control system and reducing its hull integrity by 46%.
Offensively, the surviving figher manages to hit the Admiral Clinton with its assault rocket destroying the battleship. The Admiral R’kazk’tar is hit by an assault rocket from the two fighers and a torpededo from the light cruiser reducing its hull integrity by another 36%.
The fire from the remaining ships are focused on the UPF destroyer. It is hit by 4 laser batteries and an electron battery which knock out its masking screen launcher, short circuit its defensive systems, and reduces its hull integrity by 46%.
The surviving battleship, with its navigation control damage and seriously damaged hull, pulls to starboard but manages to hold together. Given the speed differentials, and despite the greater acceleration of the smaller UPF ships, Spacefleet decides to not purse the main surviving group of sathar vessels but the upper two flight of fighters do go after the lone light cruiser. The assault scouts and the frigate and destroyer group go after the surviving sathar fighters. The fire on the sathar fighter induces a navigation control hit. The fire on the light cruiser cause 9 HP of damage.
Defensively, the sathar light cruiser fires at the incoming fighters but only manages to hit one with a proton battery lightly damaging its hull.
Offensively, the UPF fighters hit the light cruiser with all eight assault rockets destroying it while the frigates and destroyer destroy two of the three surviving fighters with the remaining fighter having its combat control system damaged, its assault rocket launcher knocked out, its hull integrity reduced by 38% and a fire started onboard.
Final positions after the second round of combat, the destroyed sathar light cruiser, damaged UPF battleship and UPF fighters are off the top of the map while the fleeing sathar ships are off the left side. Click for full size image.
Turn 3
The fire on the battleship burns through the hull reducing its hull integrity by another 10%. Its navigation control damage causes the large ship to pull to port and the strain on its severely damaged hull causes it to break apart destroying the vessel after only 10 days of active duty. The remaining sathar fighter is obliterated by the combined fire of the destroyer and frigates.
Repair Turn 1
The lightly damaged fighters manage to repair their systems almost immediately and the destroyer manages to repair some of its hull. The sathar heavy cruiser manages to repair some of its hull as well.
Final Repairs
After another hour and a half the damaged UPF destroyer manages to fix as much as it can in space. All of its systems are fixed but the hull is stuck at 66% integrity and it will need to get into the starship construction center at Pale to complete repairs.
After another hour the sathar heavy cruiser has repaired enough of its hull that the surviving ships resume their acceleration out of the system. Another 2.5 hours later, it has repaired as much as it can outside of a shipyard. All of the internals systems are back online but it’s hull is stuck at 75% integrity until it gets back to SSC#5 for final repairs.
Lessons Learned
I knew the sathar were going to lose this one but I expected them to do a little better than they did. They managed to take out the two battleships, part of their primary objective, but didn’t do as much collateral damage as I was expecting/hoping they would. Part of that was the dice were just not cooperative, especially on the defensive fire round of the UPF move in turn one. I rolled a bunch of 80’s on the sathar’s to hit rolls and nothing really connected. Although the same thing happened to the UPF at another point so I guess it evens out.
The sathar misjudged the positions on the first round and were unable to make pass at the assault carriers like they wanted. They managed to get some ships out of the battle but not as many as I was hoping they would. The UPF really cleaned up.
The loss of the battleships will be significant, those won’t be replaced anytime soon. It will be interesting to see how that affects the fights going forward.
What are your thoughts on the battle? Share in the comments below.
As I’ve been working/playing through the Second Sathar War in the Detailed Frontier Timeline, I’ve used a bunch of designations for the various groups of ships that the UPF has created. It thought I’d give a quick overview of how I’m using them and what each name represents. This may evolve in the future, but it’s what I’m using at the moment.
Some Background
In the setting material, there are two designations explicitly given, namely Task Force (Prenglar and Cassidine) and Strike Force (Nova). It then goes on to say there are other patrol groups and strike forces exist. The exact quote from the rules is:
Each of these battleships is the flagship of a fleet task force. Task Force Cassidine (flagship: Admiral Harsevoort) is centered at Triad; Task Force Prenglar (flagship: Admiral Morgaine) is based at the UPF base orbiting Morgaine’s World; and Strike Force NOVA (flagship: Admiral Clinton) has a home base at Gran Ouivera, but spends much time patrolling the travel lanes of the Frontier.
Many smaller strike forces and patrol groups are active throughout the Frontier. The composition of these task forces does not remain constant, as ships are often reassigned from one group to the other. The patrol groups usually consist of one or two assault scouts and a frigate. Small strike forces often contain several frigates, a destroyer and a light cruiser.
p48 -Knight Hawks Campaign Book
From there, I’ve expanded things out a bit. Here’s what I’m currently doing.
Designations
Task Force (TF)
A task force is a large group of ships, centered on a battleship or heavy cruiser, that is organized for a specific purpose. In the case of Task Force Prenglar and Cassidine, I see that purpose as the defense of the two core worlds of the Frontier, which is why these task forces include the UPF minelayers and are named for the systems they defend.
Strike Force (SF)
Similar to a task force, a strike force is a larger group of ships that is centered on a light cruiser or larger vessel (but not an assault carrier, these are always ancillary vessels). The main purpose of a strike force is rapid deployment and offensive action.
The main difference between a task force and a strike force (other than the light cruiser requirement) is speed. In a strike force, no ship can have an ADF of less then two and thus the strike force is capable of risk jumps. The inclusion of a minelayer, with its ion drives and ADF of one, precludes this designation. For example, in the Detailed Frontier Timeline, the group that was going to be Strike Force Meteor initially has a minelayer added to it when the battleship arrives (in a few days from now in the timeline as I post this) so it gets the Task Force Designation instead of the Strike Force as originally intended. When the minelayer leaves, it will probably be reverted to the Strike Force designation.
As I’m writing this, I thought of a related designation that I have never used. That would be Rapid Strike Force (RSF) and would be a group that is all light cruisers or smaller and have a minimum ADF of 3. There would be no fighters or assault carriers in this group. But maybe that’s being a bit to specific.
Patrol Group (PG)
This is the generic designation for any group of Spacefleet vessels but typically carries the connotation of a traveling group that is moving around the Frontier. These groups could be organized for any reason, from pirate deterrence, to exploration, to local militia support, to just showing force around the Frontier.
A notable example of this from the Detailed Frontier Timeline was Patrol Group Virgo. Originally constructed to be a show of force in the Dixon’s Star system to help cool the corporate war heating up between PGC and Streel, it was augmented by some Streel vessels and the Truane’s Star militia to deploy to the Zebulon system to counter the imminent sathar threat there. (Had these ideas been more crystalized in my mind back then, I probably would have changed the designation at that point to Strike Force.) After that fight, and with the events surrounding the militia/civilian Discovery Squadron, they were deployed into the Rim to support the Flight. Thus they took on a number of different roles before finally being dissolved.
Repair Group (RG)
This is one I made up for the timeline. I needed a designation that allowed me to refer to a small group of ships that were currently non-combatants that were traveling to a shipyard for repairs and so the repair group was born. I don’t know that this one would get used much outside of wartime but I’m still thinking through its use.
Shuttle Group (SG)
This is another one I made up for the timeline but imagine that it could be used regularly. The specific use I invented it for was a designation to give an assault carrier that was transporting fighters between the shipyards and the systems (that don’t contain shipyards) where those fighters were going to be stationed.
The thought was that this was primarily for a non-combat role but if an assault carrier with 8-12 fighters showed up, pirates might very well think twice as they are definitely combat capable, especially against small numbers of vessels. But I can also see it being used in other contexts. For example, if you use the Jump Tug (Star Frontiersman issue 9, also a write-up on the starfrontiers.us website) in your setting, I can see Spacefleet having a few of these to move assault scouts and fighters over long distances to save on having to do overhauls every jump. In any case, this designation would be used for any group of ships, military or civilian, used by Spacefleet to rearrange their assets in the Frontier.
A Note on Sathar Designations
If you’re following the Detailed Frontier Timeline, you will have noticed that I’m referring to all the sathar fleets using SBF designations. SBF is short for “sathar battle fleet.” The SBF designation is then followed by a letter-number combination, i.e. SBF-E1 or SBF-J3. The letter designation simply represents the sathar starship construction center the fleet originated from and the number is just incremented for each fleet.
This was just a shorthand to help me keep track of the sathar ships. It doesn’t even reflect how Spacefleet would refer to them. They would probably either refer to them by the system they first appeared in or just give them incrementing some index for them.
Your Thoughts
Those are the designations that I’m currently using. Beyond the three main fleets (TF Prenglar, TF Cassidine, & SF Nova) I see most of the Spacefleet ships grouped into Patrol Groups as this is the generic designation. The others have more specific uses.
What designations (if any) do you use in your game? What other ones do you imagine Spacefleet using? Share your ideas in the comments below.