Cessna Damaged in Emergency Landing; Pilot Uninjured

Though the emergency landing was skillfully executed, the rocky river bar proved unforgiving. [Photo by Paul]

A week after reports surfaced of a downed aircraft in a remote area near Hyampom, the pilot has come forward to share the story behind the emergency landing that severely damaged his 1973 Cessna—but left him unharmed.

In an exclusive interview with Redheaded Blackbelt, Paul, a crop duster from the San Joaquin Valley who grew up in Hyampom, recounted how a sudden loss of engine power during his approach to the remote airstrip forced a split-second decision. That decision—made at low altitude—meant the difference between life and death.

“I could either go into all their trees on the edge of the river, thinking I could make it to the airport, which I knew I couldn’t,” Paul said. “Or crank it over and put it down on the gravel bar.”

Though scanner traffic initially placed the downed plane off Corral Bottoms Road near Forest Service Road 3M40, Paul said he landed just 500 yards from the Hyampom Airport. The change in approach direction was due to a Temporary Flight Restriction (TFR) in place for controlled burns in the area. As he lined up, the Cessna 182P lost all engine power. “I was only a couple [of] hundred feet off the ground when I realized there’s no power.”

Thanks to thousands of hours in the cockpit as an agricultural pilot, Paul made his decision quickly—within 15 seconds—and brought the plane down on a gravel bar alongside the river. Unfortunately, the surface was rougher than expected. “The gravel is pretty big, …where I landed, …not quite the size of my head, [but] some of it,” he recalled.

The noselanding gear gave out, causing the nose of the aircraft to slam down onto the rocks. While the plane’s fuselage suffered extensive damage, Paul walked away without a scratch.

The plane had dropped off radar around 10:55 a.m. on June 13 as Paul descended toward the Hyampom Airport. However, emergency services weren’t alerted until after noon, when a 911 caller spotted the nose-down aircraft. By the time responders arrived, the pilot was no longer on site.

Paul told Redheaded Blackbelt that his brother had been waiting at the airstrip and saw the final moments of the flight. He rushed to the river’s edge, finding Paul standing outside the aircraft, shaken but unhurt. After checking for fuel leaks and securing the plane, the brothers loaded up Paul’s luggage and headed to their family property nearby.

There, Paul began the necessary notifications. The insurance company arranged for a recovery crew to disassemble the plane for transport to a repair hangar the following day. On June 18, the day of our interview, Paul was already knee-deep in the paperwork: “It takes forever, so I’m sitting in front of the computer on that forum right now starting to work on it,” he said, referring to the non-injury incident report that must be filed within 10 days.

Despite the close call, Paul remained calm and pragmatic. “I can’t beat myself up too much,” he said. “There’s nothing I can do about it.”

Perhaps it’s his decades of experience flying low and fast that not only helped him land safely—but also helped him get right back in the cockpit. Our phone call had to be rescheduled because Paul was already back at work in the skies above Tracy.

The cause of the engine failure is still unknown. The disassembly crew found about 70 gallons of fuel remaining in the plane’s tanks before transporting it.

While the FAA has not yet released its final report, Paul’s account offers a rare, grounded perspective on what it’s like to face a mechanical failure mid-flight—and walk away.

Earlier: Pilot Missing After Apparent Emergency Landing Near Hyampom, Plane Found Intact