# NTSB investigations: Cessna R172E: Hard landing

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 LAX07CA162](https://openairdocs.org/ntsb/LAX07CA162.md): Cessna R172E · Dayton, NV · Accident · No injuries · Data collection · Final report · May 12, 2007 · N9274Z · Substantial damage
  > The pilot's misjudged flare, which resulted in a hard landing.
- [NTSB NYC05CA132](https://openairdocs.org/ntsb/NYC05CA132.md): Cessna R172E · Patuxent River, MD · Accident · No injuries · Data collection · Final report · Aug 10, 2005 · N7880N · Substantial damage
  > The pilot's improper recovery from a bounced landing, resulting in a hard landing.
- [NTSB SEA89LA142](https://openairdocs.org/ntsb/SEA89LA142.md): Cessna 172E · Yerington, NV · Accident · No injuries · Limited investigation · Final report · Jul 30, 1989 · N14454 · Substantial damage
  > The pilot's failure to maintain adequate airspeed during a landing go-around in high density altitude conditions.
- [NTSB ATL89LA170](https://openairdocs.org/ntsb/ATL89LA170.md): Cessna R172E · Birmingham, AL · Accident · No injuries · Limited investigation · Final report · Jun 16, 1989 · N48257 · Substantial damage
  > Improper flare by the pilot, which resulted in a hard landing. The fact that the pilot was asked twice to expedite the landing created pressure on the pilot and was considered to be a factor.
- [NTSB LAX84LA347](https://openairdocs.org/ntsb/LAX84LA347.md): Cessna R172E · Payson, AZ · Accident · No injuries · Limited investigation · Final report · Jun 10, 1984 · N42FG · Substantial damage
  > The purpose of the flight was to give the pvt plt a recurrency checkride as required by the civil air patrol. The commercial rated check plt is not a CFI. According to the check plt the pvt plt was attempting a touch and go landing. The pvt plt flared too…

## 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 ('2072413')
    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" = 200))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

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

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