ERA13CA132 · Triad International Technology RV6A
Triad International Technology RV6A · Accident: abrupt maneuver during landing
From Houston County Airport (M93) to Ellington Airport (LUG)
Event
- NTSB case
- ERA13CA132
- 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
Triad International Technology RV6A
- Aircraft type
- Triad International Technology RV6
- 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
- N956TT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Houston County Airport (M93), McKinnon, TNTo Ellington Airport (LUG), Lewisburg, 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
- Abrupt maneuver
- 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/owner stated that during the approach for landing he was flying “slightly high and slightly too fast.” In an attempt to salvage the landing, the pilot reduced power, which resulted in a hard bounce on the runway with the airplane returning to a height of about 15 feet. The pilot then applied power in an attempt to remain airborne but lost directional control of the airplane. As the pilot attempted to regain heading control, he again reduced power, which resulted in the left wing impacting the ground then the airplane spinning around in a field just west of the taxiway and runway. Postaccident examination revealed substantial damage to the right wing and fuselage. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s improper landing flare and failure to maintain directional control during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA132
- Event ID
- 20130214X53155
- Case number
- ERA13CA132
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 1b2d3dc470d218ee1a46d96e7fe7e434ec0add83b057f77c3dc4cda2eabf054a; retrieved 2026-09-15T20:55:43.446Z.