Skip to content

Atlas / NTSB / ERA13CA044

NTSB CAROL · Event

Event ERA13CA044

2012-10-20 Miami, Florida, United States Airport · TMB None 1 aircraft Status: Completed

Registry · N974BC

FAA Aircraft Registry record.

Make / Model

CESSNA 172R

Year of manufacture

1997 · 15 years old at event

Engine

LYCOMING I0360 SER A&C (200 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

19970424

ADS-B equipped

Yes — Mode-S AD929D

Registrant of record

L & W AIRCRAFT INVESTMENT LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The flight instructor's improper power management during a steep, obstacle-clearance approach, which resulted in a hard landing.

Factual narrative

According to the flight instructor, he was demonstrating the technique required to land the airplane over a 50-foot obstacle to a short runway. At 50 feet over the runway, 60 knots airspeed, with flaps deployed, he reduced the throttle to idle and pitched the nose down to "increase airspeed" and flare the airplane prior to touchdown. Immediately after reducing the engine power to idle, the airplane "sunk" and the instructor responded with a full-throttle application. The airplane was "too close to the ground" and the engine did not respond in time to prevent a hard landing, which resulted in substantial damage to the engine firewall. The instructor reported that there were no mechanical malfunctions or failures that would have precluded normal operation of the airplane. According to the flight instructor, he was demonstrating to a student pilot the technique required to land the airplane on a short runway over a 50-foot obstacle. About 50 feet over the runway, at an airspeed of 60 knots, with flaps fully deployed, the instructor reduced the throttle to idle and pitched the nose down to "increase airspeed" and flare the airplane before touchdown. Immediately after reducing the engine power to idle, the airplane "sunk," and the instructor responded with a full throttle application. However, the airplane was "too close to the ground," and the engine did not respond in time to prevent a hard landing, which resulted in substantial damage to the engine firewall. The instructor reported that there were no mechanical malfunctions or failures that would have precluded normal operation of the airplane. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C
  • C Personnel issues-Action/decision-Action-Delayed action-Instructor/check pilot - C
  • Aircraft-Aircraft structures-Fuselage-Gear attach fittings (on fus)-Capability exceeded

Verbatim from NTSB's published report. Source file NTSB_2012_ERA13CA044.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