FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23LA298 · Douglas A-4K

12 Jul 2023 · MCAS Cherry Point, NC, United States

Draken International Douglas A-4K · Accident: runway excursion during takeoff

Report a problem

Event

NTSB case
ERA23LA298
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
Government
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

Douglas A-4K

Aircraft type
Douglas A-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
N143EM
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 53 years (built 1970)
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
Public Aircraft
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
Runway excursion
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
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that a preflight inspection and flight control checks revealed no anomalies, and the pilot, maintenance personnel, and another pilot confirmed that the airplane was properly configured for takeoff. During the takeoff roll, as the pilot reduced forward stick pressure to rotate the airplane, he felt the nose strut extend; however, the airplane did not rotate. The pilot applied full aft stick and nose-up trim, but the airplane remained on the runway. As the airplane approached the end of the runway, the pilot chose to eject, and subsequently sustained serious injuries during the ejection and subsequent landing under parachute. The airplane departed the runway surface and continued an additional 3,000 ft through the runway overrun area, resulting in substantial damage from the impact and subsequent fire. Postaccident examination of the airplane’s wreckage revealed that the horizontal stabilizer trim was at 0° (the normal takeoff setting was between 6° and 8° nose up) and the wing flaps were retracted. Examination and operational testing of the horizontal stabilizer actuator and trim components revealed no anomalies. Further examination of the airplane revealed that the front left throttle quadrant air-to-air refueling store control head cannon plug was loose. The cannon plug was resting against the horizontal stabilizer manual override push-pull rod end in a way that could limit operation. The cannon plug also showed evidence of severe chafing consistent with contact with the push-pull rod end. However, it is likely that the airplane’s manual trim override was working normally, since functional tests of both the normal horizontal stabilizer trim and manual trim override were part of the after engine start checks, and the pilot reported no anomalies. Based on the available information, it could not be determined whether the trim system exhibited a runaway condition or if the pilot inadvertently actuated nose-down trim while holding the stick forward during the takeoff roll, as both situations would have presented the same to the pilot. According to the operator, a runaway nose-down trim condition during the takeoff roll was a known issue in the accident airplane make and model. Regardless of the reason for the nose-down trim, the pilot should have recognized the airplane’s failure to rotate as a runaway nose-down trim scenario and immediately completed the associated emergency procedure, which included employing the manual trim override. The procedure likely would have resulted in the airplane becoming airborne, and thus preventing the accident.

Probable cause

The pilot’s failure to identify and appropriately respond to an anomalous nose-down trim condition during the takeoff roll, which resulted in his decision to eject and the airplane’s subsequent runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA298
Event ID
20230713192623
Case number
ERA23LA298
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, cause areas. 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: 682e6ed2426213ad54cd60d7db5eb06696170fc0b432c90d79590f1580b38340; retrieved 2026-09-16T17:51:36.577Z.