“Of course, sir.” Meharry took the thick stack of personnel sheets Barin handed him. “How many? And are we supplying food service support?”
“There’s five on the forensic team, about a dozen civilians, and I was told that I could have as much for support as I wanted. The major said the more I could get out of his hair the better. And yes, I’m supposed to arrange food service. And all I’ve had here is hospital food.” Barin put a plaintive note in that and was relieved to see Meharry smile.
“Let’s see if—yes, here’s a good cook on your list. And another. Clerks—hmmm. Koniston’s always cheerful and doesn’t make funny noises when he’s working—” Meharry looked up and explained that. “Andersson’s a good clerk, but he drives me nuts; he’s always hissing or clicking his tongue or something. We don’t need that in a small team. Koniston, Bunley, Mohash and . . . let’s see, is Simi—no. Well . . . Purto, then. Four clerks ought to be enough. Communications . . . we should ask Ensign Pardalt, sir.”
“She’s the one who built that whatchamacallit to get a signal out?”
“Yes, sir. She was a junior instructor in history, I think it was, and after that they moved her into communications. She probably knows all the techs.”
“I’ll find her,” Barin said. “I’m guessing we need a couple of techs—”
“Sir, I’d recommend four. If we have personnel on both Stack islands, we’ll want a primary and backup for each team.”
“Yes, of course. Do you think you can pick out the rest of what we need, and have a list for me when I get back from seeing Ensign Pardalt?”
“Yes, sir.” Meharry paused, then went on. “Sir, am I supposed to be on your team, or with forensics?”
“They said they’d assigned you to me, because then you’d be handy to answer any questions.”
“Yes, sir.”
Barin found the communications building easily enough, but locating Ensign Pardalt took longer. She was not in her temporary office, or anywhere in the main control rooms. Finally a pivot said she was probably down in data analysis. Data analysis was in the basement.
At first he thought the young woman hunched over a stack of printouts was an enlisted tech; she didn’t look up, which gave him a chance to notice the insignia before he blundered. He watched her a moment longer. Sleek red hair, hanging forward a little as she scanned the papers and tapped on her handcomp. Pale brows drawn together with intensity of concentration.
“Excuse me,” Barin said. “I’m looking for Ensign Pardalt.”
She looked up, and blinked at him a moment, then flushed and pushed back her seat to stand. “Sir, sorry . . . I’m Ensign Pardalt.”
“I’m Jig Serrano,” Barin said. “Sorry to interrupt you, but I need some advice.”
“Advice? From me?” She looked almost scared.
“Yes,” Barin said. “I’m supposed to assemble a support team for a trip out to the Stack Islands, and I need the names of some decent communications techs. Corporal Meharry suggested that you might know who on this list would work best in a situation like that.” He held out the list.
“Oh . . . well, I don’t know them all . . .” But she scanned down the list; he recognized total concentration and said nothing more.
“How many?” she asked.
“Four or five,” Barin said.
She rattled off four names, marking them with her stylus.
“Thanks,” Barin said. “May I ask what you’re doing?”
“Trying to figure out who disabled the weather satellite so that no one saw the Bonar Tighe’s troop shuttles approaching the Stack Islands,” she said. “The problem is, MetSat IV had been acting up for a couple of years. So it could have been just a random glitch—”
“Convenient, though,” Barin said. “The previous acting up could have been cover for this.”
“Yes. But I can’t think of a way to prove or disprove that.”
It sounded tedious enough to him. “I don’t suppose you’d like to come along on our little jaunt?”
She looked alarmed. “Not really, sir, but of course if you need me . . .”
“No, that’s all right. I’m just glad I don’t have your job.”
Chapter Twelve
Heris Serrano had a few days’ peace while Seabolt thought of some other nonsense to obsess over. So far they’d been lucky; no mutineer had attacked them, and they’d detected no sign that one had passed. She was working on another drill schedule when she got a call from the bridge.
“Captain, I just wondered . . . what if an ansible transmits a pre-message alert, but then no message?” Jig Hargrove, the junior officer on communications this shift, had an earnest face that turned even the simplest question into Something Serious.
“What do you mean?” Heris asked.
“You know how—” Heris winced; all the junior officers had picked up Seabolt’s habit of starting every explanation with that phrase. “—how an ansible sends out an ID and clear-channel blip before sending a message?”
“Yes,” Heris said. “And the following message will be delayed by the time it takes the ansible to return a ‘ready’ message to the originator, and the originator’s message to arrive.”
“Yes, so we expect a lag, up to about four hours, between the initiation sequence and the message. But I’ve been waiting almost the whole shift for a message, and nothing’s come through. And Commander Denehy said to report anything out of the ordinary. I just don’t know if this is.”
“How long, exactly?” Heris asked.
“Six hours, eighteen minutes. I guess it could be a ship that’s farther than three light-hours from the ansible, but most people don’t try to raise one until they’re a lot closer than that.”
“What’s the ID? Why do you think it’s a ship?”
“Well, this is the system—” Hargrove held out a description. “It’s got no inhabited worlds, and no permanent settlement, though there’s a research station on that eccentric planetoid. I suppose it could be that.”
“I suppose,” Heris said absently, looking at the system specs. “One mapped jump point, but only a yellow rating . . . oh, because of the planetoid. What are its backjump stats?”
“Sorry, Captain—I don’t know. Just its com status.”
“Commander de Fries—” The senior navigation officer looked up. “I need a backjump analysis of these coordinates—” Heris flicked them to his screen.
“Right away, Captain.”
Heris turned back to Jig Hargrove. “Does that ansible have reversible scan capability?”
“No, Captain. The note on it in the catalog says it’s just a single-channel model, for the use of the research station. It’s not even very secure; its access code is in all the updated files. Anyone could have tripped it—though I suppose it could have been just damage.”
“Captain—” That was de Fries.
“Yes?”
“Backjump analysis: because this isn’t considered that stable a jump point, the only mapped one-jump location is CX-42-henry—”
“That’s one of the one-to-go points for Copper Mountain,” Heris said.
“That’s right, Captain. Copper Mountain is the nearest two-jump outlet, estimated FTL time eleven days, and that’s due to the short leg in from CX-42-henry. There’s a notation that successful jumps were made to the vicinity of RG-773-alpha, but there weren’t enough to qualify for a mapped route. Estimated FTL time on that one is nineteen days. Some of the scientists considered it a more direct route to their home systems, over in Sector Five.”
“I suppose it would be,” Heris said. “Do you have any data on that system which would tell us how far that planetoid is now from the ansible? How long a lag there might be between an initiating signal and the following message?”