# Incident 20100715040239I: Beech B36TC, Johnson City, KS, July 15, 2010

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 15, 2010, 07:57 local time
- Place: Johnson City, KS
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 37.5704° N, 101.7448° W: Placed by OpenAirDocs: center of Johnson City, KS, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.5704&lon=-101.7448&mi=10
- Aircraft: N6484L, registered now (https://openairdocs.org/aircraft/N6484L) (OpenAirDocs)
- Registry model: Beech B36TC (registry code 1151609, https://openairdocs.org/model/beech-b36tc) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: BEECH B36TC
- Reported engine: CONT MOTOR TSIO-520 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 10,000 total, 1,000 in this make and model, 15 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100715040239I

## Narrative

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

AIRCRAFT N6484L DEPARTED DENVER, CO (APA) ENROUTE TO LIBERAL, KS (LBL).  DURING CRUISE AT 11,000 FT, THE ENGINE POWER DROPPED; THEN THE ENGINE QUIT.  THE AIRCRAFT MADE AN EMERGENCY LANDING ON A DIRT ROAD (ROAD 2) 4 MILES WEST OF HIGHWAY 27 IN STANTON COUNTY NEAR JOHNSON CITY, KS. THERE WAS NO APPARENT DAMAGE TO THE AIRCRAFT.

## Other reports on N6484L (1)

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

- [Incident 19850226022279I](https://openairdocs.org/incident/19850226022279I), Feb 26, 1985: Beech B36TC (N6484L), Fort Collins, CO. Tire blew on landing, aircraft veered off runway. No damage.

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.