New SHOCKING Update From NTSB on Greg Biffle Crash…

The NTSB has released a preliminary report regarding the tragic crash that claimed the lives of Greg Biffle and his family.

The accident involved a Cessna Citation 550 that went down in Statesville, North Carolina, on December 18, 2025.

This report, made public on January 30, 2026, provides critical insights into the circumstances surrounding the crash.

What it quietly reveals is the ruling out of several dramatic explanations that people often jump to in the wake of such incidents.

There is no evidence of catastrophic mechanical failure, no thrust reverser deployment, and no doors opening mid-flight.

Instead, the report indicates something more subtle and uncomfortable: a capable jet, a highly experienced pilot, and a sequence of events where safety margins slowly eroded.

This situation is not about one single failure; it’s about how systems, workload, and timing stacked up against the crew faster than they could manage.

This preliminary report does not definitively explain why the accident occurred.

Rather, it lays out the factual sequence as clearly as the available data allows.

However, the data is limited.

The aircraft was not equipped with a flight data recorder, which is not required for planes of its age.

The investigators do have cockpit voice recordings, albeit recorded on an older analog system with significant quality issues.

Additionally, they have access to a limited set of parameters from the Garmin GTN 750 navigation unit, which provides snapsH๏τs of airspeed, alтιтude, and heading, but not the comprehensive system picture available on modern jets.

Despite these limitations, this report is extremely useful because it narrows down the problem space.

It clearly indicates what did not happen.

Both engines remained attached to the aircraft, and both thrust reversers were found stowed.

The throttle quadrant positions were consistent with forward thrust, and the baggage door that was initially speculated to have opened during flight actually separated during impact.

This information eliminates several theories right away.

Moreover, the report provides a detailed timeline of crew actions, system behavior, and environmental conditions.

When you piece these elements together, a pattern emerges that suggests a gradual accumulation of workload and complexity rather than a single dramatic event.

This is where the true value of the report lies; it constrains the narrative.

While it does not finish the story, it tells us where not to look, setting the stage for understanding why the airplane’s cockpit configuration and certification details are so important in this case.

The aircraft involved was a Cessna Citation 550 manufactured in 1981.

This older generation light jet is capable, but it reflects a different era of design.

These airplanes are often relatively affordable to acquire compared to newer jets, but they are expensive to operate correctly and demand disciplined systems management, especially when situations deviate from the norm.

The flight was conducted under Part 91 regulations as a personal flight, which means the regulatory structure differs significantly from Part 135 or airline operations.

The procedures, oversight, and margins are largely defined by the crew in the cockpit.

The cockpit setup in this case is critical.

The left seat was occupied by an ATP-rated pilot, a retired airline captain with extensive jet experience and multiple type ratings.

This was not a low-experience pilot at the controls.

However, his CE 500 type rating included a limitation that is easy to overlook but very important: a second-in-command (SIC) was required.

There is no indication in the report that this aircraft was being operated under a single pilot exemption, meaning it was certified and operated as a two-pilot airplane.

In the right seat was the pilot’s adult son, who held a private pilot certificate, was instrument-rated, and had approximately 175 total flight hours.

However, he was not qualified to act as SIC under the regulations.

That does not mean he couldn’t ᴀssist with radios or checklists—he did—but legally and operationally, he was not an SIC.

A third pilot was also present in the cabin, seated near the cockpit.

This pᴀssenger held multiple ratings, including multi-engine and instrument, and had around 3,500 hours of experience, but he was not seated at the controls and did not have access to the primary flight instruments.

What you end up with is a non-standard crew configuration: a highly experienced PIC, a low-time right seat pilot ᴀssisting with tasks, and an experienced pilot observing from the cabin.

In normal conditions, this may not matter much, but once automation drops out, instruments begin behaving abnormally, and workload spikes, this configuration becomes highly relevant.

When things start to get busy in a jet, knowing who is flying, who is monitoring, and who is troubleshooting is essential.

It defines how quickly margins disappear.

The airplane was positioned on the south parking ramp at Statesville for pᴀssenger loading and pre-flight.

Ground personnel reported that the aircraft was fully fueled, which is normal.

What matters is how the airplane was powered and what that means operationally.

Engine start was accomplished using onboard battery power only.

This airplane does not have an APU, and there was no external power cart connected.

While this is a normal configuration for this aircraft, it does mean that the electrical system is already working harder than it would be with external support.

The first start attempt on the left engine was unsuccessful.

Both engines were eventually started by 9:53.

That detail is significant—not because a failed start is rare, but because it indicates that the electrical system had already been exercised before the airplane ever moved.

During taxi, the crew discussed an inoperative thrust reverser indicator light on one engine.

Importantly, they verified that the thrust reverser itself was functioning normally.

This was an indication issue, not a mechanical failure, which is critical because it allows us to dismiss another theory.

The airplane was not dispatched with a known thrust reverser malfunction, and nothing about the wreckage suggests a reverser problem later on.

Meanwhile, the weather conditions were quietly shifting.

Early AOS reports showed good visibility and relatively high ceilings.

However, by the time the airplane was taxiing and preparing for departure, ceilings were lowering and moisture was increasing.

