NTSB CAROL · Event
Event MIA01LA085
Aircraft involved
Probable cause & findings
The improper emergency procedure performed by the pilot due to his electing to perform a run-on landing resulting in excessive airspeed at touchdown and subsequent roll-over following ground contact with grass. A contributing factor was the inadequate 100-Hour inspection performed last to the helicopter resulting in the total loss of engine power due to fuel starvation.
Factual narrative
On February 24, 2001, about 1703 eastern standard time, a Hiller UH-12B, N5307V, registered to Historic Banning Mills, experienced a loss of engine power and rolled over during a run-on landing on a road near Whitesburg, Georgia. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 personal flight. The helicopter was substantially damaged and the commercial rated pilot and two passengers were not injured. The flight originated about 1630 from a helipad located at Historic Banning Mills, Whitesburg, Georgia. The pilot stated that the purpose of the flight was to photograph the parent's house of the adult passenger. The flight was returning when the accident occurred. While descending for approach to a ball field about 250 to 300 feet above ground level (agl) at an indicated airspeed between 60-65 knots, the helicopter yawed. He corrected the yaw with anti-torque pedal and noted that the engine rpm and main rotor rpm needles were "split"; the main rotor rpm was in the green arc and the engine rpm was indicating zero. He rolled the throttle to the right towards the fuel-on position, then lowered full collective and maintained 40-45 knots while descending for an autorotative landing to the down sloping road. He cleared a bridge ahead and at approximately 15 feet agl, he applied aft cyclic to decelerate "somewhat", and pulled full collective. He touched down at an indicated airspeed between 20 and 30 knots on the road that curved to the left and later reported, "we didn't hit real easy." He lowered full collective after touchdown and while sliding, the right skid contacted grass on the side of the road causing the right skid to collapse. The helicopter then rolled onto its right side and slid approximately 4-5 feet before coming to rest. There was no postcrash fire or fuel leakage. A record of conversation with the pilot is an attachment to this report. Examination of the helicopter by an FAA Airworthiness Inspector revealed 8-9 gallons of fuel on board; the carburetor bowl was found approximately 1/2 full with a slight amount of contamination. The engine driven fuel pump would not produce 2 psi flow and would not produce any flow with a minor restriction. Additionally, the auxiliary fuel pump strainer was "so clogged and corroded it had to be removed with a metal hook and screw driver", (see photographs 1 and 2). A copy of the FAA inspector statement is an attachment to this report. Review of the maintenance records revealed that the helicopter was inspected last in accordance with a 100-Hour inspection that was signed off on January 5, 2001. The helicopter had accumulated approximately 24 hours since the inspection at the time of the accident. Excerpts from the maintenance records are an attachment to this report. Review of the helicopter flight manual pertaining to engine failure when flying above 325 feet agl revealed to maintain 50-60 mph glide speed and to pull cyclic stick steadily back at approximately 75 feet agl. Additionally, "when 10-15 feet above the landing surface, level the helicopter with forward cyclic stick and then apply collective pitch, as necessary, to cushion the landing impact." The flight manual also states, "To reduce the rate of descent and forward speed during an autorotation landing, the helicopter's flight path should be flared or leveled out, prior to ground contact." Excerpts from the flight manual is an attachment to this report. The purpose of the flight was to photograph the parent's house of the adult passenger; the flight was returning when the accident occurred. While descending for approach to a ball field about 250 to 300 feet above ground level (agl) at an indicated airspeed between 60-65 knots, the helicopter yawed. He corrected the yaw with anti-torque pedal and noted that the engine rpm and main rotor rpm needles were "split"; the main rotor rpm was in the green arc and the engine rpm was indicating zero. He rolled the throttle to the right towards the fuel-on position, then lowered full collective and maintained 40-45 knots while descending for an autorotative landing to the down sloping road. He cleared a bridge ahead and at approximately 15 feet agl, he applied aft cyclic to decelerate "somewhat", and pulled full collective. He touched down at an indicated airspeed between 20 and 30 knots on the road that curved to the left and later reported, "we didn't hit real easy." He lowered full collective after touchdown and while sliding, the right skid contacted grass on the side of the road causing the right skid to collapse. The helicopter then rolled onto its right side and slid approximately 4-5 feet before coming to rest. There was no postcrash fire or fuel leakage. Examination of the helicopter by an FAA Airworthiness Inspector revealed 8-9 gallons of fuel on board; the carburetor bowl was found approximately 1/2 full with a slight amount of contamination. The engine driven fuel pump would not produce 2 psi flow and would not produce any flow with a minor restriction. Additionally, the auxiliary fuel pump strainer was "so clogged and corroded it had to be removed with a metal hook and screw driver." The helicopter was inspected last in accordance with a 100-Hour inspection that was signed off on January 5, 2001; the helicopter had accumulated approximately 24 hours since the inspection at the time of the accident. Review of the helicopter flight manual pertaining to engine failure when flying above 325 feet agl revealed to maintain 50-60 mph glide speed and to pull cyclic stick steadily back at approximately 75 feet agl. Additionally, "when 10-15 feet above the landing surface, level the helicopter with forward cyclic stick and then apply collective pitch, as necessary, to cushion the landing impact." The flight manual also states, "To reduce the rate of descent and forward speed during an autorotation landing, the helicopter's flight path should be flared or leveled out, prior to ground contact." Excerpts from the flight manual is an attachment to this report. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_MIA01LA085.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 (fuel starvation, engine failure, 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 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…
- 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.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