FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23LA304 · Cessna 182 J

23 Jul 2023 · Stow, MA, United States

Cessna 182 J · Accident: collision during takeoff/landing

From Lake Placid Airport (LKP) to an unrecorded destination

Report a problem

Event

NTSB case
ERA23LA304
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 182 J

Aircraft type
Cessna 182
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
N7ET
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Placid Airport (LKP), Lake Placid, NYTo not recorded
Aircraft age
About 58 years (built 1965)
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 · aborted after 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
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

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

NTSB narrative

The pilot reported that the airplane approached fast and bounced twice on the 3,110-ft-long runway. After the second bounce, he attempted to abort the landing, but trees at the end of the runway were already too close to clear. He turned right to avoid the trees, but then turned left to avoid a house, and collided with the trees. The airplane was substantially damaged during the accident and all three occupants of the airplane were seriously injured. Postaccident examination of the wreckage by a Federal Aviation Administration inspector did not reveal evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation, nor did the pilot report any.

Probable cause

The pilot’s delayed decision to abort the landing, which resulted in a collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA304
Event ID
20230724192681
Case number
ERA23LA304
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: b7fc38c4a044f1c5ae0dc22b6d608651e64d635f50b5a3425cabd1c6f5e7ee21; retrieved 2026-09-16T17:53:18.750Z.