MIA07CA094 · Rotor Flight Dynamics, Inc. Dominator
Rotor Flight Dynamics, Inc. Dominator · Accident: loss of control on ground/water during takeoff
From Johnson County Airport (6A4) to an unrecorded destination
Event
- NTSB case
- MIA07CA094
- 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
- 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
Rotor Flight Dynamics, Inc. Dominator
- Aircraft type
- Rotor Flight Dynamics DOMINATOR
- Category
- Gyroplane
- 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
- UNREG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Johnson County Airport (6A4), Mountain City, TNTo not recorded
- 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
- Takeoff · roll/run
- First occurrenceThe 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 on ground/water
- 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
- Pilot in command › Physiological condition
- Pilot in command › Preflight planning/preparation, poor
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated to the FAA inspector that he had an accident back in the 1960's, and his back was injured. As a result of this, about 10 times a year, his legs will quit working and he will fall. On May 5, 2007, he flew his aircraft. On a latter flight that day, during the takeoff roll, he lost the use of his legs and could not control the rudders. He lost control of the aircraft and it turned over. He was trapped under the aircraft. Gas from the aircraft got on his body causing third degree chemical burns and he broke three ribs, and dislocated a shoulder. One of the EMT personnel who attended to the pilot at the accident site stated to the FAA inspector that they have records showing the pilot having an accident in the same aircraft at the same airport in March of 2007. The FAA inspector did confirm with the pilot that the same thing happened in March. He was not hurt that time; however, the aircraft was damaged. He said he now knows that he lost the use of his legs at that time, but he did not realize it then. No mechanical abnormalities with the aircraft was reported by the pilot.
Probable cause
The pilot's decision to attempt operation of the airplane with a known physical impairment (loss of leg control) which resulted in his loss of aircraft control during takeoff and the airplane nosing over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07CA094
- Event ID
- 20070828X01249
- Case number
- MIA07CA094
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 435a1c10e5c21c741c2f2a577cecb2bf902a7c815ed56a4e0f873b3185dcaf34; retrieved 2026-09-21T08:48:59.540Z.