Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Navy to hold hearing for sailor accused of igniting warship

The Navy will hold a hearing Monday to review whether there is enough evidence to order a court martial for a San Diego-based sailor charged with setting the fire that destroyed the USS Bonhomme Richard in the summer of 2020

Via AP news wire
Monday 13 December 2021 05:09 GMT
Navy Ship Fire
Navy Ship Fire (Copyright 2020 The Associated Press. All rights reserved.)

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

The Navy will hold a hearing Monday to determine whether there is enough evidence to order a court martial for a San Diego-based sailor charged with setting the fire that destroyed the USS Bonhomme Richard in the summer of 2020.

Ryan Sawyer Mays, a junior sailor, was charged with aggravated arson and the willful hazarding of a vessel in a case that marked the maritime branch’s worst warship blaze outside of combat in recent memory.

Mays, who was a crew member, has maintained his innocence. He told investigators he helped fight the blaze. The amphibious assault ship burned for nearly five days, sending acrid smoke over San Diego

About 160 sailors and officers were on board when the fire started July 12, 2020, in the lower storage area of the 840-foot (256-meter) vessel, which had been docked at Naval Base San Diego while undergoing a two-year $250 million upgrade.

More than 60 sailors and civilians were treated for minor injuries, heat exhaustion and smoke inhalation. Left with extensive structural, electrical and mechanical damage, the billion-dollar ship was later scrapped.

Mays was assigned to the ship after dropping out of training to become a Navy SEAL and he was described by some fellow sailors as a person who had disdain for the Navy, according to investigators.

Mays’ lawyer, Gary Barthel, did not respond to a request for comment before the hearing.

Officials assessing the ship’s damage found three of four fire stations on the ship had evidence of tampering: Fire hoses were disconnected and one was cut, according to court documents.

They also found uncapped bottles containing small amounts of highly flammable liquid near the ignition site, including one that tested positive for a heavy petroleum distillate such as diesel, kerosene or jet fuel, according to the court documents.

Mays told investigators he was in the hangar bay when he became aware of the fire, according to court documents. He described how he assisted firefighters, alerting at least one crew member of the threat, and eventually helped fight the blaze, according to court documents.

Winds coming off the San Diego Bay whipped up the flames that shot up the elevator shafts and exhaust stacks. Two explosions — one heard as far as 13 miles (21 kilometers) away — caused the fire to grow even bigger.

Dozens of Navy officials, including several admirals, are facing disciplinary action for systematic failures that investigators said prevented the blaze from being put out sooner, according to investigators.

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in