FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23LA316 · Cessna 152

27 Jul 2023 · Maiden, NC, United States

Flight Level Aviation Cessna 152 · Accident: collision during takeoff/landing on approach

From Lake Norman Airpark (14A) to an unrecorded destination

Report a problem

Event

NTSB case
ERA23LA316
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 152

Aircraft type
Cessna 152
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
N6194Q
Onboard fatalities
Unknown
Route
From Lake Norman Airpark (14A), Mooresville, NCTo not recorded
Aircraft age
About 42 years (built 1981)
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
Collision during takeoff/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

  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight instructor and student departed on an instructional flight and flew to a nearby grass airstrip for pattern work. Although the flight instructor had flown into the airstrip before, he did not check the runway length before the flight departed and thought it was longer than the actual published 2,400-ft length. After arriving at the destination airstrip the, student entered left downwind for runway 13, resulting in a right quartering tailwind of about 5 knots. The flight instructor told the student to perform a short field landing. The student turned early onto the base leg of the airport traffic pattern, then turned onto final approach, resulting in the airplane being high and fast. After informing the student that the airplane was high and fast the student pitched the airplane down, which increased the airspeed, but he did not reduce power. The airplane continued to be high and fast, and somewhere before the midpoint of the runway the flight instructor told the student to go around. He repeated the instruction after the student hesitated. The student leveled off, added full power, removed carburetor heat, but left the flaps extended at 30° while he pitched for Vx airspeed. While climbing slightly, and with insufficient runway remaining to land, the flight instructor took the controls from the student and at that time realized the flaps were still at 30°. The airplane subsequently collided with trees beyond the end of the runway before descending to the ground resulting in substantial damage to the fuselage, wings, and empennage. The flight instructor reported there was no preimpact mechanical failures or malfunctions of the airplane that would have precluded normal operation. He also reported that the accident could have been prevented by executing a go-around much earlier.

Probable cause

The flight instructor’s inadequate supervision of the landing approach and go-around, and his delayed remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA316
Event ID
20230728192735
Case number
ERA23LA316
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, coordinates, 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: 6fa67fcea4963c8a61a8320e6f1c33f02149d5e6580c3f2733d032c66e5c0bc6; retrieved 2026-09-16T17:55:32.962Z.