Greg Biffle Crash Prelim Report 2 How AMBIGUITY Took Down the Citation

Understanding the Accident's Nature

• 💡 The Cessna Citation 550 crash involving Greg Biffle and his family was not due to a clear failure like thrust reverser deployment or engine tearing apart.
• 🔑 Instead, the preliminary report indicates a situation where the airplane never clearly failed, but the cockpit became unreliable, leading to a loss of trust in its indications.
• ⚠️ Unreliable systems are often more dangerous than broken ones, as they present questions rather than clear checklists, forcing constant diagnosis.

Early Signs of System Ambiguity

• 📌 The report highlights that almost every abnormal event was described in soft language, like things being "not working properly" instead of "failed."
• ✈️ Early issues included an inoperative thrust reverser indication light (though the reverser worked), suggesting that cockpit indications could not be taken at face value.
• 📊 During takeoff, a comment about the left engine making more power than the right, and later a pilot reporting the left-side altimeter was "not working properly," forced cross-checking over checklist execution, consuming time and mental bandwidth.
• ⚙️ The landing gear indicator lights not illuminating after selection forced the crew to interpret the airplane's state rather than simply reading it, adding to diagnostic workload.

Electrical System Instability

• ⚡ The preliminary report, though not explicitly stating "electrical failure," reveals a clear electrical pattern throughout the flight, starting with battery-only engine starts.
• 🔊 The cockpit voice recorder (CVR) showed intelligible audio from the left seat disappearing, then severe degradation across all channels, before suddenly returning, suggesting a power or audio panel issue.
• 🛰️ Garmin GTN750 data also showed airspeed and heading data stopping and then returning, indicating potential transient power interruptions or loss of valid inputs.
• ❓ A passenger's question about alternator power and the pilot's subsequent comment, "that was the problem," strongly suggested an electrical switching or reset event, highlighting crew uncertainty about the electrical system's state.

Autopilot Disengagement and Workload

• 📉 The autopilot disengaged when the cockpit was already under strain from uncertain indications and tightening weather, removing a critical tool for managing workload.
• ✅ This disengagement is a safety feature in the Citation 550, designed to prevent the autopilot from flying with unreliable or inconsistent flight instrument data.
• 🧠 The pilot instantly inherited pitch control, bank control, and airspeed management, significantly increasing cognitive load in instrument conditions while troubleshooting continued.

Crew Configuration Challenges

• 👥 The aircraft required a qualified second in command, but instead had a low-time pilot in the right seat and an experienced pilot in the cabin, meaning help was not the same as redundancy.
• 🎯 In a two-pilot jet, responsibilities are divided for workload containment, ensuring one pilot flies while another monitors systems, radios, and checklists.
• ⚠️ This incomplete structure meant the PIC carried most of the decision-making load, and critical functions like enforcing discipline or calling for a go-around could fall through the cracks.

Critical Final Approach

• 🛑 By the time the airplane was turning toward final, the crew faced a severe workload problem, not just an airplane problem.
• 📉 The recorded data showed airspeed and altitude decaying together on final, indicating divided attention and defensive pitch management rather than stabilization.
• 💥 The impact geometry confirmed the airplane struck approach lights in a shallow descent, remaining flyable to the end, but having run out of margin due to an unstable approach and high workload.