FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA263 · Cessna 172 M

6 Jun 2022 · Westminster, MD, United States

Clearview Flying Club Cessna 172 M · Accident: loss of control in flight on approach

Report a problem

Event

NTSB case
ERA22LA263
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
Event fatalities
Unknown
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 172 M

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
N29501
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 48 years (built 1974)
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
Approach · VFR go-around
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
Loss of control in flight
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 flight instructor reported that during a dual training flight with a student pilot, they returned to their base airport and practiced two landings without incident. During the third landing, the student pilot applied too much elevator back pressure in the landing flare, and the instructor stated “power.” Subsequently, the student pilot applied full power to go-around, instead of a “slight amount of power” which was what the flight instructor expected. After the application of full power, the airplane drifted beyond the right side of the runway, was near the aerodynamic stall speed, and was approaching trees ahead. The flight instructor reported that she “eventually” was able to take the flight controls, where she reduced power to idle, lowered the nose of the airplane, and landed in a down sloping grass area beyond the end of the runway. During the runway excursion, the airplane impacted trees, which resulted in substantial damage to the right wing and fuselage. Neither pilot reported any preimpact mechanical malfunctions or failures that would have precluded normal operation with the airplane.

Probable cause

The student pilot’s loss of control during a go-around and the delayed remedial action initiated by the flight instructor, which resulted in a runway excursion and collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA263
Event ID
20220607105207
Case number
ERA22LA263
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, cause areas. 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: cc2d42d0a25a288840ea5c548b53d44d19f33b9a2ff6dc9e2b93b490bfdc901d; retrieved 2026-09-16T15:17:52.756Z.