FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA112 · SOCATA TBM 700

5 Feb 2026 · Crockett, TX, United States

SOCATA TBM 700 · Accident: collision with terrain/object (non-CFIT) on approach

From Houston Executive Airport (TME) to an unrecorded destination

Report a problem

Event

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

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
N313BP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Houston Executive Airport (TME), Houston, TXTo not recorded
Aircraft age
About 18 years (built 2008)
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
Approach · VFR go-around
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
Collision with terrain/object (non-CFIT)
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

  • Aircraft › Aircraft oper/perf/capability

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that he performed a visual approach and landing at the destination airport with wing flaps fully extended. As the airplane crossed the runway threshold and with the airplane in ground effect, he reduced engine power to idle. When the airplane was about to touch down, it ballooned upward about 20 to 30 ft, and the pilot then initiated a go-around using full engine power with the landing gear extended and without reducing the flap setting. During the go-around, the stall warning sounded as the airplane drifted left and away from the runway. The airplane impacted the ground and was destroyed by post-crash fire. The pilot stated there was no mechanical malfunction/failure of the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain airplane control during a go-around that resulted in a collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA112
Event ID
20260209202419
Case number
CEN26LA112
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: 24f6edbad8d36f0a9243283199728bac23d7b0527f066596f58851c9617a2cdf; retrieved 2026-09-16T20:44:18.227Z.