THE CAPTAIN REFUSED TO FLY WITH THE MAN IN SEAT 1A — UNAWARE HE OWNED THE AIRLINE

Chapter 13

Theme:
Font Size:
24px

Leila noted the claims without treating them as an excuse. The forged message was a separate serious breach, potentially subject to legal action. She asked for his devices and records through proper channels. Jonah consented to preservation under an agreement his lawyer reviewed. He also provided a copy of the report classification specifications as they had existed before a late revision. In the earlier version, all events remained visible to safety analysts. In the final version, a subset became inaccessible without elevated permissions.

“Who approved that change?” Patel asked.

“Peter's office,” Jonah said. “I signed the implementation note. I should have refused.”

Patel regarded him steadily. “You might be right that the design was unsafe as a management tool. That doesn't make it acceptable to mislead a flight crew.”

“I know,” Jonah answered. “It's the first thing anyone has said to me that I actually agree with.”

After the meeting, Jonah watched from a window as the investigators left. He had imagined himself exposing an injustice. Instead, his action had helped create another one. Parker had made his own choices, and Malcolm had become a target without warning. Jonah could not claim to have caused every part of the scene, but he could not pretend his warning had been harmless.

Later he wrote a statement acknowledging the unauthorized access and the content he had fabricated. His lawyer advised him that candor would not guarantee leniency. Jonah signed anyway. He had spent months believing he was the only person willing to tell the truth. Now he understood that the truth included his own conduct.

Rafi Sethi had spent the previous three days examining permissions that most Northstar employees never knew existed. He liked clear systems. A user either had access or did not; a report either closed with an attributable action or remained open; an edit either left a trace or it did not. The ClearPath environment had failed all three tests in ways that were painfully ordinary. Historical accounts survived contract changes, shared tokens were treated as harmless shortcuts, and some report statuses could be changed without displaying the actor's name to the employee who filed the original observation.

On Tuesday he demonstrated the defect to Leila Brooks using a training database. A simulated baggage-equipment report appeared as OPEN on the submitting worker's screen. Rafi changed the classification through a privileged service process. The employee-facing screen now showed RESOLVED, although no mechanic had been assigned and no action had occurred.

Leila frowned. "It doesn't say why."

"It doesn't even say who," Rafi answered.

"Can we establish which real reports were touched this way?"

"Sometimes. There are underlying logs. But they were not designed to be read by the people responsible for the equipment. Some logs expire before an ordinary complaint is escalated."

He did not dramatize the finding. It was not proof that every resolved report had been falsified, nor proof that an aircraft had been operated unsafely. It was evidence that the company's reporting design allowed the appearance of closure to outpace the actual work of resolution. Leila asked him to document the test, preserve the production logs in a lawful manner, and bring in an independent software assurance specialist before any corrective change erased historical evidence.

That afternoon Rafi went to visit his sister, Priya, who worked as a community nurse. Her son had built a small airport out of cardboard and was landing paper airplanes on the kitchen table. Rafi watched the child rebuild a crumpled runway with tape.

"You look miserable," Priya said, handing him tea.

"I found a button that can make an unfinished problem look finished."

"Then remove the button."

"If I remove it now, I may destroy the record of how it was used."

Priya sat opposite him. "In the hospital we have to correct charts sometimes. You can't just erase the old number. You have to show what you changed and why."

"That's exactly what I'm trying to explain at work."

"Are they listening?"

"Some of them. The others think I'm accusing everyone who's ever pressed the button."

She glanced at her son's airplanes. "Maybe they hear blame because nobody ever taught them the difference between a record and a verdict."

The phrase stayed with Rafi. The next morning he met with a small working group that included a station manager, a mechanic, a gate agent, and Mina Cho. Mina was there because she had preserved a photograph of the confirmation number for a latch report that later vanished from her ordinary view. She sat with her hands folded and watched Rafi's demonstration.

"If I saw RESOLVED," she asked, "would I know whether the equipment was fixed?"

"Not in the old design."

"Then why call it resolved?"

The station manager looked uncomfortable. "There were operational categories. Some reports were duplicates, some were low priority."

"Could a duplicate still be important?" Mina asked. "If four people report the same latch, that tells you something the first report didn't."

Rafi nodded. "Exactly. We treated duplicates as clutter instead of considering whether repetition might be the signal."

The mechanic, Hana Okafor, asked whether a worker could see a report's full history without seeing confidential personnel details. Rafi proposed two layers: a worker-facing action history identifying the stage of review and the responsible department, and a restricted audit log preserving individual administrative actions for authorized reviewers. The group argued for an hour about complexity, training time, and whether managers would tolerate a dashboard that looked worse before it looked better.

News in the same category

THE CAPTAIN REFUSED TO FLY WITH THE MAN IN SEAT 1A — UNAWARE HE OWNED THE AIRLINE

23 Part