Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: Pilsner
I hope you are right, and my concerns are unfounded.

You sound like a concern troll nitpicking a few select
instances in an effort to demonize the whole Navy.

27 posted on 06/14/2022 2:25:53 AM PDT by philman_36 (Pride breakfasted with plenty, dined with poverty and supped with infamy. Benjamin Franklin)
[ Post Reply | Private Reply | To 24 | View Replies ]


To: philman_36
You sound like a concern troll nitpicking a few select instances in an effort to demonize the whole Navy.

Is it possible to cherry pick "a few select instances" and give a false impression, good or bad, of a large organization? Sure.

What reason do we have, on June 14th, 2022, to be confident that these "instances" are not representative of the current culture of the US Navy? Representative of the least efficient ships hopefully, but representative of what one would expect to find in the US Navy.

And what reason do we have to be confident that these "instances" are not representative of the average US Navy ship, which were unfortunate enough to encounter a nonroutine situation that exposed them?

A theme that runs through these mishaps is orders and procedures are not followed. The US Navy, and its COs, have adopted standing orders and procedures that cannot realistically be followed, given the state of the crews and ships, so they are not. The chain of command knows that. But rather than adopting standings orders and procedures that make sense, given the state of the crews and ships, and then ruthlessly ensuring they are followed, and accepting responsibility, they turn a blind eye, and hope

28 posted on 06/14/2022 5:28:51 AM PDT by Pilsner
[ Post Reply | Private Reply | To 27 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson