FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA198 · Piper PA 46-350P

10 Mar 2013 · Rogers, AR, United States

Piper PA 46-350P · Accident: turbulence encounter during landing

From Chattanooga Metropolitan Airport (Lovell Field) (KCHA) to Rogers Municipal Airport-Carter Field (KROG)

Report a problem

Event

NTSB case
CEN13LA198
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
Instrument Meteorological Cond

Piper PA 46-350P

Aircraft type
Piper PA-46
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
N71DH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chattanooga Metropolitan Airport (Lovell Field) (KCHA), Chattanooga, TNTo Rogers Municipal Airport-Carter Field (KROG), Rogers, AR
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 · 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
Turbulence encounter
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While on approach, ice accumulated on the wings’ leading edges. The pilot stated that the airplane was flying and handling well but that the air was turbulent during the descent. According to the pilot, when the airplane was about 75 to 100 feet above ground level, he encountered “severe turbulence” and a “downdraft,” which resulted in his inability to control the airplane's descent. Subsequently, the airplane landed hard on the runway. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The sudden loss of control was consistent with inadequate airspeed for the weather conditions and leading edge ice buildup on the wings, which led to an aerodynamic stall.

Probable cause

The pilot’s failure to maintain control due to a sudden turbulence encounter while on final approach. Contributing to the accident was ice buildup on the wings’ leading edges.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA198
Event ID
20130318X44236
Case number
CEN13LA198
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-03-11.
  • API snapshot SHA-256: 0e52fa42aba841a3fafe0c2fb5673effd5b901ee46722db00c9b3c1967b8facf; retrieved 2026-09-15T21:07:34.920Z.