DFW07FA084 · Beech 58P
Beech 58P · Accident: hard landing
From Dallas Love Field (DAL) to T40 · Marietta, OK
Event
- NTSB case
- DFW07FA084
- 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
Beech 58P
- Aircraft type
- Beechcraft 58
- 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
- N584DP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dallas Love Field (DAL), Dallas, TXTo T40 · Marietta, OK
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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 › Flare, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While landing to a grass runway, the pilot landed approximately 25-feet before the runway threshold in an area of rising terrain. Moments later the right landing gear failed and separated from the airframe. The airplane rotated clockwise as it departed the right side of the runway and dropped over a large embankment. The airplane continued along the bottom of the embankment and turned approximately 270-degrees before coming to rest in an upright position. A post crash fire ensued. Following the accident the pilot reported that the right main landing gear collapsed on landing. An examination of the right landing gear revealed that the upper structural truss member, which was manufactured straight, was deformed in a bow shape consistent with a hard landing. The right landing gear actuator rod was also found deformed. Pieces were submitted to the NTSB materials laboratory for examination. All submitted fracture features were on slant planes, and the pieces were deformed adjacent to the fractures consistent with overstress fracture. The examination of the airframe and engines revealed no evidence of pre impact mechanical failure/malfunction.
Probable cause
The pilot's improper landing flare. A contributing factor was the premature touchdown in an area of rising terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07FA084
- Event ID
- 20070321X00313
- Case number
- DFW07FA084
- 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: 58d8d07f06efaf1144eaac16a599eb7f59a1a7d994ba975a3fc824a09330b0a6; retrieved 2026-09-20T16:47:33.858Z.