# NTSB investigations: Cessna 172S, CT

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 GAA18CA345](https://openairdocs.org/ntsb/GAA18CA345.md): Cessna 172 · Danbury, CT · Accident · No injuries · Data collection · Final report · Jun 9, 2018 · N383ME · Substantial damage
  > A collision with a bird during initial climb.
- [NTSB ERA17LA261](https://openairdocs.org/ntsb/ERA17LA261.md): Cessna 172 · Danbury, CT · Accident · 1 fatal · Limited investigation · Final report · Jul 30, 2017 · N612DF · Substantial damage
  > The pilot's exceedance of the airplane's critical angle of attack during initial climb, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's decision to operate the airplane above its maximum gross weight, which likely reduced…
- [NTSB ERA10CA278](https://openairdocs.org/ntsb/ERA10CA278.md): Cessna 172S · East Haddam, CT · Accident · No injuries · Data collection · Final report · May 24, 2010 · N169ER · Substantial damage
  > The pilot's delayed decision to attempt a go-around, and his subsequent failure to maintain directional control while landing.
- [NTSB ERA09LA064](https://openairdocs.org/ntsb/ERA09LA064.md): Cessna 172S · Groton, CT · Accident · Minor injuries · Limited investigation · Final report · Nov 19, 2008 · N2337F · Substantial damage
  > The student pilot’s failure to maintain a proper descent profile to avoid trees during the night visual approach and the flight instructor’s inadequate oversight.
- [NTSB IAD02FA086](https://openairdocs.org/ntsb/IAD02FA086.md): Cessna 172S · Plainville, CT · Accident · 2 fatal · Field investigation · Final report · Aug 17, 2002 · N35073 · Destroyed
  > An in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent…

## 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."eventStateOrRegion" = 'CT' AND c."eventCountry" = 'USA'
  AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072439', '2072442'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?model=2072439&state=CT

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