Chapter 8 - The Second Aircraft
“FLIGHT 218 HAS PASSENGERS ON BOARD, AND THE CAPTAIN IS WAITING FOR AN ANSWER.”
Sarah Mitchell was standing in Meridian Air's operations center when she delivered the news.
The enormous room was filled with computer monitors displaying weather patterns, aircraft locations, crew assignments, and flight schedules across the United States.
Under normal circumstances, it was the kind of place where problems were solved before passengers ever noticed them.
That morning, it felt like the center of a gathering storm.
I stood beside Sarah while an operations supervisor spoke with the crew in Phoenix.
“The aircraft is holding at the gate,” he said. “Boarding is complete, but the captain hasn't accepted the maintenance release.”
“Good,” Sarah replied.
A dispatcher looked toward us.
“We've located the original discrepancy. The electronic record says it was resolved by a third-party maintenance provider.”
“Asterion?” I asked.
“Yes.”
My stomach tightened.
The same contractor whose managing partner was Evelyn Sloan's brother.
The same contractor associated with unexplained payments.
The same contractor whose privileged credentials appeared in suspicious electronic maintenance records.
Sarah turned toward me.
“We're not assuming every Asterion record is fraudulent. But we cannot rely on questionable signoffs without verifying the underlying work.”
I nodded.
“Then follow the process. Inspect what needs inspecting.”
The supervisor returned to his headset.
A moment later, Captain Vanessa Reed, the pilot assigned to Flight 218, joined us by telephone.
“I've reviewed the discrepancy,” she said. “I'm not accepting this aircraft until Maintenance Control explains the conflicting entries.”
Sarah nodded.
“That's the correct decision.”
There was a pause.
Then Captain Reed said something I would remember long afterward.
“I've got a little girl in row seventeen who's traveling to Denver for cancer treatment. Her father asked the flight attendant whether we were leaving on time.”
Nobody spoke.
Finally, she continued.
“I want that child to reach her appointment. But I also want her to reach it safely.”
I closed my eyes.
There it was again.
The human reality behind every decision.
A canceled flight was not merely a line in a financial report.
It could mean missed medical treatment, lost wages, a funeral someone could not attend, or a family unable to reunite.
That was why airline leadership had to take reliability seriously.
But reliability built on falsified records was not reliability at all.
“Captain Reed,” I said, “we'll arrange another aircraft if necessary. The airline will work with that family to find a safe way to reach Denver.”
“Thank you, ma'am.”
“I'm the one who should thank you.”
After the call, I asked the operations team to identify passengers with urgent medical travel needs and coordinate appropriate rebooking support without exposing anyone's private information.
We couldn't erase the disruption.
But we could refuse to treat passengers as anonymous numbers.
Later that morning, the digital forensics team completed its first fleet-wide review.
Nineteen suspicious maintenance entries had been identified across eight aircraft.
Not all eight airplanes had unresolved safety concerns. Several records were ultimately supported by legitimate maintenance evidence.
Others could not be immediately verified.
Sarah organized technical reviews for the affected aircraft, coordinating with Maintenance Control, the operating crews, independent inspectors, and the FAA as appropriate.
One aircraft already airborne had an entry requiring additional review. After discussing the available technical information with Maintenance Control, its captain elected to land at a suitable alternate airport for inspection.
Nobody panicked.
Nobody ordered a dramatic emergency descent.
Qualified professionals made a careful operational decision based on what was known.
I found that more reassuring than any confident executive speech.
By noon, media reports were describing a widening maintenance investigation at Meridian Air.
Our stockholders were demanding information.
Employees were frightened.
The financing group requested an immediate update.
And Adrian Whitmore's supporters were telling directors that I had created a crisis that could destroy the company.
But new evidence was beginning to reveal something far more disturbing.
Sarah entered my office carrying an internal audit report.
“The problem may not be limited to individual maintenance releases.”
“What do you mean?”
“Asterion appears to have been given unusual authority to manage electronic inspection documentation. The contractor could initiate administrative sessions that should have required tighter internal oversight.”
“Who approved that access?”
“We're investigating.”
David leaned forward.
“Was the arrangement disclosed to the audit committee?”
“Not in the form we've found.”
I looked at the report.
Asterion had been hired eighteen months earlier to support maintenance documentation, equipment inspections, and operational efficiency.
Its services were supposed to supplement Meridian Air's internal maintenance department.
But the contract had gradually expanded.
Asterion was now handling portions of the data reconciliation process, producing inspection-support reports, and receiving substantial payments for work that could not always be matched to independent source documents.
“How much did Asterion receive?” I asked.
David opened a spreadsheet.
“More than eighteen million dollars in twelve months.”
“And how much of that can we verify?”
“We don't have a reliable figure yet.”
I stared at him.
Eighteen million dollars was enough to fund significant aircraft maintenance, employee training, and passenger service improvements.
Yet we were struggling to establish whether the company had received the services it paid for.
“Who approved the invoices?”
“Finance.”
“Evelyn.”
“Her department. We're tracing the specific approvals.”
I nodded.
“Keep following them.”
At three that afternoon, Sarah received a call from a technology specialist who had worked on Asterion's original software integration.
Her name was Jana Hayes.
She had left the contractor four months earlier.
Jana wanted to speak with us, but only if she could do so confidentially.
We arranged a secure call with Julia present.
Her face appeared on the screen.
She was a woman in her early thirties, with anxious blue eyes and dark hair pulled into a loose ponytail.
“Before I say anything,” she began, “I need to know whether you can protect me from retaliation.”
Julia explained the reporting protections available to her, their limitations, and the steps we could take to preserve her identity during the initial investigation.
Jana listened carefully.
Then she looked into the camera.
“I helped build the reporting interface Asterion used for Meridian.”
“What did that interface do?” Sarah asked.
“It was supposed to synchronize maintenance-support records with Meridian's internal systems.”
“Was it capable of changing aircraft release status?”
“Not originally.”
I leaned forward.
“What changed?”
Jana swallowed.
“About six months ago, management ordered us to create a privileged administrative workflow. They called it the exception-reconciliation process.”
“Who ordered it?”
“I received the technical request through Asterion's management.”
“Did the request identify an executive sponsor?”
“Yes.”
She glanced away from the screen.
“Evelyn Sloan.”
I felt my pulse quicken.
Jana continued.
“The new workflow could create a clean-looking summary record even when supporting documentation was still missing.”
Sarah's expression hardened.
“Are you saying the interface could falsely indicate completed maintenance?”
“It could present a discrepancy as administratively resolved. If someone also misused valid certifying credentials, the resulting record could look legitimate to another system.”
I sat completely still.
That was how a dangerous gap could develop.
The airline's official systems were designed to require qualified maintenance personnel to certify work.
But someone had built a pathway that could make incomplete information appear complete.
“Why did you leave Asterion?” I asked.
Jana looked down.
“Because I told them the design was dangerous.”
“What happened?”
“My manager said I didn't understand the business requirements.”
Her voice became bitter.
“I understood them perfectly. They wanted the dashboard to look clean.”
“Did you keep any records?”
She hesitated.
“Yes.”
“Where?”
“In an encrypted archive I created before I resigned.”
Julia leaned forward.
“We can arrange a lawful, secure review. Please don't alter or distribute the original files.”
Jana nodded.
“I have one more thing to tell you.”
I waited.
“When they demonstrated the new workflow, they used an example aircraft record.”
“Which aircraft?”
Jana took a slow breath.
“The example contained the same maintenance issue you're investigating now.”
I frowned.
“Flight 604?”
“The aircraft later assigned to Flight 604.”
Sarah looked at me.
“How long ago was the demonstration?”
Jana checked her notes.
“Three weeks before the flight.”
I stared at the screen.
The supposedly emergency exception process had been demonstrated using the same aircraft's maintenance issue weeks before the cancellation.
Then Jana added the final detail.
“The project file had a name.”
“What was it?”
May you like
She looked directly into the camera.
“Operation Clear Sky. And the instructions said the project had to be completed before Meridian's four-hundred-million-dollar financing closed.”
