"Was the photograph stored safely?"
Rachel opened the folder and removed a photograph taken on a mobile phone.
It showed the picture lying face down on a shelf in a supply room, partly covered by a cardboard box.
The frame was intact.
Olivia studied the image.
Her father had been standing in front of the first Sterling hangar, his work shirt rolled to the elbows, a wrench tucked into his back pocket. His expression was serious because the photograph had been taken by a customer who had insisted on documenting the opening of the business. Olivia remembered that the customer had made James Sterling pose three times before he was satisfied.
"That's not a storage area," Olivia said.
"No."
"Did Lauren put it there?"
"She says she placed it on a shelf after someone told her the facilities team would collect it. Nobody collected it."
"Who told her that?"
"She couldn't remember whether it was the facilities coordinator or someone from Mr. Voss's office."
Olivia set the photograph down.
"Has the physical photograph been recovered?"
"Yes. Facilities found it this morning. It's now in my office, inside a protective sleeve."
"Good. Please leave it there until we know where it belongs."
Rachel nodded.
Olivia turned to the access report.
"Let's look at the authorization."
Rachel opened her laptop and displayed the timeline.
At 6:18 a.m., Adrian Voss had emailed Rachel requesting that the aircraft assignment be changed.
At 6:24, Rachel had forwarded the request to the operations department because her own account did not have permission to amend aircraft dispatch records.
At 6:37, a user associated with the executive operations office had opened an old authorization template.
At 6:41, a completed document had been uploaded.
At 6:44, the passenger manifest had been revised.
At 6:51, the updated manifest had been transmitted to Captain Mercer.
At 7:02, the executive ramp's access list had been updated.
Olivia pointed to the final entry.
"Why was the access list changed at 7:02?"
Rachel enlarged the record.
"The system indicates that your name was removed from the list of authorized passengers."
"Who removed it?"
"The entry was made under the shared operations credential."
"Can we tell which terminal was used?"
"Yes. The access record identifies the workstation in the executive operations office."
"Who was logged into that workstation?"
"The system doesn't track individual sessions for that credential."
Olivia leaned back.
"So someone created an authorization using a retired template, embedded an image of my signature, revised the manifest, and removed my name from the access list. But the company can't identify the individual who performed any of those actions because the relevant account was shared."
"That's correct."
"Who approved the shared credential?"
Rachel glanced at her notes.
"The software transition team. The project record says it was a temporary measure to avoid interrupting operations during migration."
"Temporary for how long?"
"The record doesn't specify an expiration date."
"Who was responsible for retiring it?"
"The project record lists the operations director."
"Thomas?"
"Yes."
Olivia considered that.
Thomas Bell had not hidden the shared credential. He had admitted that it existed and had immediately agreed that it should be suspended. But his department had allowed a temporary workaround to become part of the company's daily routine.
That was a failure of control, even if it was not the cause of the forged authorization.
"Did you speak to Thomas?"
"Yes. He's reviewing the system migration records. He says the shared credential was intended for routine schedule maintenance, not for approvals that required the controlling shareholder's consent."
"Does the system distinguish between routine changes and approvals requiring my consent?"
"Not reliably."
Olivia closed the laptop.
"Then we have a governance problem whether or not we find the person who created the document."
Rachel nodded.
"There's another issue."
Olivia waited.
"The acquisition team received a briefing document yesterday evening. It describes the proposed transaction and the expected management structure after completion."
"Expected by whom?"
"The document doesn't say."
Rachel opened another file.
Olivia read the first page.
The acquisition proposal described Sterling Aviation as a founder-led organization entering a new stage of development. It suggested that the founder's role could transition toward strategic oversight while a professional management team assumed responsibility for daily operations.
That was not, in itself, unreasonable. Companies changed leadership structures all the time. Founders retired, executives were promoted, boards reorganized responsibilities, and shareholders negotiated new terms.
But the next paragraph was more troubling.
It described Olivia as having expressed a desire to reduce her operational involvement following the transaction.
She read the sentence again.
"Who wrote this?"
"The document properties identify corporate development as the authoring department. The revision history lists several contributors, but I haven't confirmed who wrote that specific paragraph."
"Does the document cite a conversation with me?"
"No."
"An email?"
"No."
"Board minutes?"
"No."
Rachel looked uncomfortable.
"It may have been an assumption."