# Accident 19990613006889A: Cessna 172P, Sevierville, TN, June 13, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 13, 1999, 09:15 local time
- Place: Sevierville, TN
- Airport: Seymour Air Park Inc Airport
- Damage: Substantial damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 35.8700° N, 83.7710° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=35.8700&lon=-83.7710&mi=10
- Aircraft: N5494K, a cancelled registration (https://openairdocs.org/deregistered/N5494K-1999-10-28) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320D2J
- Fatal injuries: 0
- Pilot flight hours: 297 total, 99 in this make and model, 51 in the last 90 days
- NTSB investigation: [NTSB MIA99LA182](https://openairdocs.org/ntsb/MIA99LA182) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990613006889A

## Narrative

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

ACFT STRUCK POWER LINES DURING AN ATTEMPTED GO-AROUND, OTHER CIRCUMSTANCES ARE UNKNOWN. (FROM .19) ON JUNE 13, 1999, ABOUT 0915 EASTERN DAYLIGHT TIME, A CESSNA 172P, N5494K, REGISTERED TO AND OPERATED BY MORRISTOWN FLYING SERVICE, INC., COLLIDED WITH A POWER LINE AND TREES DURING TAKEOFF FOLLOWING AN ABORTED LANDING AT SEYMOUR AIR PARK, INC., A PRIVATE AIRTRIP LOCATED NEAR SEYMOUR, TENNESSEE.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND NO FLIGHT PLAN WAS FILED FOR THE 14 CFR PART 91 PERSONAL FLIGHT.  THE AIRPLANE WAS SUBSTANTIALLY DAMAGED AND THE COMMERCIAL-RATED PILOT AND PILOT-RATED PASSENGER SUSTAINED MINOR INJURIES.  THE FLIGHT ORIGINATED ABOUT 0840, FROM THE MOORE-MURRELL AIRPORT, MORRISTOWN, TENNESSEE. ACCORDING TO THE AIRCRAFT OWNER WHO SPOKE WITH THE PILOT AND TRAVELED TO THE ACCIDENT SITE, THE PILOT INIATED A FIRST APPROACH TO THE RUNWAY, THEN PERFORMED A GO-AROUND AND RETURNED FOR LANDING.  THE AIRPLANE WAS LANDED ON THE RUNWAY AND THEN PILOT INITIATED A GO-AROUND.  DURING CLIMBOUT, THE MAIN LANDING GEAR COLLIDED WITH THE TOP POWER LINE THAT WAS MARKED.  THE AIRPLANE THEN COLLIDED WITH TREES ABOUT 25 FT AGL, THEN IMPACTED A FENCE AND CAME TO REST UPRIGHT  . THE INVESTIGATION CONTINUES. (-23) PILOT EXECUTED A REJECTED LANDING AND DURING THE 90 AROUND HIT A POWER LINE.  THIS CAUSED THE AIRCRAFT TO LOSE FLYING SPEED AND CRASH. (.4) THE PILOT STATED THAT HE HAD FLOWN INTO THE AIRSTRIP A MINIMUM OF 15 TIMES AND DURING THE FIRST APPROACH, HE RECOGNIZED THAT HE FLIGHT WAS HIGH.  HE PERFORMED A GO-AROUND, ORBITED THE AIRPORT 1 TIME TO ALLOW FOR DEPARTING TRAFFIC, THEN REENTERED THE TRAFFIC PATTERN TO LAND.  WHILE OVER THE APPROACH END OF THE RUNWAY WITH THE FLAPS FULLY EXTENDED, HE RECOGNIZED THAT THE FLIGHT WAS AGAIN 'HIGH' BUT THOUGHT SUFFICIENT RUNWAY REMAINED AFTER LANDING TO STOP THE AIRPLANE. THE AIRPLANE WAS LANDED 'TOO FAR DOWN THE RUNWAY TO BE ABLE TO STOP...', AND HE RETRACTED THE FLAPS TO 10 DEGREES, APPLIED FULL POWER, AND BEGAN TO CLIMB.  DURING THE CLIMB THE LEFT MAIN LANDING GEAR COLLIDED WITH A MARKED POWER LINE.  THE AIRPLANE THEN COLLIDED WITH TREES, A FENCE, AND CAME TO REST UPRIGHT.  THE PILOT FURTHER STATED THAT THERE WAS NO ENGINE FAILURE OR MALFUNCTION.  EXAMINATION OF THE AIRPLANE BY AN FAA AIRWORTHINESS INSPECTOR REVEALED CONTROL CONTINUITY FOR ROLL, PITCH, AND YAW.

## 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 MIA99LA182](https://openairdocs.org/ntsb/MIA99LA182), Jun 13, 1999: Cessna 172P (N5494K), Seymour, TN, substantial damage. Probable cause: The failure of the pilot to perform a go-around earlier resulting in a long landing, insufficient runway remaining to stop, and subsequent in flight collision with a marked power line during an…

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.