It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: AugustusMasonicus
I think I'll wait for the Navy to make a comment on that.
originally posted by: carewemust
a reply to: research100
Yes, some Sailors and/or contractors were injured and taken to the hospital...but none are life-threatening, thank God.
originally posted by: mightmight
There's a renewed fire on the stern. Black smoke, indicating fuel burning.
If you check the progression of the fire on the linked stream four the past four hours, it looks like the fire has been spreading through the entire hangar deck.
originally posted by: mightmight
a reply to: AugustusMasonicus
this good enough?
twitter.com...
San Diego Fire Chief Colin Stowell told CNN that all fire personnel immediately withdrew from the ship and a nearby pier was evacuated following an explosion onboard that was traced to a 55-gallon drum filled with a chemical used for cleaning tools. He said that there was also explosive ordnance onboard and that firefighters had to be especially cautious.
originally posted by: CriticalStinker
originally posted by: mightmight
a reply to: AugustusMasonicus
this good enough?
twitter.com...
Jet fuel doesn't melt steel seams. The shell will remain.
On 5 August 2017, after taking off from Bonhomme Richard a U.S. Marine Corps MV-22 Osprey of Marine Medium Tiltrotor Squadron 265 with the 31st Marine Expeditionary Unit crashed in Shoalwater Bay on the east coast of Australia.
originally posted by: Krusty the Klown
At this point the Admiral says the ship is salvagable, but you would think that might be premature, when no investigations or inspections have been carried out.
originally posted by: AugustusMasonicus
a reply to: mightmight
Which refutes your point that the 'ship is lost'. Firefighting is still occurring.