Thursday, June 21, 2012

Just Take Note la!

If you can recall, our Navy and Armed Forces usually get over heavy comments by the general public for incidents that affect our military assets. I personally am of the opinion that if the Standard Operating Procedures has been adhered to, if shit happens, shit happens! That is what a court-martial is supposed to do, to find out who to partition the blame if any, and those uninformed are just making useless allegations otherwise.

The reason I am writing this is to say who are we to blame our military men for such incidents without investigations, when unheard of reasons may be the cause of incidents that cause great losses.

A case in point, a recent mishap affecting the great US Navy that may have happened as a result of all things, a vacuum cleaner malfunction.

US Navy blames vacuum cleaner for submarine fire

A fire that caused damage estimated at USD400 million to one of the US Navy's Los Angeles-class nuclear attack submarines probably started inside a vacuum cleaner, according to early findings. Officials at Portsmouth Naval Shipyard in Kittery, Maine, said on 6 June that it was likely that the vacuum cleaner had sucked up an unidentified "heat source", which had then ignited other debris in the appliance

[first posted to - 14 June 2012]

and the news of the incident itself

Submarine fire caused deciding senator to miss biofuel vote

The US Senate Armed Services Committee's final action on the Fiscal Year 2013 (FY13) defence authorisation bill narrowly approved provisions to severely restrict the Pentagon's ability to invest in or use biofuels because the deciding vote was not cast due to a submarine fire. Senator Susan Collins, a moderate Republican from Maine who usually votes with committee Democrats in support of renewable energy measures, left the closed hearing room in the midst of roll call votes on 24 May to participate in a conference call with the commander of the Portsmouth Naval Shipyard in Maine, where a Los Angeles-class nuclear attack submarine, drydocked in the third month of a 20-month overhaul, had been ablaze since the evening before

[first posted to - 31 May 2012]

No comments: