It seems more like he panicked when he leaked his letter to the press. It is hard to fault his leaders for removing him from that post.
-
-
- 1 more reply
New conversation -
-
-
He did what he thought he had to do. The Navy did what they absolutely had to do.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Opsec first. Can’t let the world know we have a vulnerable crew floating at sea.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Fact of the day! Deep pull
End of conversation
New conversation -
-
In his statement on the topic, Secnav was quite transparent and sympathetic. This was not the typical “lost confidence etc” announcement. This situation is highly nuanced.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
No, what he did was break rank, caused a panic with sailor family’s and put in doubt the readiness of the ship. He was rightfully removed.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I don’t have all the details, but there seems to be some issues with leaking this outside Chain of Command. OPSEC would my biggest concern, since you’re alerting Nation States in a region that you have situation on your vessel that could make your crew Non-Mission Capable.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
This Tweet is unavailable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.