# NTSB investigations: Cessna 172R: In flight collision with terrain/water

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 DEN07CA154](https://openairdocs.org/ntsb/DEN07CA154.md): Cessna 172R · Fort Collins, CO · Accident · No injuries · Data collection · Final report · Aug 13, 2007 · N249FS · Substantial damage
  > The student pilot's improper flare and recovery from a bounced landing.
- [NTSB NYC05FA075](https://openairdocs.org/ntsb/NYC05FA075.md): Cessna 172R · Armonk, NY · Accident · 2 fatal · Field investigation · Final report · Apr 23, 2005 · N61AF · Destroyed
  > The flight instructor's failure to maintain the proper altitude\clearance during the approach, which resulted in an in-flight collision with trees. Factors in this accident were low ceilings, fog, and gusty wind conditions.
- [NTSB DEN04LA017](https://openairdocs.org/ntsb/DEN04LA017.md): Cessna 172R · Cloudcroft, NM · Accident · Serious injuries · Limited investigation · Final report · Nov 1, 2003 · N9864F · Destroyed
  > the dual student's failure to maintain clearance from the terrain. Also causal was the flight instructor's inadequate supervision. Low altitude flight and rising terrain are contributing factors.
- [NTSB ATL03FA070](https://openairdocs.org/ntsb/ATL03FA070.md): Cessna 172R · Cherokee, NC · Accident · 1 fatal · Field investigation · Final report · Mar 28, 2003 · N35255 · Destroyed
  > The pilot's failure to maintain adequate terrain clearance, which resulted in an in-flight collision with mountainous terrain.
- [NTSB DEN00FA009](https://openairdocs.org/ntsb/DEN00FA009.md): Cessna 172R · Aspen, CO · Accident · 1 fatal · Field investigation · Final report · Oct 23, 1999 · N9548A · Substantial damage
  > the pilot's improper decision to fly directly up the center of the valley and not circle climb to gain sufficient terrain clearance altitude. A factor was inadequate route performance planning by the pilot.

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

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

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