It was still legal VFR, but the trend was not favorable.

None of this is dramatic or unsafe by itself, but it does define the environment the crew was about to launch into: departing VFR into weather that was steadily compressing vertical space.

This is the window, and it is narrowing.

The airplane departed runway 10 at approximately 1:06 PM local time.

The plan was straightforward: depart VFR and pick up an IFR clearance airborne.

That’s a common technique at non-towered airports and, by itself, it’s not a red flag.

The division of labor was also logical: the pilot in the left seat was flying the airplane, while the right seat occupant handled radios and checklists.

That’s where the right seat can be helpful, even if the pilot isn’t acting as SIC.

During the takeoff roll, the rear pᴀssenger commented that the left engine appeared to be producing more power than the right, suggesting it might be a faulty gauge.

There’s no indication that the airplane was not accelerating normally, and the takeoff continued.

At that moment, this is still an observation, not a failure.

After liftoff, the airplane entered an immediate left climbing turn.

At 1:07:19, the pilot stated his intention to remain VFR until they received their IFR clearance.

That statement is significant because it frames every decision that follows: the goal is still to stay clear of clouds while sorting things out.

Between about 1:08 and 1:10, the right seat attempted three times to contact ATC to activate the IFR clearance.

Each attempt was unsuccessful due to controller workload.

This is where the plan starts to fray—not because it was bad, but because it wasn’t working.

While those calls are being made, the airplane is maneuvering to remain clear of clouds.

That’s one task.

At the same time, engine indications have already been discussed.

That’s another task.

And the airplane is being hand-flown in a climbing turning profile.

That’s a third task.

This is the point where workload starts to outpace capacity.

Not abruptly, but gradually, the airplane descends as low as about 1,300 feet MSL while maneuvering, which is consistent with trying to stay visual in тιԍнтening conditions.

At this stage, nothing has failed catastrophically, but the crew is now spending more effort just staying legal and upright and less effort staying ahead of the airplane.

This is where options begin to narrow—not because anyone made a single wrong choice, but because the margin for absorbing new problems is shrinking.

Around 1:09 to 1:10, the discussion turns toward climbing higher.

That’s a logical thought, but it immediately runs into the VFR constraint.

Almost simultaneously, the autopilot disengages.

Whether that disengagement was intentional or automatic doesn’t change the outcome.

What matters is what comes next.

The pilot reports that his left side altimeter is not working properly and suggests that additional left-side flight instruments may also not be functioning correctly.

That’s the pivot point in this accident.

In the Citation 550, the autopilot relies on left-side instrument data.

If that system fails or becomes unreliable, the autopilot will disengage.

There is a provision to bootstrap the right-side instruments, but that does not restore automation.

Once that happens, the crew must hand-fly the jet.

At that moment, this is no longer about troubleshooting and indications; it’s a sudden transition to raw data flying in instrument conditions while still trying to sort out navigation, clearance, and weather.

Control is briefly transferred to the right seat at about 4,500 feet MSL.

There’s no evidence that the right-side instruments were malfunctioning.

From a systems standpoint, that makes sense, but from a human factors standpoint, it adds complexity.

The right seat pilot is low-time and not a qualified SIC, and the PIC is now troubleshooting while monitoring rather than directly flying.

Shortly after that, the CVR audio quality degrades severely.

During that degraded period, the rear pᴀssenger asks about alternator power.

This airplane does not have alternators.

That comment is subtle, but it’s important.

It suggests uncertainty about what electrical source or system is actually at fault.

A few seconds later, the CVR audio suddenly returns to normal, and the pilot states that “was the problem.”

Without specifying what was corrected, whatever action was taken—whether it was a reset, a bus selection change, or something else—appears to have stabilized at least part of the system.

However, it did not restore time or margin.

The airplane turns back towards Statesville and descends.

Around 1:13 PM, the crew reports they can see the ground.

That tells us they had been in IMC without an IFR clearance and have now transitioned back to visual conditions.

That’s a relief, but it’s a late one.

Approach setup begins.

Flaps are requested, then the landing gear.

The gear indicator lights do not illuminate, adding yet another uncertainty at a moment when workload is already high.

A transmission goes out on CTA: “We’re having some issues here.”

From this point on, the data shows a continuously deteriorating approach profile.

Airspeed and alтιтude both decay.

The airplane aligns with runway 28, opposite the departure runway.

There is no indication of a major engine failure, no thrust reverser deployment, and no doors opening.

Those doors are closed now.

What remains is a picture of a jet that has lost automation, experienced instrument anomalies, accumulated task after task, and arrived at the runway environment with very little margin left to stabilize the approach.

The wreckage confirms what the data suggests: both engines were intact, thrust reversers were stowed, and flight controls were accounted for.

The accident was not driven by a single mechanical break; it was driven by a sequence where systems behavior, workload, and timing converged in a way that left no room for recovery.

The final report will need to address some hard questions about the exact nature of the instrument failure, the behavior of the electrical system, and how the crew’s options narrowed step by step.

But even at this stage, the shape of the accident is already clear: it didn’t explode into being; it quietly ran out of space.