NYC08LA021 · Luscombe 8A
Luscombe 8A · Accident: loss of control in flight during takeoff
From Roscoe Field (82J) to an unrecorded destination
Event
- NTSB case
- NYC08LA021
- 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
- N2099K
- Operator
- John Jenista
- Onboard fatalities
- Unknown
- Route
- From Roscoe Field (82J), Pensacola, FLTo not recorded
- 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
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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, tailwheel assembly › 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 takeoff, the tail wheel airplane was about 2 feet in the air when it suddenly veered to the left. The pilot attempted to land on the remaining runway; however, the airplane continued left and impacted trees to the left of the runway. Postaccident examination of the airplane revealed the tail wheel leaf spring was separated from the tail wheel assembly, and the wheel was "jammed" against the rudder. The fracture surface appeared to be a fatigue failure. The airplane's most recent annual inspection was completed about 9 months prior to the accident, with no anomalies noted. Checking the tail wheel spring was a requirement during an annual inspection. Without removing the outer clip, a pilot would not be able to check the spring during a preflight inspection.
Probable cause
The fatigue fracture of the tail wheel spring during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08LA021
- Event ID
- 20071106X01732
- Case number
- NYC08LA021
- 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: fa581a5a175017c9c23f7e92c4c31539d166bd6876e15d5872bec467774716f7; retrieved 2026-09-22T03:18:47.362Z.