An Oklahoma football legend boarded what should have been a routine two-hour flight with a pilot friend who had climbed from beginner to business-jet captain almost frighteningly fast, but somewhere over Indiana the trip quietly turned into an unofficial flying lesson, the wrong hands ended up on the throttles, both engines went silent, and by the time the men in back realized this was no ordinary approach into South Bend, the people up front were already trapped inside a chain of mistakes too deadly to undo…

The air traffic controller could see the runway.

He could see the jet too.

That was what made the whole thing so maddening.

South Bend was right there—runway ahead, lights laid out in straight practical certainty, the airport sitting exactly where airports are supposed to sit when pilots are in trouble and trying to make the hardest promise in aviation: just let us get there. The controller had already done what controllers do in moments like that. He had stripped away procedure and pride and all the normal choreography of arrival and given the airplane the most generous sentence in the English language.

If you can hear me, you are cleared for the visual approach. Runway niner or any runway. All runways are available.

In other words: take whatever strip of pavement you can get this machine onto and nobody in this tower is going to bother you with details.

That is the sort of mercy pilots pray for when engines quit.

The Hawker Beechcraft 390 was almost there.

Then the controller saw something wrong.

The main landing gear wasn’t down.

Even from the tower, even in the stress of the moment, he could see the airplane coming in wrong—too clean underneath, too naked where the wheels should have been. He keyed the microphone and told them to go around.

That instruction would later sit inside the investigation like one more tiny knife.

Not because the controller did anything wrong. He didn’t. He saw what he saw and did what any sane person would do with an aircraft on short final looking not yet configured to land. But because by then the men in that cockpit were already beyond the point where a go-around was just another maneuver. By then the whole flight was held together with bad decisions, partial recoveries, systems nobody fully understood in the moment, and the kind of confidence that arrives in pilots right before reality reminds them it does not care about their self-image.

The controller watched the jet take back off.

Then watched it circle.

Then watched it bounce three, maybe four times on the next attempt and climb away again, not cleanly, not safely, but stubbornly, like a man trying to solve his own mistake with one more try and one more and one more until the laws of physics finally lose patience.

Then the airplane vanished.

A few moments later it crashed into a house.

Two men in the front died on impact.

Two passengers in the back somehow walked away.

And everyone who later learned how the whole thing began had the same reaction, though they arrived at it from different angles and with varying levels of politeness.

What in God’s name were they doing?

Because this was not one catastrophic failure.

It was a chain of choices, each one perfectly capable of being defended by a certain kind of confident man right up until it killed an Oklahoma football legend and another pilot in a quiet Indiana neighborhood.

Steve Davis was sixty years old and still carried the sort of name that means something in Oklahoma even after the world has changed outfits around it. For people of a certain age he was not just a former quarterback; he was a chapter. The Oklahoma Sooners. Back-to-back national championships in 1974 and 1975. The kind of college football hero who gets baked into local memory until his name no longer belongs entirely to him. He belonged a little to stadium noise, to old men who could still tell you where they were when he beat Nebraska, to people who spoke of him not in sentences but in shorthand: Steve Davis, like that explained everything necessary about poise and toughness and winning.

What fewer people knew outside aviation circles was that Steve Davis also flew airplanes.

He had over eighteen hundred hours total, more than fifteen hundred of them in multi-engine airplanes. Which sounds, and is, substantial. He was not a dabbler. Not a man who rented a Cessna twice a year and called himself “basically a pilot” over barbecue. He had real time. Real experience. Enough to make friends think of him as a pilot without irony and enough to feel at home in an airplane cockpit.

But there was a catch.

His logbook showed the last flight entered back in September 2008, nearly five years before the crash. Whether he had truly quit flying after that or simply stopped logging, no one could say with confidence. The NTSB did not dig deeply into his recent proficiency because, officially and legally, Steve Davis was not the pilot in command that day. He was a passenger in the right seat. A knowledgeable passenger, maybe even a participating one, but still not the legal owner of the final decisions.

And crucially, based on what investigators could confirm, he had no experience in business jets.

That detail matters more than it sounds like it should.

