LAX07CA283 · Luscombe 8E
Luscombe 8E · Accident: airframe, component or system failure during landing
From Ramona Airport (RNM) to Ramona Airport (RNM)
Event
- NTSB case
- LAX07CA283
- 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
Luscombe 8E
- Aircraft type
- Luscombe 8
- 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
- N2826K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ramona Airport (RNM), Ramona, CATo Ramona Airport (RNM), Ramona, 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
- Landing · landing roll
- 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
- Airframe, component or system failure
- 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
- Landing gear, normal brake system › Jammed
- Landing gear, wheel › Incorrect
- Landing gear, wheel › Movement restricted
- Miscellaneous, bolt/nut/fastener/clamp/spring › Sheared
- Unknown › Maintenance, installation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot lost directional control of the airplane during landing rollout. It veered off the runway, ground looped, and a wing broke. An examination of the airplane's records and landing gear revealed that years earlier, the left wheel had been replaced with an incorrect part, which incorporated different sizes of bolt holes for each half of the wheel. During subsequent operation of the airplane one through bolt that held the wheel halves together sheared. The bolt became lodged in the brake caliper, which caused the left wheel to lock up. This induced a turning moment, which resulted in the pilot's loss of directional control.
Probable cause
the installation and subsequent failure of an incorrect part, which jammed in one wheel's brake caliper and induced the pilot's loss of directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA283
- Event ID
- 20071101X01697
- Case number
- LAX07CA283
- 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: 7e72fc93a48837757637afdb3dca5159114153e8ee5d8e0ecce3d7de2caf88b1; retrieved 2026-09-22T03:23:18.337Z.