# NTSB investigations: Air Tractor AT-301: Fuel exhaustion

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 GAA18CA371](https://openairdocs.org/ntsb/GAA18CA371.md): Air Tractor AT 301 · Hutchinson, MN · Accident · No injuries · Data collection · Final report · Jun 20, 2018 · N3169D · Substantial damage
  > The pilot’s improper preflight fuel planning, which resulted in fuel exhaustion and the subsequent total loss of engine power.
- [NTSB CEN12CA274](https://openairdocs.org/ntsb/CEN12CA274.md): Air Tractor AT-301 · Cedar Bluffs, NE · Accident · No injuries · Data collection · Final report · May 3, 2012 · N3166W · Substantial damage
  > The pilot's improper fuel management, which resulted in a loss of engine power due to fuel exhaustion.
- [NTSB WPR10CA332](https://openairdocs.org/ntsb/WPR10CA332.md): Air Tractor AT-301 · Garfield, WA · Accident · No injuries · Data collection · Final report · Jul 6, 2010 · N8878S · Substantial damage
  > A loss of engine power due to fuel exhaustion.
- [NTSB WPR09LA374](https://openairdocs.org/ntsb/WPR09LA374.md): Air Tractor AT-301 · Firebaugh, CA · Accident · No injuries · Limited investigation · Final report · Jul 29, 2009 · N23189 · Substantial damage
  > A total loss of engine power due to fuel exhaustion that was due to the failure of company ground personnel to refuel the airplane. Contributing to the accident was unsuitable terrain for a forced landing.
- [NTSB CHI08CA251](https://openairdocs.org/ntsb/CHI08CA251.md): Air Tractor AT-301B · Monticello, IA · Accident · Minor injuries · Data collection · Final report · Aug 13, 2008 · N3161D · Substantial damage
  > Poor preflight planning in that the pilot failed to assure an adequate fuel supply was on board for the flight which resulted in fuel exhaustion. Factors associated with the accident were the low altitude of the airplane when the loss of power occurred and…

## 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 ('0390103', '0390105')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '192' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb-events/192/sequence?model=0390103

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