New Audio From Inside the Cockpit Exposes the Chaos Before Greg Biffle’s Plane Went Down

An audio clip has begun circulating that relates to the ill-fated Cessna Citation 550 piloted by Greg Biffle.

This recording, while not an emergency call, provides a rare glimpse into the final moments in the cockpit, allowing us to hear the crew’s attempts to communicate their situation and the challenges they faced.

On December 18, 2025, around 10:15 AM, a Cessna Citation 550 departed from runway 10 at Statesville, North Carolina.

Onboard were seven individuals, including Biffle, his wife, two children, Dennis Dutton, his son Jack, and another pilot.

The weather conditions were marginal VFR, with low clouds and ragged layers limiting visibility.

Since Statesville is an uncontrolled airport, all communication was conducted over the Unicom frequency, requiring pilots to announce their positions and intentions.

Just minutes after takeoff, the aircraft exhibited erratic flight patterns, including fluctuating speeds and altitudes—signs that any experienced pilot would recognize as indicators of serious trouble.

Tragically, less than ten minutes after departure, the plane crashed before it could land again.

In the audio clip, the voice transmitting the announcements sounds like that of a co-pilot, though it is not definitively identified.

The speaker made three consecutive transmissions, each conveying the same urgent message: they were experiencing issues and needed space to return.

The opening words, “Statesville traffic,” immediately indicate that they were broadcasting on the Unicom frequency, where pilots announce their positions without air traffic control oversight.

The speaker states, “We’ve got an issue with…,” but the sentence trails off, suggesting either interruption or difficulty articulating the problem.

This vague phrasing hints at the chaos in the cockpit, where multiple issues may have been overwhelming the crew.

The audio does not specify the nature of the issues, leaving room for speculation.

Possibilities include an engine failure, which could explain the erratic flight path, or perhaps a malfunction with the baggage compartment door, which has caused problems on Citations in the past.

Control issues, such as trim malfunctions or multiple system warnings, could also have contributed to the chaos.

The repeated use of “troubles” implies that the crew was facing more than one abnormal situation, intensifying the pressure in the cockpit.

The voice itself, lacking the calmness of an experienced captain, suggests it might have been Jack Dutton, a pilot in training, rather than a seasoned airline veteran.

As the situation unfolded, the crew made the critical decision to return to the airport and attempt an immediate landing.

Announcing the deployment of the landing gear at low altitude indicates they were entering a committed phase, with limited options remaining.

The flight path data shows they began turning back early, initially aiming for runway 10 but ultimately executing a tight turn toward runway 28.

This tight turn raises concerns.

The Citation 550 is not designed for steep turns, especially under abnormal conditions.

The combination of low altitude, gear down, and potential engine issues creates a precarious situation, where even slight miscalculations can lead to disaster.

As they approached the runway, the crew announced they were on final.

However, this did not indicate a stabilized approach.

The ADSB data revealed they were significantly below the standard glide slope, with a speed of around 106 knots—lower than normal for a Citation 550 in such conditions.

At approximately one nautical mile from the runway, they should have been around 300 feet above ground, but they were much lower, leading to the tragic outcome of hitting the approach lights before reaching the runway.

This scenario exemplifies controlled flight into terrain, where the aircraft remains controllable but is too low and slow to clear obstacles.

The combination of drag from the landing configuration and potential engine failure severely limited their ability to maintain altitude.

Analyzing this incident reveals several critical lessons for pilots:

Stabilized Approach: Once on final, if speed is below minimum, altitude is below glide slope, or drag is excessive, recovery chances diminish significantly.An unstabilized approach should be abandoned immediately.
Engine Malfunctions: Pilots must be prepared to handle engine failures, especially during critical phases like takeoff.Severe vibrations and low altitude complicate these situations.
Workload Management: Low clouds can exacerbate the challenges of flying, especially when multiple issues arise simultaneously.Pilots must be aware of the silent enemy of workload, which can overwhelm even experienced crews.
Climb Straight Ahead: In the event of trouble shortly after takeoff, the standard procedure is to climb straight ahead to gain altitude and time before troubleshooting.

The audio from the cockpit captures a moment of desperation and determination.

The crew’s efforts to communicate their troubles and intentions reflect their professionalism, even in the face of overwhelming challenges.

This incident serves as a somber reminder of the fragility of life and the complexities of aviation.

As we await further analysis and data from the investigation, we must respect the lives lost and the efforts of those onboard.

Each flight carries lessons that can enhance safety and prevent future tragedies.

Understanding these lessons is crucial for all pilots, ensuring that they are better prepared for the unexpected.