ERA20CA168 · Dayton-Wright DH-4
Saving Liberty Dh4 Dayton-Wright DH-4 · Accident: flight control system malfunction/failure during takeoff
From Bowling Green Warren County Regional Airport (BWG) to Bowling Green Warren County Regional Airport (BWG)
Event
- NTSB case
- ERA20CA168
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Dayton-Wright DH-4
- Aircraft type
- Dayton Wright DH-4
- 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
- N32517
- Operator
- Saving Liberty Dh4
- Onboard fatalities
- Unknown
- Route
- From Bowling Green Warren County Regional Airport (BWG), Bowling Green, KYTo Bowling Green Warren County Regional Airport (BWG), Bowling Green, KY
- Aircraft age
- About 102 years (built 1918)
- 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
- Takeoff
- 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
- Flight control system malfunction/failure
- 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 systems
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the first flight test of the antique airplane, which was in the process of being restored, he had difficulty controlling the airplane in the roll axis. After takeoff, he noticed that the airplane required some right aileron to keep the wings level. After turning crosswind, the problem worsened, and required that he apply more pressure to the control stick (in the right aileron direction). As he turned downwind, he used nearly full right aileron to maintain control, and the force on the control stick was so high that he was unable to hold it with one hand. When he removed his left hand from the control stick to adjust the throttle, the airplane would roll toward the left. As the airplane approached the base leg, the pilot was unable to keep the wings level; the airplane entered a slip and he was unable to prevent the airplane from turning left. The airplane descended, touched down in the grass to the right of the runway, and came to rest nose down.
Examination of the airplane revealed that the aileron control system was continuous. However, due to the airplane damage, the rigging of the aileron system could not be evaluated.
The airplane sustained substantial damage to the forward fuselage, lower wing, and horizontal stabilizer.
Probable cause
A primary control (aileron) system anomaly that progressively worsened during a test flight that resulted in a loss of control. The reason for the anomaly was not determined due to impact damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA168
- Event ID
- 20200504X13237
- Case number
- ERA20CA168
- 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: b1279e746beebdc92736da283d6ab006ba6113339c37a220c445c2b6ea3920e6; retrieved 2026-09-16T11:32:50.652Z.