Chapter 9 - The Money Hidden Behind the Maintenance Records
“THIS WAS NEVER JUST ABOUT KEEPING ONE AIRPLANE ON SCHEDULE.”
David stood before a large display screen in our temporary investigation office.
On the wall were three sets of documents.
The first showed suspicious maintenance-record changes.
The second showed payments to Asterion Aviation Services.
The third showed the refinancing agreements Evelyn Sloan had spent months negotiating.
Individually, each set of records raised questions.
Together, they suggested a disturbing financial motive.
The four-hundred-million-dollar refinancing was supposed to help Meridian Air stabilize its debt and modernize its fleet.
Lenders had requested detailed information about maintenance costs, operating performance, potential liabilities, and significant compliance concerns.
Those were reasonable requests.
A lender financing an airline needed to understand the risks.
But our financial statements and operational reports had presented a picture that was becoming increasingly difficult to reconcile with the evidence.
David pointed toward the maintenance-expense summary.
“Several costs were recorded as contracted efficiency services rather than as direct aircraft repair expenses.”
“Is that necessarily wrong?” I asked.
“No. The classification depends on the actual services and accounting rules. But the invoices we're reviewing don't consistently match identifiable work.”
Julia opened another file.
“Asterion charged Meridian for inspection-support services on dates when internal records show no corresponding inspection activity.”
I frowned.
“How many?”
“The independent accountants are still working through them.”
“And the payments?”
David enlarged the vendor ledger.
Asterion had received regular transfers from Meridian Air.
Some were ordinary contractual payments.
Others were unusually large and approved outside normal review cycles.
An independent financial investigator had also found related-party connections involving Nathan Sloan, Evelyn's brother.
“Was Evelyn's relationship with Nathan disclosed to the board?” I asked.
“Not in the conflict-of-interest records we reviewed.”
I sat back.
For eight years, Evelyn had lectured me about financial discipline.
She had challenged departmental budgets, demanded efficiency improvements, and pressured managers to explain minor expenses.
Yet a company associated with her brother had received millions of dollars without the transparency our governance rules required.
“Do we know she personally benefited?” I asked.
“Not yet,” David answered.
“Then don't assume it. Keep the allegations separate from what we can prove.”
He nodded.
I had no intention of allowing my anger to compromise the investigation.
If Evelyn had committed wrongdoing, the evidence needed to establish it.
If someone else had used her position without her knowledge, that also needed to be discovered.
Truth was not something we were entitled to simplify simply because we disliked the people involved.
That afternoon, I visited the maintenance employees' break room.
I had asked the local station manager not to arrange a formal appearance.
No photographers.
No speeches.
No carefully chosen employees waiting to shake my hand.
I wanted to speak with the people whose jobs were being discussed in every corporate meeting.
The room smelled of coffee, microwave meals, and machine oil.
A dozen employees sat around worn tables.
Conversation stopped when I entered.
I could feel their suspicion.
A young mechanic stood near the vending machine.
“Are we getting laid off?”
The question was direct.
I appreciated that.
“I don't know yet,” I answered. “We're reviewing the financial situation and the maintenance operation. I won't promise something I can't guarantee.”
Another employee folded his arms.
“That's what executives always say before they start cutting people.”
He wasn't wrong to be skeptical.
I pulled out a chair.
“Then tell me what you need to know.”
For the next forty minutes, they did.
They told me about supervisors who pressured technicians to close tasks quickly.
About overtime requests denied while employees were expected to do the same amount of work.
About safety concerns treated as scheduling failures.
About workers who felt they had to choose between reporting a problem and protecting their next paycheck.
One woman named Denise Parker, a maintenance planner who had been with the company for seventeen years, spoke last.
“Ms. Carter, I don't think you understand how people like us experience your company.”
I nodded.
“Then help me understand.”
“When the airline does well, the executives get bonuses. When a plane breaks, we get asked why we didn't prevent it. When we refuse to sign something, we get called difficult.”
Her eyes were steady.
“It's hard to believe safety comes first when the people who protect it are the first ones threatened.”
I had no immediate answer.
So I listened.
Denise continued.
“I've got a son in college. My husband's recovering from a stroke. I can't afford to lose this job.”
“I'm sorry you're carrying all of that.”
She shook her head.
“I don't need sympathy. I need a company that doesn't make me choose between my family and my integrity.”
That sentence stayed with me.
Later, I returned to the executive floor and asked for the previous eighteen months of performance-incentive criteria.
The documents confirmed something I had feared.
Senior executives received substantial bonuses based partly on operating margin, fleet availability, and completion of the financing.
There was a safety-compliance component, but it had little practical weight in the overall compensation formula.
A manager could receive a large financial reward for meeting performance targets.
A technician received no comparable reward for preventing an unsafe departure.
The imbalance was obvious.
And I had approved an earlier version of that compensation framework.
It was another uncomfortable truth I would have to confront.
At seven that evening, Jana's encrypted archive arrived through the independent investigation team's secure evidence process.
The digital specialists began preserving the original files and verifying their integrity.
One document caught their attention.
It was a presentation prepared for Operation Clear Sky.
The title was bland.
OPERATIONAL DATA RECONCILIATION — PHASE THREE.
But the internal comments were not.
One note read:
Outstanding maintenance exceptions must not interrupt the refinancing closing window.
Another stated:
Executive Operations will manage unresolved exception visibility until completion of financial certification.
I stared at the words.
“Visibility,” I repeated.
David nodded grimly.
“They weren't necessarily fixing the underlying problems. They were managing whether other people could see them.”
I looked through the remaining pages.
Then I found a spreadsheet attached to the project.
It listed the aircraft scheduled for special documentation handling.
Flight 604's aircraft was included.
So was the aircraft assigned to Flight 218.
At the bottom of the spreadsheet was an approval field.
Two executives were listed.
ADRIAN WHITMORE — OPERATIONS
EVELYN SLOAN — FINANCE
I leaned back slowly.
For the first time, we had a documented connection between both executives and the same project.
David's phone rang.
He answered, listened, and then turned toward me.
“Naomi, the independent accountants have identified a payment account that may have received funds from Asterion.”
“Whose account?”
“We need the bank records to confirm it.”
“What's the beneficiary listed as?”
He paused.
Then he said:
“Whitmore Strategic Consulting.”
I stared at him.
Adrian Whitmore had not simply been under pressure to make the refinancing happen.
The preliminary records suggested that a company connected to him might have been receiving money from the contractor whose systems helped conceal the maintenance discrepancies.
May you like
And the question was no longer whether he had acted recklessly.
It was whether he had been paid to look the other way.
