FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA331 · Cessna 172M

23 Jun 2014 · Miami, FL, United States

Pilot Training Center Cessna 172M · Accident during landing

From Miami Executive Airport (TMB) to Miami Executive Airport (TMB)

Report a problem

Event

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

Cessna 172M

Aircraft type
Cessna 172
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
N621AA
Onboard fatalities
Unknown
Route
From Miami Executive Airport (TMB), Miami, FLTo Miami Executive Airport (TMB), Miami, FL
Aircraft age
About 39 years (built 1975)
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
Miscellaneous/other
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
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was conducting touch-and-go practice takeoffs and landings in the airport traffic pattern. She reported that during the landing flare for the final landing, her seat slid aft. The airplane ballooned and subsequently landed hard, resulting in substantial damage to the engine firewall and cabin floor structure. The accident airplane make/model was the subject of a Federal Aviation Administration (FAA) airworthiness directive (AD) regarding seat slippage, issued three years prior to the accident. Review of the airplane's maintenance logs revealed that the airplane had received the inspections required by the AD, and examination of the seat rail and latching mechanism by an FAA inspector revealed no anomalies.

Probable cause

The pilot's failure to ensure the security of the seat prior to flight, which resulted in a loss of control and subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA331
Event ID
20140708X41119
Case number
ERA14CA331
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2014-06-24.
  • API snapshot SHA-256: 75a908cf64d250fc69fcd16bfc22707fda6a1dc294f49d89a22964ad548906d3; retrieved 2026-09-16T00:51:21.163Z.