“Get Him Off My Plane!” Billionaire Ordered—Then the Pilot Revealed Who the Single Dad Was

“Get Him Off My Plane!” Billionaire Ordered—Then the Pilot Revealed Who the Single Dad Was

Chapter 5

Theme:
Font Size:
24px

Its conclusion on page 16 stated that the TF90 feedback regulator demonstrated a statistically significant latency pattern under sustained thermal load that exceeded acceptable variance thresholds and recommended immediate escalation to the chief safety officer and the board’s technical oversight committee. Across the bottom of the conclusion page, in the digital equivalent of a rubber stamp, was a single line in red text. Reviewed, no action required, DL. Derek Langford. Gavin sat with that for a moment, not because he was surprised. He’d stopped being surprised by Derek Langford around the time he’d found his own personnel file had been doctored, but because there was a difference between suspecting something and having it in your hands on a page. And the difference mattered. It mattered because a suspicion was something you could carry alone and a document was something you could show to other people.

“Aldrich,” he said. “Yeah.” “Did you know this file existed?” Aldrich leaned over and read the header. Something moved across his face. Not guilt exactly, but the complicated expression of someone working out whether they should have known something that they didn’t. “No,” he said. “That project code. It’s not in any of our active development trees. It was filed outside the standard documentation chain, which means it wouldn’t show up in a standard audit.” “Right.” Gavin closed the file carefully. “It would only show up if someone went looking for skipped sequence numbers in the filing index.” Aldrich looked at him. “How often do you go looking for skipped sequence numbers?” “Every time,” Gavin said. “My old supervisor used to say that a documentation gap is never an accident. I used to think he was being paranoid.” He straightened up from the terminal. “I don’t think that anymore.”

He photographed the file on his phone. Then he photographed the TF90 installation, the serial number, the calibration log with its copied values. He was thorough about it. The way his Air Force training had made him thorough about documentation, the understanding that what you could prove was the only thing that survived contact with people who were motivated to say otherwise. Then he climbed down from the aircraft and went to find Marissa Sterling. She was in a conference room off the main terminal, a glass-walled room with a long table that had been set up for what was probably supposed to be a post-flight celebration. There were still centerpieces on the table, small Sterling Crest Aviation logos on chrome stands, and the incongruity of it, the party decorations in the room where the crisis was being managed, was the kind of detail Gavin noticed and didn’t comment on.

Marissa was at the head of the table with two people he didn’t recognize. Lawyers probably based on the laptops and the practiced neutrality of their expressions. And a man he recognized as Richard Haw, the company’s chief financial officer, who looked like someone had recently told him distressing news about something he thought was fine. Derek was there, too. Seated two chairs down from Marissa, his hands folded on the table, performing the patience of a man with nothing to be patient about. Gavin walked in and put his phone on the table in front of Marissa. “There’s a 17-page internal safety review from 14 months ago that recommended immediate escalation on the TF90 issue,” he said. “It was filed in a non-standard location outside the regular documentation chain. It was reviewed and suppressed by Derek Langford.”

The room went quiet in a way that had a specific quality to it. The quiet of people who just understood that the thing they were in the middle of was significantly larger than they’d thought 10 minutes ago. Marissa picked up the phone and looked at the photograph. Derek unfolded his hands. “That review was assessed by my office and determined to be within acceptable parameters,” he said. “The notation reflects a legitimate executive decision.” “The notation says no action required,” Gavin said. “The review itself says the component exceeds acceptable variance thresholds. Those two statements cannot both be true.” “Engineering reviews require interpretation.” “Derek.” Marissa’s voice was quiet and even, and something about the way she said his name made him stop. She was still looking at the phone. “This review recommends escalation to the board’s technical oversight committee. Did the technical oversight committee receive it?” A half second pause. “I’m almost invisible. The decision was made at the divisional level that escalation wasn’t warranted.” “That’s not an answer to my question.” Another pause. “The committee was not convened for this review.”

Marissa set the phone down. She looked at the two lawyers who were typing. Then she looked at Richard Haw, whose expression had settled into something that Gavin read as controlled alarm. The face of a CFO calculating what a suppressed safety review meant for the company’s liability exposure in real time. Then she looked at Derek. “I need you to step out,” she said. “Marissa, right now, Derek, take Porter with you.” She glanced at the security chief. “He stays in the building.” Porter stood. Derek looked at Marissa for a moment. The look of a man trying to find the version of this conversation where he still had leverage and then he stood, straightened his jacket, and walked out. Porter followed him. The glass door closed. The room felt like it exhaled.

Marissa looked at Gavin. “Sit down,” she said. It wasn’t an order this time. It was something closer to a request. “Please.” He sat. “Tell me everything,” she said. “From the beginning, not the component, the whole thing. Start 3 years ago.” Gavin looked at her for a moment. She had her tablet in front of her and her hands flat on the table, and she was looking at him with the expression of someone who had decided to stop managing the situation and start understanding it, which were two different things that required different kinds of listening. He told her he’d been a senior systems engineer on the CS7 development project brought in during the second phase when the aircraft had moved from concept design into actual engineering. He’d been assigned to the propulsion and flight control systems which put him in contact with the component supplier evaluation process.

News in the same category

“Get Him Off My Plane!” Billionaire Ordered—Then the Pilot Revealed Who the Single Dad Was

20 Part