Author: dailycastsocal

SAN DIEGO, Calif. — A Navy jet that crashed into San Diego Bay dangerously close to homes, hotels, and restaurants had ascended to about 8,000 feet with no one on board after its pilots ejected following a landing attempt failure in February, as reported by Team 10. Documents acquired through a Freedom of Information Act request from the recently concluded investigation into the incident are revealing new insights into the turbulent moments prior to the crash of the $67 million EA-18G Growler. These documents highlight issues related to runway conditions, a midair fuel leak, and a warning from air traffic control that led to confusion inside the cockpit. Records indicate that the pilot sensed something was off with the brakes just moments before the incident. On the day of the crash, both the pilot and the electronic warfare officer were forced to use a backup jet due to a fuel leak. They took off from North Island and engaged with a tanker for midair refueling. Encountering a “minor leak from the basket,” they opted to return to base instead of risking over 500 miles offshore. Capt. Brandon Viets/Premier Sportsfishing via AP This image, provided by Premier Sportsfishing, illustrates the rescue of two pilots after their E/A-18G Growler crashed off the San Diego coast on February 12, 2025. As they prepared to descend, the crew was informed that there was water on the runway at North Island. The pilot landed but encountered tailwinds and higher-than-normal speeds. He recounted to investigators, “I knew I would have to use the brakes a bit more.” When applying the brakes, he observed they felt “mushy or at least a bit different than normal.” U.S. Navy The Growler caused an explosion in the water near Shelter Island after crashing into San Diego Bay. Fearing that the jet would fail to stop in time, the pilot initiated a go-around maneuver. A tower controller then warned, “Not enough runway.” “This was communicated in a very concerned tone, resulting in confusion and anxiety,” the pilot noted. ‘Eject! Eject! Eject!’ Retired Air Force accident investigator Rich Martindell expressed surprise at the air traffic controller’s warning, deeming it inappropriate. “The tower didn’t have the necessary information about the aircraft’s speed and overall situation,” he remarked in an interview. Having flown the F/A-18 Super Hornet, a similar aircraft without the Growler’s electronic warfare capabilities, Martindell added that the controller could not have accurately assessed the available runway. “This unnecessarily complicated the issue and introduced doubt among the crew regarding the situation.” According to the pilot’s statement to an investigator immediately following the brake issues, “It felt like the jet was not going to fly, and the water was getting closer, so I called for ejection with ‘EJECT, EJECT, EJECT’ before we pulled the handles.” Jack Fischetti Surveillance footage captured the jet falling within a dangerous proximity to homes, hotels, and restaurants. The crew parachuted safely into San Diego Bay and were rescued by a fishing vessel. The jet ascended to about 8,000 feet before plummeting for over a minute and crashing into San Diego Bay near Shelter Island, according to the Navy’s findings. “It appears to have stalled. It got nose-high, lost airspeed, and then the video shows it entering the water, nose-first, shortly after the ejection,” stated Martindell. Amol Brown/Team 10 Retired Air Force accident investigator Rich Martindell scrutinized documents from the Navy’s investigation, which Team 10 acquired after filing a Freedom of Information Act request. He was taken aback that an air traffic controller indicated to the pilot that he lacked sufficient runway to land. The chaotic descent of the Growler was captured on a resident’s doorbell camera and nearby surveillance systems, showing it nose-diving into the bay. “Had this aircraft continued for even one more second, it could have hit Shelter Island or a populated area in Point Loma — a very near tragedy,” warned retired U.S. Marine Corps Col. Steve Ganyard in an ABC News segment post-crash. Navy says human error, weather to blame Following Team 10’s acquisition of the documents, the Navy confirmed in October that the investigation into the incident was completed and ruled out mechanical failure. Instead, the investigation concluded that human error, compounded by various factors including adverse weather, led to the crash. “The aircraft was unable to safely stop on the runway due to wet conditions and landing with a tailwind. The investigation concluded that the pilot should have executed maximum braking techniques,” stated Navy Cmdr. Amelia Umayam, spokesperson for Naval Air Forces, U.S. Pacific Fleet. The Navy spent several weeks recovering debris from the water, managing to retrieve approximately 85% of the aircraft, including significant components. “The U.S. Navy maintains well-established and rigorous programs for crew resource management, compliance with training protocols, professionalism, and airmanship,” Umayam emphasized in an official statement. “In the ensuing days and weeks following the crash, leadership across the organization reiterated to all crews the necessity of strict adherence to these programs to ensure safe and effective flight operations.” Martindell remains convinced that the air traffic controller’s warning was a contributing factor in the incident and may have influenced the pilot’s decision-making just before ejection. “He likely would have made a different decision; that call certainly had an effect on his choice to opt for ejection.” Team 10 Investigative Reporter Austin Grabish specializes in military investigations, the Medical Board of California, and the U.S.-Mexico border. If you have a story for Austin to investigate, email austin.grabish@10news.com Source link