Because the airplane he was sitting in on March 17, 2013 was not a Cherokee or a Baron or some familiar piston twin where old multi-engine instincts might at least get invited to the party. It was a Hawker Beechcraft 390, more commonly known as the Beechcraft Premier I, a sleek little business jet with twin engines, a pressurized cabin, and enough performance to flatter anybody sitting in it. It was technically certificated for single-pilot operation, which is one of those legal facts that can be either a marvel of engineering or a setup for overconfidence depending on who is occupying the left seat.

On that flight, the left seat belonged to Wes.

Wes was fifty-eight years old.

And if Steve Davis’s background made him look more qualified to outsiders than he really was for this airplane, Wes’s background made him look legally qualified while raising a whole different, more unnerving question.

Why had anyone let him get this far this fast?

Wes had begun learning to fly in January 2011.

That is not a typo.

Two years before the crash, he was a student pilot. By April of that same year he had his private certificate with about seventy-one hours total time. Ten months later he added an instrument rating with a little over three hundred hours. A few weeks after that, he got his multi-engine rating. By May 2012—roughly sixteen months after first beginning to fly—he obtained a type rating in the Hawker 390 with around four hundred fifty hours total.

Legally, all of that was permissible.

Practically, it should have made people sweat.

There is an old joke in aviation that the regulations will let you do all kinds of things common sense would recommend against. That’s because regulations are floor, not ceiling. They answer the question “What is minimally allowed?” not the more useful question “What kind of pilot do you need to be before this specific machine and mission stop being a very expensive way to audition for a report?”

Going from zero to private pilot in a year is ordinary enough. Going from private pilot to instrument, multi-engine, and then typed in your own business jet in a matter of months is something else entirely. It can be done. It has been done. But legality does not create wisdom by osmosis. There is a difference between accumulating ratings and consolidating judgment, and the latter is the part the FAA cannot simply stamp into you after a checkride.

By the time of the crash, Wes had roughly one hundred seventy hours in the Premier.

One hundred seventy.

For a single-pilot jet, that is not nothing. It is also not nearly enough to justify the kind of confidence that later came out of the cockpit voice recorder. It is enough to know where the switches are. Enough to feel less afraid. Enough, unfortunately, to be at peak danger if you are a certain kind of personality—successful, self-assured, used to upgrades, used to doing the next thing as soon as the previous certificate ink dries, the kind of person who has never had enough time in one phase of flying to discover what he doesn’t know before he starts collecting more complexity.

If you wanted to build a pilot vulnerable to confidence bias in a lab, you could do worse than a man who had moved up that ladder so quickly and without enough seasons of ordinary flying in between.

The airplane itself was not the problem.

The NTSB found nothing mechanically wrong with it before the accident sequence. That is one of the maddening things about this case. The jet was capable. The systems worked. The route was routine. The weather was not performing apocalyptic theatrics. Four men climbed aboard a machine fully capable of making a quiet two-hour trip from Tulsa to South Bend, and somehow managed to turn it into a dead-stick emergency, a bounced attempted landing, and a fatal crash into a house.

That kind of accident doesn’t happen because fate had a dark sense of humor.

It happens because somewhere in the chain, a person starts treating the cockpit like a classroom or a toy or an extension of his own confidence instead of what it is: a machine that will kill you without malice if you mismanage it badly enough.

The other two men on board that day sat in the back.

One was named Chris.

The other was his father-in-law.

The reports never turned them into central characters in the public story, perhaps because survival in aviation accidents has an odd way of becoming secondary when the front seats contain a famous name and an especially stupid sequence of events. But if you care about the human shape of the thing, they matter a great deal. They were the ordinary men in the back who had trusted the front without seeing what was really happening there. According to Chris, he had flown with Wes three or four times before. And according to Chris, Wes had never once provided a safety briefing—not on those flights and not on the accident flight.

That is not, by itself, what killed anyone.

But it tells you something.

A safety briefing is not just ritual. It is attitude in verbal form. It says the pilot understands that passengers are not luggage, that flying carries risk, that professionalism is not something you save for checkrides or uniforms. The absence of a briefing does not prove recklessness, but it does suggest a man operating from familiarity instead of discipline. It suggests somebody who thinks, on some level, that because he has gotten away with informal habits before, informality is now a system.

And systems built out of habit are often the first things to fail when an actual emergency shows up.

