# Accident 20011110031039A: Esbenshade J M STARDUSTER TOO SA300, Greeley, CO, November 10, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 10, 2001, 12:00 local time
- Place: Greeley, CO
- Airport: Greeley-Weld County Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.3558° N, 104.7578° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.3558&lon=-104.7578&mi=10
- Aircraft: N6925, a cancelled registration (https://openairdocs.org/deregistered/N6925-2002-05-06) (OpenAirDocs)
- Registry model: Esbenshade J M STARDUSTER TOO SA300 (registry code 8660391, https://openairdocs.org/model/esbenshade-j-m-starduster-too-sa300) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- NTSB investigation: [NTSB DEN02LA009](https://openairdocs.org/ntsb/DEN02LA009) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20011110031039A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE PILOT DESCENDED FROM ALTITUDE AND STARTED A SCENIC FLIGHT OVER THE PLATTE RIVER. HE HIT SOME UNMARKED WIRES OVER THE PLATTE RIVER. HE LANDED ON THE RIVER BANK, IMPACTING TREES.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DEN02LA009](https://openairdocs.org/ntsb/DEN02LA009), Nov 10, 2001: Esbenshade Starduster Too SA300 (N6925), Evans, CO, destroyed. Probable cause: the pilot's failure to maintain clearance of the wires. A contributing factor was the trees the airplane struck while the pilot was attempting to regain aircraft control.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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