ERA12FA017 · Luscombe 8A
Luscombe 8A · Accident: loss of engine power (total) en route
From Thomasville Regional Airport (TVI) to Flying Harness Farms Airport (37FL)
Event
- NTSB case
- ERA12FA017
- 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
- 1 · 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
- N41907
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Thomasville Regional Airport (TVI), Thomasville, GATo Flying Harness Farms Airport (37FL), Bell, 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
- En route · cruise
- 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
- Loss of engine power (total)
- 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 power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he noted the engine oil temperature rising during cruise flight. He elected to reduce power and fly to the nearest airport. While en route, at an altitude of about 1,000 feet above ground level and a distance of 4 miles, the engine experienced a catastrophic failure. The pilot landed the airplane on an open field; however, he could not stop the airplane on the remaining surface and it impacted two trees in a wooded area beyond the field.
A postaccident examination revealed that the No. 2 cylinder piston connecting rod had separated from the crankshaft. One of the bolts securing the rod cap was missing. The bolt and nut were recovered from internal engine debris; however a safety cotter pin necessary to secure the bolt was not located. About 20 engine-operating hours before the accident, all of the engine’s the piston connecting rod bearings and their respective bolts and nuts were replaced. Thus, it is likely that at that time one of the two nuts was not properly secured with a cotter pin on the No. 2 cylinder piston connecting rod, allowing the nuts to slowly unthread over time.
Probable cause
Maintenance personnel’s improper installation of the No. 2 cylinder’s connecting rod, which resulted in the disconnection of the rod and a subsequent loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA017
- Event ID
- 20111008X70843
- Case number
- ERA12FA017
- 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. 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: ff047bcc267fd494435d8c3499ff0b576e67187af2d190a4d84c456c109d1d8b; retrieved 2026-09-13T21:55:08.285Z.