The flight departed Tulsa and climbed normally. Air traffic control cleared them to 41,000 feet, which in a jet sounds glamorous to non-pilots and annoyingly procedural to everyone else. They settled into cruise. The passengers in the back presumably relaxed into whatever people do in business jets when they trust the front—talking, looking at phones, maybe thinking about the purpose of the trip, maybe not thinking about aviation at all because the whole point of paying for someone else to know what they’re doing is that you get to be blissfully ignorant of how many switches stand between you and a field in Indiana.

The NTSB did not release a full transcript of the cockpit voice recorder, only the relevant portions. That matters because partial transcripts are like hearing one side of a marriage argument through a wall: enough to know the shape of the thing, not enough to feel fully charitable toward anyone.

The recording available to investigators begins about two hours into the flight. That alone tells you something. They were close to destination. This was not some departure blunder or weather diversion halfway through the trip. They had done the easy parts. The airplane was in the air. The route was nearly complete. The crash happened not because they failed at basic flight, but because they failed at what should have been a routine descent and arrival.

At cruise, Wes was already talking about fuel, return planning, and the systems of the aircraft. Not just to himself, but to Steve, as if the right seat were not occupied by a passenger but by a student or at least a curious companion who had enough pilot in him to appreciate being shown the machine. At one point Steve said, “A lot of stuff to learn.”

That line hung in the report like a warning sign nobody in the cockpit was reading.

Yes. A lot of stuff to learn.

Which is exactly why maybe you should not turn the final descent of a live passenger-carrying jet flight into a little private seminar.

There is a sort of man—and aviation has never exactly suffered from a shortage of them—who loves teaching most when the teaching also flatters him. He likes the sound of his own competence passing through the room. He likes being the authority, the explainer, the one who can make a difficult system seem manageable because he already understands it. Wes, from the transcript, sounded very much like that kind of man.

The problem was that his own understanding was too thin for the arrogance of the setup.

When air traffic control cleared them to begin descent, Wes started quizzing Steve.

Minimum rate of descent.
Autopilot modes.
Vertical speed.

He explained that he was using a vertical-speed mode to maintain one thousand feet per minute. That is fine as far as it goes. But anyone who has spent enough time in automation knows the trap: the airplane does not care about your airspeed if you tell it to chase a vertical speed. It will obediently keep going downhill while you, the supposedly smarter organism in the loop, are expected to manage the power so the thing doesn’t quietly accelerate into a warning horn.

Wes said they needed to watch their speed because they’d get too fast if they didn’t manage the throttles.

In other words, he had already set up a task for Steve and a task for himself without seeming entirely committed to either one.

This would become the rhythm of the next ten minutes.

Wes talking.
Wes instructing.
Wes letting Steve touch things.
Wes not fully flying.
Wes not fully monitoring.
Wes doing the pilot equivalent of showing off your kitchen knives while something is already on the stove burning.

Two minutes into the descent, Wes said they needed to get the power back or it would start beeping at them.

Then the overspeed warning began.

Already.

That should have been the cue for the whole lesson to die immediately. My airplane. My throttles. Eyes inside. Slow the jet. Brief the approach later, or not at all, or never, if humility had suddenly shown up with enough force.

Instead the interaction got murkier.

Steve said something like, “Just pull it way back.”

Wes responded with a series of encouraging little control-room noises. There you go. There you go.

This is where the report becomes so frustrating that you want to throw the page across the room.

Because although Wes never formally said “You have the controls,” the sequence makes it increasingly clear that Steve was likely manipulating the power and perhaps flying portions of the descent. Steve, whose last logged flight was five years earlier. Steve, who had no jet time. Steve, who was a pilot in the broad sense but not in the only sense that matters at 41,000 feet descending toward one of the busiest phases of flight in a light business jet.

And the two men in the back likely had no idea that any of this was happening.

That, to me, is one of the ugliest parts of the story. Not just that an unqualified man may have been handling the controls. That the passengers were denied even the right to know their lives had quietly become a training exercise.

Wes asked Steve at one point how many hours he had in the jet.

Steve dodged the question, saying instead that he was uncomfortable with the speed management and moving the throttles around.

That should have shut the lesson down.

That should have been the giant blinking billboard over the whole operation.

