ATL00FA019
2000-01-01 · MONTEAGLE, Tennessee, United States · Fatal · 1 aircraft · Status: Completed
Aircraft involved
Probable cause & findings
The pilot's failure to adequately evaluate weather conditions that resulted in the continuation of visual flight into instrument weather conditions and the subsequent collision with trees.
Factual narrative
HISTORY OF FLIGHT
On January 1, 2000, at 1302 central standard time, a Bellanca BL-17-30A, N8821V, collided with trees and burst into flames in a heavily wooded area near Monteagle, Tennessee. The personal flight was operated by the pilot under the provisions of Title 14 CFR Part 91 with no flight plan filed. Instrument weather conditions prevailed at the time of the accident. The airplane was destroyed; the private pilot and his passenger were fatally injured. According to the initial report from local law enforcement authorities, the flight departed Asheville, North Carolina, at an undetermined time, and the exact route of flight was not known. Reportedly, the pilot and his passenger spent the evening prior to the accident at a local hotel in Asheville, North Carolina. Circumstances of the history of flight are also not known. The flight departed Asheville, North Carolina, at an undetermined time on the morning of the accident. The intended route of flight was not determined, a review of the Federal Aviation Administration Flight service system failed to disclose that the pilot had received a pre-flight weather briefing for the intended flight. The flight was first heard only seconds before the airplane collided with trees. According to a witness near the accident site, he heard the airplane overhead followed by a high revving engine sound and the sound of the airplane colliding with trees. Another witness reported hearing an explosion during the sequence of events. Subsequent to the collision, smoke was sighted in the vicinity of the accident site. Within minutes of the collision, emergency response personnel from surrounding counties were on site. According to Monteagle Chief of Police, upon arriving at the accident site, he noticed that fog and low clouds were about 20 feet above the ground, and the mountain top was obscured.
PERSONNEL INFORMATION
The pilot held a private pilot certificate with airplane single-engine land, and instrument ratings. A review of pilot information from the Federal Aviation Administration (FAA), his total flight time was 400 hours but the approximately flying time in the Bellanca BL-17-30A was not determined. The pilot held a current third class medical certificate, dated August 10, 1999, valid with no waivers or limitations.
AIRCRAFT INFORMATION
The four place Bellanca BL-17-30A airplane, N8821V, was owned and operated by the pilot. N8821V was powered by a fuel injected, 300 horse power Continental Motors IO-520-K engine. A review of the airplane maintenance logbooks showed that the last annual inspection was completed on July 28, 1999. The airframe tachometer was not recovered at the accident site, however, according to the airframe maintenance logbook the last entry was recorded on December 24 1999, at 1916.5 hours.
METEOROLOGICAL INFORMATION
A review of weather data from reporting facilities in the vicinity of the accident site showed the following observations: The Chattanooga 1353 weather observation reported broken clouds at 300 feet with 1.75 miles visibility: the altimeter setting was 30.15 inches of mercury. The winds were light and variable. The area forecast for middle Tennessee at the approximate time of the accident called for broken cloud conditions between 2000 and 3000 feet, and visibility under the cloud layer between 3 and 5 miles. Marginal visual flight rule weather conditions were also forecasted for middle Tennessee. A review of the FAA flight service files failed to show that the pilot had received a preflight or inflight weather briefing.
WRECKAGE AND IMPACT INFORMATION
Examination of the accident site disclosed that wreckage debris was scattered over an area approximately 800 feet long and 60 feet wide. Wreckage debris was orientated on a northwesterly magnetic heading. Several freshly broken trees were scattered along the wreckage path. Fire damage was confined to the last third of the wreckage path. The main wreckage, which consisted of the cockpit and center section of the airframe, was heavily fire damaged. Further examination of the airframe disclosed that the airplane rested inverted at the accident site. Several pieces of the airframe including engine cowling were torn from the airplane and were scattered throughout the length of the wreckage path. Other wreckage debris was lodged in trees along the wreckage path. The engine assembly was located approximately 100 feet northwest of the main wreckage. Examination of the engine assembly revealed that many externally installed components were torn from their normally installed positions. Further examination of the engine showed a large hole on the top and front portions of engine case halves. The three propeller blades separated from the engine assembly. One propeller blade rested 48 feet northwest of the main wreckage the second and third propeller blades remained attached to the hub assembly and was 39 feet east of the main wreckage. Examination of the propeller blades showed twisting and chordwise scraping on each blade. The examination of the engine failed to disclose a system malfunction or a component failure. Examination of the remainder of the airframe also failed to disclose a mechanical malfunction or the failure of related component assemblies.
MEDICAL AND PATHOLOGICAL INFORMATION
On January 3, 2000, a limited postmortem examination of the pilot was performed by Dr. Charles Harlan at the office of the Forensic Pathology Association in Nashville, Tennessee, The toxicology examinations were performed by the FAA Toxicology and Accident Research Laboratory, Oklahoma City, Oklahoma. The tests were negative for carbon monoxide, cyanide, drugs and alcohol.
ADDITIONAL INFORMATION
The airplane wreckage was released on August 30, 2000 to Mr. Kevin Twist, an insurance adjuster, Atlanta, Georgia. Circumstances of the history of flight are not known. The intended route of flight was not determined, a review of the Federal Aviation Administration Flight service system failed to disclose that the pilot had received a pre-flight weather briefing for the intended flight. The flight was first heard only seconds before the airplane collided with trees. Subsequent to the collision, smoke was sighted in the vicinity of the accident site. Upon arriving at the accident site, rescue personnel noticed that fog and low clouds were about 20 feet above the ground, and the mountain top was obscured. Examination of the engine and airframe failed to disclose a mechanical malfunction or the failure of related component assemblies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_ATL00FA019.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, maintenance). All research papers
- Embry-Riddle Scholarly Commons 2023 · Conference paper The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Semantic Scholar 2024 · Article (Defence Science Journal) Modelling of Human Factors in Aviation Maintenance Using HFACS ME Human Factors Analysis and Classification System Maintenance Extension and Bayesian Network
Aircraft maintenance is a complex task involving a skilled human workforce, spare parts, and various other resources. Human factors are an inherent element of the human workforce.