NTSB CAROL · Event
Event CEN14LA371
Aircraft involved
Probable cause & findings
The noncertificated pilot’s failure to maintain control of the gyroplane following a total loss of engine power due to a loose spark plug.
Factual narrative
HISTORY OF FLIGHTOn July 10, 2014, about 1730 eastern daylight time, an unregistered amateur-built Air Command model 532 gyroplane was substantially damaged when it impacted terrain while maneuvering near Lada Airport (7MI5), Petersburg, Michigan. The pilot, who had an expired student pilot certificate, was fatally injured. The gyroplane was owned and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 without a flight plan. Day visual meteorological conditions prevailed for the local flight that departed 7MI5 at an unknown time. An acquaintance of the pilot reported that the pilot arrived at the departure airport around 1700 with the gyroplane on a trailer; however, the pilot did not mention that he intended to fly that evening. There were no witnesses to the accident flight. On the morning of July 11, 2014, the gyroplane wreckage was discovered in a potato field about 1/4 mile east of the departure airport. PERSONNEL INFORMATIONAccording to Federal Aviation Administration (FAA) airman records, the pilot did not possess a valid pilot certificate. On October 25, 2002, he was issued a student pilot certificate in conjunction with a third-class medical certificate. When applying for the medical certificate, the pilot reported having 45 hours total flight time, of which 22 hours had been accumulated during the preceding 6 months. The student pilot certificate subsequently expired in October 2004. The pilot's flight logbook was not located during the investigation, which precluded a review of his recent flight experience and total time in the accident gyroplane. AIRCRAFT INFORMATIONA review of FAA aircraft registry records established that the amateur-built gyroplane did not have an airworthiness certificate or registration number. The single-seat gyroplane was powered by a Rotax model 532 engine, serial number 3671761. No maintenance documentation was located during the investigation. METEOROLOGICAL INFORMATIONAt 1735, the automated surface observing system (ASOS) located at Toledo Suburban Airport (DUH), about 9 miles south of the accident site, reported the following weather conditions: wind from 120 degrees at 5 knots, visibility 10 miles, clear sky, temperature 25 degrees Celsius, dew point 14 degrees Celsius, and an altimeter setting of 30.14 inches of mercury. AIRPORT INFORMATIONA review of FAA aircraft registry records established that the amateur-built gyroplane did not have an airworthiness certificate or registration number. The single-seat gyroplane was powered by a Rotax model 532 engine, serial number 3671761. No maintenance documentation was located during the investigation. WRECKAGE AND IMPACT INFORMATIONThe gyroplane wreckage was located in a potato field about 1/4 mile east of the departure airport. A wreckage debris path originated from the initial point-of-impact on a northerly heading and measured about 30 feet long. All airframe components were located along the wreckage debris path or amongst the main wreckage. Flight control continuity could not be established due to the extent of the damage; however, all observed flight control system discontinuities were consistent with overstress. One of the two main rotor blades had separated from the mast hub assembly; however, the observed damage to the rotor blade was consistent with ground impact. Examination of the engine revealed that the forward spark plug of the two-cylinder, two-stroke, Rotax model 532 engine was loose and could be removed by hand without the aid of any tools. No additional preimpact anomalies were noted with the engine that would have prevented its normal operation. Additionally, the throttle was found in the full-aft position, there was the smell of automobile fuel present at the accident site, and the 3-blade propeller exhibited minor damage. MEDICAL AND PATHOLOGICAL INFORMATIONOn July 12, 2014, an autopsy was performed on the pilot at the Wayne County Medical Examiner's Office located in Detroit, Michigan. The cause of death was attributed to multiple blunt-force injuries that were sustained during the accident. Toxicological testing was completed by NMS Labs located in Willow Grove, Pennsylvania. The toxicological test results were negative for ethanol and drugs of abuse. The pilot, who had an expired student pilot certificate, was conducting a personal local area flight in the unregistered amateur-built gyroplane. An acquaintance of the pilot reported that the pilot had arrived at the departure airport with the gyroplane on a trailer; however, the pilot did not mention that he intended to fly that evening. There were no witnesses to the accident flight. The gyroplane wreckage was discovered the following morning in a potato field about 1/4 mile east of the departure airport. A postaccident examination of the gyroplane did not reveal any airframe or flight control anomalies that would have prevented normal operation. One of the main rotor blades had separated from the mast hub assembly; however, the observed damage to the rotor blade was consistent with ground impact. Examination of the two-cylinder, two-stroke, engine revealed that the forward spark plug was loose and could be removed by hand. No additional preimpact anomalies were noted with the engine that would have prevented its normal operation. It is likely that the loose spark plug resulted in a loss of cylinder compression and a total loss of engine power. During the subsequent forced landing, the gyroplane impacted terrain and tumbled about 30 ft. The wreckage debris path was consistent with an uncontrolled collision with terrain. A review of aircraft registry records established that the amateur-built gyroplane did not have an airworthiness certificate or registration number. Further, there was no maintenance documentation for the gyroplane. The pilot did not possess a valid pilot certificate; his student certificate had been expired for more than 9 years. Additionally, a pilot logbook was not located during the investigation, which precluded a review of the pilot's recent flight experience and total time in the accident gyroplane. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft power plant-Ignition system-Spark plugs/igniters-Incorrect service/maintenance - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-(general)-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2014_CEN14LA371.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 (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 ↗