The guy touching the controls is telling you he is uncomfortable with the jet.

And you keep going.

This is not merely arrogance. It is what confidence bias looks like when it starts writing checks your skill cannot cash. It is the voice in your head saying, I got this, without the humility to ask whether “this” includes supervising a rusty piston pilot in the right seat while descending a complex business jet into an airport.

As they continued down, Wes called for the 10,000-foot checklist. Again, routine. Necessary. The sort of thing pilots do all the time.

The trouble was that routine tasks are only routine when somebody is still flying the airplane.

Wes was running the checklist while also talking while also instructing while also not fully monitoring speed. It was a mess. A very calm, professional-sounding mess, which is often how sophisticated people get themselves killed. The voice in the cockpit isn’t panicked, so nobody inside it fully appreciates how badly the fundamentals have already been abandoned.

At one point Wes told Steve to “pull the power out.”

Steve asked, in effect, “Just pull it on down?”

Wes said yes. Let’s get back to 200.

If you know the Hawker 390, your stomach drops there.

If you don’t, here’s the problem in plain language.

The throttles in that jet have an idle stop. Pull them back to idle, and that’s fine. But if you lift the throttles and move them past that stop, you go to cutoff. That means you shut down the engines. In normal operation, there is a clear tactile distinction. In a properly managed cockpit with a qualified pilot at the controls, this is not a casual hazard. But cockpit design is only half the story. The other half is what words you use while an underqualified man is handling the levers.

“Pull the power out.”

That is a terrible phrase in that moment.

Because words mean things. And in aviation, vague words can kill just as dead as bad weather.

The cockpit voice recorder captured two clicks.

Then a power interruption.

Then Wes saying, “Uh-oh.”

That may be the most horrifyingly understated phrase in the report.

Uh-oh.

Not because it is dramatic. Because it isn’t. Because it is the exact tiny stupid sound a human being makes when the full consequences of his own casualness arrive one second too late.

Steve said, “What?”

And Wes told him he had gone back behind the stops and they lost power.

Both engines.

Gone.

At 6,700 feet.
About 18 miles from the airport.
With two passengers in the back.
And a business jet suddenly becoming a glider because the man in the left seat had turned the arrival into a tutorial for the man in the right.

If you’ve never flown, let me translate the emotional shape of that for you.

Imagine you are a passenger in the back of a car and the driver and front-seat friend have been chatting casually about how this particular model handles corners. You don’t really care. You trust them. Then, without warning, the engine dies on the highway because the friend reached for the wrong control while the driver was explaining something instead of driving. That’s the scale of betrayal the people in the back suffered. They were not merely victims of mechanical fate. They were victims of cockpit unseriousness.

Now, to be fair, almost nobody trains specifically for dual engine shutdown caused by accidental cutoff in cruise. Pilots train engine failures. Fire procedures. Single-engine work. Simulated losses. But this particular combination—both engines off because you let the wrong hands do the wrong thing with the wrong wording at the wrong time—is not exactly a standard script.

Still, the emergency was survivable.

That’s the infuriating part.

They had altitude.
They had distance.
They had a runway ahead, not directly under them but reachable.
They had air traffic control.
They had at least, eventually, one engine that could be restarted.
They had enough options that good emergency management might still have delivered all four men to the ground shaken and embarrassed and very much alive.

Wes declared an emergency.

To his credit, quickly.

He told ATC they had dead engines, dead stick, no power.

He said they had no hydraulics and the aircraft was barely controllable.

That statement was only partly true, or perhaps temporarily true, because the situation inside the cockpit was now turning into the second half of the tragedy: not the initial mistake, but the inadequate response.

When both engines were shut down, they lost more than thrust. They lost electrical power in ways that turned an already unusual emergency into a systems-management trap. There was evidence from the recorder that at some point one engine did begin to spool, suggesting at least partial restart efforts. But the restart did not restore everything because the electrical system was not configured properly afterward.

Here’s where Wes’s inexperience comes back like a hammer.

At some point after the power interruption, he moved the battery toggle switch to standby, which is a step associated with electrical power loss procedures. In isolation, that may have made sense in the moment. The problem was that once the left engine was eventually restarted, the generator needed to be reset and the battery switch needed to be where it belonged if they were going to get all their electrical systems back. Displays. Radios. Gear indication. Normality, or at least a close enough impersonation of it that a single-engine approach could be flown like the manageable event it should have been.

