My fingers tightened around the phone.

"Which one?"

"The first case."

"Was the instruction executed?"

"The record suggests that the bag was held for additional processing. We're checking the final disposition."

I thanked him.

The pattern was becoming unmistakable.

Westbridge had not merely appeared in Apollo's records by accident. Similar changes had occurred in other cases, involving passengers whose circumstances made them dependent on assistance arrangements.

The cases did not yet prove a single coordinated conspiracy. The details differed, and some might have had legitimate explanations.

But the recurring combination of vendor authorizations, altered travel classifications, and unexplained handling instructions justified a broader investigation.

I called Officer Shaw and shared the update.

She listened carefully.

"This gives us a stronger basis to examine the authorization process," she said. "We'll need the underlying records and statements from the other passengers."

"Can you contact them?"

"The investigators are working through the appropriate channels."

"Please make sure the company doesn't contact them first."

"We can request that the airline preserve the communications and avoid unnecessary contact while the review is underway. We can't prevent every lawful communication, but we'll make sure the investigators are aware of the concern."

I nodded.

It was the kind of careful answer I had learned to expect from people who understood the limits of their authority.

Unlike Vance, Shaw did not pretend she could guarantee an outcome she did not control.

That made me trust her more.

At 9:02 a.m., Meridian Air's compliance director joined a video conference with Shaw, Ortega, Sloan, and me.

His name was Andrew Keller.

He appeared on the screen from an office filled with glass walls and neatly arranged binders. He introduced himself, apologized for the disruption, and stated that the airline was conducting an internal review.

I had heard those words many times before.

An internal review could uncover misconduct.

It could also become a way to control the flow of information until the organization had settled on an explanation.

I waited for him to finish.

"Mr. Keller," I said, "can you confirm that my reservation was canceled under an operational authorization?"

"Yes."

"Can you confirm that the authorization was associated with Marcus Vance's employee credentials?"

"The current audit records indicate that his credentials were used in the approval sequence."

"Can you confirm that my signature was attached to a receiving-party document I never signed?"

"The document is under examination. The airline has not yet made a final determination regarding its authenticity."

"Can you confirm that the receiving-party authorization was created through a Westbridge account?"

"Yes."

"Can you confirm that the company had no documented consent from Apollo or me?"

"At present, we have not located a valid consent form."

"Can you confirm that a baggage instruction directed our luggage through Phoenix?"

"Yes. That instruction has been suspended."

I leaned closer to the camera.

"Then what remains uncertain?"

Keller paused.

"Responsibility. We know that the records were changed. We need to determine who initiated the changes, whether anyone acted under instructions, and whether the vendor's account was used appropriately."

"Will you preserve all relevant records?"

"Yes."

"Will you provide them to the investigators?"

"Subject to the applicable procedures, yes."

"Will you review the other passenger cases?"

"Absolutely."

"Will you suspend Westbridge's access while the investigation is underway?"

Keller looked toward someone outside the camera's view.

Then he returned his attention to the screen.

"The airline has temporarily restricted the account's ability to create new receiving-party authorizations."

"Is that a complete suspension?"

"It is a restriction on the relevant functions."

"Can the account still access passenger information?"

"That is being reviewed."

I exhaled.

"Then the restriction isn't complete."

"Mr. Mercer, I understand your frustration."

"No. I want you to understand the problem. A company that appears to have used passenger information without consent was able to create an authorization that separated a minor from her legal guardian. The airline's system accepted a document bearing a forged signature. The same account family appears in other passenger cases. If the company can still access information, the risk hasn't necessarily ended."

Keller did not interrupt.

I continued.

"I am not asking you to decide who is guilty before the investigation is complete. I am asking you to prevent the same process from being used again while you investigate."

After a long pause, he nodded.

"I'll recommend an immediate suspension of the vendor's access to passenger-specific assistance records pending review."

"Thank you."

The meeting ended with a list of actions and deadlines.

It was not a victory.

But it was the first time the airline had treated the problem as a system failure requiring changes rather than a passenger complaint requiring an apology.

At 10:37 a.m., Evelyn Price agreed to provide an initial statement through her legal representative.

She denied creating the forged authorization.

She stated that Westbridge had received a request to coordinate Apollo's transfer and that she believed the request had been approved by an authorized airline employee.

She also denied intending to remove Apollo from her legal guardian's custody unlawfully.

The statement was brief and carefully worded.

It did not explain why she had purchased a ticket on Flight 842 after Daniel Mercer's reservation was canceled.

It did not explain why she had told Apollo that her uncle had approved the transfer.

It did not explain why the yellow document bore a signature that appeared to have been forged.

But it introduced another possibility.

