CEN09CA046 · Hemp Timothy LEGACY 200
Hemp Timothy LEGACY 200 · Accident: runway excursion during landing
From E80 · Belen, NM to Socorro Municipal Airport (ONM)
Event
- NTSB case
- CEN09CA046
- 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
Hemp Timothy LEGACY 200
- Aircraft type
- Hemp Timothy LEGACY 200
- 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
- N273TE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From E80 · Belen, NMTo Socorro Municipal Airport (ONM), Socorro, NM
- 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 · landing roll
- 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
- Runway excursion
- 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
- 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
While performing a landing to 5,841-foot long runway, the private pilot crossed the runway threshold at 110 knots at 50 feet above ground level. The pilot attempted to perform a "soft landing" which resulted in a longer flare distance. After touchdown, insufficient runway remained to allow the airplane to be stopped on the prepared surface. The airplane departed the end of the runway and was substantially damaged. The pilot was able to egress without assistance. The pilot stated that the accident could have been prevented if he would have maintained a slower airspeed on final approach and shortened the flare distance.
Probable cause
Failure of the pilot to land with sufficient runway to stop the airplane on the runway. Contributing to the accident was the airplane's speed on final approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA046
- Event ID
- 20081104X83918
- Case number
- CEN09CA046
- 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: 54e1a9cf16519ca03e5ae6a58072c4365edd243ea8874931f09d138c8bb9f4b4; retrieved 2026-09-15T10:31:37.060Z.