NTSB CAROL · Event
Event ATL95FA054
Aircraft involved
Probable cause & findings
THE PILOT'S FAILURE TO MAINTAIN FLYING SPEED RESULTING IN AN AERODYNAMIC STALL. A FACTOR WAS SUNGLARE.
Factual narrative
HISTORY OF FLIGHT
On February 24, 1995, at 1750 eastern standard time, a Piper PA-30B, N7972Y, collided with the ground, after the pilot lost control of the airplane while attempting a landing at the Macon County Airport in Franklin, North Carolina. The personal flight operated under the provisions of 14 CFR Part 91, with no flight plan filed. Visual weather conditions prevailed at the time of the accident. The airplane was destroyed by impact forces and a post-impact fire. The pilot and passenger were fatally injured. The exact departure time and location of the flight from Florida were not determined. After departing the Sarasota, Florida area, no recorded radio contact was reported with N7972y. Airport personnel at Macon County Airport reported that the pilot radioed for landing advisories, and was advised to land on runway 7. Moments later N7972Y was seen east of the airport on what was believed to have been a final approach to runway 25. As the airplane approached the runway, the pilot terminated the final approach 150 feet above the ground, and flew parallel to the runway. The pilot continued the parallel heading until he was beyond the departure end of runway 25. When the airplane was beyond the departure end of runway 25, the pilot entered a steep left descending turn, and the airplane collided with the ground. Witnesses reported that the pilot never established a go-around climb attitude, and did not retract the landing gear before entering the steep turn.
PERSONNEL INFORMATION
Information on the pilot is included in this report at the data field labeled "First Pilot Information." The pilot's flight logs were not recovered for examination; pilot flight experience information was never recovered.
AIRCRAFT INFORMATION
Information on the aircraft is contained in this report at the data field labeled "Aircraft Information." Aircraft maintenance logs were destroyed in the post-impact fire, and some aircraft historical information was not recovered.
METEOROLOGICAL INFORMATION
Visual weather conditions prevailed at the time of the accident. Weather information is contained in this report at the data field labeled "Weather Information." During the pilot's modified traffic pattern to runway 7, he flew a westerly head into the sun.
WRECKAGE AND IMPACT INFORMATION
The accident site examination revealed that, the airplane impacted the ground 250 feet right of the extended centerline and 700 feet from the end of runway 07. Debris from the left wing tip was found at the first impact point west of the main wreckage. Aircraft wreckage debris was scattered over an area 90 feet long and 40 feet wide. The post-impact fire destroyed the center section of the airframe and the empennage. Emergency locator transmitter (ELT) data was not recovered. Fire damage extended outboard from the wing roots of both wings to about mid- span. Portions of the flight control surfaces were also fire damaged. Propeller blades from both engines sustained impact damage along the leading edges. Despite the extensive fire damage, the examination of the wreckage failed to reveal a mechanical malfunction or system failure.
MEDICAL AND PATHOLOGICAL INFORMATION
The postmortem examination on the pilot was performed by Dr. Thomas A. Sporn on February 25, 1995, at the Office of the Chief Medical Examiner in Chapel Hill, North Carolina. The cause of death was reported as massive trauma secondary to the aircraft accident. The toxicological examinations were negative for drugs and alcohol.
ADDITIONAL INFORMATION
According to airport personnel, the pilot had made several flights into Franklin, and he was familiar with the airport. The traffic pattern flown by the pilot was not in accordance with the normal procedure for a visual approach to runway 7. Airport personnel stated that the downwind leg for a normal traffic pattern for runway 7, extends north between the next two mountain ridges. The aircraft wreckage was released to: Mr. Jamie McArthur 5257 Challedon Drive Virginia Beach, Virginia AS THE FLIGHT APPROACHED THE DESTINATION AIRPORT, THE PILOT REQUESTED LANDING ADVISORIES; RUNWAY 7 WAS THE ACTIVE RUNWAY. THE PILOT ESTABLISHED A FINAL APPROACH FOR THE OPPOSITE RUNWAY. AS THE AIRPLANE APPROACHED THE MID-FIELD POINT, AND ONLY SEVERAL FEET ABOVE THE GROUND, THE PILOT EXECUTED A SLIGHT CLIMB. THE CLIMB CONTINUED UNTIL THE AIRPLANE WAS BEYOND THE DEPARTURE END RUNWAY 25. AT THIS POINT, THE PILOT ENTERED A STEEP LEFT TURN. THE AIRPLANE COLLIDED WITH THE GROUND 700 FEET BEYOND THE DEPARTURE END OF RUNWAY 25, AND BURNED. AT THE TIME OF THE APPROACH, THE SUN WAS ON THE WESTERN HORIZON. EXAMINATION OF THE ACCIDENT SITE DISCLOSED THAT WRECKAGE DEBRIS WAS SCATTERED OVER AN AREA 90 FEET LONG AND 40 FEET WIDE. THE POST-IMPACT FIRE DESTROYED THE AIRFRAME CENTER SECTION AND EMPENNAGE. THE WRECKAGE EXAMINATION FAILED TO DISCLOSE A MECHANICAL MALFUNCTION. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1995_ATL95FA054.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, go-around, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- 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 …
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- 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.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
Browse the full corpus — academia portal ↗