Evelyn Price might have been a participant.

She might have been acting under instructions.

Or she might have believed that the paperwork was legitimate because someone had deliberately presented it that way.

I had no intention of deciding which explanation was true before the evidence was examined.

I knew too well how easily suspicion could become certainty when people were angry.

Instead, I asked Ortega to focus on the sequence of events.

When had Evelyn received the authorization?

Who had communicated with her?

Who had booked her ticket?

Who had created the document?

Who had approved it?

And who had told her that she could take custody of Apollo?

Those questions would matter more than her initial denial.

At noon, Officer Shaw sent me a copy of the airline's preliminary transaction timeline.

It began at 8:11 a.m., when Evelyn Price met Marcus Vance near the gate.

At 8:17 a.m., a Westbridge account created the receiving-party authorization.

At 8:19 a.m., Vance's employee credentials approved the transaction.

At 8:21 a.m., a document was printed at the ground-services office.

At 8:29 a.m., our boarding passes were scanned.

At 8:34 a.m., my reservation was canceled.

At 8:36 a.m., Apollo's classification was changed to unaccompanied minor.

At 8:39 a.m., a baggage handling instruction was added.

At 8:45 a.m., Evelyn Price's ticket was purchased.

At 8:51 a.m., her boarding pass was scanned.

At 9:02 a.m., Flight 842 departed.

The sequence was clear.

The receiving authorization existed before the flight began boarding.

The document was printed before our reservations were changed.

My ticket was canceled before Evelyn's boarding pass was scanned.

And the baggage instruction was added while Apollo was still at the gate.

I studied the timestamps.

One detail stood out.

The document had been printed at 8:21 a.m., but the receiving authorization had been created at 8:17.

That meant the printed form could have been generated directly from the vendor account.

If so, the person who collected it might have been able to use it as proof of consent without knowing that the signature had been forged.

I asked Shaw whether the original electronic file had been recovered.

"Not yet," she replied. "The airline is working with its information-security team."

"Can they determine whether the signature was copied from another document?"

"They're examining that possibility."

I thought about my own records.

I had signed hundreds of forms during my career. Some were stored digitally. Others existed only as scanned copies.

A person with access to a legitimate signature could reproduce it without ever meeting me.

But that still left the question of access.

Who had obtained my signature?

The court-appointed guardianship order contained my name, but not the signature used on the yellow slip.

The airline's booking record contained my electronic confirmation, but the approval form did not appear to have been generated through the passenger account.

The Westbridge letter Elena received had no signature from me.

Then I remembered a document I had signed shortly after Elena entered hospice.

It was a temporary medical-contact authorization allowing me to communicate with certain providers about Apollo's treatment.

The form had been submitted to the hospital.

It contained my signature.

It also contained Apollo's full name, date of birth, and the name of her legal guardian.

If someone had accessed that form, they might have copied my signature and obtained the information needed to create the false authorization.

I called Shaw.

"I may know where they obtained my signature."

I explained the medical-contact form.

She asked me to locate a copy and forward it.

I searched the files on my phone.

The form was there.

I opened it and compared the signature to the one on the yellow slip.

The resemblance was immediate.

The forged signature had copied the general shape of the original, including the long final stroke.

But it had reproduced the wrong letter formation and omitted a small mark I always made beneath the last name.

I sent both documents to Shaw.

"If the signature was copied from this form," I said, "someone had access to a document that contained both my identity and Apollo's medical information."

"That is a reasonable line of inquiry," she replied.

"Can the hospital identify who accessed the form?"

"We'll ask them to preserve and examine the relevant access logs."

I put the phone down.

The pieces were finally beginning to connect.

The hospital's scheduling system had been accessed by a third-party account.

Westbridge had obtained information about Apollo's appointments.

A receiving authorization had been created using the vendor's account.

An airline employee's credentials had approved it.

And my signature might have been copied from a legitimate medical-contact form.

The scheme did not require a sophisticated hacker or a hidden room full of computers.

It required access to ordinary records, a willingness to misuse that access, and enough cooperation from separate systems to make a false instruction appear legitimate.

That was what made it dangerous.

At 2:14 p.m., the hospital confirmed that the medical-contact form had been accessed during the period under review.

The access occurred through the same temporary administrative account associated with the scheduling records.

The hospital had not yet established who used the account or whether the access was directly connected to Westbridge.

But the account's activity was now under formal investigation.

I read the update twice.

Apollo sat beside me, looking at the medical documents spread across the table.

"Does that mean they stole your signature?" she asked.

"It means someone may have accessed a document that contained it."

"Can they do that to other people?"

"Unfortunately, yes. That's why we're trying to establish how it happened and prevent it from happening again."

