# Incident 20220818014719I: Beech A36, Huntsville, AL, August 18, 2022

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 18, 2022, 15:55 local time
- Place: Huntsville, AL
- Airport: Huntsville Exec Tom Sharp Jr F
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 34.8594° N, 86.5575° W: Placed by OpenAirDocs at HUNTSVILLE EXEC TOM SHARP JR FLD (MDQ), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=34.8594&lon=-86.5575&mi=10
- Aircraft: N26BR, registered now (https://openairdocs.org/aircraft/N26BR) (OpenAirDocs)
- Registry model: Beech A36 (registry code 1151604, https://openairdocs.org/model/beech-a36) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH A36
- Reported engine: CONT MOTOR IO 520 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 832 total, 694 in this make and model, 26 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20220818014719I

## Narrative

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

PILOT WAS IN THE TRAFFIC PATTERN FOR HUNTSVILLE EXECUTIVE (MDQ).  AS THE AIRCRAFT WAS TURNED ONTO FINAL, THE AIRCRAFT ENGINE LOST POWER AND QUIT.  UNABLE TO MAKE THE RUNWAY, THE PILOT ELECTED TO LAND IN A BEAN FIELD JUST SHORT OF THE RUNWAY THRESHOLD.

## Other reports on N26BR (1)

Matched to the same aircraft by N-number and date.

- [Incident 20050815019689I](https://openairdocs.org/incident/20050815019689I), Aug 15, 2005: Beech A36 (N26BR), Charleston, SC, Minor damage. (-23) Upon landing at jzi on runway 9 the aircraft struck a deer. The aircraft sustained minor damage to the landing gear and doors. The pilot and passenger on…

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.