FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17LA083 · Maule MX7 160

11 Jan 2017 · Carthage, TN, United States

Maule MX7 160 · Accident: loss of control in flight during landing

From Lebanon Municipal Airport (M54) to Carthage, TN

Report a problem

Event

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

Maule MX7 160

Aircraft type
Maule MX7
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
N3156K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lebanon Municipal Airport (M54), Lebanon, TNTo Carthage, TN
Aircraft age
About 22 years (built 1995)
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 · flare/touchdown
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
Loss of control in flight
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot was landing on his 1,100 ft-long private grass airstrip. He set up for a landing to the north due to obstacles and the runway's upslope in that direction. A witness reported that the wind was "blowing hard," gusting, and variable at the time of the landing. The witness described the approach as normal until just before touchdown, when the left wing dropped and the right wing rose. The airplane then collided with the ground and came to rest on its nose with structural damage to the left wing and forward fuselage. The pilot reported that there were no mechanical malfunctions or failures before the accident, and the witness reported that the engine sounded normal during the event. Recorded weather information from nearby airports indicated wind from the south; one airport reported gusts of up to 29 knots. The pilot subsequently reported that the accident was the result of wind gusts that he had not anticipated.

Probable cause

The pilot's inadequate compensation for gusting tailwind conditions, which resulted in a loss of airplane control during the landing flare.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17LA083
Event ID
20170111X80048
Case number
ERA17LA083
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: 97dda60b71282a3fae2e48d2cf11ec16ee412ecaf24e762a4928e54621b8fc99; retrieved 2026-09-16T04:56:43.460Z.