Scenario Book 1 (SFU)

From Trekipedia
Jump to: navigation, search
Scenario Book 1
Cover

Cover
Published 1992
Advertising

SG34.0 Merchant, Pirate, Soldier, Spy

by Stephen V. Cole
Previously published as "SL27.0 Merchant, Pirate, Soldier, Spy" in Captain's Log Issue 2.

Wars tend to be confusing times, and not everything is as it seems. Take the case of a starship commander, patrolling a distant portion of the frontier, out of immediate contact with his superiors, who comes upon a pirate ship molesting a convoy. As he approaches, one freighter lashes out with sudden fury at the pirate. "Q-ship!" the commander gloats, "We've got the pirate now!" Before he can reach battle range, however, the sub-space communication system comes alive with claims and accusations.

"This is Fleet Captain Andros in the pirate vessel. We are not pirates but a naval unit on a secret naval mission. Security idenfication X3-54G. What appears to be one of our Q-ships is, in fact, a pirate marauder. We lured him here for a rendezvous. Please render assistance in capturing him."

"This is Captain Gran in the Q-ship. We are a naval unit on a secret mission. Security identification Y7-23T. The pirate ship is an enemy spy, not a pirate. Please render assistance in capturing him."

"Dammit, he's the spy, not me. Don't you remember me from the Academy? We used to go to the beer gardens together!"

"Don't fall for that! He may have been a spy even then!"

"Convoy leader, can you confirm the identity of the Q-ship?"

"Negative. He joined us after we cleared port. None of us have been on board his ship."

"This is the Q-ship. What would you expect from a secret naval mission?"

"Or from a pirate!"

The commander was perplexed, to say the least. Both identification codes were valid; both ships claimed to be clandestine units of his own navy. Either might be a pirate, spy, or friend. Worse, they might both be enemies, or they might both be friends!

Related Data


SH50.0 Landing Party

by Graeme Cree
Previously published as "SL28.0 Landing Party" in Captain's Log Issue 2.

In Y155, as tensions grew between the Federation and the Klingon Empire, the Federation accelerated its efforts to survey planets in the neutral zone. The Klingons considered these surveys to be a "provocation," and used them to create incidents.

On one such mission, the light cruiser Texas, under Commander Nita Howell, was making a standard survey of Vanecek VI when cosmic radiation from a solar flare forced the Texas to withdraw for 31.8 hours. A landing party had been previously transported to the surface, and remained behind (protected by the atmosphere) to complete the survey. When the Texas returned to the system, however, it found that a Klingon battlecruiser had entered the system and was blocking the way.

Related Data


SH51.0 The Federation Exchange

by Jeffrey L. Moore
Previously published as "SL31.0 The Federation Exchange" in Captain's Log Issue 2.

Even during wartime, the Orions managed to maintain trade across the Federation-Klingon border. In one case, the Federation captured a freighter under Orion control and, after some fast plea-bargaining, obtained the coordinates for a planned rendezvous with the Klingons. The Federation was able to substitute a Q-ship for the captured freighter, giving the Klingons a considerable surprise.

Related Data


SH52.0 Who Invited the Romulans?

by Evan Tingley
Previously published as "SL18.0 Who Invited the Romulans?" in Captain's Log Issue 1.

In Y157 a small incident on the Gorn-Federation border (the first contact between those two races) almost touch­ed off a major war. The two races, however, quickly realiz­ed that they were a great deal alike in their desire to avoid conflict (although radically different physically). Still suspicious of each other, delegations of the two races agreed to meet in a neutral area (an asteroid belt) to discuss the situation. It was agreed that only Starliner Pods would approach the meeting site. The Romulans (mortal enemies of both the Federation and the Gorns) sought to prevent the meeting, or better yet, leave both parties feeling they had been betrayed.

Related Data


SH55.0 Mercy Mission

by Don Jacques
Previously published as "SL39.0 Mercy Mission" in Captain's Log Issue 2.

In Y164, the Federation tug al Rashid was routinely carrying personnel and cargo to a Federation base station near the point where the Federation bordered the Kzinti and Klingon Empires. Tragedy struck unexpectedly. The tug's APR leaked, spreading deadly fumes throughout the ship and the pods it was carrying. Many crewmembers became ill; some died. The ship's warp engine controls locked, sending the ship on an uncontrolled plunge into the neutral zone. Eventually, the controls were unlocked with explosive charges, stopping the ship, but leaving the left warp engine out of commission and the ship incapable of movement.

No Federation ships were nearby, but two Kzinti ships arrived and offered to tow the al Rashid toward the Federation border, expecting to rendezvous with a Federation squadron dispatched to the rescue. Before the ships could proceed, however, two Klingon ships arrived. The Klingon commander offered to "rescue" the tug from the "Kzinti pirates" and tow it to a convenient Klingon base, and he wouldn't take "no" for an answer.

Related Data


