SEA07LA098 · Luscombe 8F
Luscombe 8F · Accident: airframe, component or system failure during landing
From Love Field (97FL) to Ocala International Airport - Jim Taylor Field (KOCF)
Event
- NTSB case
- SEA07LA098
- 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 8F
- 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
- N882JB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Love Field (97FL), WEIRSDALE, FLTo Ocala International Airport - Jim Taylor Field (KOCF), Ocala, 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
- 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, axle › Failure, total
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 reported that during the landing roll on runway 18, the aircraft suddenly veered to the right. The pilot attempted to control the aircraft using the rudder and control stick with no success. The left wing struck the ground and the right wing raised as the left main landing gear collapsed and the aircraft came to a stop. At the time of the accident, the local METAR information was reporting the winds from 250 degrees at 12 knots. The sky was clear. In a post accident inspection, an airframe mechanic determined that the left axle broke at the exit of the landing gear strut.
Probable cause
The failure of the left main axle during the landing roll, which resulted in the collapse of the left main landing gear. A crosswind on the landing runway was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07LA098
- Event ID
- 20070417X00428
- Case number
- SEA07LA098
- 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: 315f170515f6552fac4b3f2736615cb654a786bd65f8665b1a272b7bd1ac1482; retrieved 2026-09-22T03:55:47.787Z.