"An arrogant flight attendant summoned security to put me in handcuffs at seat 14A because I looked poor

Chapter 26

Theme:
Font Size:
24px

The interview was conducted by the outside investigators.

I did not attend.

But afterward, with Natalie's permission, Naomi Fletcher briefed me on the central facts.

Natalie had discovered the unusual access activity while reviewing system performance.

At first, she assumed it was part of a legitimate compliance review.

Then she noticed that the account had opened several unrelated complaints in rapid succession.

Some involved senior managers.

One involved a former employee who had alleged retaliation.

Another concerned the maintenance-reporting process.

Natalie checked whether an authorized review had been scheduled.

She found no matching request.

She reported the activity to her supervisor, Peter Lang.

Peter told her the access was legitimate and instructed her not to pursue it.

Natalie asked whether she should document the explanation in the audit record.

Peter told her it wasn't necessary.

That was the moment she became concerned.

She didn't know whether anyone had misused the information.

She didn't know whether the access had been approved verbally.

But she believed the activity needed to be documented.

She submitted a formal report.

Two days later, her position appeared on the revised restructuring list.

When Naomi asked how she felt about the sequence of events, Natalie gave an answer that stayed with me.

“I don't know whether they're trying to get rid of me because I reported it. That's what frightens me. I can't tell whether I'm imagining a connection or whether someone is making a decision I can't see.”

I understood that uncertainty.

It was the feeling of knowing something was wrong without yet having enough information to explain it.

Natalie had not demanded that anyone be fired.

She had not asked for a promotion.

She wanted to know whether the access was authorized and whether her job was being eliminated for legitimate reasons.

Those were reasonable questions.

The company owed her a careful answer.

Four days later, the investigators identified the person who had accessed the files.

It was not Eleanor Price.

It was Michael Rourke, her chief of staff.

Michael had worked at Northstar for nearly nine years.

He was known as organized, discreet, and exceptionally efficient.

He managed board schedules, prepared briefing materials, and coordinated sensitive communications.

According to the access logs, he had used the administrative account to open seventeen complaint records.

When interviewed, he acknowledged accessing them.

He said he had been preparing a confidential briefing for Eleanor about management risks.

The investigators asked for the briefing.

Michael produced a draft document.

It summarized several employee complaints, including some that involved senior managers.

At first glance, the explanation appeared plausible.

But Daniel Cho found something troubling.

The draft briefing had been created after Natalie reported the access activity.

Its metadata showed that the document had been assembled several days later.

That didn't prove Michael had acted improperly.

He could have begun gathering information before preparing the formal document.

But it raised another question.

Why had he accessed complaints unrelated to the board's scheduled reviews?

The investigators continued examining the records.

They discovered that Michael had communicated with Peter Lang, Natalie's supervisor, shortly after the unusual access was reported.

The messages were brief.

One asked whether the system activity had attracted attention.

Another requested confirmation that the issue was being handled internally.

Peter replied that he had spoken with the analyst.

Then, two days later, the restructuring list changed.

When the investigators asked Peter about those messages, he initially described them as routine administrative communications.

But he could not explain why Michael had been concerned about an audit alert.

Nor could he produce a legitimate business request authorizing the access.

The review widened.

For the first time, I began to suspect that the problem involved more than an outdated administrative account.

On Friday afternoon, Olivia entered my office carrying a folder.

Her expression was grim.

“Vanessa, the investigators found a connection between Michael Rourke and the restructuring proposal.”

I put down my pen.

“What connection?”

“He contacted Peter Lang before Natalie's position was added to the elimination list.”

I looked at her.

“Did he direct Peter to add it?”

“There's an email suggesting he wanted the analytics team reorganized.”

“That's not necessarily improper.”

“No. But the timing and the surrounding communications are concerning.”

She handed me the document.

Michael had written:

We need to ensure the current reporting structure doesn't create unnecessary complications for the board's information flow. Please review whether the analytics oversight function can be consolidated.

I read it twice.

“That's vague.”

“Very.”

“Could it refer to legitimate organizational concerns?”

“Yes.”

“Could it also be an attempt to remove the person who identified the access?”

“Yes.”

I placed the paper down.

“What does Peter say?”

“He says Michael suggested the consolidation but didn't specifically instruct him to eliminate Natalie.”

“Was Natalie's position already at risk?”

“The department was under review, but the investigators haven't found a documented decision to eliminate her role before she raised the concern.”

News in the same category

"An arrogant flight attendant summoned security to put me in handcuffs at seat 14A because I looked poor

45 Part