CEN16LA137 · Matthews H Thomas JODEL F11 A
Matthews H Thomas JODEL F11 A · Accident: controlled flight into terrain/object (CFIT) on approach
From Fort Stockton Pecos County Airport (FST) to 6TE2 · Marathon, TX
Event
- NTSB case
- CEN16LA137
- 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
Matthews H Thomas JODEL F11 A
- Aircraft type
- Matthews H Thomas JODEL F11
- 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
- N3068M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Stockton Pecos County Airport (FST), Fort Stockton, TXTo 6TE2 · Marathon, TX
- Aircraft age
- About 14 years (built 2002)
- 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
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport pilot stated that he was landing in the experimental amateur-built airplane at his 1,600-ft-long private runway when he attempted a "late" go-around. The airplane impacted trees, a powerline, and terrain, resulting in substantial damage. The pilot reported that there were no pre-impact mechanical malfunctions or anomalies with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to conduct a go-around in a timely manner, which resulted in impact with trees and a powerline.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA137
- Event ID
- 20160331X35959
- Case number
- CEN16LA137
- 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, 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: 65f408d231fbe2bd1b5c257c4b0541328cfd02b65c7362728858b6fb99af631f; retrieved 2026-09-16T03:15:48.778Z.