68 years old physician/pilot dies in fatal plane crash

Advertisement

"Not That Bad"

The technician had the pitch trim cable in his hands, and he didn't like what he saw. It was frayed — visibly, obviously frayed — along with two loose bolts securing the autopilot's pitch servo assembly to its mount. He told the pilot standing next to him at the Fayetteville avionics shop that the cable needed to be replaced before the airplane flew again.

The pilot, 68-year-old Robert Phillip Mathis of Corinth, Mississippi, looked at the same cable and came to a different conclusion. "Not that bad," he reportedly said. "I've seen worse cables." When the technician kept pressing the point, Mathis told the shop's secretary the man was "overreacting."

The Autopilot Problem That Started It

Mathis had flown his 1972 Beechcraft 58 Baron, N811PB, from Corinth to the Fayetteville shop that morning specifically because of an autopilot issue — something wasn't right, and he wanted it looked at. The technician's inspection found more than he'd bargained for: not just whatever fault Mathis had brought the plane in for, but a frayed elevator pitch control bridle cable and loose hardware on the pitch servo mount, sitting right in the chain of components that controls how the aircraft's nose moves up and down.

The technician recommended the cable be replaced. Mathis declined. He told the shop he'd fly the airplane without the repair being completed, closed out the work order, and departed Fayetteville Executive Airport at 1:55 p.m. on 29 October 2024, bound for home.

A Trim Issue, Then Nothing

Less than half an hour later, at 2:22 p.m., Mathis declared an emergency, reporting a trim issue. It was the last anyone heard from him. The Baron disappeared from radar shortly after. An ALNOT — an alert notice for a missing aircraft — went out, and search crews began working through the dense forest along the Van Buren and Stone County line in Arkansas. The wreckage was located the following day, in a heavily wooded area near Clinton. Mathis did not survive.

What a Frayed Cable Actually Does

A pitch trim system exists to relieve the constant physical pressure a pilot would otherwise have to hold on the control yoke to keep an aircraft flying level — it's a small, unglamorous system that quietly does an enormous amount of work on every flight. When a trim cable frays or the hardware securing it loosens, the system can behave unpredictably: binding, slipping, or in the most difficult case, allowing the trim to move on its own in a way the pilot has to physically fight to counteract. Combined with loose bolts on the very servo assembly that connects the autopilot to that same pitch control system, the airplane Mathis flew out of Fayetteville that afternoon had two separate, related points of vulnerability in exactly the system that keeps an aircraft's nose where a pilot wants it.

The NTSB's investigation, documented under case CEN25FA033, is still working through exactly how that vulnerability translated into the loss of control that followed — whether the trim cable failed outright, whether the loose servo hardware contributed, or some combination of both. What's already on the record, though, is the conversation that happened before the airplane ever left the ground: a trained technician identifying a real defect, recommending a real fix, and a pilot who chose to fly anyway.

The Choice Before the Flight

Every pilot eventually faces some version of this decision — a mechanic flags something, and the pilot has to weigh whether it's serious enough to ground the airplane. Most of the time, that judgment call is unremarkable, made correctly, and never becomes a story. This time, the person making the call had just been told, directly and specifically, that a component in his aircraft's flight control system needed replacing before it flew again. He decided otherwise.

The Weight of "I've Seen Worse"

There's a particular kind of authority that comes with decades of flying experience, and it can cut both ways.

What a Second Opinion Is For

The system that connects a pilot to a mechanic exists specifically to introduce a second, disinterested set of eyes into decisions the pilot is too close to make objectively — someone with no stake in getting the airplane back in the air quickly, whose only job is to assess airworthiness.

Accident Facts

Incident date
29 Oct 2024, ~14:22 local
Registration
N811PB
Aircraft
Beechcraft 58 Baron (1972)
Airports
Fayetteville Executive (FYV) → Corinth-Roscoe Turner (CRX); crashed near Clinton, AR
Fatalities
1 (pilot, sole occupant)
Investigation status
NTSB investigation (CEN25FA033) — preliminary findings document a frayed pitch trim cable and loose autopilot servo mount hardware identified before
Category
Crash, Fatal, Control problem
Reconstruction
7:58
Timeline
Before departure —
Mathis brought the 1972 Beechcraft 58 Baron, N811PB, to the Fayetteville shop for an autopilot problem, where a technician found a frayed pitch trim cable and loose autopilot servo hardware.
1.
Before departure —
The technician recommended replacing the cable, but Mathis declined the repair and departed Fayetteville Executive Airport at 1:55 p.m. for home.
2.
2:22 p.m. —
Less than half an hour later, Mathis declared an emergency and reported a trim issue; the Baron disappeared from radar shortly afterward.
3.
After the event —
Search crews located the wreckage the following day near Clinton, Arkansas, and Mathis did not survive.
4.
Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

Sources

The weekly incident