Fifteen Marines injured in California training incident

The injured Marines were evacuated to hospitals in the area


Afp September 14, 2017
US Marines work with an instructor on the firing range as they train to be a member of a Fleet Antiterrorism Security Team (FAST) unit at a training ground in Chesapeake, Virginia, September 25, 2012. PHOTO: REUTERS/Jonathan Ernst

LOS ANGELES: Fifteen US Marines were injured Wednesday, five critically, when their amphibious assault vehicle caught fire during a training exercise, a military spokesperson said.

The incident occurred at Camp Pendleton, California while a Marine battalion was undergoing a combat readiness evaluation, Marine spokesperson Paul Gainey confirmed.

US Marines to return to Afghanistan's Helmand province

"Officials are investigating the circumstances surrounding the incident at this time," his statement said.

No other details were given about the fire or possible causes. The injured Marines were evacuated to hospitals in the area, with eight taken to the Burn Center at University of California San Diego Health.

Three of those were in critical condition and five in serious condition. Two more were in critical condition at the University of California Irvine Medical Center, the Marines said.

US calls off rescue for three marines missing off Australia

Amphibious Assault Vehicles have been used by the Marines since the 1970s and are designed for landings from the sea. Wednesday's incident followed two other fatalities at Camp Pendleton, the Marines' biggest base on the west coast of the United States.

On August 30, a 22-year-old Marine was found dead during a training exercise. The cause of death has not yet been established.

In 2015, a 19-year-old Marine was found shot dead in the head on a firing range at the base. In mid-June, seven sailors were killed when the destroyer USS Fitzgerald collided with a container ship off Japan.

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