# Accident 20030705020659A: Beech F35, Middlesboro, KY, July 5, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 5, 2003, 14:47 local time
- Place: Middlesboro, KY
- Airport: Middlesboro-Bell County Airport
- Damage: Destroyed
- Phase of flight: Descent
- Operating rules: General operating rules (Part 91)
- Location: 36.6258° N, 83.6794° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.6258&lon=-83.6794&mi=10
- Aircraft: N205, a cancelled registration (https://openairdocs.org/deregistered/N205-2018-01-16) (OpenAirDocs)
- Registry model: Beech F35 (registry code 1151514, https://openairdocs.org/model/beech-f35) (OpenAirDocs)
- Registry engine: Continental E225 series (registry code 17015, https://openairdocs.org/engine/continental-e225-series) (OpenAirDocs)
- Reported make and model: BEECH F35
- Reported engine: CONT E2258
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 1,974 total, 600 in this make and model
- NTSB investigation: [NTSB NYC03FA148](https://openairdocs.org/ntsb/NYC03FA148) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030705020659A

## Narrative

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

(-23) AIRCRAFT DEPARTED TYS ENROUTE TO 1A6. RADAR SERVICE TERMINATED 30NM NORTH OF TYS. AIRCRAFT CRASHED 2 MILES EAST OF 1A6. PILOT AND 1 PASSENGER FATALLY INJURED.

## 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 NYC03FA148](https://openairdocs.org/ntsb/NYC03FA148), Jul 5, 2003: Beech F-35 (N205), Middlesboro, KY, destroyed, 2 fatal. Probable cause: The pilot's improper decision to descend into clouds, and his exceeding the maximum speed and design stress limits of the airplane, which resulted in an in-flight breakup and subsequent 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.