DFW05CA062 · Cessna 310-J
Cessna 310-J · Accident: hard landing
From Kent County Airport (22F) to Lubbock Preston Smith International Airport (LBB)
Event
- NTSB case
- DFW05CA062
- 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
- 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
Cessna 310-J
- Aircraft type
- Cessna 310
- 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
- N3138L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kent County Airport (22F), Jayton, TXTo Lubbock Preston Smith International Airport (LBB), Lubbock, TX
- 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
- Substantial
Cause areas
- Pilot in command › Aircraft control, 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
A twin-engine airplane made a hard landing followed by a loss of control while attempting to land. The 830-hour private pilot lost control of the twin-engine airplane while attempting to land following a cabin door opening just after take-off. After the door opened, the pilot elected to land and secure the door; however, the pilot could not achieve a safe landing gear indication. The pilot then elected to fly to his home field where additional help would be available. After becoming fatigued while holding the cabin door closed, the pilot declared an emergency and received vectors to the nearest runway. On short final, the pilot let go of the door and the airplane banked to the right, striking the runway with the right wing. The airplane then landed hard collapsing the gear.
Probable cause
The pilot's failure to maintain aircraft control, and his inadequate flare which resulted in a hard landing. A contributing factor was the pilot's diverted attention to the open cabin door.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA062
- Event ID
- 20050208X00156
- Case number
- DFW05CA062
- 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: 8927de79c45c77f464b75614e4da8c55cb4e52fe83509ebaf150e64668b0675d; retrieved 2026-09-22T06:19:30.367Z.