Falcon Guard

23

The Falcon Guards were deployed for an advance across a wide expanse of flatland free of the strange thorny grasses that covered much of Prezno Plain. Aidan was impressed, never in memory having seen a BattleMech mustering as clean-lined and militarily correct as this one. Though Summer Mandaka's death had been unfortunate and wasteful, it had given him the opportunity to reassign Joa

After years as a warrior who sometimes forgot that he was not alone in the field, Aidan had finally learned that delegation was the key to command. The thought made him smile inwardly. The young Aidan would never have considered assigning someone else to conduct training. He would have done it himself—and likely have been less successful. Joa

He recalled his own cadet days. Back then, how many times he would gladly have murdered Joa

The 'Mech Stars were lined up in two echelons, the advance guard and the main body. The mixed 'Mech and Elemental Trinary Delta was in front, dispersed as skirmishers. Next came the Stars of Trinary Alpha, Bravo, and Charlie, formed up as a column with the single Nova Star of Trinary Echo, whose remaining Elementals were arranged in Star formation on each of the column's flanks. To the rear of the main column was the one remaining Star of Trinary Alpha 'Mechs, commanded by Star Captain Joa

Their objective cities were Olalla and Humptulips, and they would begin their march toward them the moment the rest of the Jade Falcon Clusters and the command group had formed up. The Clan Command Center had pla

The operation looked simple enough on the battle charts and plans, the kind of direct engagement the Clans favored. Yet Aidan knew that the I

It was time to join his Cluster. Leaning slightly toward his headphone, and shaping its flexible metal cord to draw the mike closer to his mouth, he radioed Joa

"Sir, your transmission was disrupted. Some kind of static. Adjust. Repeat."

Aidan touched the microphone. Twisting the head, he tightened it. "Any better, Star Captain?"

"Aff. No glitches."

"I am taking command of the Guards."

"Roger, Star Colonel."

Aidan began his Timber Wolfmoving forward. Was he mistaken, or did he detect a small, almost infinitesimal, delay in the response of the 'Mech's right leg when he depressed the right-foot pedal to turn the 'Mech toward the command lineup? Probably his imagination, he thought.

Coming up beside Joa

"Is something wrong, Star Colonel?" Joa

"I must have entered the wrong code." He punched the code once more. "There, that is better."

As he instructed his Cluster on the terrain, reviewing combat opportunities and ambush threats, the entire left side of the primary-screen image flashed on and off in an irregular rhythm. The distortion did not interfere with his briefing, but it made him uneasy.

After the briefing, Aidan began a normal checkoff on all controls. Nothing unusual until he pressed the button to display his armor status on his secondary screen. What he saw made Aidan draw in his breath so sharply that Joa

"Is everything all right, Star Colonel?" Joa

"Everything except that my display is saying that most of my torso armor has been blasted away. Red spots all over the chest and flashing. I may be down before we proceed from muster. Let me check again." When he touched the button once more, the onscreen information showed the proper prebattle armor configurations. "All right. My 'Mech is still functional, after all."

"It is that Timber Wolf. "Horse broke in. "The jinx. I told you about it."

"What is wrong with the commander's Timber Wolf?"Joa

Aidan did not let Horse explain about the legends attached to this 'Mech that had changed pilots so many times in recent years.

"That is all superstition," he said abruptly. "And this is no time for talk of tales and legends. Any 'Mech can have a glitch or two, and these are probably not even glitches. I am a bit eager for battle, that is all. My fingers hurry too much. The techs have checked out this 'Mech without finding anything wrong. It will be fine once we get into battle. Now, let us check the internal-damage screen."

As the rest of the checkoff went without a hitch, Aidan wondered if there was something to what Horse said about the bad luck this BattleMech could bring. On the other hand, how could it bring him luck any worse than he had already experienced in his career as a Clan warrior? Its defects, if they could be called that, were merely mechanical. No MechWarrior worth his salt was fazed by mechanical defects. In a BattleMech, the pilot had either an alternate control or configuration for any malfunctioning unit.

It was foolishness to attribute the Timber Wolfsmechanical oddities to some eerie expression of the 'Mech's personality. 'Mechs had only what their pilots gave them. And, Aidan vowed, he would get this one under control if it killed him. Then he shuddered at his own thought. What a weird idea—as if a 'Mech could turn on its pilot. He had to purge such superstitions. There was no point to them, especially with an important battle waiting to be fought.

24

The city of Olalla, or at least those parts of it for which Aidan had been able to obtain intelligence, wavered on his main screen. This time it was not a 'Mech deficiency; the image was wavering on the screens of all the Falcon Guard pilots. The data was insufficient, creating gaps that in turn made the image unsteady. Pieces of the city seemed to want to close with other sections, as if the computer denied the missing parts. The projection for Humptulips was even less informative.