# NTSB investigations: Cessna 182L: 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 CHI01LA121](https://openairdocs.org/ntsb/CHI01LA121.md): Cessna 182L · Stromsburg, NE · Accident · No injuries · Limited investigation · Final report · Apr 20, 2001 · N6412K · Substantial damage
  > the inadequate in-flight planning/decision and the flight to a destination alternate not performed by the pilot. Contributing factors were the crosswind and gusts.
- [NTSB ATL95FA003](https://openairdocs.org/ntsb/ATL95FA003.md): Cessna 182L · Ft. Mcclellan, AL · Accident · 2 fatal · Field investigation · Final report · Oct 3, 1994 · N3499R · Destroyed
  > The pilot's continued VFR flight into IMC conditions, and his failure to maintain a proper altitude over mountainous terrain. Factors were the low ceiling, fog, and drizzle weather conditions, and the mountainous terrain at the accident site.
- [NTSB DEN90LA024](https://openairdocs.org/ntsb/DEN90LA024.md): Cessna 182L · Dove Creek, CO · Accident · Serious injuries · Limited investigation · Final report · Nov 22, 1989 · N42699 · Substantial damage
  > Improper flare by the student pilot, his failure to maintain runway alignment, and a delay by the flight instructor (CFI) in initiating remedial action, which resulted in a loss of airspeed and a stall/mush after the aircraft drifted over a cultivated field…
- [NTSB NYC86FA057](https://openairdocs.org/ntsb/NYC86FA057.md): Cessna 182L · So.Glastonbury, CT · Accident · 2 fatal · Field investigation · Final report · Jan 3, 1986 · N3349R · Destroyed
  > The acft was on a VOR instrument apch when it collided with 250 ft high terrain approx 6 miles south of the arpt and approx 2 miles north of the vor/faf. Shortly before the accident the pilot notified ATC that he was in turbulence; then reported he was clear…

## 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 ('2072726')
    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=2072726&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.