The briefing room at Nellis Air Force Base smelled like stale coffee, overheated circuit boards, and ozone.
Outside, the Nevada sun had turned the flight line into a sheet of white fire. The temperature had climbed to 108 degrees before noon, and every aircraft beyond the thick briefing-room windows seemed to float above the concrete in a shimmering mirage.
I sat in the last row with my flight suit unzipped at the collar and a crescent of black grease stubbornly trapped beneath my right thumbnail.
Four days of live-fire exercises had left everyone exhausted.
I had slept maybe eight hours total in ninety-six.
My shoulder hurt.
My eyes burned.
And the coffee in my paper cup tasted like somebody had filtered hot water through an old combat boot.
But none of those things bothered me nearly as much as the man standing beside the smart board.
Bradley Fisk.
Civilian contractor.
Software specialist.
Two master's degrees, as he would remind us several times before lunch.
Bradley wore crisp khakis, polished shoes, and a dark polo shirt that looked as though it had come straight out of a catalog. His identification badge rested perfectly against his chest.
Not one bead of sweat marked his clothes.
Not one speck of grease stained his hands.
He clicked to another telemetry graph.
"The issue with the new telemetry patch," he announced, "is simply that end users are misinterpreting the bleed-air warnings."
End users.
That was apparently what pilots were now.
People who strapped themselves into thirty-million-dollar machines and flew through live-fire ranges had been reduced to the same category as somebody trying to reset a home printer.
Bradley continued.
"When you yank the stick back aggressively, airflow disruption creates a localized pressure drop across the intake. The sensors aren't failing. The engine is merely experiencing a micro stall."
He smiled.
"It's basic fluid dynamics."
Several pilots shifted in their seats.
Nobody spoke.
Then Bradley's eyes found me.
"Let me simplify it."
There was something about those four words that made Lieutenant Miller, sitting two rows ahead of me, turn his head slightly.
He knew.
Bradley didn't.
"Captain, right?"
"Jensen."
"Right. Jensen."
He came down the aisle carrying his laser pointer like a professor preparing to educate a particularly slow student.
"Think of it like a vacuum cleaner. Put your hand over the hose, the motor struggles. Your jet is doing essentially the same thing. The computer isn't broken. It's warning you because of improper handling."
I stared at him.
For a second, the only sound in the room was the wheezing air conditioner.
Then I looked back at the schematic.
"Mr. Fisk, the TF34-GE-100 isn't starving for air."
His eyebrows rose.
"The telemetry patch your company uploaded Tuesday narrowed the acceptable tolerance parameters for stage-one fan-blade vibration. At twenty degrees angle of attack, turbulent air from the leading edge strikes the nacelle obliquely. The engine remains within mechanical limits, but your software flags it as a failure."
I leaned back.
"In other words, your laboratory simulation doesn't match what happens under a combat loadout."
Miller looked down quickly.
I suspected he was trying not to smile.
Bradley's expression tightened.
"Well, Captain Jensen, I deeply appreciate the armchair engineering."
Armchair.
That nearly made me laugh.
Instead, I said nothing.
Bradley straightened.
"But I hold two master's degrees in aerospace mechanics from top-tier institutions."
There it was.
"The data doesn't lie," he continued. "The software is functioning perfectly. The problem is operator error."
His eyes flicked toward me.
"You're pushing the airframe beyond its designated parameters."
He turned away.
"We just need pilots to be gentler with the flight controls. The jet isn't a toy to be whipped around the sky."
Miller practically folded into his chair.
I looked down at the empty coffee cup in my hand.
Then crushed it.
Crunch.
Bradley either didn't hear it or pretended not to.
What he didn't know was that three years earlier, over hostile territory, I had flown an A-10 that by every reasonable engineering standard should have fallen out of the sky.
A 57-millimeter anti-aircraft shell had gone through my right engine nacelle.
The blast destroyed a third of my control surfaces.
Primary hydraulics disappeared.
Warning lights covered the instrument panel.
Smoke filled the cockpit.
The control stick became so heavy that pulling it felt like trying to move a telephone pole embedded in concrete.
Forty-two Army Rangers were trapped below me.
They were taking fire from three directions.
And I had exactly one functioning aircraft between them and men who wanted them dead.
I stayed.
I stayed long enough to empty almost everything I carried.
Then I flew home using manual reversion.
The physical force required to move the controls tore my rotator cuff away from the bone.
I didn't know that until afterward.
At the time, pain was simply another warning light I couldn't afford to acknowledge.
I landed.
The Rangers lived.
The aircraft lived too, although barely.
That aircraft was parked outside.
Tail number 81-0964.
My bird.
Bradley knew none of this.
To him I was simply a tired woman sitting in the back row.
Someone who needed a vacuum-cleaner analogy.
"Let's move to the flight line," he announced.
He clapped his hands.
"I'll walk everyone through the sensor nodes. Sometimes physically touching the hardware helps people understand the basic physics."
Miller turned and looked at me.
His expression said one thing.
Please don't kill him.
I stood.
My shoulder protested.
"After you."
The hangar doors opened.
Heat hit us like an explosion.
The smell of JP-8 fuel hung in the air.
Aircraft maintainers moved between equipment carts and grounded jets. Far beyond the apron, brown Nevada mountains sat beneath a bright washed-out sky.
Bradley put on sunglasses.
I didn't.
There she was.
81-0964.
Gray.
Scarred.
Beautiful.
Some people saw aircraft as serial numbers.
Others saw machines.
Pilots knew better.
Every aircraft had moods.
Habits.
Sounds.
Temperatures.
Tiny vibrations.
There were things 81-0964 could tell me through the control stick that no computer display ever could.
I walked toward her.
My hand touched the skin beneath the cockpit.
Hot.
Familiar.
Bradley came up behind me carrying a thin inspection pointer.
He gestured toward the engine.
"Here's where your misunderstanding begins."
I turned.
"My misunderstanding?"
"The sensor isn't giving a false positive."
He tapped near the nacelle.
"You're creating the condition."
"Am I?"
"Yes."
He smiled.
"The jet isn't the problem, Captain."
A pause.
"You are."
Two maintainers nearby stopped working.
Miller closed his eyes briefly.
I could almost hear his internal prayer.
Bradley continued.
"If you'd stop pulling so aggressively—"
I stepped closer to the nacelle.
"Open the diagnostic overlay."
"What?"
"The diagnostic overlay."
Bradley hesitated.
"That isn't necessary."
"You came out here to teach me how the system works."
I looked at him.
"Teach me."
The maintainers were definitely listening now.
Bradley pulled out a ruggedized tablet.
He entered several commands.
A graph appeared.
I pointed.
"Stage-one vibration threshold."
"Yes."
"What was the acceptable transient ceiling before your patch?"
Bradley glanced at the screen.
"That's not relevant."
"Then you don't know."
His jaw tightened.
"Of course I know."
"Say it."
Nobody moved.
The heat hummed around us.
Bradley looked at the figure.
"Nine-point-eight."
"And now?"
He swallowed.
"Seven-point-two."
I nodded.
"Why?"
"Improved safety margin."
"Based on what operational dataset?"
"The laboratory validation model."
"Combat loadout?"
Silence.
"Twenty-degree angle of attack?"
Silence.
"High-density-altitude conditions?"
Silence again.
I looked at Miller.
He lowered his head.
This time he was definitely smiling.
Bradley snapped his tablet cover shut.
"The engineering team validated the patch."
"I'm sure they did."
"Captain—"
"Put the jet in the air."
His expression changed.
"What?"
"You say I'm flying it wrong."
I nodded toward 81-0964.
"Show me."
A laugh escaped somebody behind us.
Bradley didn't laugh.
"I'm not a pilot."
"Then I will."
He opened his mouth.
I continued.
"You sit in mission control. Watch the telemetry. We'll reproduce the maneuver exactly."
Bradley shook his head.
"There's no reason to risk an aircraft just to prove a point."
"We're already risking aircraft every time your patch throws a false engine warning during tactical maneuvering."
His eyes hardened.
"The software isn't wrong."
"Then you have nothing to worry about."
For the first time, Bradley didn't answer immediately.
Then another voice came from behind us.
"Captain Jensen."
We turned.
Colonel Nathan Reeves was walking across the apron.
Wing commander.
Twenty-four years of service.
A man who could stop a room by entering it.
He looked at me, then Bradley.
"I heard we're discussing the telemetry problem."
Bradley straightened immediately.
"Yes, Colonel. I've identified pilot technique as the primary factor."
Reeves looked toward me.
"Have you?"
Bradley nodded confidently.
"Captain Jensen is exceeding recommended handling parameters."
Colonel Reeves stared at him.
Then at 81-0964.
Then back at Bradley.
Something almost resembling amusement appeared in his eyes.
"Mr. Fisk."
"Sir?"
Reeves nodded toward me.
"Do you know what aircraft you're standing beside?"
Bradley glanced at the tail number.
"An A-10C."
Reeves shook his head.
"No."
He stepped closer.
"That's the aircraft Captain Jensen brought home from the Korengal Valley after losing hydraulics, control surfaces, and half the right engine assembly."
Bradley's smile disappeared.
Nobody spoke.
Colonel Reeves continued.
"She flew manual reversion for forty-three minutes with a torn shoulder while supporting forty-two Rangers on the ground."
Bradley looked at me.
For the first time since the briefing began, he wasn't looking at a tired woman.
He was looking at something he didn't understand.
Reeves finished quietly.
"So before you tell Captain Jensen she doesn't know how to fly this aircraft..."
The colonel touched the scarred metal near the nacelle.
"...you may want to ask why the Air Force still studies the mission she flew in it."
Bradley's face lost its color.
But embarrassment wasn't what worried me.
Because just then, from somewhere inside 81-0964, came a faint electronic chirp.
A warning tone.
The aircraft wasn't powered for flight.
It shouldn't have made that sound.
I turned toward the cockpit.
The chirp came again.
My exhaustion vanished instantly.
"Chief!"
Master Sergeant Alvarez looked up from across the apron.
"Ma'am?"
"Kill external power."
Bradley frowned.
"Why?"
I didn't answer him.
The warning chirped a third time.
Then the right-engine telemetry indicator on Bradley's tablet suddenly turned red.
I stared at the screen.
That wasn't the false positive we'd been arguing about.
This was something else.
Something much worse.
And whatever had just happened to my aircraft had started after Bradley's software patch.
---