Skip to content

Atlas / NTSB / ERA10CA398

NTSB CAROL · Event

Event ERA10CA398

2010-07-24 White Plains, New York, United States Airport · HPN None 1 aircraft Status: Completed

Registry · N1166W

FAA Aircraft Registry record.

Make / Model

CESSNA 172S

Year of manufacture

2006 · 4 years old at event

Engine

LYCOMING IO-360-L2A (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20061204

ADS-B equipped

Yes — Mode-S A045BC

Registrant of record

FLIGHT OPERATIONS AIRCRAFT LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The student pilot's improper landing flare and the flight instructor's delayed remedial action resulting in a bounced landing.

Factual narrative

The certificated flight instructor (CFI) and student pilot were returning to the airport at the conclusion of a lesson. The CFI stated that the student was flying the airplane, and the landing approach was "stable and normal except for the fact that it was low." The CFI took control of the airplane, added power to avoid landing on the runway's displaced threshold, and transferred control back to the student. The CFI stated that the student reduced power "abruptly," and that the airplane's nose "dropped" and impacted the runway before he could recover. The CFI performed an aborted landing, and subsequently landed normally. Later inspection of the airplane revealed damage to the engine firewall. The CFI stated that there were no mechanical malfunctions or anomalies with the airplane. The certificated flight instructor (CFI) and student pilot were returning to the airport at the conclusion of a lesson. The CFI stated that the student was flying the airplane, and the landing approach was "stable and normal except for the fact that it was low." The CFI took control of the airplane, added power to avoid landing on the runway's displaced threshold, and transferred control back to the student. The CFI stated that the student reduced power "abruptly," and that the airplane's nose "dropped" and impacted the runway before he could recover. The CFI performed an aborted landing and subsequently landed normally. Later inspection of the airplane revealed damage to the engine firewall. The CFI stated that there were no preaccident mechanical malfunctions or anomalies with 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-Incorrect action performance-Student pilot - C
  • C Personnel issues-Action/decision-Action-Delayed action-Instructor/check pilot - C

Verbatim from NTSB's published report. Source file NTSB_2010_ERA10CA398.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 ↗