# Accident 20031024029199A: Amtr ROTORWAYEXEC, Cushing, MN, October 24, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 24, 2003, 18:54 local time
- Place: Cushing, MN
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 46.1397° N, 94.5770° W: Placed by OpenAirDocs: center of Cushing, MN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=46.1397&lon=-94.5770&mi=10
- Aircraft: N422DS, a cancelled registration (https://openairdocs.org/deregistered/N422DS-2004-10-15) (OpenAirDocs)
- Registry model: Shapowal David ROTORWAY EXEC 90 (registry code 13017PY, https://openairdocs.org/model/shapowal-david-rotorway-exec-90) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMTR ROTORWAYEXEC
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031024029199A

## Narrative

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

(-23) ON 10/24/2003, AT APPROXIMATELY 1830 HOUR LOCAL TIME, N422DS, AN EXPERIMENTAL, AMATEUR-BUILT ROTORWAY EXEC 90 HELICOPTER, DEPARTED PRIVATE PROPERTY NEAR PILLAGER, MN FOR A PERSONAL, RELOCATION FLIGHT TO THE PROPERTY OF THE NEW OWNER/OPERATOR (WILLIAM BRUMMUND) NEAR CUSHING, MN. THE VFR FLIGHT BEGAN JUST AFTER SUNDOWN. WHILE TRYING TO LOCATE HIS PROPERTY THE PILOT BECAME DISORIENTED/LOST DUE TO DARKNESS. AT 1854 HOURS LOCAL TIME, HE ATTEMPTED TO LAND NEAR THE PARKING LOT OF A LIGHTED RESTAURANT, ON AZURE ROAD, 3 TO 5 MILES NORTH OF CUSHING, MN. DURING THE APPROACH, THE HELICOPTER STRUCK TWO POWER LINES AND CRASHED 30 TO 40 FEET NORTH OF THOSE POWER LINES. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED, AND THE PRIVATE PILOT, THE SOLE OCCUPANT, RECEIVED MINOR INJURIES. NO FLIGHT PLAN HAD BEEN FILED.

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

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.