ERA10CA132 · SOCATA TBM 700
SOCATA TBM 700 · Accident: landing gear not configured
From Fort Lauderdale Executive Airport (FXE) to General Dewitt Spain Airport (M01)
Event
- NTSB case
- ERA10CA132
- 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
- N850VM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Ft Lauderdale, FLTo General Dewitt Spain Airport (M01), Memphis, TN
- 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
- 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
- Landing gear not configured
- 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was approaching his destination airport near dusk, and wanted to land before it was dark. The pilot forgot to lower the landing gear and the airplane touched down with the landing gear in the retracted position, which resulted in substantial damage to the fuselage skin, stringers, and wing attach fittings. The airplane was equipped with a landing gear configuration warning, which activated during landing; however, the pilot mistook it for a different warning indicator. The pilot further stated that he normally used a pre-landing checklist, but was distracted by the deteriorating weather conditions and did not utilize it. The pilot reported 3,079 hours of total flight experience, which included 50 hours in the same make and model as the accident airplane.
Probable cause
The pilot’s failure to extend the landing gear before landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA132
- Event ID
- 20100204X61041
- Case number
- ERA10CA132
- 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. 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: ced18e3c6c23b548f3d6c3741ba1bb4a3afcba2c212cb6e6d203e234cfdabaf0; retrieved 2026-09-15T13:39:57.332Z.