ERA19FA134 · Hogan Innovator
Hogan Innovator · Accident: loss of control in flight on approach
From Tom B. David Field (CZL) to Tom B. David Field (CZL)
Event
- NTSB case
- ERA19FA134
- 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
Hogan Innovator
- Aircraft type
- Hogan INNOVATOR
- 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
- N257AR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tom B. David Field (CZL), Calhoun, GATo Tom B. David Field (CZL), Calhoun, GA
- Aircraft age
- Not recorded
- 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 · VFR pattern downwind
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, who was also the owner/designer/builder of the experimental amateur-built airplane, had no recent flight experience and a medical certificate that had expired about 20 years before the accident flight. Despite assurances to his employees that he would not fly the airplane on what was its second test flight, video from inside the accident airplane showed that the pilot departed on the accident flight and the airplane immediately displayed rapid divergences in both the pitch and roll axis that were demonstrated on the airplane's first test flight. The airplane remained at treetop height throughout the upwind leg and into the crosswind turn and reached about 200 ft above ground level in level flight on the downwind leg. As the airplane accelerated, rapid pitch oscillations (phugoid) were exhibited. A handheld radio secured to the copilot's seat shoulder harness and the pilot himself were seen to "float" in the cockpit each time the airplane pitched nose down as the amplitude of the phugoid progressively increased, the duration of weightlessness displayed each time also increased. During one phugoid, an audible "oil pressure" warning was heard. The video ended abruptly as the pilot became unseated for about the fourth time and as the airplane appeared near treetop height. The airplane then impacted terrain.
The pilot had no experience in the accident airplane, which was the prototype for an airplane he intended to mass produce. A test pilot had completed the airplane's first flight in the traffic pattern. He described significant stability issues, which were captured by onboard video, and said the airplane departed controlled flight uncommanded about a dozen times. After the test pilot was able to safely land the airplane, it was disassembled, returned to the factory, modified according to the accident pilot's specifications based on captured data and the test pilot's observations, and then brought back to the departure airport for taxi testing the day before the accident.
According to employees of the company, the pilot was pressured by investors and missed deadlines, and was sleep-deprived and ill from a "severe" cold for which he was self-medicating. This pressure likely influenced the pilot's decision to test the prototype airplane himself despite his lack of experience and the stability issues demonstrated by the airplane on its initial test flight.
Examination of the wreckage and aircraft data captured from avionics systems, as well as statements from witnesses confirmed that the engine operated smoothly and continuously through the end of the flight. The condition of the wreckage precluded a thorough accounting of the flight control system; though based on statements provided by the previous test pilot, it is likely that the stability portrayed in the video of the first test flight remained during the accident flight, and when combined with the pilot's lack of experience, resulted in him being unable to maintain control of the airplane.
Probable cause
The pilot's failure to maintain aircraft control during the airplane's second test flight, which resulted in a collision with terrain. Contributing to the accident was the pilot allowing external pressures to guide his decision to fly the airplane when he possessed little total flight experience, no recent flight experience, and no experience in the accident airplane or similar airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19FA134
- Event ID
- 20190323X91950
- Case number
- ERA19FA134
- 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: 652049479162ef4437260922f182fba1ede770286a1101f39270a5549642ea48; retrieved 2026-09-15T06:55:54.663Z.