FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL02LA106 · Beech 35

23 May 2002 · Hernando, MS, United States

Beech 35 · Accident: dragged wing, rotor, pod, float or tail/skid during initial climb

From Hernando Village Airpark (H75) to an unrecorded destination

Report a problem

Event

NTSB case
ATL02LA106
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

Beech 35

Aircraft type
Beechcraft 35
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
N2925B
Operator
John R Osborne · private individual
Onboard fatalities
Unknown
Route
From Hernando Village Airpark (H75), Hernando, MSTo 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
Initial climb
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
Dragged wing, rotor, pod, float or tail/skid
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 › Clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted the ground, during a soft field takeoff. After taking off, the pilot lowered the nose and attempted to enter ground effect. The airplane then started to drift to the left. The pilot neutralized the wings, and corrected with right rudder. The airplane's right wing pitched up and the left wing struck the ground. The airplane came to rest approximately 1,500 feet down the runway. The pilot did not report a mechanical problem with the airplane.

Probable cause

The pilot's failure to maintain wing tip clearance during an attempted takeoff that resulted in the collision with the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL02LA106
Event ID
20020530X00769
Case number
ATL02LA106
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: e248e4697e3b9cac8c24cbf6bef9e64c438f1d2c5ee7378e28d6d099cd6ded27; retrieved 2026-09-21T19:43:41.904Z.