That gave me the idea.

Not a good idea.

A useful one.

I called my supervisor from the parking garage.

“I want to stay covered.”

Silence.

“How covered?”

“Meridian still thinks I'm an ordinary passenger.”

“They know local police released you.”

“They don't know why.”

Another pause.

“What are you proposing?”

“I file a complaint exactly like everyone else.”

“We already have eighty-six.”

“Not like this one.”

“You have a recording.”

“Yes.”

“You have a witness.”

“Yes.”

“And you want to give them a chance to process a complaint whose underlying facts we already know.”

“Yes.”

My supervisor exhaled.

“You understand the risk.”

I did.

If Meridian flagged me as disruptive, I could be restricted from flying.

If someone inside the company decided to escalate the original report, I could spend days dealing with consequences that would be inconvenient even with federal credentials.

More important, the complaint process itself could become contaminated if the company learned too early that I was investigating them.

The cleaner choice was to end the undercover phase, preserve the evidence, and proceed.

The harder choice was to wait.

“What do you expect them to do?” my supervisor asked.

I looked across the parking structure at aircraft moving behind the terminal glass.

“I don't know.”

That was true.

Then I added, “That's why I want to see it.”

The authorization took two hours.

At 1:43 that afternoon, I submitted a passenger complaint through Meridian Atlantic Airways' website.

I described the incident accurately.

I wrote that the cart had been bumped by the passenger beside me.

I wrote that a second passenger had witnessed it.

I wrote that the flight attendant accused me of conduct I had not committed.

I wrote that law enforcement detained me after landing.

I did not mention my occupation.

I did not mention the recorder.

I did not mention the investigation.

The automated email arrived thirty seconds later.

Thank you for contacting Meridian Atlantic Airways. Your concerns are important to us.

I had read that sentence in thirty-seven complaint files.

This time it had my name above it.

Three hours later, another message arrived.

Due to the nature of the onboard event, your complaint has been referred to Corporate Customer Integrity and Safety for review.

I had seen that department name before too.

It appeared in forty-three of the eighty-six cases.

I closed my laptop.

For the first time all day, I looked at my wrists.

The red lines from the cuffs were fading.

The record was not.

Part III — The First Draft

Three days later, Meridian called me.

I was sitting in a federal conference room with my supervisor and two attorneys when my phone vibrated.

Unknown number.

I put it on speaker.

“Mr. Davis?”

“Yes.”

“This is Meridian Atlantic Airways calling about your recent travel experience.”

The voice was male, practiced, pleasant.

“I understand there was an incident aboard Flight 2208.”

“There was.”

“We've reviewed the preliminary crew documentation, and I'd like to hear your perspective.”

“My perspective is in the complaint.”

“Of course. I'd just like to clarify a few details.”

“Go ahead.”

He asked whether I had consumed alcohol before or during the flight.

No.

He asked whether I had touched the cart.

No.

He asked whether I had been upset because my predeparture beverage was delayed.

“No.”

“Did you express dissatisfaction with the level of service?”

“I asked for water.”

A pause.

“Did you raise your voice when making that request?”

“No.”

“According to our crew report, there was a pattern of increasing agitation.”

“What did I do?”

Another pause.

“The report describes verbal escalation.”

“What words did I use?”

“I don't have a direct quotation.”

“What action did I take?”

“The report indicates you made physical contact with service equipment.”

“I did not.”

“Mr. Davis, I'm not making a determination on this call.”

“Then what are you doing?”

“Gathering information.”

“From me?”

“Yes.”

“Are you gathering it from the passenger in 4A?”

Silence.

“I don't have access to the witness list.”

“He gave police a statement.”

“That would be a matter for local authorities.”

“Are you gathering information from Ashley Brown?”

Another pause.

“I can't discuss employee interviews.”

The call lasted eleven minutes.

When it ended, nobody in the conference room spoke for several seconds.

One of the attorneys finally said, “He never asked about the spill.”

“No,” I said.

“He asked about your reaction to the spill.”

“Yes.”

My supervisor looked at the transcript being generated from the call.

“They started with the crew's conclusion.”

“That is how most of the complaint files read.”

The distinction was subtle but important.

A neutral investigator asks what happened.

Meridian's reviewer had asked why I became agitated.

The behavior had already been assumed.

Only the explanation remained open.

On day five, the preservation orders went out.

The airline did not know the full scope of the inquiry, but it was legally required to retain digital records connected to a defined set of complaints, including mine.

That was when the case changed.

Not because of my recording.

Because of Ashley Brown's first draft.

The forensic team found it inside Meridian's incident-reporting system.

The file had been autosaved at 8:04 a.m., twelve minutes before Brittany submitted her report.

Ashley had written:

Passenger in 4A moved arm after coffee spilled on sleeve. Arm contacted cart. Cart shifted toward 4B. Coffee landed on laptop belonging to passenger in 4B. Passenger in 4B requested napkins. Passenger did not make contact with cart.

At 8:09, the draft changed.

Passenger in 4B became upset after coffee contacted personal property. Interaction became tense.

At 8:13, it changed again.

Passenger in 4B became verbally confrontational following service incident and interfered with beverage cart.

The final version, submitted under Ashley's employee credentials at 8:17, contained a sentence nearly identical to Brittany's:

Passenger became verbally confrontational after a service-related issue, physically interfered with cabin equipment, and failed to comply with repeated crew instructions.

The same language the trooper had read to me in Boston.

The same structure we had seen elsewhere.

I stared at the version history on the screen.

“Did Ashley make the edits?”

The forensic examiner shook his head.

“Not all of them.”

He enlarged the audit trail.

The first two versions came from Ashley's assigned handheld device.

The final edit came from the lead-attendant terminal in the forward galley.

Brittany's login.

Nobody said anything.

The examiner opened another field.

“There is more.”

The final report had passed through a dropdown workflow labeled EVENT CLASSIFICATION.

The selected category was Passenger Conduct — Aggressive/Noncompliant.

Under it was a checkbox.

Populate recommended language.

It had been checked.

The system had inserted a paragraph automatically.

Verbally confrontational.

Physical interference.

Failed to comply.

There was the template.

Not the six words yet.

But the beginning of it.

I leaned closer to the monitor.

“Who created the classification language?”

“We're tracing that.”

“Was it available to all crews?”

“Yes.”

“Does it require factual inputs before it generates text?”

The examiner hesitated.

“Some.”

“What kind?”

“One or more behavior boxes.”

He opened them.

Raised voice.

Refusal of instruction.

Physical interference.

Threatening posture.

Unauthorized movement.

Brittany had checked three.

Raised voice.

Refusal of instruction.

Physical interference.

The system built the paragraph around those selections.

“What if none are checked?”