LAX07LA078 · Republic RC-3
Republic RC-3 · Accident: propeller failure/malfunction en route
From Gillespie Field (SEE) to Blythe, CA
Event
- NTSB case
- LAX07LA078
- 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
Republic RC-3
- Aircraft type
- Republic RC-3
- 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
- N6248K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gillespie Field (SEE), El Cajon, CATo Blythe, CA
- Aircraft age
- Not recorded
- 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
- En route · cruise
- First occurrenceThe 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
- Propeller failure/malfunction
- 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
- Propeller system/accessories › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During cruise flight, the propeller assembly departed from the crankshaft flange and fell from the airplane. The pilot executed a forced landing to an open field. The recently overhauled propeller assembly had been installed on the engine for approximately 8 hours prior to the separation. Examination of the airframe revealed the six propeller to crankshaft attachment bolts were fractured, and all failed as a result of fatigue cracking. No chemical composition or other material deficiencies were found on the bolts. Bolt fatigue is most commonly the result of insufficient preload from under torquing the fastener, or improper installation, or from the loss of preload during service. The equal amounts of fatigue on all six bolts suggested that all bolts were equally affected.
Probable cause
The failure of the propeller to crankshaft attachment bolts due to fatigue. A contributing factor was the improper installation of the propeller assembly by maintenance personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07LA078
- Event ID
- 20070209X00167
- Case number
- LAX07LA078
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: a2b76fa2f48b5e973a2b3a18f7cd89c1543509b7ea20a2c54e461d4521711af2; retrieved 2026-09-22T04:03:21.221Z.