# NTSB investigations: Piper PA-28RT-201: Loss of engine power(total) - nonmechanical

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 SEA97LA052](https://openairdocs.org/ntsb/SEA97LA052.md): Piper PA-28RT-201 · Chehalis, WA · Accident · Serious injuries · Limited investigation · Final report · Jan 26, 1997 · N344LC · Destroyed
  > The failure of the first pilot to conduct an adequate preflight inspection, and his failure to properly manage the aircraft fuel supply. This led to fuel starvation and a subsequent loss of engine power. Factors contributing to the accident are the false…
- [NTSB FTW94LA276](https://openairdocs.org/ntsb/FTW94LA276.md): Piper PA-28R-201 · Tulsa, OK · Accident · Minor injuries · Limited investigation · Final report · Aug 23, 1994 · N94AA · Substantial damage
  > Loss of engine power following fuel starvation caused by improper tank selection by the pilot. A factor was the lack of suitable terrain for the forced landing.
- [NTSB NYC87LA001](https://openairdocs.org/ntsb/NYC87LA001.md): Piper PA-28RT-201 · Caldwell, NJ · Accident · No injuries · Limited investigation · Final report · Oct 1, 1986 · N8320A · Substantial damage
  > The pilot in command allowed the aircraft to become too low during a night simulated emergency (engine out) during an instructional flight. The aircraft contacted the tops of trees, became uncontrollable and crashed to the ground.
- [NTSB LAX82FYM18](https://openairdocs.org/ntsb/LAX82FYM18.md): Piper PA-28RT-201 · San Carlos, CA · Accident · No injuries · Final report · Jul 31, 1982 · N2090W · Substantial damage
  > After landing at the airport, the pilot taxied to the transient parking area, parked and got a cup of coffee. He stated that he then made a quick preflight check, but did not visually inspect the fuel tanks. During the takeoff, the engine began to surge at…

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

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

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