She looked at the yellow slip.

"I keep thinking about what would have happened if I hadn't noticed the paper."

I pulled my chair closer to hers.

"You noticed something was wrong. You asked questions. You kept the evidence."

"But what if I hadn't?"

I considered my answer.

"Then we would still have investigated the records. It might have taken longer, but the truth wouldn't have depended entirely on what you noticed."

She looked unconvinced.

I took her hand.

"You helped us understand what happened. That matters. But this was never your responsibility to prevent. The adults and the organizations involved were responsible for making sure the paperwork was accurate and your safety was protected."

She looked down.

"I know."

I wasn't certain she did.

She had spent too much of her childhood watching adults struggle with problems they could not control. She had learned to become vigilant because vigilance made her feel useful.

I wanted her to understand that she could be careful without becoming responsible for every danger around her.

"You did enough," I said. "You don't have to carry the whole investigation."

She nodded slowly.

Then she placed the yellow slip inside a clear document sleeve and closed the folder.

For the first time, she seemed willing to let someone else hold part of the burden.

At 4:30 p.m., the airline announced that Westbridge's access to the relevant passenger-assistance system had been suspended pending the investigation.

The company would no longer be able to create new receiving-party authorizations through that interface.

The airline also agreed to review the three other passenger cases, notify the appropriate authorities, and audit the process used to verify guardian consent.

Marcus Vance had been removed from his operational duties while the investigation continued.

Evelyn Price remained under investigation.

No final determination had been made about the roles of the other people involved.

I understood that the process would take time.

But for the first time, the system that had been used against us had been changed because we had challenged it.

The records could no longer be altered as easily.

The vendor could no longer create the same authorization through the same channel.

And the airline had been forced to acknowledge that the problem extended beyond one canceled reservation.

That evening, Apollo and I walked along the waterfront.

The air was cool, and the sky had begun to turn gold over the water. She wore a light jacket and carried no bag except the small one containing her phone and a book.

We stopped near a railing overlooking the harbor.

For several minutes, neither of us spoke.

Then Apollo said, "Do you think Mom knew?"

I looked at her.

"Knew what?"

"That Westbridge was going to do something like this."

I thought about Elena's handwritten note.

We never requested this.

Ask the hospital where they got our information.

"I think she knew something was wrong," I said. "She didn't know exactly what it was, but she trusted her instincts enough to ask questions."

Apollo watched the water.

"She always said that being polite didn't mean you had to agree with someone."

I smiled.

"She did."

"And she said that official people can be wrong."

"She was right about that, too."

Apollo was quiet for a while.

Then she slipped her hand into mine.

"I wish she were here."

"So do I."

We stood together until the light faded.

For the first time since the flight, the silence between us felt peaceful.

The investigation was not finished.

But Apollo was safe.

And the truth was finally moving in the right direction.

The Boarding Pass She Kept

Six weeks after Flight 842, I returned to Milwaukee for the first formal review meeting involving Meridian Air, Westbridge Medical Transit, and the investigators examining the disputed passenger records.

By then, the story had changed.

It was no longer described internally as a reservation error.

It was a review of unauthorized record changes, a disputed receiving-party authorization, possible misuse of passenger information, and a series of decisions that had placed a minor at risk.

Those words mattered.

They forced the people involved to examine what had actually happened rather than hiding behind the language of operational inconvenience.

Apollo remained in San Diego with me while we waited for her medical appointment. The specialist had reviewed her updated records and arranged an evaluation that would not require another hurried transfer.

She had also begun sleeping better.

The first week after the incident, she woke several times each night, convinced that someone was waiting outside the room to take her somewhere. She checked the door lock before going to bed and kept the gray folder beside her pillow.

I never told her that she was being unreasonable.

After what she had experienced, her fear made sense.

Instead, we established a routine.

We ate breakfast together.

We went for short walks when she felt up to it.

We kept the curtains open during the day and the lights low at night.

And when she wanted to talk about the flight, I listened without trying to turn every memory into another piece of evidence.

The investigation could use her statement.

Her life could not become an extension of it.

The meeting took place in a conference room at Meridian Air's regional operations office.

Patricia Sloan was there, along with Andrew Keller from compliance. Two representatives from the airline's legal department attended remotely. Officer Shaw and Sergeant Ortega joined through a secure video connection.

A chair had been reserved for Apollo, but she had chosen not to attend.

She had already provided her statement.

She did not owe the airline another performance of her fear.

I sat at the table with the documents arranged in front of me.

The first item was the original itinerary.

The second was the forged receiving-party authorization.

The third was the baggage-routing instruction.

The fourth was Elena's letter from Westbridge.

The fifth was the hospital's preliminary access report.