ERA09LA302 · Hazelwood Michael S RV-8
Hazelwood Michael S RV-8 and Nanchang China CJ-6A · Accident: midair collision while maneuvering
Event
- NTSB case
- ERA09LA302
- 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
Aircraft 1 · Hazelwood Michael S RV-8
- Aircraft type
- Hazelwood Michael RV-8
- 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
- N875MH
- Operator
- Michael Hazlewood
- Onboard fatalities
- Unknown
- Route
- From Pryor Field Regional Airport (DCU), Decatur, ALTo Big River Airpark (5AL5), Muscle Shoals, AL
- 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
- Maneuvering · low-altitude flying
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Nanchang China CJ-6A
- Aircraft type
- Nanchang China CJ-6
- 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
- N81817
- Operator
- Billy Kennamore
- Onboard fatalities
- Unknown
- Route
- From Pryor Field Regional Airport (DCU), Decatur, ALTo Big River Airpark (5AL5), Muscle Shoals, AL
- 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
- Maneuvering · low-altitude flying
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
This report was modified on September 10, 2010.
Both pilots were friends and neighbors who were visiting an airport open house. Prior to returning to their home airport, the pilots discussed if they would be flying home together or separately. The pilot of the RV-8 decided to fly home separately, departed first, and performed some aerobatics near the airport traffic pattern. As the pilot of the CJ-6A prepared to depart, a photographer asked him to make some low passes over the runway, so that the photographer could take pictures. The CJ-6A took off and remained in the left airport traffic pattern. As the CJ-6A turned from base leg to final leg, the pilot of the RV-8 radioed via the common traffic advisory frequency that he was at the CJ-6A's 6 o'clock position, but did not provide distance information. He then radioed that he was at the CJ-6A's 4 o'clock position and again did not provide distance information. The CJ-6A then began a pass over the runway at approximately 200 feet above ground level. During that time, the RV-8 closed on the CJ-6A "dramatically," in excess of 30 knots, from above and behind. About the midpoint of the runway, the pilot of the CJ-6A began a climbing right turn. The RV-8's left wing then hit the CJ-6A, partially separating it. The RV-8 subsequently descended uncontrolled and impacted terrain.
Probable cause
The RV-8 pilot's failure to maintain adequate clearance from the CJ-6A while maneuvering.
This report was modified on September 10, 2010.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA302
- Event ID
- 20090525X10235
- Case number
- ERA09LA302
- 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: 199811338cef017e7b7f832633d5f9bf69613f3eeecb0d46495700569b361da9; retrieved 2026-09-13T18:04:25.409Z.