But the battery switch stayed in standby.

That single oversight tangled everything.

No full electrical recovery.
No normal system function.
No easy landing gear operation.

The NTSB believed that at some point Wes tried to use the alternate gear extension procedure but did not fully extend the handle, so the gear never locked down.

And through all of this, think about the workload.

Noisy, then suddenly quiet.
Emergency declared.
Airport ahead.
One engine maybe alive, maybe not fully integrated.
Electrical weirdness.
Gear issues.
No full displays.
No complete radio communication because power restoration is incomplete.
A pilot with limited jet experience.
A second man in the right seat who helped cause the whole problem and likely wasn’t useful enough afterward.
Two passengers in the back who had no idea what checklist the front was trying and failing to complete.

This is how overconfidence gets people killed. Not simply by creating the first mistake. By ensuring that when the first mistake happens, the pilot does not have enough true competence left over to dig out.

The controller kept trying to save them.

If you can hear me, turn right 20 degrees.
The airport is at your 12 o’clock.
Five miles.
Cleared visual.
Any runway.

Those transmissions read like heartbreak on the page because they show exactly how close the airplane still was to survival.

Then came the first approach with the gear up.

The controller saw it and told them to go around.

Some people later argued that maybe they never heard him, and that may be true. The loss of electrical functionality muddied everything about what they were receiving and transmitting. Or maybe Wes saw it himself and chose the go-around. Either way, the result was the same. The airplane climbed away from a runway it might or might not have survived landing on with the gear not fully extended.

Here’s where the whole story becomes especially cruel.

At some point after the dual shutdown, Wes did apparently get the left engine running again. That means the airplane was no longer simply falling. A single-engine business jet, while not ideal, is absolutely not an automatic death sentence. With one engine and proper configuration, he should have had enough performance and control to slow the whole thing down, think, communicate, work the checklist, and set up for the best ugly landing of his life.

But because the electrical configuration remained wrong, the airplane stayed half-blind and half-broken in ways that created new problems where solved ones should have been.

They touched down on the next attempt.

That matters because it means they had made it all the way back to pavement.

And then they bounced.

Three or four times.

Then took back off.

You can analyze that in a dozen technical ways—speed, flare, control, asymmetry, pilot-induced oscillation, configuration confusion, compromised approach—but emotionally it lands the same way every time: they were almost safe and still couldn’t stop making the day worse.

After the bounce sequence, the aircraft climbed away again and disappeared out of sight, then crashed into a home.

Wes and Steve died on impact.

The two passengers in the back survived with serious injuries and somehow walked away from the wreckage.

A person on the ground was injured.
No one in the house died.
Which is another one of those hideous little miracles aviation accidents sometimes leave behind like insults.

The NTSB’s conclusion was blunt.

The probable cause was Wes’s inadequate response to the dual engine shutdown, which had itself been caused by his decision to let Steve, who was not qualified to operate the jet, manipulate the controls.

That is the official wording.

The unofficial wording is uglier and truer.

He wanted to teach.
He wanted to impress.
He wanted to play check airman in a machine he had barely known long enough to stop being dangerous in it.
He got distracted.
He was not as good as he thought he was.
And by the time reality introduced itself properly, four lives and a house were already on the table.

I don’t think arrogance is exactly the right word, though it is the easy one.

Arrogance suggests a man who consciously thinks he is untouchable. Wes, from the record, sounds more like a man suffering from confidence bias—the internal voice that says I’ve got this before the outer world has handed you enough evidence either way. It’s a particularly vicious trap for successful people, because life rewards confidence right up until it doesn’t. If you’ve spent years moving from one achievement to the next, your brain starts treating acceleration itself as proof of fitness.

Private certificate?
Got it.
Instrument rating?
Got it.
Multi-engine?
Got it.
Jet type rating?
Got it.
Own business jet?
Sure.
Teach your pilot friend how it works on descent into South Bend with passengers in the back?
Why not.

That last one is where confidence stops being a virtue and starts sounding like a eulogy drafting itself.

