The baggage control room had more screens than Juma wanted to look at. Lucy Njeri stopped him before he stepped fully inside.
“Passengers stay at the viewing point,” she said. “The controller accesses movement logs.”
Naima held up the SMS saying her bag had departed on flight 332. “I did not board. Why did my bag leave?”
The airport baggage controller, a man named David, requested her tag number and ID. He opened only her record and printed the movement log.
`Passenger status: group reprotected.`
Naima gave a humourless laugh. “Group again.”
David continued down the page. The bag had been scanned onto the flight 332 cart, passed the loading point and been acknowledged at the destination station.
“Can you bring it back?”
“The flight has gone. I cannot bring it back. I can secure the destination release.”
Samuel Rono, the dispatcher, called the destination station and asked for the bag to be placed in a secure cage and released only against the original passenger ID. Naima listened as he read the call reference and saved it in her phone.
“My laptop is inside. And my clothes.”
“We can hold it at destination,” Samuel said. “It will not come back today.”
Juma still had equipment cases in the irregular cage, along with several bags belonging to passengers who remained at the airport. David explained that the automated forward queue was using the group reprotection state. If they did not want the remaining bags sent toward routes passengers had not individually confirmed, each tag needed a manual hold.
Juma never touched the control panel. He read his tag aloud, Lucy verified it and David entered `MANUAL HOLD—PASSENGER PRESENT`. Brian handled his own tag remotely through a booking agent because he was elsewhere. Every record required owner verification.
“Why did the automation run again after we opened the dispute?” Juma asked.
David printed the event history for Naima’s bag. One line made Lucy stop moving.
`Group reprotected — EM-04 — 09:17.`
Juma checked the time of his settlement meeting. The group-reprotection event ran seven minutes after he had refused to sign.
“He sent my bag because he was angry,” Naima said.
Juma shook his head. “We do not know motive. We know credential and time.”
“Seven minutes after you walked out of the room.”
“Yes. That is timing, not proof of retaliation.”
David stepped in. “Reprotection can also be a batch job triggered by a case update. We need the initiator and rule.”
That distinction mattered. Juma did not want Mrema assigned a motive the logs had not established. He requested his own movement history. His equipment case had not forwarded because the manual reclaim from the previous day had blocked automation. Naima had no such exception, so hers travelled.
Lucy helped separate four remaining tags. Each owner received a manual-hold receipt, and the cart seal was recorded before the bags moved into the cage. Juma made certain his sample case was not mixed with Brian’s property.
Naima sat down, anger thinning into exhaustion. “I am here without my laptop, without clothes, and my bag is in another city because the system thinks I’ve been rebooked.”
“I’ll open an official tracing case,” David said. “That is what the destination station can act on.”
Naima read the printed tracing sheet. It said the physical passenger had not boarded and the baggage had been forwarded under automated group reprotection. It was her fact, not Juma’s narrative.
Samuel returned with the destination reference. “The bag is in the secure cage. They will not release it without ID. If you travel tomorrow, you can collect it.”
“If I am allowed to travel tomorrow.”
Juma opened his notebook. G-17 had now affected boarding, accommodation, rebooking and baggage. One operational shortcut had propagated into multiple systems.
David pointed to the initiator field. “This is what the operational review needs preserved. Not for passengers to investigate—so the authority can review the event properly.”
“We already have an airport-service reference,” Juma said.
“Then I will link the baggage event there.”
That was irreversible. A baggage controller who had not been part of the gate argument was now inside the official review, and Naima’s movement log would no longer survive only as a story she told.
Before saving the manual holds, David reconciled physical custody. Lucy read each remaining tag aloud, Samuel confirmed the cart seal, and the controller printed that four tags were still at origin. Juma signed only for his own case. Naima signed only her tracing request for the bag at destination.
The separation prevented a new version of the same mistake: nobody would later write “Juma says Naima’s bag is in another city.” Each person had a record in their own name.
Naima asked whether the airline could courier her laptop out of the bag. David explained that baggage rules did not allow them to open sealed luggage on a remote request. She could request delivery after identity verification at destination, but the seal could not simply be broken because she needed one item.
Naima accepted it, though it meant working without her equipment. Juma lent her a spare charger. Neither pretended that solved the cost.
Samuel called the destination station again on speaker, read the cage seal and asked the agent there to repeat the tag suffix. The response came back: “Do not release without passenger ID.” Naima stored that number. Juma did not copy it into his own notes because it belonged to her baggage case; he wrote only that a secure-destination confirmation existed under her tracing reference.
David also explained why `group reprotected` could cause an unaccompanied bag to move. After an irregular flight, the system normally tried to forward baggage onto the next protected itinerary. In ordinary cases, that saved time. The problem was that G-17 created a common reprotection assumption without individual confirmation. The automation itself was not a villain. The input and the rerun needed review.
Juma asked David to link the 09:17 event to the airport-service case. David did so and printed an acknowledgment. The time after the settlement was no longer a rumour; it was an official baggage event whose initiator required review.
Lucy sealed the remaining cage under a new number and David wrote it on each manual-hold receipt. If automation tried to run again, physical custody would now have a clear counter-record.
David closed the file and looked toward Grace, who had joined by phone.
“If one code has touched boarding and baggage, we need to see who started it and who ran it again.”