# Accident 20050824019839A: Maule BEEDEEM4, Ritter, OR, August 24, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 24, 2005, 15:08 local time
- Place: Ritter, OR
- Damage: Destroyed
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 44.9439° N, 119.3386° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.9439&lon=-119.3386&mi=10
- Aircraft: N11WG, a cancelled registration (https://openairdocs.org/deregistered/N11WG-2014-08-28) (OpenAirDocs)
- Registry model: Maule BEE DEE M-4 (registry code 5460102, https://openairdocs.org/model/maule-bee-dee-m-4) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: MAULE BEEDEEM4
- Reported engine: CONT O300*
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 1,730 total, 25 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB SEA05FA180](https://openairdocs.org/ntsb/SEA05FA180) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050824019839A

## Narrative

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

(-23) DURING VMC FLIGHT FROM ONTARIO, OREGON TO KELSO, WASHINGTON THE AIRCRAFT CRASHED IN A REMOTE AREA BY RITTER, OREGON. AIRCRAFT DAMAGE:DESTROYED. AIRCRAFT BURNED IN POST CRASH FIRE. BODY BURNED BEYOND RECOGNITION.

## 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 SEA05FA180](https://openairdocs.org/ntsb/SEA05FA180), Aug 24, 2005: Maule Bee Dee M-4 (N11WG), Ritter, OR, destroyed, 1 fatal. Probable cause: The loss of control for an undetermined reason which resulted in a ground collision.

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.