# NTSB investigations: Cessna 172S: In flight collision with object

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 MIA07CA045](https://openairdocs.org/ntsb/MIA07CA045.md): Cessna 172S · Sanford, FL · Accident · No injuries · Data collection · Final report · Jan 27, 2007 · N20956 · Substantial damage
  > The inadvertent inflight collision with a bird resulting in damage to the airplane and the pilot having limited control capability.
- [NTSB DFW05CA253](https://openairdocs.org/ntsb/DFW05CA253.md): Cessna 172S · Batesville, TX · Accident · No injuries · Data collection · Final report · Sep 29, 2005 · N5343U · Substantial damage
  > The pilot's failure to maintain clearance from the tree. A contributing factor was the gusty winds.
- [NTSB LAX04CA309](https://openairdocs.org/ntsb/LAX04CA309.md): Cessna 172S · Willits, CA · Accident · Minor injuries · Data collection · Final report · Sep 2, 2004 · N897TW · Destroyed
  > the pilot's inadvertent descent and controlled flight into obstacles while maneuvering to land. Contributing factors were the dark, nighttime condition, which impaired the pilot's visual perceptions, and the pilot's failure to obtain a pertinent Notice to…
- [NTSB ATL04LA140](https://openairdocs.org/ntsb/ATL04LA140.md): Cessna 172S · Asheville, NC · Accident · Serious injuries · Limited investigation · Final report · Jun 25, 2004 · N2116P · Substantial damage
  > The CFII's inadequate visual lookout and failure to maintain clear of objects during flight. Factors were clouds and dark night.
- [NTSB FTW03FA182](https://openairdocs.org/ntsb/FTW03FA182.md): Cessna 172S · McKinney, TX · Accident · 2 fatal · Field investigation · Final report · Jul 8, 2003 · N166ME · Destroyed
  > The CFI's failure to maintain airspeed sufficient for flight resulting in an inadvertent stall/spin during the forced landing. A contributing factor was the impact with a bird, which affected the performance of the airplane.
- [NTSB CHI03FA149](https://openairdocs.org/ntsb/CHI03FA149.md): Cessna 172S · Sidnaw, MI · Accident · 1 fatal · Field investigation · Final report · Jun 6, 2003 · N975SP · Destroyed
  > The improper short/soft field landing procedure by the pilot and his lack of recent experience in type of operation. Contributing factors were the short/soft field runway, the trees and his delay in aborting the takeoff.
- [NTSB MIA02FA104](https://openairdocs.org/ntsb/MIA02FA104.md): Cessna 172S · Lutz, FL · Accident · 1 fatal · Field investigation · Final report · Jun 4, 2002 · N942SP · Destroyed
  > The suicidal act by the pilot resulting in the in-flight collision with trees then the ground. A contributing factor in the accident was the pilot's depression. Findings in the investigation were the pilot's overdose of zolpidem and citalopram before the…
- [NTSB NYC01FA217](https://openairdocs.org/ntsb/NYC01FA217.md): Cessna 172SP · Matawan, NJ · Accident · 2 fatal · Field investigation · Final report · Aug 27, 2001 · N629PD · Substantial damage
  > The pilot's failure to maintain runway alignment during the initial climb. Factors were the pilot's failure to perform a go-around, the pilot's lack of flight experience in nighttime conditions, the nighttime conditions, and a tailwind.
- [NTSB SEA01LA077](https://openairdocs.org/ntsb/SEA01LA077.md): Cessna 172S · Renton, WA · Accident · No injuries · Limited investigation · Final report · Apr 24, 2001 · N435SP · Substantial damage
  > A Canadian goose which crossed the aircraft's flight path and impacted the left wing during the aircraft's final approach.
- [NTSB ATL01LA023](https://openairdocs.org/ntsb/ATL01LA023.md): Cessna 172SP · Austell, GA · Accident · Serious injuries · Limited investigation · Final report · Jan 19, 2001 · N43PD · Destroyed
  > The pilots failure to follow instrument flight procedures and descended below the published the minimum descent altitude and subsequently collided with trees short of the runway.

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

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

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