Missile alert employee not cooperating in probe

So apparently the employee that sent the missile warning is not wanting to speak with investigators.

The Hawaii state employee who mistakenly sent an alert warning of a ballistic missile attack has refused to cooperate with federal and state investigators, officials said Thursday. Lisa Fowlkes, head of the Federal Communications Commission Public Safety and Homeland Security Bureau, said the agency was disappointed by the refusal.

Meanwhile, U.S. Sen. Brian Schatz, a Democrat from Hawaii, told the committee he was introducing legislation making it clear that the authority to issue missile alerts rests with the U.S. departments of Defense and Homeland Security, not with state and local governments.

Spokesman Richard Rapoza said the Hawaii Emergency Management Agency has encouraged all employees to cooperate with investigations of the erroneous message. He said the worker who sent it has also refused to cooperate with the state agency's internal investigations.

The employee issued a written statement about the incident after it happened and he is not wanting to speak further about it.

"He has taken the position that he provided a written statement shortly after the incident, and doesn't need to speak to investigators because he has nothing to add," Rapoza said in an email.

The name of the worker has not been released. He continues to work at the agency but has been reassigned to a section where he doesn't have access to the warning system.

Seems kind of fishy to me. I mean if I make a mistake at work you better believe my place is like office space and I will have 5 different bosses come talk to me about it.

I wouldn't have a job if I issued a written statement on my mistake and then never want to speak about it. What does ATS think?

Link

If he was entrusted with the position of emergency warnings, he should be responsible enough to explain his actions. In what world are you not liable for your actions?
He caused sheer panic, he should be personally liable for any damages due to his negligence.
But then again, Noone seems to be liable for sh#t lately.
Maybe give him a box of tide pods and let nature take its course.

It was not an accident, in my opinion.

a reply to: PraetorianAZ

The fish smell started when he only got reassigned .

Looks he was provided a written statement to give out to the press .Likely by an attorney and anything he says off the script can likely lead to:

1. Opening him up to liability for the royal F up.

or

2. Exposing the whole BS story.


Uhm on the line as which it is but leaning toward liability not for him but all involved in his department.

[snipped]

a reply to: PraetorianAZ

Is this a poorly planned psych op meant to get the war drums beating to NK?

If so it was poorly planned and executed.


The babies being thrown on the floor played much better with the public in Gulf war Part 1 and harder to disprove.


.

a reply to: PraetorianAZ

There's a theory on the Q thread that the false alarm was deliberately activated in order to enable a "bulk data transfer" from Hawaii to DC, presumably on behalf of Trump/White Hats. And that this data transfer blocked any other activity until it completed, therefore that system could not be used to issue a false alarm. All of this was based on posts from Q regarding the false alarm, specifically mentioning "BDT."

That's how I understood it at least. Hopefully someone will correct me if I'm misunderstanding or misexplaining it.

What's to explain?
He simply pushed the wrong button by accident and an alert went out warning of a missile attack on Hawaii.

And it took 38 minutes to let people know that it was an accidental alert.

a reply to: Boadicea

Just to add: The Bulk Data Transfer is set up to automatically happen if there is an impending nuclear attack, to save the data f4om bwing destroyed.

a reply to: PraetorianAZ

The Hawaii state employee who mistakenly sent an alert warning of a ballistic missile attack has refused to cooperate with federal and state investigators, officials said Thursday.

Well that's .. suspicious, if the official narrative, that it was a case of choosing the wrong item in a drop down menu, is true.

Huh.

originally posted by: Jefferton
It was not an accident, in my opinion.

Ummm..."We have a winner"...that seems to be the only scenario that makes sense...

I'm more curious as to the why...and who he's trying to protect...




YouSir

a reply to: butcherguy

He simply pushed the wrong button by accident and an alert went out

Its kind of plausible. Supposedly if you select the real alert option their is a dialog the prompts the user with a "Are you Sure CLick OK" button to continue.
its not unusual for people to automtically just click on dialog prompts and continue , So I can see that happening.

However, I'm really surprised their was not a user prompt that required authentication before sending the alert. Or a multi check process in place.

If that is the case then the complete department needs to be fired from the directors down for allowing such a designing in the first place.

And it took 38 minutes to let people know that it was an accidental alert.

At first I was skeptical but the amount of incompetence with the software is likely very high and it appears they had no way of sending an alert with a modified message to say it was sent by accident. In other words they could only send certain predefined messages.

