# NTSB investigations: Cessna 152: Landing area overshoot

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB CEN25LA354](https://openairdocs.org/ntsb/CEN25LA354.md): Cessna 152 · Baldwin City, KS · Accident · No injuries · Class 4 · Limited · Final report · Aug 30, 2025 · N89585 · Substantial damage
  > The pilot’s decision to continue the night landing without runway lights which resulted in the runway overrun.
- [NTSB ERA16CA294](https://openairdocs.org/ntsb/ERA16CA294.md): Cessna 152 · Newnan, GA · Accident · No injuries · Data collection · Final report · Aug 17, 2016 · N5250B · Substantial damage
  > The student pilot's improper decision to land long and maintain excessive speed during the landing roll. Contributing to the accident was the student pilot's decision to maintain full flaps and aft yoke inputs at a higher speed, reducing his ability to stop…
- [NTSB CEN16LA259](https://openairdocs.org/ntsb/CEN16LA259.md): Cessna 152 · Bridgeport, TX · Accident · No injuries · Limited investigation · Final report · Jul 8, 2016 · N5331B · Substantial damage
  > The pilot's unstabilized approach and uneven braking due to insufficient runway remaining, which resulted in a loss of directional control during landing. Contributing to the accident was the bound flap jackscrew, which jammed the flaps and led to the pilot’s…
- [NTSB ERA09LA247](https://openairdocs.org/ntsb/ERA09LA247.md): Cessna 152 · Cross City, FL · Accident · Minor injuries · Limited investigation · Final report · Apr 16, 2009 · N64988 · Substantial damage
  > Loss of engine power for undetermined reasons.
- [NTSB LAX08CA252](https://openairdocs.org/ntsb/LAX08CA252.md): Cessna 152 · Glendale, AZ · Accident · No injuries · Data collection · Final report · Aug 1, 2008 · N757PS · Substantial damage
  > The student pilot's misjudged altitude and distance, and failure to attain the proper touchdown point, that led to a landing overrun.

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2071835')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '380' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb-events/380/sequence?model=2071835

---
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.