CEN18LA292 · Grumman AA5 B
RJM-AV8 Grumman AA5 B · Accident: system/component malfunction/failure (non-power) while maneuvering
From Pearland Regional Airport (LVJ) to an unrecorded destination
Event
- NTSB case
- CEN18LA292
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Grumman AA5 B
- Aircraft type
- Grumman AA5
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N74420
- Operator
- RJM-AV8
- Onboard fatalities
- Unknown
- Route
- From Pearland Regional Airport (LVJ), Pearland, TXTo not recorded
- Aircraft age
- About 43 years (built 1975)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot and his flight instructor were conducting a local instructional flight when the airplane began to shake violently. A reduction of engine power revealed that the one of the propeller blades had separated about midspan. The flight instructor took control of the airplane and completed an uneventful forced landing in a nearby field. A postaccident examination revealed several fractured engine mounts. A laboratory examination of the propeller revealed that about one-half of one blade had fractured. Further examination of the flat portion of the fracture surface revealed a pattern of crack arrest lines and striations that were consistent with fatigue cracking. The pattern of crack arrest lines indicated that the fatigue cracking emanated from the trailing edge tip of the blade. Damage to the fracture surface at the trailing edge tip of the blade obscured the exact initiation point of the fatigue cracking. The propeller had accumulated about 4,499 hours since its last overhaul, and about 11 hours since it was last examined during an annual inspection.
Probable cause
The propeller blade separation due to a fatigue fracture.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA292
- Event ID
- 20180723X31358
- Case number
- CEN18LA292
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: cb3684df4735375cd46b4499f7575e036a3654a7f6388dba8145d2b1d9784094; retrieved 2026-09-16T07:57:19.701Z.