# NTSB investigations: Lycoming I0360 series, OR: 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 SEA02FA185](https://openairdocs.org/ntsb/SEA02FA185.md): Cessna 172S · Medford, OR · Accident · 2 fatal · Field investigation · Final report · Sep 30, 2002 · N514SP · Substantial damage
  > Terrain clearance was not maintained during cruise flight. Dark night and mountainous terrain were factors.
- [NTSB SEA00FA038](https://openairdocs.org/ntsb/SEA00FA038.md): Hughes 269C · Sherwood, OR · Accident · No injuries · Field investigation · Final report · Jan 18, 2000 · N9297F · Substantial damage
  > The pilots failure to arrest the helicopter's descent rate during a planned approach to a hover. Factors include uneven terrain.
- [NTSB SEA93LA001](https://openairdocs.org/ntsb/SEA93LA001.md): Hughes 269C · Hillsboro, OR · Accident · No injuries · Limited investigation · Final report · Oct 1, 1992 · N7400F · Substantial damage
  > The pilot in command's failure to maintain proper altitude during the hover. Factors contributing to the accident were the pilot in command's lack of total experience in rotorcraft and his diversion of attention while hovering.
- [NTSB SEA91LA137](https://openairdocs.org/ntsb/SEA91LA137.md): Hughes 269B · Warrenton, OR · Accident · Minor injuries · Limited investigation · Final report · Jun 19, 1991 · N9380F · Substantial damage
  > The pilot failed to maintain proper rotor speed during a simulated autorotation.
- [NTSB SEA82DA121](https://openairdocs.org/ntsb/SEA82DA121.md): Lake LA-4 · Newport, OR · Accident · No injuries · Final report · Jul 16, 1982 · N1216L · Substantial damage
  > The pilot reported that during takeoff, he had accelerated to about 40 mph, and was on the step, when he hit a wave of sufficient size to bounce and become momentarily airborne. He was still accelerating and bounced a second time when it became apparent that…

## 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" = 'OR' AND c."eventCountry" = 'USA'
  AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41515')
    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?engine=41515&occurrence=230&state=OR

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