The airline would also examine whether loyalty-program benefits were being interpreted inconsistently across different routes and cabin teams.
None of those measures could guarantee that the problem would never recur.
But they were concrete steps.
They required more than an apology.
They required Blue Ridge to examine the decisions it had previously treated as routine.
At 6:20 p.m., Nathan was leaving his office when Daniel called.
"We have the first complete report on the additional support."
Nathan stopped beside the elevator.
"How much?"
"Before I give you the number, I want to explain the assumptions."
"Go ahead."
"The review covers the last eighteen months. We excluded ordinary product support, contractual emergency response, and work covered by separate paid amendments. We included only the additional labor we could reasonably identify and classify."
"Good."
"Some time records are incomplete. We used conservative estimates where we had supporting email or ticket records."
"And the result?"
Daniel paused.
"Approximately nine hundred and forty hours of additional work."
Nathan looked toward the elevator doors.
"Across eighteen months?"
"Yes."
"That is significant."
"It is. But I want to be careful. It doesn't mean Blue Ridge owes us money. Much of the work was provided without a separate agreement to pay for it."
"I understand."
"The estimated labor cost is substantial, but we should not present it as an outstanding debt."
"Agreed."
Daniel continued.
"The report also shows that most of the requests came from a relatively small number of Blue Ridge managers. Several were operationally reasonable. Others were last-minute reporting requests. A few were repeated variations of the same analysis."
"Did the account team ever tell Blue Ridge that the requests were outside scope?"
"Yes, in several cases. But the documentation doesn't always show whether the client understood that the work was being provided as a courtesy."
Nathan rubbed his forehead.
"Then our own process was part of the problem."
"Yes."
"Make sure the report says that."
"I will."
Nathan stepped into the elevator.
"Anything else?"
"One detail. The work wasn't evenly distributed. Three employees performed nearly half of the additional hours."
"Who?"
Daniel gave him the names.
Nathan recognized two of them as senior engineers who had worked with Blue Ridge since the early years of the relationship.
"Have they been compensated for the overtime?"
"Where it was recorded, yes. But some of the work was completed during normal hours by shifting other tasks later."
"So the cost wasn't always visible as overtime."
"Correct. It appeared as delayed work elsewhere."
Nathan closed his eyes briefly.
That was the part he disliked most.
The favors had not simply consumed time. They had displaced other work.
A request from Blue Ridge might have been completed quickly, but the consequences could have appeared days later in another client's delayed report or an engineer's overloaded schedule.
The cost had been distributed across the company.
It had become difficult to see precisely because it had been absorbed so quietly.
"Daniel, I want to review the staffing impact as well as the labor estimate."
"I've already asked the team to do that."
"Good."
The elevator doors opened.
Nathan walked toward the parking garage.
"One more thing," he said. "How many other accounts have the same pattern?"
"We're still checking. Blue Ridge isn't unique in asking for additional help. The question is whether our teams are documenting it consistently."
"Then we need to establish a company-wide standard."
"That could take time."
"Start with the largest accounts and the most heavily used support teams."
"All right."
Nathan ended the call.
He sat in his car for several minutes before starting the engine.
Nine hundred and forty hours.
That number represented more than twenty-three full workweeks if calculated on a forty-hour schedule.
It represented engineers answering messages after dinner, analysts revising reports before meetings, and managers telling their teams that one more favor would help preserve an important relationship.
It represented work that had been done because people wanted to be helpful.
It also represented a process that had failed to protect their time.
Nathan thought about his father at the transit depot.
He remembered the way his father had treated work as something that deserved honesty. A repair was either complete or incomplete. A part was either installed or missing. A problem could be difficult, but pretending it did not exist never made it easier to solve.
"Don't let people confuse kindness with a blank check," his father had once told him.
Nathan had not understood the full meaning of the sentence when he was young.
He understood it now.
The next morning, Blue Ridge would issue its first formal statement about Flight 418.
Nathan had no control over what it would say.