ERA11LA208 · Jennings John C Mini Max
Jennings John C Mini Max · Accident: collision during takeoff/landing
From Clinton, SC to Clinton, SC
Event
- NTSB case
- ERA11LA208
- 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
Jennings John C Mini Max
- Aircraft type
- Jennings John MINI MAX
- 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
- UNREG
- Operator
- John Carrol Jennings
- Onboard fatalities
- Unknown
- Route
- From Clinton, SCTo Clinton, SC
- 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
- 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
- Collision during takeoff/landing
- 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)
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
According to a witness, as the amateur-built airplane began its takeoff climb, the left wing hit a small tree. The airplane then tilted to the left and collided with larger trees before impacting the ground. An examination of the accident site revealed that the takeoff area was adjacent to the pilot’s home. The takeoff area had 150 yards of cleared trees with 100-foot-tall trees on both ends of the clearing. The left wing impacted a tree approximately 20 above ground level, shearing off about half of the wing; the airplane then impacted larger trees before colliding with the ground. The non-certificated pilot likely did not have sufficient clearance from obstacles to perform a takeoff.
Probable cause
The pilot's inadequate performance planning, which resulted in a collision with a tree during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA208
- Event ID
- 20110325X22454
- Case number
- ERA11LA208
- 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, 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: 975c2a907ea1ed87d581c51e545c93276150972e47ecb0ad9e1083ba9ee825a7; retrieved 2026-09-13T21:17:39.808Z.