NYC08CA205 · Luscombe 8A
Luscombe 8A · Accident: system/component malfunction/failure (non-power) during takeoff
From Indiantown Airport (X58) to Witham Field (SUA)
Event
- NTSB case
- NYC08CA205
- 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 8A
- 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
- N37012
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indiantown Airport (X58), Indiantown, FLTo Witham Field (SUA), Stuart, FL
- 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
- Takeoff
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The Luscombe 8A was taking off from a turf runway, and had climbed to an altitude of about 10 feet above ground level, when the left rudder cable failed. The airplane yawed to the right and the left wing and nose contacted the ground. The airplane subsequently came to rest on the right side of the runway and sustained substantial damage to the left wing and fuselage. Examination of the airplane revealed that the left rudder cable had separated at the first pulley under the cabin floor. The separated end of the cable was frayed and displayed evidence of corrosion. The airplane had been operated for about 25 hours since its most recent annual inspection, which was performed about 11 months prior to the accident. At the time of the inspection, a mechanic noted that the control cables were inspected for damage per a required Airworthiness Directive.
Probable cause
An inadequate annual inspection that failed to detect a damaged rudder cable which resulted in the cable's subsequent failure during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA205
- Event ID
- 20080826X01319
- Case number
- NYC08CA205
- 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, 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: 9ecff75d4f3e281906070e3dce660b27f7f92810769237e71cde5b3df2ea4f36; retrieved 2026-09-15T10:06:15.896Z.