Her sister put down the toast. “Then show them where you were.”
June had returned home in a taxi at 11:48 Friday night and had called her sister from the building entrance. There would be a receipt and a phone log. She forwarded the notice to Leena and requested an exact preservation copy of the access entry. She did not delete the email or post it online, although anger tempted her to do both.
Leena called within an hour. “Do not attend a disciplinary interview without counsel,” she said. “We need to know whether someone used your account or whether the access record itself is misleading.”
“Can they do that?”
“Apparently someone has done something. We need evidence before naming what.”
Tessa reviewed the station's badge system. June's card had been physically scanned at the archive door on Thursday evening when she helped the investigators. After the incident, the account remained active, though the physical badge had been collected when June left the airport. A separate digital token could have remained valid in Apex's identity-management cache. The system used that token to create a plausible login record without requiring a person to be present.
At first the discovery looked like evidence of another deliberate forgery. Then Ben Orlov found a more subtle possibility. The old archive workstation had stored a session under June's account during the legal evidence copy. A scheduled reconciliation process imported that session into the modern directory hours later, assigning its import time as though it were a new login. The same software design made a delayed technical event resemble a fresh human action.
“Can we prove the difference?” Leena asked.
Ben showed her the raw event identifiers, preserved during the emergency copy. Both access entries shared the same original session hash. The later timestamp was an administrative replay, not evidence of a second visit. There was no sign that June had copied or leaked the clearance image.
The finding should have ended the allegation. Instead, employee relations requested more time to assess confidentiality concerns. June stared at the message and understood a painful asymmetry: an employer could suspend her with a sentence, while clearing her name required engineers, investigators, and a legal review.
Elias called after Leena told him what had happened. He did not offer to intervene through informal contacts. He asked whether June had independent advice and whether she was keeping copies of the messages. She said she was.
“I thought speaking up would be the difficult part,” she told him.
“Sometimes it's the beginning of the difficult part.”
“Does it get easier?”
“People get more practiced at standing upright while they're uncomfortable.”
June nearly laughed. It sounded like advice from someone who had spent a lifetime learning not to provide false reassurance.
That afternoon, the airline's safety oversight committee requested an external review of the disciplinary process. Aruna Desai supported the request, despite warnings that it would make management look weak. “We already look weak,” she said in the meeting. “The question is whether we're willing to become reliable.”
June kept the suspension letter. She placed it beside the old training certificate she had framed when she joined Meridian. The documents represented two different versions of the company. She hoped the investigation would decide which one the company intended to be.
CHAPTER 20
Victor Hale'S Version
Victor Hale spent the first week of his suspension in a hotel room overlooking a parking garage. His lawyer had advised him not to contact witnesses or discuss the case publicly. He obeyed. He also spent hours replaying the moment he tore the paper ticket. It seemed to him, now, like an absurdly small gesture on which an entire career had turned. He did not initially consider the aircraft.
When Leena interviewed him again, his lawyer was present. Hale admitted that he had instructed staff to deny unsupported legacy documents. He said he believed the process protected passenger records from fraud. He also admitted ordering Apex to reduce the number of anomalies appearing on operations dashboards. He continued to deny authorizing the falsification of maintenance certifications.
“What did you believe AUTO-CLOSE meant?” Leena asked.
“Automated triage,” he replied. “A recommendation, not a sign-off.”
“Did you ask to see the technical controls?”
“I received a summary.”
“Did you speak with the engineers whose reports were disappearing?”
“No.”
“Why not?”
He looked at her. “Because the reports weren't supposed to be disappearing.”
Leena allowed the answer to sit without commentary. On the table was a copy of an email in which Hale urged Apex to prevent “red events” from reaching an investor briefing. She asked him what the phrase meant.
“Repeated faults that would turn out to be reporting noise.”
“Did you know they would turn out that way?”
“I trusted the analysis.”
“Whose analysis?”
Hale paused. “Apex's.”