# Accident 20021124031879A: Beech A36, Salem, UT, November 24, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 24, 2002, 18:21 local time
- Place: Salem, UT
- Damage: Destroyed
- Operating rules: General operating rules (Part 91)
- Location: 40.0497° N, 111.6247° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.0497&lon=-111.6247&mi=10
- Aircraft: N367T, a cancelled registration (https://openairdocs.org/deregistered/N367T-2003-06-11) (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
- People aboard: 2
- Fatal injuries: 2
- NTSB investigation: [NTSB FTW03FA048](https://openairdocs.org/ntsb/FTW03FA048) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20021124031879A

## Narrative

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

(-23) ON VFR FLIGHT FROM ST. GEORGE, UTAH (SGU) TO SPANISH FORK, UTAH (U77), AIRCRAFT CRASHED AND BURNED IN THE FOOTHILLS EAST OF SALEM, UTAH. BOTH THE PILOT AND SINGLE PASSENGER RECEIVED FATAL INJURIES. A WITNESS REPORTED SEEING THE AIRCRAFT FLYING LOW OVERHEAD IN HEAVY SNOW, HEARING IT HIT THE MOUNTAINSIDE AND SEEING THE FIREBALL.

## 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 FTW03FA048](https://openairdocs.org/ntsb/FTW03FA048), Nov 25, 2002: Beech A36 (N367T), Salem, UT, destroyed, 2 fatal. Probable cause: The pilot's inadequate inflight planning/decision to continue flight from visual to instrument meteorological conditions, which resulted in his failure to maintain clearance from terrain while in…

## Other reports on N367T (2)

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

- [Accident 20000316008569A](https://openairdocs.org/incident/20000316008569A), Mar 16, 2000: Beech A36 (N367T), Provo, UT, No damage. (-23) No narrative
- [Incident 19990825025989I](https://openairdocs.org/incident/19990825025989I), Aug 25, 1999: Beech A36 (N367T), Glen Canyon Nat, UT, Minor damage. (-23) The pilot stated he made a low approach to Bullfrog airport to check out the conditions at the airfield. He stated he made a go around and raised the…

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.