ERA17FA106 · Beech C23
Beech C23 · Accident: loss of control in flight on approach
From Barrow County Airport (WDR) to Barrow County Airport (WDR)
Event
- NTSB case
- ERA17FA106
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech C23
- Aircraft type
- Beechcraft 23
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N24695
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Barrow County Airport (WDR), Winder, GATo Barrow County Airport (WDR), Winder, GA
- Aircraft age
- About 44 years (built 1973)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot, who had recently purchased the airplane, and a flight instructor were conducting a local instructional flight. Another pilot reported that, while approaching the airport for landing, he heard an airplane (likely the accident airplane) announce over the common traffic advisory frequency that they would be departing runway 31; however, he did not see the airplane depart. A witness, who was driving on a highway near airport, observed the accident airplane fly in front of her heading south/southeast. She stated that the airplane seemed to be flying low and fast as it went over the highway. It then began to nose down, then level out, and "tilt to the right." The witness then lost sight of the airplane behind trees.
The airplane impacted trees and terrain on a southeasterly heading about 500 ft west of the departure end of runway 31 (the runway 13 threshold). Given the location and orientation of the wreckage, it is possible that the flight instructor and student departed runway 31 and were attempting to return to the airport to land on the opposite runway (13) when they experienced a loss of control. As the airplane turned back toward runway 13, the pilots would have encountered an 8-knot gusting to 14-knot tailwind, which would have increased the airplane's ground speed and closure rate with terrain and obstacles surrounding the airport and the runway.
Weight and balance calculations revealed that, although the airplane was operating below its maximum gross weight at the time of the accident, its center of gravity (CG) was forward of the limit established by the manufacturer. Since airplane stability and control are affected by improper balance, exceedance of the forward limit would likely have resulted in a nose-heavy condition and difficulty in controlling and raising the nose, especially during takeoff and landing.
Although the reason for the decision to land on the opposite runway could not be determined, it is likely that the airplane's forward CG affected its control characteristics and that the trim required to help relieve the control forces imposed by the forward CG may have resulted in reduced pitch control travel at the lower airspeeds required for approach and landing. Examination of the airplane and engine did not reveal evidence of any preimpact malfunctions or failures that would have precluded normal operation. There was evidence of fuel onboard, and the lack of airframe, flight control, and engine anomalies were also consistent with a loss of control event.
Toxicology testing revealed that the flight instructor had used amphetamine at some time before the flight, but whether the drug was being used to treat an underlying condition such as attention-deficit/hyperactivity disorder (ADHD) or narcolepsy, or whether he had used the amphetamine illicitly to get high and was in/or entering the withdrawal phase of use, also could not be determined. Overall, whether the flight instructor's use of amphetamine or effects from an underlying medical condition contributed to the accident circumstances could not be determined.
Probable cause
The flight instructor's inadequate preflight planning and operation of the airplane outside its center of gravity envelope, which resulted in a loss of control while maneuvering.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17FA106
- Event ID
- 20170216X50911
- Case number
- ERA17FA106
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 27a88515e2acf80026c318ee9a18473b25091e9d3248cbacc81fbfc78394c635; retrieved 2026-09-15T05:58:47.029Z.