ERA20FA027 · Grumman OV-1 D
Grumman OV-1 D · Accident: collision with terrain/object (non-CFIT) while maneuvering
From Witham Field (SUA) to Witham Field (SUA)
Event
- NTSB case
- ERA20FA027
- 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
- 1 · 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
Grumman OV-1 D
- Aircraft type
- Grumman OV-1
- 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
- N10VD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Witham Field (SUA), Stuart, FLTo Witham Field (SUA), Stuart, FL
- Aircraft age
- About 51 years (built 1968)
- 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
- Maneuvering · aerobatics
- 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
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was for the pilot to visually locate the aerobatic box in preparation for his airshow performance the following day; he told his crew chief that he did not intend to perform aerobatics during the accident flight due to the low cloud ceiling and wind. After takeoff, the pilot performed a left climbing turn followed by a left descending turn, then flew parallel to the runway while descending to about 500 ft. About the midpoint of the runway, he began a climbing left turn followed by a right climbing turn of increasing pitch attitude. The right turn was described by several witnesses as being about 10° to 45º past 90°, with one witness describing it as an “overbank” and another describing it as a “…crisp right roll to about 135°.” The airplane began descending and accelerating, and several witnesses reported that the pilot was attempting “pulling,” or applying aft elevator control input. The airplane was destroyed when it impacted the ground near the runway in a nose- and right-wing-low attitude.
Witnesses reported hearing no issues with the engines, and examination of the wreckage revealed no evidence of preimpact failure or malfunction with either engine, the airframe, flight controls, or propellers. An impact signature on adjacent structure from the elevator was consistent with up-elevator input at impact. It could not be determined why the pilot did not roll left to recover from the inverted attitude while descending rather than attempting to pull through it.
The pilot had not reported any use of medication at the time of his most recent medical examination. Although postaccident toxicology testing identified the antidepressant medication citalopram and its metabolite, given the circumstances of this accident, it is unlikely that effects from his use of citalopram or his depression were factors in the accident. Although ethanol was also detected, it is likely that the identified ethanol was from sources other than ingestion and did not contribute to the accident.
While a video depicted dark coloration that was somewhat translucent near and on the airplane just before impact, that coloration did not appear in any prior or subsequent frames until ground contact. All primary and secondary flight controls were accounted for, there was no evidence that any other parts separated from the airplane in-flight, and no bird remains were noted among the wreckage.
Probable cause
The pilot’s improper recovery from a low-altitude aerobatic maneuver, which resulted in descent into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20FA027
- Event ID
- 20191102X80415
- Case number
- ERA20FA027
- 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: 50647bc9fbedae074bf5b1f89ed380c574b733ddb6f9f222ce20e8c3bb7ca41e; retrieved 2026-09-15T07:08:00.377Z.