# NTSB investigations: Cessna 172L: Overrun

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 CHI06CA182](https://openairdocs.org/ntsb/CHI06CA182.md): Cessna 172L · Waterford, OH · Accident · No injuries · Data collection · Final report · Jul 8, 2006 · N7805G · Substantial damage
  > The pilot's selection of unsuitable terrain for landing. The runway's downhill slope, the wet grass, the fence, and the embankment were factors.
- [NTSB ATL06CA084](https://openairdocs.org/ntsb/ATL06CA084.md): Cessna 172L · Lexington, TN · Accident · No injuries · Data collection · Final report · May 23, 2006 · N7624G · Substantial damage
  > The pilot's failure to attain the proper touchdown point during landing.
- [NTSB ATL06CA046](https://openairdocs.org/ntsb/ATL06CA046.md): Cessna 172L · Long Island, NC · Accident · No injuries · Data collection · Final report · Feb 23, 2006 · N3803Q · Substantial damage
  > The student pilot's failure to achieve the proper touch down point on landing resulting in an overrun, on-ground collision with a ditch, and subsequent nose over. A factor in the accident was the inadequate supervision of the student pilot by the flight…
- [NTSB FTW03LA175](https://openairdocs.org/ntsb/FTW03LA175.md): Cessna 172L · San Antonio, TX · Accident · Serious injuries · Limited investigation · Final report · Jun 22, 2003 · N912KD · Substantial damage
  > The pilot misjudged his altitude and airspeed, and his failure to perform a go-around.
- [NTSB CHI99LA237](https://openairdocs.org/ntsb/CHI99LA237.md): Cessna 172L · Montezuma, IA · Accident · No injuries · Limited investigation · Final report · Jul 14, 1999 · N19752 · Substantial damage
  > the pilot inadvertently landed on the wrong runway and exceeded the proper touchdown point on the runway. Factors associated with the accident were the gusty tailwind, the fence, and the ditch.
- [NTSB LAX99LA082](https://openairdocs.org/ntsb/LAX99LA082.md): Cessna 172L · Santa Paula, CA · Accident · No injuries · Limited investigation · Final report · Jan 26, 1999 · N7639G · Substantial damage
  > The instructor pilot's misjudged altitude and speed, which resulted in a failure to attain the proper touchdown point causing an overrun and collision with a block wall. A factor was the wet runway, which may have hindered brake effectiveness.
- [NTSB SEA94LA102](https://openairdocs.org/ntsb/SEA94LA102.md): Cessna 172L · Colville, WA · Accident · No injuries · Limited investigation · Final report · Apr 16, 1994 · N3854Q · Substantial damage
  > The pilot's failure to attain a proper touchdown point, and his excessive airspeed at the point of touchdown. Factors include the student pilot's lack of recent experience, and a ravine off the end of the runway.
- [NTSB CHI90FA196](https://openairdocs.org/ntsb/CHI90FA196.md): Cessna 172 · Canton, MI · Accident · No injuries · Field investigation · Final report · Jul 25, 1990 · N4330Q · Substantial damage
  > The pilot's inadequate takeoff procedure, premature liftoff and delayed reaction to abort the takeoff.
- [NTSB SEA86LA006](https://openairdocs.org/ntsb/SEA86LA006.md): Cessna 172 · Emmett, ID · Accident · Minor injuries · Limited investigation · Final report · Oct 5, 1985 · N2867Q · Substantial damage
  > While landing in calm wind conditions on a 2400 ft rwy, the left brake failed & the acft contd off the departure end, then hit a fence. An exam revealed the left brake pads were worn & the left actuator cylinder was losing fluid. The brake backing plate & the…
- [NTSB NYC84LA140](https://openairdocs.org/ntsb/NYC84LA140.md): Cessna 172L · Mayville, NY · Accident · Minor injuries · Limited investigation · Final report · Apr 15, 1984 · N3977Q · Substantial damage
  > On an apch to land, after a go-around, the acft crossed over wires & touched down on the 1st half of the rwy. The plt applied brakes on the wet grass rwy, but noted a lack of braking action. He applied power to go around, but decided the acft would not clear…

## 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 ('2072432')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?model=2072432&occurrence=340

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