ERA13LA093 · Russom ROY G HUMMEL H5
Russom ROY G HUMMEL H5 · Accident: loss of control in flight during initial climb
From Tom B. David Field (CZL) to Tom B. David Field (CZL)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA13LA093
- 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
Russom ROY G HUMMEL H5
- Aircraft type
- Russom Roy HUMMEL H5
- 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
- N156FH
- 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
- Initial climb
- 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 › Physical
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The experimental amateur-built airplane was completed about 4 months before the accident and had been flown less than 4 hours by the pilot/builder. Witnesses reported that when the airplane took off, the engine sounds, ground roll, and departure were all "normal." Then, about 300 feet above the ground, the airplane began a slow roll to the right (the airport traffic pattern was to the left), reaching about 90 degrees of bank and 60 degrees of nose-down pitch when it descended into trees. Witnesses reported no engine power changes until impact. Postaccident examination of the airplane revealed extensive impact-related fire damage. The throttle and mixture controls were at their full power positions, and the carburetor heat control was in the full cold position. Flight control continuity was confirmed, but numerous flight control surfaces had separated from the cockpit controls, consistent with impact overload. No preexisting mechanical anomalies were found that would have precluded normal operation.
The 76-year-old pilot had no recent Federal Aviation Administration medical examinations, but none were required as he was operating the airplane as a sport pilot. Although the cause of death was listed as blunt force trauma, the autopsy report also revealed severe atherosclerotic coronary artery disease but did not contain information about the extent of occlusions, the vessels involved, or evidence of interventions, such as stents. The report identified extensive fibrosis and scarring throughout the heart muscle, suggesting previous coronary artery blockage event(s); but with no further details of the scarring and no microscopic examination. The exact extent of cardiac disease and whether there had been any recent coronary events could not be determined. Extensive scarring of the heart muscle creates an increased risk of irregular heart rhythms that can lead to dizziness or sudden incapacitation.
Toxicology was positive for blood pressure medications that, by themselves, should not have degraded the pilot's ability to safely operate the airplane but with other factors, could have resulted in low blood pressure, dizziness, or even unconsciousness. Based on the pilot's recent reported dizziness, the findings of severe coronary artery disease, and evidence of heart muscle damage, it is likely that the pilot was impaired or incapacitated when he lost control of the airplane as a result of low blood pressure due to medications, worsening heart disease, or an irregular heart rhythm.
Probable cause
The pilot’s impairment or incapacitation due to the effects of medication, worsening cardiac disease, or cardiac arrhythmia, which resulted in his loss of control of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA093
- Event ID
- 20121218X70907
- Case number
- ERA13LA093
- 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: addc7a4c97276cc97380f2387bd7de589294f6c27a6158a4c2e3d247efefe9c1; retrieved 2026-09-14T15:50:54.176Z.