# Landing area overshoot

- Type: NTSB defining event
- NTSB code: 380
- CICTT category: Undershoot/Overshoot
- Defining event in: 233 cases
- In the sequence of: 400 cases
- Fatal cases: 6
- All cases: https://openairdocs.org/ntsb-events/380/cases.md
- Cases with it anywhere in the sequence: https://openairdocs.org/ntsb-events/380/sequence.md
- Page: https://openairdocs.org/ntsb-events/380

## Cases per year (defining / in the sequence)

- 2008: 18 / 35
- 2009: 12 / 26
- 2010: 24 / 38
- 2011: 20 / 30
- 2012: 18 / 24
- 2013: 10 / 17
- 2014: 13 / 19
- 2015: 10 / 20
- 2016: 10 / 28
- 2017: 10 / 14
- 2018: 7 / 14
- 2019: 3 / 13
- 2020: 8 / 11
- 2021: 11 / 21
- 2022: 13 / 16
- 2023: 7 / 8
- 2024: 15 / 25
- 2025: 16 / 25
- 2026: 8 / 16

## Phase of flight

- Landing: 101 cases
- Landing-flare/touchdown: 63 cases
- Landing-landing roll: 62 cases
- Emergency descent: 4 cases
- Landing-aborted after touchdown: 2 cases
- Autorotation: 1 cases

## In the probable cause of these cases

- [Descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040) (Aircraft): 106 cases
- [Aircraft control](https://openairdocs.org/ntsb-findings/02063040) (Personnel issues): 72 cases
- [Decision making/judgment](https://openairdocs.org/ntsb-findings/02041520) (Personnel issues): 68 cases
- [Airspeed](https://openairdocs.org/ntsb-findings/01062010) (Aircraft): 42 cases
- [Incorrect action performance](https://openairdocs.org/ntsb-findings/02041015) (Personnel issues): 29 cases
- [Identification/recognition](https://openairdocs.org/ntsb-findings/02041510) (Personnel issues): 17 cases
- [Landing distance](https://openairdocs.org/ntsb-findings/01061030) (Aircraft): 17 cases
- [Delayed action](https://openairdocs.org/ntsb-findings/02041025) (Personnel issues): 16 cases
- [Tailwind](https://openairdocs.org/ntsb-findings/03034015) (Environmental issues): 13 cases
- [Lack of action](https://openairdocs.org/ntsb-findings/02041030) (Personnel issues): 13 cases

## Aircraft models (registry)

- [Piper PA-28-140](https://openairdocs.org/model/piper-pa-28-140): 5 cases
- [Cessna 182P](https://openairdocs.org/model/cessna-182p): 5 cases
- [Cessna 172N](https://openairdocs.org/model/cessna-172n): 5 cases
- [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161): 4 cases
- [Cessna 172S](https://openairdocs.org/model/cessna-172s): 4 cases
- [Cessna 172M](https://openairdocs.org/model/cessna-172m): 4 cases
- [Piper PA-18-150](https://openairdocs.org/model/piper-pa-18-150): 3 cases
- [Cessna 182Q](https://openairdocs.org/model/cessna-182q): 3 cases
- [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300): 2 cases
- [Piper PA-25-235](https://openairdocs.org/model/piper-pa-25-235): 2 cases

## Newest cases

- [NTSB CEN26LA328](https://openairdocs.org/ntsb/CEN26LA328), Sep 26, 2026: Maule M-5-210C (N367X), Ozark, AR, substantial damage, investigation ongoing
- [NTSB ANC26LA081](https://openairdocs.org/ntsb/ANC26LA081), Aug 9, 2026: Cessna A185F (N7336H), Hope, AK, substantial damage, investigation ongoing
- [NTSB ERA26LA263](https://openairdocs.org/ntsb/ERA26LA263), Jul 5, 2026: Ryan Navion A (N5205K), Newport, NH, substantial damage. Probable cause: The pilot’s failure to attain an appropriate touchdown point, which resulted in a runway overrun.
- [NTSB ERA26LA246](https://openairdocs.org/ntsb/ERA26LA246), Jun 15, 2026: Cessna 402 (N499CA), Provincetown, MA, substantial damage, investigation ongoing
- [NTSB WPR26FA151](https://openairdocs.org/ntsb/WPR26FA151), Apr 9, 2026: Piper PA-32R-301T (N4190E), Marana, AZ, substantial damage, 2 fatal, investigation ongoing
- [NTSB WPR26LA087](https://openairdocs.org/ntsb/WPR26LA087), Jan 19, 2026: Kitfox Series 7 (N775DZ), Lemmon Valley-Golden Valley, NV, substantial damage. Probable cause: The pilot’s inability to maintain clearance from terrain during a go-around.
- [NTSB DCA26WA160](https://openairdocs.org/ntsb/DCA26WA160), Jan 15, 2026: ATR ATR42 (P2-KSA), Simberi, Papua New Guinea, substantial damage
- [NTSB ERA26LA088](https://openairdocs.org/ntsb/ERA26LA088), Jan 8, 2026: Cirrus Design SR22 (N29UA), Philippi, WV, substantial damage. Probable cause: The pilot’s failure to obtain the proper touchdown point, which resulted in a runway overrun.
- [NTSB GAA26WA081](https://openairdocs.org/ntsb/GAA26WA081), Dec 12, 2025: Gulfstream G-VSP (VH-PFL), Bibi, Japan, minor damage
- [NTSB ERA26LA059](https://openairdocs.org/ntsb/ERA26LA059), Nov 30, 2025: Columbia Aircraft Mfg LC41-550FG (N1294P), Chatham, MA, substantial damage. Probable cause: The pilot’s failure to attain a proper touchdown point while landing with a quartering tailwind, which resulted in a long landing and subsequent runway excursion.

NTSB has coded findings and defining events since 2008; earlier cases used its older occurrence and cause codes and aren't counted.

Findings: https://openairdocs.org/ntsb-findings.md. Defining events: https://openairdocs.org/ntsb-events.md. Phases of flight: https://openairdocs.org/ntsb-phases.md. Every investigation, filtered by finding, event, phase, state, year or model: https://openairdocs.org/ntsb.md (for example ?state=MI&fatal=1).

NTSB's definitions: Accident and incident, 49 CFR 830.2 (https://www.ecfr.gov/current/title-49/subtitle-B/chapter-VIII/part-830/subpart-A/section-830.2), CICTT occurrence categories (PDF) (https://www.ntsb.gov/safety/data/Documents/datafiles/OccurrenceCategoryDefinitions.pdf), CICTT phases of flight (PDF) (https://www.ntsb.gov/safety/data/Documents/datafiles/PhaseofFlightDefinitions.pdf), and NTSB coding manual, before 2008 (PDF) (https://www.ntsb.gov/GILS/Documents/codman.pdf). NTSB publishes no definitions for its findings, only their names.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.