ERA22LA360 · Cessna 172K
Cessna 172K · Accident: landing area overshoot
From Katama Airpark (1B2) to an unrecorded destination
Event
- NTSB case
- ERA22LA360
- 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 172K
- 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
- N7437G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Katama Airpark (1B2), Edgartown, MATo not recorded
- Aircraft age
- About 52 years (built 1970)
- 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 · flare/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
- Landing area overshoot
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Prior to landing, the pilot obtained a weather report, which included wind from 190° at 10 knots. The first attempt to land on runway 23 “felt high” and the pilot elected to perform a go-around maneuver. He landed “long” during the subsequent landing and was unable to slow the airplane before it overran the end of the runway. He stated that he was unable to perform a go-around maneuver due to trees at the departure end of the runway. The airplane came to rest against trees, resulting in substantial damage to the left wing and fuselage. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wind reported at an airport about 6 nm east around the time of the accident was 170° at 7 knots gusting to 16 knots.
Probable cause
The pilot’s failure to attain a proper touchdown point, which resulted in a runway overrun in gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA360
- Event ID
- 20220805105672
- Case number
- ERA22LA360
- 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: bb1ea13b70b3b6e98c8a497dfa418bbb75f704a45fd256a764cd52d3f14010a2; retrieved 2026-09-16T15:34:22.275Z.