"Kill the power!"
Master Sergeant Alvarez didn't ask questions.
He ran.
The ground crew moved with him.
Bradley stood beside me staring at his tablet as though the machine had betrayed him personally.
A red warning box pulsed across the display.
RIGHT ENGINE SENSOR NETWORK—UNCOMMANDED RESET.
I felt the familiar tightening in my chest that came whenever machines stopped behaving according to physics.
Aircraft didn't have opinions.
They didn't have bad days.
They didn't make spontaneous decisions.
If something happened, there was a reason.
We just hadn't found it yet.
External power shut down.
The cockpit displays went dark.
Bradley's tablet remained connected long enough for the warning to blink once more before disappearing.
Colonel Reeves stepped closer.
"What did we just see?"
Bradley answered too quickly.
"A transient communication error."
I looked at him.
"You don't know that."
"We were cycling diagnostic modes."
"No, you were displaying them."
"Same bus."
"Different command authority."
His jaw hardened again.
"Captain, with respect—"
"Stop saying that before insulting me."
Miller coughed into his fist.
Reeves glanced toward him.
Miller suddenly became fascinated with a crack in the concrete.
Alvarez returned.
"External is disconnected, ma'am."
"Any maintenance commands active?"
"No."
"Battery?"
"Cold."
Bradley shook his head.
"Then it couldn't have happened."
I stared at him.
"It did."
His cheeks flushed.
"What I mean is the architecture doesn't permit an uncommanded reset without a software handshake."
"Then something initiated a handshake."
"Impossible."
Colonel Reeves folded his arms.
"That word gets expensive around aircraft, Mr. Fisk."
Bradley closed his tablet.
"I need access to the server logs."
"You'll have it," Reeves said. "But nobody touches this aircraft until Captain Jensen and maintenance sign off."
Bradley's expression tightened.
"Colonel, my company owns the telemetry software package."
Reeves stepped closer.
"And the United States Air Force owns the aircraft."
That ended the argument.
For the next three hours, we tore through data.
The maintenance bay became our temporary war room.
Screens displayed logs, sensor records, timestamp histories, and command sequences. Technicians brought in cables and diagnostic equipment.
Bradley's confidence gradually returned.
Data was his territory.
He sat at the center terminal, typing quickly.
"Here."
A string of code appeared.
"At 1147, the engine vibration sensor sent a status query."
I leaned over his shoulder.
"Why?"
"It was scheduled."
"No."
I pointed toward the earlier timestamps.
"Queries occur every fifteen minutes. That one occurred six minutes after the previous cycle."
Bradley stopped.
I watched his eyes move across the screen.
For the first time, he wasn't trying to prove me wrong.
He was trying to understand.
"Could maintenance have requested it?"
Alvarez answered from behind us.
"No."
Bradley typed again.
"Mission computer?"
"Cold," I said.
"Ground diagnostic terminal?"
"No active session."
His face changed.
Colonel Reeves noticed.
"What?"
Bradley zoomed in.
"There's an authentication key attached to the request."
"Whose?"
He hesitated.
"Mine."
Nobody spoke.
Bradley stared at the display.
"That's impossible."
There was that word again.
He stood abruptly.
"My credentials were used."
"By you?" Reeves asked.
"No."
"Who else has access?"
"Nobody."
Reeves looked toward base security.
Two officers had been quietly standing near the door.
"Apparently somebody does."
Bradley turned.
"Colonel, this could be a logging artifact."
Reeves' voice became colder.
"Could be."
Bradley swallowed.
"But until we know, your access is suspended."
His eyes widened.
"You can't—"
"I can."
One of the security officers stepped forward.
"Sir, we'll need your badge and tablet."
Bradley looked at me.
For some reason, I saw betrayal in his expression.
As though I had engineered this.
"Captain."
I shook my head.
"Don't."
"You think I did this."
"I think your credentials did."
"I wouldn't sabotage an aircraft."
"Then help prove you didn't."
He looked away.
Security escorted him from the room.
Miller came beside me.
"Well."
I rubbed my shoulder.
"Don't say it."
"I wasn't going to."
"You absolutely were."
He smiled faintly.
"I was only going to say his day got worse."
"Lieutenant."
"Yes, ma'am."
"Coffee."
"Immediately."
By sunset, the desert cooled from murderous to merely hostile.
The investigation expanded.
Cybersecurity specialists arrived.
Bradley's company executives called.
Then lawyers called.
Then more executives called because lawyers had called.
By 2100, the Air Force had discovered something disturbing.
Someone had accessed the telemetry update package eighteen hours before installation.
The access originated from Bradley's credentials.
But the physical device signature didn't match his assigned laptop.
Cloned credentials.
Someone wanted the system to believe Bradley had made the changes.
Which meant Bradley might be arrogant.
But arrogant and guilty were not necessarily the same thing.
At 2200, I found him sitting alone outside the security office.
His lanyard was gone.
Without it, he looked strangely smaller.
Less like a visiting expert.
More like a man who'd realized his career could disappear overnight.
He saw me.
"Come to enjoy the view?"
I stopped.
"No."
"Could've fooled me."
I leaned against the opposite wall.
"Your credentials were cloned."
His expression changed.
"You know?"
"Cyber found a device mismatch."
Bradley exhaled.
He rubbed both hands across his face.
For the first time all day, he looked tired.
"I've spent twelve years building flight-control software."
"Telemetry."
He gave me a look.
"Telemetry and control-support architecture."
"Better."
Despite everything, the corner of his mouth moved.
Then disappeared.
"I would never intentionally compromise an aircraft."
"I believe that."
He looked surprised.
"Why?"
"Because people who sabotage aircraft don't usually spend an hour publicly arguing that their software is perfect."
A short laugh escaped him.
"That's your defense of me?"
"It's what you get."
He stared down the corridor.
"Someone changed the package."
"Yes."
"And used my credentials."
"Yes."
"Why?"
"That's the useful question."
He looked at me.
"Why help me?"
"I don't care about protecting your ego, Bradley."
It was the first time I'd used his first name.
"I care about preventing pilots from flying with compromised software."
He nodded slowly.
Fair enough.
The next morning, the answer became worse.
The software changes weren't random.
Somebody had deliberately reduced vibration tolerances.
At first glance that made the system more sensitive.
Safer.
But buried deeper was another modification.
Whenever multiple warnings appeared simultaneously, the patch suppressed one category of secondary engine-temperature alerts to reduce "pilot workload."
It sounded reasonable.
Except under a specific combination of high angle of attack, external stores, and desert temperature, an actual lubrication failure could be masked behind the vibration warning.
A pilot might assume the warning was another false positive.
And continue flying.
Until the engine destroyed itself.
Bradley stared at the analysis.
"No."
He moved closer.
"No, no, no."
I understood the horror in his voice.
"That wasn't in your version?"
"Absolutely not."
"Can you prove it?"
He began typing.
"I keep hash records of every release."
A minute later, he found them.
The production file didn't match his signed version.
Reeves stood behind us.
"So somebody altered a flight-safety patch after approval."
"Yes," Bradley whispered.
"Could it cause a loss of aircraft?"
Bradley didn't answer immediately.
Then he looked at me.
"If the exact conditions occur?"
"Yes."
"How long before engine failure?"
"Could be minutes."
My stomach tightened.
"Which aircraft have the patch?"
Nobody wanted to answer that.
Alvarez eventually did.
"Twelve."
"Where?"
"Six here."
"And the rest?"
He looked at Reeves.
"Four transferred yesterday to Red Flag support at Tonopah."
A pause.
"And two departed Nellis twenty minutes ago."
The room froze.
"Call them," I said.
Alvarez grabbed the radio.
Bradley looked at the tracking screen.
Two icons were moving northeast across Nevada.
One belonged to Captain Avery.
The other belonged to Lieutenant Miller.
I stared.
"Miller's airborne?"
"He swapped onto the test sortie this morning," Alvarez said.
The radio operator spoke rapidly.
No response.
"Try guard."
Static.
Again.
Nothing.
Then one aircraft icon changed color.
Yellow.
Engine advisory.
Bradley whispered, "Oh God."
Five seconds later it turned red.
My fatigue vanished.
"Get me a jet."
Colonel Reeves looked at me.
"Jensen—"
"Get me a jet."
Bradley stood.
"I need to go."
I stared at him.
"What?"
"If that warning is coming from the modified software, I need to see the raw stream in real time."
"You're not flight crew."
"I wrote the original architecture."
"This isn't a conference room."
His face hardened.
"No. It isn't."
For once, there was no arrogance in his voice.
"That's exactly why I need to see what my software is doing before it kills someone."
We looked at each other.
Then Colonel Reeves made the decision.
"Bradley goes to mission control."
He pointed at me.
"Jensen flies."
Outside, alarms began echoing across the flight line.
Maintenance crews sprinted toward another A-10.
I ran beside them.
My shoulder screamed when I climbed the ladder.
I ignored it.
Helmet.
Harness.
Oxygen.
Battery.
Systems.
The canopy came down.
Through the glass, I saw Bradley standing beneath the wing.
No smile.
No condescension.
He raised one hand.
I gave him a single nod.
The engines came alive.
Minutes later, I accelerated down the runway.
The desert blurred beneath me.
Then the aircraft lifted.
"Nellis Control, Hawg One airborne."
Static crackled.
Then Reeves' voice.
"Hawg One, Miller reports intermittent right-engine pressure and unreliable telemetry."
"Copy."
"Jensen."
"Sir?"
"Bring them home."
I looked toward the distant mountains.
Three years earlier, forty-two Rangers had needed me to keep an aircraft alive.
Today it was one young lieutenant.
But one was enough.
I pushed the throttles forward.
And somewhere ahead of me, Miller's engine was beginning to die.
---