CHI82FEG04 · Bently B8M
Bently B8M · Accident: in flight collision with object on approach
From Williamsburg, OH to Williamsburg, OH
Event
- NTSB case
- CHI82FEG04
- 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
- 0
- 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
Bently B8M
- Aircraft type
- Bently B8
- 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
- N2774L
- Operator
- John Cochran
- Onboard fatalities
- Unknown
- Route
- From Williamsburg, OHTo Williamsburg, OH
- 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
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s); Wire, transmission
- 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
- Pilot in command › Aircraft handling, improper
- Pilot in command › Judgment, poor
- Pilot in command › Lack of total experience
- Pilot in command › Lack of total experience in kind of aircraft
Approximate · Estimated position: the centre of Williamsburg, OH, the place the record names. Not the accident site.
NTSB narrative
AFTER TAKEOFF THE ACFT CLIMBED TO ABOUT 250 FT AGL & THEN MADE A GRADUAL SHALLOW 180 DEG LEFT TURN HEADING BACK TOWARD THE STRIP. IT GRADUALLY STARTED LOOSING ALTITUDE WITHOUT ANY NOTICABLE VARIATIONS OR DISRUPTIONS IN ITS FLT PATH WHEN IT CLIPPED THE TREES & POWER LINES. THE 6 HRS IN MAKE/MODEL DOES NOT REFLECT ACTUAL FLT TIMES BUT RATHER IS THE TOTAL AMOUNT OF TRAINING TIME ACCUMULATED GOING UP & DOWN THE RWY PRACTICING PILOT/AIRCRAFT CONTROLABILITY PRIOR TO HIS FIRST SOLO FLT. THERE WAS NO CFI ENDORSEMENT FOR THIS FLT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI82FEG04
- Event ID
- 20020917X03090
- Case number
- CHI82FEG04
- 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. 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: 65c67a6ed92e69e7ad10de388204245925ed6916f950af636c347a4345114011; retrieved 2026-09-21T07:53:13.443Z.