I keep thinking about Chris in the back seat.

About how he said Wes had never given a safety briefing on any of the flights.

About the moment the lights flickered and the airplane went strangely quiet.

About realizing, as a passenger, that something was deeply wrong without having any real knowledge of what had happened or what chance you still had.

It’s one thing to die in an accident no one could prevent. There is a bleak impartial dignity in that.

It’s another thing to nearly die because the pilot up front decided to use your transport as a sandbox for ego and informal instruction.

That is betrayal, not merely accident.

And Steve?

He is harder.

Because he was not innocent in the full operational sense, even if he was legally a passenger.

He had flight time.
He knew enough to know what he didn’t know.
He ducked the question about jet hours rather than answering it.
He admitted discomfort with the throttles.
And yet he still appears to have touched them, moved them, and participated in a sequence that got everybody nearly killed and two men actually killed.

That does not mean he deserved what happened.

It means the cockpit was a place where male competence blurred into performance and mutual flattery until the airplane itself had to separate them.

There is something especially American about this particular crash.

Not just the celebrity angle, though that helped the story travel. Not just the business jet, though that adds a whiff of money and status and private transportation confidence. What feels particularly American is the whole philosophy behind it: success everywhere else becoming mistaken for mastery here too. The idea that if you are accomplished, resourced, decisive, and have passed enough tests fast enough, you can shortcut the slow humiliating years where judgment is actually built.

Aviation does not care about your résumé.

It cares whether, at the exact second the speed is wrong or the throttles are mishandled or the battery switch is in the wrong place, you know what the airplane needs more than you need to feel competent.

That’s it.

And Wes did not.

After the crash, the story turned into the usual combinations of grief, local legend, and aviation outrage.

Oklahoma mourned Steve Davis not as a cautionary footnote but as Steve Davis—the quarterback, the champion, the familiar name now stapled to a business jet accident report nobody would have believed if it had been fictionalized too heavily.

Pilots read the NTSB findings and swore at the pages.

People who had flown with men like Wes—successful, recent, over-upgraded, just current enough to be dangerous—felt a particular chill.

And the surviving passengers had to carry the weirdest burden of all: living on in the knowledge that they had walked away from a crash caused not by weather or bad luck or hidden failure, but by a front-seat culture so casual and so overconfident it managed to shut down both engines within sight of a perfectly usable airport.

The phrase that keeps returning to me from the CVR is not “dead stick” or “uh-oh” or even the overspeed beeping.

It’s Steve’s line.

“A lot of stuff to learn.”

Yes.

Exactly.

That was the truth in the cockpit. A lot of stuff to learn.

Which is why the man in the left seat should have been flying the airplane instead of pretending to be instructor, examiner, host, and pilot all at once.

If this story makes people think twice about flying with a friend, good.

Not because friends are inherently dangerous.
Because friendship in a cockpit is not a substitute for professionalism.
Because familiarity can erode discipline faster than malice ever could.
Because a lot of very smart, very accomplished men become fatally stupid the second they stop distinguishing between what is legal and what is wise.

None of this needed to happen.

That is the ugliest sentence in accident investigation, but sometimes it is the truest one.

The engines didn’t fail on their own.
The weather didn’t ambush them.
The airport didn’t disappear.
The controller didn’t send them somewhere impossible.
The airplane didn’t ask to be a classroom.
The passengers in back didn’t volunteer to be human collateral for a lesson nobody should have been teaching.

Wes made the first fatal mistake when he let Steve play with the controls of a jet he wasn’t qualified to fly.

The second when he failed to monitor properly.

The third when he mismanaged the emergency after the shutdown.

And the rest were just consequences piling up fast enough that by the time the runway appeared, salvation was no longer a matter of wanting it.

It was a matter of having earned it through earlier judgment.

They hadn’t.

That’s the hardest truth in the whole case.

By the time the controller was offering any runway, by the time the gear warning should have mattered, by the time the left engine was spooling and the house at the edge of the airport still had no idea it was about to be part of the story—by then the chances they needed were already gone, spent on smaller bad decisions that had felt manageable when they were made.

That’s how pilots die most often, if we’re being honest.

Not in one dramatic mistake.

In a string of little permissions.

And this flight was full of them.