FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA109 · Cessna 172S

27 Jan 2014 · Immokalee, FL, United States

Rexair Sales & Leasing Cessna 172S · Accident: hard landing

From Immokalee Regional Airport (IMM) to Immokalee Regional Airport (IMM)

Report a problem

Event

NTSB case
ERA14CA109
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 172S

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
N21670
Onboard fatalities
Unknown
Route
From Immokalee Regional Airport (IMM), Immokalee, FLTo Immokalee Regional Airport (IMM), Immokalee, FL
Aircraft age
About 10 years (built 2004)
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
Hard landing
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

According to the flight instructor and the student pilot, they flew from their home airport to another airport where the student pilot completed four landings without the flight instructor touching the controls. After the fourth landing, the flight instructor got out of the airplane so the student pilot could complete three solo takeoffs and landings. The first two landings were uneventful; however, according to the student pilot, just before the landing flare for the third landing, the airplane was "pushed" to the left side of the runway, "possibly by a wind gust," then landed hard. The flight instructor noted that during the approach, the airplane appeared to be slower than normal, followed by a hard landing. The main landing gear touched down first, then there was a "gallop on the nose wheel," and the airplane bounced twice before all landing gear were on the ground. The flight instructor subsequently performed a partial inspection the airplane, determined there was no damage, and the two flew it back to their home airport. During a subsequent rental, at an en route stop, another pilot noted propeller damage, and further inspection revealed firewall damage. Neither the flight instructor nor the student pilot reported any preexisting mechanical anomalies or damage to the airplane. Wind, recorded about the time of the accident, was 10 degrees from the right of runway heading, at 6 knots.

Probable cause

The student pilot's improper landing flare, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA109
Event ID
20140130X70327
Case number
ERA14CA109
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: 68940f81a97dfd27af623fbb0efe920f3643e5339ea7a21ea2f2a54bc81ce052; retrieved 2026-09-15T23:17:36.540Z.