On December 3, 2023, a Beech C23, registration N76SB, was on what should have been a routine IFR flight near Midland, Virginia. The pilot had spent the flight practicing instrument approaches at nearby airports before returning home for one final approach into Warrenton-Fauquier Airport. It was daytime, but the weather told a different story—low ceilings, mist, and reduced visibility set the stage for a high-risk environment. What followed was a classic setup for a controlled flight into terrain accident, where everything appears normal right up until it isn’t.
The Pilot and Experience Level
The pilot was a 62-year-old commercial pilot with an instrument rating and approximately 628 total flight hours. While he held the appropriate certifications for the flight, a closer look at his instrument experience tells a more nuanced story. He had logged about 81 hours of simulated instrument time but only 3.4 hours of actual instrument experience.
That distinction is critical. Simulated instrument time—typically flown under a hood in good weather—doesn’t fully replicate the workload, stress, and sensory limitations of real-world IMC. When ceilings are low and visibility is reduced, actual instrument experience becomes far more relevant than practice under ideal conditions.
A Day of Practice Approaches
Earlier in the flight, the pilot had successfully completed multiple RNAV approaches at nearby airports, including Stafford Regional and Culpeper Regional. These approaches suggested that both the aircraft and the pilot were functioning normally up to that point.
Eventually, the pilot returned to his home airport for a final approach. He advised air traffic control that he intended to cancel IFR once he descended below the cloud layer. That statement, in hindsight, is telling. It suggests an expectation that he would break out of the clouds before reaching minimums—a risky assumption given the reported weather.
Weather That Didn’t Cooperate
At the time of the approach, conditions at Warrenton-Fauquier Airport were below published minimums. The ceiling was reported at 300 feet above ground level, while the approach required a minimum descent altitude between 384 and 424 feet AGL, depending on the approach category.
Visibility was also a factor. While official reports indicated about 1.75 miles, other evidence—including surveillance camera footage—suggested visibility may have been less than one mile. That’s below the required minimum for the approach.
In simple terms, the weather did not support a legal or safe descent below minimums.
The Final Approach
ADS-B data showed the airplane tracking toward the runway, descending as expected on approach. But then, about 4,350 feet short of the runway and slightly right of centerline, the data stopped.
There were no distress calls. No indication from the pilot that anything was wrong. A nearby surveillance camera captured the sound of the engine running at high power, followed by the impact and a fireball in the distance.
This wasn’t a loss of control. It wasn’t a stall. It was controlled flight into terrain—an airplane flying under control, but descending into something the pilot couldn’t see.
Impact and Aftermath
The aircraft struck approximately 80-foot-tall trees on a heading consistent with the runway approach path. The impact occurred less than half a mile from the runway threshold.
The airplane was destroyed by the collision and subsequent fire. The pilot did not survive.
Postaccident examination found no evidence of mechanical failure. The engine showed signs of normal operation, and the aircraft systems that could be evaluated appeared functional prior to impact.
A Decision at Minimums
Instrument approaches are built around a simple concept: if you don’t see the runway environment at minimum descent altitude, you go missed. No exceptions.
In this case, the pilot descended below that minimum altitude without having the required visual references. The NTSB determined that this decision—combined with weather conditions below approach minimums—led directly to the accident.
This is one of the most well-known and yet most violated rules in instrument flying. The temptation to “just go a little lower” can be strong, especially when you’re close to home or expecting to break out of the clouds at any moment.
The Human Factors
There are several human elements worth considering here. The pilot had just completed multiple successful approaches, which can build confidence—sometimes too much confidence. He was returning to his home airport, a familiar environment that can subtly lower perceived risk.
There’s also the expectation factor. If you believe you’re about to break out of the clouds, it becomes easier to justify descending just a bit further. That expectation can override strict adherence to procedures.
Additionally, while the pilot had an instrument rating, his limited actual IMC experience may have made it more difficult to accurately assess the situation in real time.
Toxicology revealed the presence of diphenhydramine, a sedating antihistamine, but at low levels. Investigators could not determine that it contributed to the accident.
Lessons to Take Away
This accident reinforces several key principles of instrument flying. First, minimums exist for a reason. They are not suggestions or guidelines—they are hard limits designed to keep you clear of terrain and obstacles.
Second, weather minimums matter just as much as altitude minimums. Even if you reach decision altitude, inadequate visibility means you still can’t continue the approach.
Third, actual instrument experience is invaluable. Flying in real IMC is fundamentally different from simulated conditions, and it requires a higher level of discipline and situational awareness.
Finally, expectations can be dangerous. Assuming that conditions will improve at the last moment can lead to decisions that erode safety margins.
A Familiar Scenario
Controlled flight into terrain accidents often follow a similar pattern. The airplane is functioning normally. The pilot is in control. But a breakdown in decision-making—often involving weather and altitude—leads to a collision with terrain.
That’s exactly what happened here.
Closing Thoughts
This accident is a reminder that instrument flying demands strict discipline. Procedures are there to protect you, especially when you can’t see what’s ahead. Once those procedures are bent, even slightly, the margin for error disappears quickly.
The pilot in this case had the training and the capability to execute a missed approach and try again. But the decision to continue below minimums removed that safety net.
And in instrument flying, once that safety net is gone, there’s often no second chance.