SH57.0 Diplomatic Disaster

by Michael J. Jaski
Previously published as "SL34.0 Diplomatic Disaster" in Captain's Log Issue 2.

In Y165, a group of Federation officials was on a tour of the frontier worlds near the Romulan border. The Romulans attempted to assassinate the diplomats by sending a force of ships into Federation space. A Romulan spy, disguised as a Federation officer, set off a bomb in the tug's left engine, disabling its warp drive.

Related Data


SH60.0 Practice, Practice, and Then What?

by Frank Crull
Previously published as "SL30.0 Practice, Practice, and Then What?" in Captain's Log Issue 2.

In Y171, the Federation and the Gorn were conducting a series of wargames in a special training zone. The exercises were necessary to give Federation captains experience in dealing with the Romulan Sparrowhawk and its three plasma torpedo launchers. These games used computer-generated battle damage simulations. As each ship scored "damage" (using weapons set on 1/1000th power) on the other, the computer analyzed the attack and "turned off" certain systems to simulate the damage.

The system worked well enough for training, but on one memorable occasion a Romulan Sparrowhawk arrived in the training area to find two "badly damaged" ships that were not expecting to conduct actual combat.

Related Data


SH61.0 Fleet of the Moment

by Jonathan D. Schuster
Previously published as "SL16.0 The Fleet of the Moment" in Captain's Log Issue 1.

In the early years of the General War, the large number of warships constantly on patrol made it hard for the Orion Pirates to maintain business as usual.

A prime example of this occurred in Y172, when an Orion raiding force, returning from Kzinti territory to their base, found themselves between Federation and Klingon squadrons preparing for a battle.

Related Data


SH62.0 Mutiny on the Demonslayer

by Douglas Jew
Previously published as "SL26.0 Who Invited the Romulans?" in Captain's Log Issue 2.

In Y175, the Klingon D-7C command cruiser Demonslayer mutinied. This time, however, the mutineers were Klingons! Commodore Jark Valgan had attempted to gain his promotion to admiral, which he considered to be long overdue, by assassinating his commander. When the plot failed, Valgan fled for his life toward Kzinti space. His officers had been deeply involved in the plot, and most supported his decision to flee. The crew, who knew that whatever happened they were along for the ride, did not oppose Valgan's action at first, but later were incited to mutiny (ironically, a mutiny in support of the empire!) by loyal crewmen.

Demonslayer roared for the border, but found its way blocked by a squadron of frigates. Valgan had already contacted the Kzinti, who were sending their nearest ship to help.

Related Data


SH63.0 Strike at Rigel IV

by Duff Johnson
Previously published as "SL42.0 Strike at Rigel IV" in Captain's Log Issue 2.

In Y177, the Romulans mounted a particularly disruptive raid deep into Federation territory. Under cover of their cloaking devices, a powerful Romulan task force made its way to Rigel IV, the home planet of the Rigelians. Since the Rigelians were one of the primary races of the Federation, destroying their home planet would have a profound effect on Federation morale and industry. The miniscule Federation peace-at-all-costs/pacifist movement would swell as genuinely terrified people suddenly started asking embarrassing questions about how the war started and what the Federation goals really were.

The Romulans knew that a successful attack on Rigel IV would have other effects. The civilian politicians on other Federation home worlds would demand that battle squadrons be permanently garrisoned in their systems; this would tie down the Star Fleet and reduce pressure on the border. Worlds on the periphery of the Federation would also receive a clear message: If the Federation cannot protect its home worlds from the Romulans, how can you expect them to protect you? Why continue paying taxes to them? Join the Romulan Star Empire, the most powerful in the galaxy!

The Romulan plan failed on one point: the one-in-a-thousand chance that a Federation battle squadron would arrive at Rigel lV for reasons unconnected with their raid.

Related Data


SH64.0 Flank Attack

by Stewart W. Frazier
Previously published as "SL45.0 Flank Attack" in Captain's Log Issue 2.

During the opening stages of the campaign that led to Operation Remus, a small Romulan squad struck at the flank of the main Gorn fleet. Driving into the rear areas, the squad was hunted down by the support group of the Gorn fleet.

Related Data


SH65.0 Miner Smuggling

by Jeffrey L. Moore
Previously published as "SL17.0 Miner Smuggling" in Captain's Log Issue 1.

In Y180 non-Klingon slaves successfully mutinied on the mining planet K't'tothos IV. They offered an immense bribe to the Orion Pirates to transport them to Federation territory. While the former slaves had no money, they did have the secret of the DERFACS fire control system since they had produced and shaped the crystals that operated it. The slaves reasoned, and the Orions agreed, that the Federation would pay handsomely for this information. The slaves would receive the greatest reward—their freedom and well-paying jobs in Federation technology labs.

The Orions loaded the 300 surviving slaves into two Slaver class transports and headed for the border. A squadron of Klingon ISF gunboats set out to intercept them.

Related Data