CHI95LA203 · Luscombe 8A
Luscombe 8A · Accident: on ground/water collision with terrain/water during takeoff
From Edward Getzelman Airport (7IL7) to an unrecorded destination
Event
- NTSB case
- CHI95LA203
- 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
- 0
- 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
- N2086K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Edward Getzelman Airport (7IL7)To 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 · rejected 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
- On ground/water collision with terrain/water
- 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
- Pilot in command › Lift-off, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT RATED PASSENGER BEGAN THE AIRPLANE'S TAKEOFF ROLL ON THE GRASS RUNWAY (2200' X 100'). THE PILOT REPORTED THAT THE AIRPLANE BECAME AIRBORNE BRIEFLY AT AN EXPECTED POINT, BUT THEN SETTLED BACK TO THE RUNWAY. THE PILOT PULLED THE THROTTLE AND BEGAN TO APPLY THE BRAKES TO ABORT THE TAKEOFF. THE AIRPLANE EXITED THE END OF THE RUNWAY, CROSSED A HAY FIELD, STRUCK A DITCH ALONG A CORNFIELD, AND BECAME INVERTED. THE TEMPERATURE AT THE TIME OF THE ACCIDENT WAS 92 DEGREES. THE PILOT HAD STATED THAT HE HAD PERFORMED A MENTAL CALCULATION OF THE AIRPLANE'S WEIGHT AND BALANCE PRIOR TO TAKEOFF. HE HAD DETERMINED THAT THE AIRPLANE WAS LOADED WITHIN LIMITS WITH TWO PEOPLE ABOARD. HE HAD STATED THAT HE WAS NOT ABLE TO COMPUTE THE AIRPLANE'S TAKEOFF DISTANCE BECAUSE THERE ARE NO PERFORMANCE CHARTS AVAILABLE FOR THE AIRPLANE.
Probable cause
the pilot's failure to attain liftoff speed. A factor in the accident was the ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA203
- Event ID
- 20001207X03682
- Case number
- CHI95LA203
- 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. 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: 92cd6718363378456e851183d52694d49792f5b1892a5cf4646302048eb21acf; retrieved 2026-09-21T13:12:52.986Z.