"Can your team identify whether the temporary account was reactivated through Project Horizon?"
"I'm checking the authorization records," she replied. "The account is linked to the legacy gateway, but the activation event was generated locally. That suggests the person may have used equipment inside the old room."
"Could the room contain a functioning Project Horizon device?"
"It could, if the equipment was never fully removed. We need to inspect the inventory and compare it against the original maintenance records."
Jonathan turned to Andrew.
"Arrange a controlled inspection of the room. No one enters alone. Photograph everything before touching anything, and preserve any equipment that could be connected to the network breach."
The team prepared the inspection while Jonathan reviewed the available information.
Victor had entered the airport using a badge connected to a canceled work order. He had accessed the old equipment room, where another legacy credential had been accepted. The room was supposed to have been decommissioned, yet its access reader remained active.
It was possible that Victor had entered to retrieve evidence.
It was equally possible that someone had brought him there to activate equipment.
At 4:41 p.m., the inspection team opened the service door.
The room was smaller than Jonathan expected. Metal cabinets lined the walls, and several racks contained disconnected network equipment. Dust covered the floor, but a narrow path between two cabinets suggested that someone had moved through the room recently.
The facilities officer photographed the scene.
"There's a powered unit at the back," she reported through the secure call. "It isn't listed on the current equipment inventory."
Priya examined the photographs.
"That looks like an authorization bridge. The casing matches the model used during the original Project Horizon trial."
"Can you identify the serial number?" Jonathan asked.
The officer moved closer without touching the device.
"The label reads NB-41-073."
Priya searched the historical inventory.
Her expression changed.
"That's the missing module."
The same device that had disappeared three years earlier had been found in a room that was supposedly decommissioned. It had apparently been connected to a local power source and used to authenticate a legacy account.
Jonathan instructed the inspection team not to disconnect it. They photographed the cables, recorded the indicator lights, and documented the network connections before the independent technical specialist began a controlled examination.
At 4:48 p.m., Elena reported that the device had attempted to communicate with the executive authentication service.
"Can you block it?" Jonathan asked.
"Yes. We can isolate the connection at the network boundary without touching the device. That should prevent further remote communication while preserving its local state."
"Proceed."
The connection was restricted.
A moment later, Priya's screen displayed a new access event.
LOCAL AUTHENTICATION REQUEST DENIED.
Then another appeared.
RECOVERY SESSION REQUESTED.
The device was still attempting to establish a privileged connection, despite the network restriction.
"Is it operating automatically?" Andrew asked.
"Possibly," Priya replied. "The device may have a scheduled process, or someone could be interacting with it locally."
Jonathan looked at the room inspection feed.
"Can the team see anyone inside?"
"No. The room is empty."
"Then we need to find Victor."
At 4:53 p.m., the airport's public announcement system called a maintenance supervisor to the central service desk. Andrew received a message from the facilities team confirming that the equipment room had been secured under independent observation.
Victor's badge had not been used since 3:52 p.m.
The investigation team searched the visitor records again and discovered that the temporary technical support account had been used to open a second door at 3:57 p.m. That door led to an internal corridor connecting the old equipment room to the former operations archive.
The archive contained historical records, retired workstations, and equipment awaiting disposal.
Jonathan looked at the map.
"Can someone access the archive without passing through the main security checkpoint?"
"Yes," Andrew said. "There is a service passage behind the maintenance offices."
"Then we need an independent inspection of that area. No confrontation unless there's an immediate safety concern."
At 5:06 p.m., the inspection team entered the archive corridor. The door was closed, but a maintenance light glowed beneath it.
The facilities officer knocked.
"Airport maintenance. Is anyone inside?"
No answer.
She waited, then knocked again.
A man's voice came from within.
"Who sent you?"
The officer identified herself and explained that the area was being inspected as part of a maintenance review.
There was a pause.
Then the door opened a few inches.
Victor Shaw stood on the other side.
He was thinner than he appeared in his old contractor photograph, with gray at his temples and dark circles beneath his eyes. He wore a faded blue jacket and held a small document case in one hand.
He looked at the facilities officer, then at the compliance representative standing behind her.
"Where is Jonathan Reed?" he asked.
The officer contacted Jonathan immediately.
Within minutes, Jonathan arrived with Rebecca Lin, the independent compliance representative. He did not bring Martin Hale or any member of the airport's direct security team.
Victor looked at Jonathan and let out a long breath.
"You're really here."
"Yes," Jonathan replied. "You asked Evelyn Brooks to contact me, and you entered the airport using a badge linked to a canceled work order. I need to understand why."
Victor glanced at the document case.
"I came to recover the original records before someone destroyed them."
"Which records?"
"The Project Horizon authorization logs. The original ones, before they were altered."
"Why are they in this archive?"
"Because I put them here."
The admission surprised everyone.
Victor explained that after Flight 608, he had been ordered to remove the remaining equipment from the trial area. While disconnecting the module, he discovered that the device had stored a local copy of the authorization history. The records showed that the temporary connection had remained active longer than the official report claimed.
He had made a copy of the logs and stored it in the archive because he believed the central records would be changed.
"Why didn't you report that at the time?" Jonathan asked.
"I did report the discrepancy. But I didn't reveal that I had kept a copy. I was afraid I would lose my job, and I thought the investigation would uncover the truth without my help."
"What happened?"
"The investigation was closed. The official records were revised, and the contractor's access was suspended. I told myself the matter was over."
"Yet you kept the logs."
"Yes."
Victor opened the document case. Inside were several sealed storage devices, a notebook, and a folder of printed work orders.
Rebecca documented the items before allowing Victor to explain their contents.
The first storage device contained a local export of the Project Horizon authorization history. The second held a series of maintenance reports. The printed documents included the original work order allowing the temporary module to remain connected during the Flight 608 incident.
Jonathan examined the papers without removing them from their protective sleeves.
"Why did you return today?"
Victor looked toward the old equipment room.
"Because someone contacted me three weeks ago and asked whether I still had the original logs. They knew the module's serial number and the exact date of the Flight 608 test."
"Who contacted you?"
"I don't know. The message came through an account I couldn't trace."
"What did they ask you to do?"
"They wanted me to confirm that the original module could authenticate a legacy account. They said the airport was preparing a controlled security review."