NTSB CAROL · Event
Event MIA96LA176
Registry · N301CH
FAA Aircraft Registry record.
Make / Model
AIRBUS HELICOPTERS INC AS350B3
Year of manufacture
2014
TCDS
H9EU · AIRBUS HELICOPTERS
Engine
TURBOMECA ARRIEL 2D (802 hp)
Seats / Engines
7 seats · 1 engine
Last airworthiness date
20141104
ADS-B equipped
Yes — Mode-S A32343
Registrant of record
COASTAL HELICOPTERS INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Improper repair of a previous crack in the blue main rotor blade by unknown persons; improper inspection of the main rotor blades by maintenance personnel, following a reported vibration problem; and subsequent failure of the main rotor blade, which resulted in an uncontrolled collision with the terrain.
Factual narrative
On July 3, 1996, about 2015 eastern daylight time, a Hiller OH-23C, N301CH, registered to an individual, lost a main rotor blade and crashed while landing at the Marathon Airport, Marathon, Florida, while on a 14 CFR Part 91 maintenance test flight. Visual meteorological conditions prevailed at the time and no flight was filed. The helicopter received substantial damage and the airline transport-rated pilot and one passenger received minor injuries. The flight originated from the Marathon Airport shortly before the accident. The pilot stated the helicopter had been purchased and trucked from Texas on June 20, 1996, with the main rotor blades removed. A mechanic had reinstalled the main rotor blades on arrival in Marathon, Florida. He began flying the helicopter and experienced a problem with vertical vibration of the main rotor blades over the previous week before the accident. Several mechanics had worked on the main rotor blades and made adjustments to correct the vertical vibration problem. At the time of the accident he was flying with a mechanic who had a balancing device to obtain the inflight balance condition of the main rotor blades. After takeoff, with the mechanic on their third test flight, he remained in the airport traffic pattern for runway 25. While on the downwind leg, the vertical vibration, which had previously gone away, returned. Shortly after it returned he heard a loud "pop" noise. He immediately turned toward the airport. As he was landing a main rotor blade separated and the helicopter crashed to the ground. Postcrash examination of the main rotor blades was performed by FAA and Hiller Aircraft Corporation Engineers. The blue main rotor blade had failed and torn out of the grip plate in a spanwise direction. There was no evidence of dry rot in the wood at the blade grip end. There had been repairs made in the wood of the blade grip end of the blade and there was no evidence of adhesive in the repaired area. A material that was not specified for use on the blade was used to seal the repaired area. There was oil contamination in the wood of the blade grip end of the blade. (See attached Hiller Aircraft Report.) Available aircraft logbook records showed the blades were removed from the aircraft and inspected on August 29, 1989, 503 flight hours before the accident. The aircraft received an annual inspection on June 1, 1996, 18 flight hours before the accident. During a previous flight, the helicopter was reported to have excessive vertical vibration and to require excessive collective forces during flight. Mechanics worked on the main rotor blades to correct the problem, then the helicopter was flown on a maintenance test flight. During the test flight, the pilot noted that the vertical vibration had 'gone away,' but before landing, the vertical vibration returned. Shortly thereafter, the pilot heard a loud 'pop'. As he flared for landing, the blue main rotor blade separated and the helicopter crashed. Examination of the separated blade showed the wood in the area of the blade grip had failed, allowing the blade to separate. Evidence of a previous repair was present in this area, which lacked adequate adhesive between some of the mating surfaces. Also, an unapproved sealant had been used over the repaired area, and oil had contaminated the wood in this area. There was no evidence of dry rot in the failed area. The logbook records did not show the previous blade repair. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_MIA96LA176.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, 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 …
- 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.
Browse the full corpus — academia portal ↗