So apparently they had to modify the code on the fly or hack it to be able to send a custom message stating to ignore the previous warning.

So it does appear to be a case of incompetence which will likely continue as nobody appears to be held responsible. Well except for the monkey pushing the button that is, and not the managers and directors that bought off on the software requirements in the first place.

Well, maybe they should be a bit more aggressiven in ascertaining something from him, the stress these people endured and now to see them read about his refusals, seems like a terrible direction.

I wish I could get away with something serious with just a simple statement, must be nice.

a reply to: interupt42

So apparently they had to modify the code on the fly or hack it to be able to send a custom message stating to ignore the previous warning.

Are you telling me there is no build in way of calling of an alert?

That was all they had to do - nevermind explaining that the alert was a mistake,the priority was to let people know they were safe.

But they had to hack the system to call of the alert?

That is ridiculous.

originally posted by: butcherguy
a reply to: Boadicea

Just to add: The Bulk Data Transfer is set up to automatically happen if there is an impending nuclear attack, to save the data f4om bwing destroyed.

Thank you for adding that -- I didn't know that part of it!

originally posted by: DupontDeux
a reply to: interupt42

So apparently they had to modify the code on the fly or hack it to be able to send a custom message stating to ignore the previous warning.

Are you telling me there is no build in way of calling of an alert?

That was all they had to do - nevermind explaining that the alert was a mistake,the priority was to let people know they were safe.

But they had to hack the system to call of the alert?

That is ridiculous.

Agreed , but that is their story from an article I read. The messages were predefined. Who knows if its true though, but if that was the case then I can see why it took 38 minutes to send a custom alert.

It would be interesting to compare the alerts that have been sent in the past and see if they are all canned responses then compare it to the Oh We Fd up alert.

originally posted by: interupt42

originally posted by: DupontDeux
a reply to: interupt42

So apparently they had to modify the code on the fly or hack it to be able to send a custom message stating to ignore the previous warning.

Are you telling me there is no build in way of calling of an alert?

That was all they had to do - nevermind explaining that the alert was a mistake,the priority was to let people know they were safe.

But they had to hack the system to call of the alert?

That is ridiculous.

Agreed , but that is their story from an article I read. The messages were predefined. Who knows if its true though, but if that was the case then I can see why it took 38 minutes to send a custom alert.

It would be interesting to compare the alerts that have been sent in the past and see if they are all canned responses then compare it to the Oh We Fd up alert.

Actually, 38 minutes is pretty darn fast if they had to hack the system. Even assuming that hack consisted of just modifying messages in plaintext, I would be impressed if they - without any preparation, mind you - managed that:

1)
Issue the alert.

2)
Realise it is the wrong alert

3)
Attempt to nullify it.

4)
Realise that it cannot be nullified.

5)
Realise that you might be able to hack system

6)
Find someone who can hack the system.

7)
Find approach to hack the system

8)
Hack the system

9)
Issue new alert.


All in 38 minutes. That is some competent and quick thinking for an agency who apparently never realised it would be a good idea to be able to call off an alert in the first place.

originally posted by: Jefferton
It was not an accident, in my opinion.

Second that, like if the Deep State wanted to scare the pants of the people of Hawaii...

Meanwhile, U.S. Sen. Brian Schatz, a Democrat from Hawaii, told the committee he was introducing legislation making it clear that the authority to issue missile alerts rests with the U.S. departments of Defense and Homeland Security, not with state and local governments

This right here I think is the key point. Seems like maybe the whole reason why this happened.

I could be wrong and the guy could just have his preferences and ways of doing things but to me it seems like he lied.

He lied about something, and he doesn't want to open himself up for opportunity to be caught in that lie when whatever he says doesn't match up with what he wrote.

That's my first guess anyhow.

-Alee

Was in Maui when the alert came out, we all got the text. Was pretty surreal. But I was struggling with pop ups on my phone, all morning, from the "westjet" app that I downloaded. So when I got the message alert, at first, I was like "naw...not falling for that". But then my father in laws flip phone was getting the alert. No apps on that phone. haha.

We did see military helicopters, later that day, patrolling. Which someone said was a regular occurrence in Hawaii. But we were there 14 days. Only saw them, that day. Also, only assuming they were military and assuming they were patrolling...haha.. They didn't look like the "tourist" helicopters. Pic