4 Mar 2021: BEECH C23 NO SERIES

4 Mar 2021: BEECH C23 NO SERIES (N67013) — Unknown operator

1 fatality • Purcellville, VA, United States

Probable cause

The pilot's improper decision to depart from the short turf runway with a tailwind.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn March 4, 2021, about 1510 eastern standard time, a Beech C-23, N67013, was substantially damaged when it was involved in an accident near Purcellville, Virginia. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot was departing from runway 19 at Krens Farm Airport (14VA), Hillsboro, Virginia. A witness reported hearing the airplane take off and looked back to watch it depart. When she saw the airplane, it was “tilted to the left” as it descended into the trees. She heard the engine the entire time and stated that it made “traditional engine noises.” In addition, she noted that relative to the airplane’s takeoff direction, a tailwind prevailed at the time of the accident. The pilot’s son reported that his father always took off from runway 19 because of the slope of the runway. METEOROLOGICAL INFORMATIONThe 1455 recorded weather observation at Leesburg Executive Airport (JYO), Leesburg, Virginia, located about 13 miles southeast of the accident location, included wind from 310° at 24 knots gusting to 29 knots. Interpolation of the crosswind component chart revealed that there was about a 21-knot right crosswind and a tailwind component of 12 knots gusting to 14 knots at the time of the accident. WRECKAGE AND IMPACT INFORMATIONThe airplane struck several trees beginning about 326 feet southeast of the departure end of runway 19 at an elevation of about 690 ft mean sea level. (see Figure 1.) From the area of the initial tree strikes, there was a debris field that was 306 ft long, oriented along a 128° magnetic heading. The main wreckage, comprised of the fuselage and right wing, came to rest in a heavily wooded area at the end of the debris field. There was no post impact fire and an odor of 100LL aviation fuel was noted at the site. All major components of the airplane were located in the vicinity of the main wreckage.

Figure 1 - Accident site diagram depicting runway (dashed white lines), the initial tree impact scars, the debris path, and the main wreckage of the airplane. Also annotated is the reported wind direction and velocity at JYO. The left wing was impact-separated at the wing root and located about 40 ft prior to the main wreckage. The outboard approximate 5 ft leading edge of the left wing was impact-damaged and crushed aft. The rudder was impact separated from the vertical stabilizer and the vertical stabilizer was impact-separated from the empennage and located about 20 ft prior to the main wreckage. The leading edge of the vertical stabilizer exhibited impact damage. The horizontal stabilator remained attached to the empennage. The right wing was impact-separated and remained attached to the fuselage through cables. Flight control continuity was established to all flight control surfaces from the flight controls in the cockpit. The engine was removed from the airframe for further examination. Crankshaft and valvetrain continuity were confirmed by rotating the propeller hub by hand. Thumb compression and suction were observed on all cylinders. The spark plugs were removed and examined. The Nos. 2 and 4 spark plugs were oil soaked. All other spark plugs were light gray in color and in new condition. Spark was observed on all towers of the left and right magneto when the input shaft was rotated. There were no anomalies noted with the engine that would have precluded normal operation prior to the accident. The fixed-pitch propeller remained attached to the engine. Both propeller blades remained attached to the propeller hub. One blade was bent aft about 45° and exhibited leading edge gouging and chordwise scratching. The other propeller blade was bent slightly aft and exhibited chordwise scratching, leading edge gouging, and tip tearing. ADDITIONAL INFORMATIONThe “Take-off Distance – Grass Surface” performance chart in the airplane’s pilot operating handbook was interpolated for the associated conditions of 11°C and 750 ft elevation. The estimated ground roll with a 0 knot wind component was 1,236 ft, and the distance to clear a 50 ft obstacle was 2,068 ft. The takeoff distance performance chart did not include a tailwind component multiplier penalty.

Contributing factors

  • Pilot
  • Decision related to condition
  • Attain/maintain not possible

Conditions

Weather
VMC, wind 310/24kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.