# Incident 20020715019579I: Luscom 8C, Bristol-Johnson, TN, July 15, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 15, 2002, 18:00 local time
- Place: Bristol-Johnson, TN
- Airport: Tri-City Regional Airport
- Damage: Minor damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 36.5951° N, 82.1887° W: Placed by OpenAirDocs: center of Bristol, TN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.5951&lon=-82.1887&mi=10
- Aircraft: N25270, a cancelled registration (https://openairdocs.org/deregistered/N25270-2026-02-14) (OpenAirDocs)
- Registry model: Luscombe 8C (registry code 8190108, https://openairdocs.org/model/luscombe-8c) (OpenAirDocs)
- Registry engine: Continental A&C75 series (registry code 17005, https://openairdocs.org/engine/continental-a-c75-series) (OpenAirDocs)
- Reported make and model: LUSCOM 8C
- Reported engine: CONT C75*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 10,000 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020715019579I

## Narrative

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

(-23) LOST POWER ON SHORT FINAL TO RUNWAY 23 AT TRI-CITIES AIRPORT, LANDED IN A FIELD 1/2 MILES NORTHEAST OF THE AIRPORT. NO INJURIES AND DAMAGE MINOR. INSPECTION BY TRI CITIES AVIATION MAINTENANCE INDICATED NO FUEL IN LEFT TANK, BUT FUEL IN RIGHT TANK AND FUEL SELECTOR IN THE OFF POSITION. ENGINE WAS STARTED AND GROUND RAN WITH NO ABNORMALITIES.

## Other reports on N25270 (1)

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

- [Accident 20000416006799A](https://openairdocs.org/incident/20000416006799A), Apr 16, 2000: Luscom 8C (N25270), Galveston, TX, Substantial damage. (-23) Pilot neglected to remove the previously attached co-pilot's seatbelt from securing the flight controls. It was when the airplane became airborne it was…

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.