# NTSB investigations: Cessna 172B: Collision with terr/obj (non-CFIT)

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 GAA17CA175](https://openairdocs.org/ntsb/GAA17CA175.md): Cessna 172 · Greenville, ME · Accident · No injuries · Data collection · Final report · Mar 2, 2017 · N7450X · Substantial damage
  > The pilot's failure to maintain directional control while taxiing in gusting crosswind conditions.
- [NTSB CEN17LA090](https://openairdocs.org/ntsb/CEN17LA090.md): Cessna 172B · Prairie Du Sac, WI · Accident · No injuries · Limited investigation · Final report · Dec 28, 2016 · N6941X · Substantial damage
  > The pilot's decision to taxi the airplane from the roadway and his subsequent failure to maintain clearance from signs and a fence after a successful emergency landing following a total loss of engine power.
- [NTSB GAA16LA001](https://openairdocs.org/ntsb/GAA16LA001.md): Cessna 172B · Redding, CA · Accident · Serious injuries · Limited investigation · Final report · Oct 3, 2015 · N7837X · Substantial damage
  > The pilot’s improper decision to land the airplane on a short runway with a tailwind and his subsequent delayed decision to abort the landing.
- [NTSB ERA14CA291](https://openairdocs.org/ntsb/ERA14CA291.md): Cessna 172B · Frankfort, KY · Accident · No injuries · Data collection · Final report · Jun 13, 2014 · N7540X · Substantial damage
  > The pilot's failure to maintain directional control during landing in crosswind conditions, resulting in a loss of control and runway excursion.
- [NTSB CEN11LA522](https://openairdocs.org/ntsb/CEN11LA522.md): Cessna 172B · Middleton, WI · Accident · No injuries · Limited investigation · Final report · Jul 23, 2011 · N7624X · Substantial damage
  > The total loss of engine power during climb after takeoff for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

## 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 ('2072406')
    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" = '470' 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/470/sequence?model=2072406

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