CEN21LA470 · SOCATA TBM 700
SOCATA TBM 700 · Accident: hard landing
From Hattiesburg Laurel Regional Airport (PIB) to an unrecorded destination
Event
- NTSB case
- CEN21LA470
- 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
SOCATA TBM 700
- Aircraft type
- Socata TBM-700
- 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
- N700DQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hattiesburg Laurel Regional Airport (PIB), Hattiesburg, MSTo not recorded
- Aircraft age
- About 18 years (built 2003)
- 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
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during landing approach, when the airplane was about 50 ft above the ground, he pulled back on the engine power and the airplane stalled. The pilot applied 100% power to perform a go-around, but the left main landing gear struck the ground and the airplane bounced before becoming airborne again. The pilot flew the airplane back to the departure airport where he performed an overflight to ensure the landing gear was extended and landed uneventfully. The pilot noted in his report that fuel was leaking out of the left wing after the event. The manufacturer of the airplane performed an alignment symmetry inspection which revealed abnormal distortion and twisting of the left wing. The manufacturer recommended replacement of the left wing and placement of the fuselage in a fuselage jig to check for potential hidden damage.
Probable cause
The pilot exceeded the airplane’s critical angle of attack during the landing approach resulting in an aerodynamic stall and subsequent hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA470
- Event ID
- 20211004104039
- Case number
- CEN21LA470
- 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, cause areas. 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: a2a82191d7d2aa01f26747fe85b4d7f9209560e56f4db8d1a731e0b191a96a28; retrieved 2026-09-16T14:37:26.455Z.