“All of them?”
“Yes.”
“Why?”
“Because I want to know whether what happened to me was unusual.”
Nobody answered.
“That should concern you more than tonight’s video.”
Daniel nodded.
“I’ll issue a preservation order.”
“Third. Commission an audit of complaints involving race, appearance, disability, language, class, religious clothing, and perceived economic status.”
A director leaned toward his camera.
“Vanessa, you’re talking about tens of thousands of records.”
“Yes.”
“That will be expensive.”
“So was the acquisition.”
Someone laughed nervously.
I did not.
“And fourth,” I continued, “review the incentive structures.”
Edward spoke for the first time.
“What does that mean?”
“It means I want to know whether employees are being pressured to remove passengers quickly instead of resolving disputes accurately.”
“That isn’t company policy.”
“Policies and incentives are not the same thing.”
His expression hardened.
“Our people are trained.”
“Then the audit will confirm that.”
He leaned back.
“This feels like a prosecution.”
“No.”
I met his eyes.
“It feels like due diligence.”
Daniel tapped his tablet.
“There’s another matter.”
He displayed a document on the screen.
A maintenance memo.
The date was six weeks earlier.
The room suddenly changed.
“What is that?” I asked.
Daniel enlarged it.
“Internal engineering correspondence regarding hydraulic irregularities on the same aircraft family.”
Edward’s face froze.
The maintenance director appeared remotely.
“I haven’t seen that.”
“You’re copied,” Daniel said.
The man leaned closer.
His face went pale.
“I don’t remember receiving it.”
Daniel scrolled.
The memo warned of premature fatigue in a specific batch of hydraulic return lines installed during heavy maintenance.
Not catastrophic failure.
Not a fleet-wide emergency.
But enough irregular measurements had appeared that one engineer had recommended accelerated inspection.
That recommendation had been postponed.
Reason:
Operational impact.
I looked at Edward.
“Did you know about this?”
“No.”
“Are you sure?”
“Yes.”
Daniel opened another email.
Edward was copied.
The room fell silent.
“Being copied doesn’t mean I read every engineering message.”
“That’s fair,” I said.
Then I looked toward the maintenance director.
“Who postponed the inspections?”
He hesitated.
“Operations planning.”
“Under whose authority?”
Another pause.
“Mine.”
“Why?”
“The engineering data did not justify emergency grounding.”
“I didn’t ask why you didn’t ground the fleet.”
He swallowed.
“I asked why you postponed the inspections.”
“Aircraft availability.”
There it was again.
Schedules.
Costs.
Utilization.
The invisible mathematics behind modern aviation.
Necessary mathematics.
Until numbers begin to outweigh judgment.
“How many aircraft have those lines?”
“Possibly thirty-eight.”
“Possibly?”
“We need serial verification.”
“How long?”
“Four hours for records. Longer for physical inspections.”
“Start now.”
Edward sat forward.
“Vanessa.”
I turned.
“Thirty-eight aircraft represent almost twelve percent of our long-haul capacity.”
“I understand.”
“If you ground them simultaneously, tomorrow morning’s network collapses.”
“I didn’t say ground all thirty-eight.”
He relaxed slightly.
“I want engineering to identify every aircraft with an affected component. Any aircraft showing anomalous pressure data gets removed from service immediately. The others receive inspections at the earliest controlled maintenance window.”
The engineering director nodded.
“That’s reasonable.”
“And nobody from finance, commercial planning, investor relations, or executive management overrides engineering.”
Nobody spoke.
I looked around the table.
“That includes me.”
That got their attention.