NYC00LA232 · Triple S Aero Inc LANCAIR IVP LANCAIR IV
Triple S Aero Inc LANCAIR IVP LANCAIR IV · Accident: in flight collision with terrain/water on approach
From I20 · Xenia, OH to I73
Event
- NTSB case
- NYC00LA232
- 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
Triple S Aero Inc LANCAIR IVP LANCAIR IV
- Aircraft type
- Triple S Aero LANCAIR IVP
- 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
- N235LP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From I20 · Xenia, OHTo I73
- 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
- Approach · VFR pattern final
- 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
- In flight 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 › Proper glidepath, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident airplane was following a slower airplane to land. While on downwind, the accident pilot radioed that he was going to extend his downwind leg. After completing the base leg and turning final, the accident pilot radioed that he was performing some 'S' turns. While on final and approximately 50 feet short of the 3,500-foot runway, the accident airplane contacted a 15-foot high levee. The airplane then impacted the ground 45 degrees nose low, and slid onto the runway, where it came to rest. The minimum airspeed for the airplane in the landing configuration was 90 knots, which equated to 5 to 6 degrees nose high, and a landing distance of approximately 2,000 feet. The pilot was not aware of the levee while executing the approach. The runway identifier and touchdown markings were not visible because of wear. According to the Airport/Facility Directory, the runway threshold was displayed 225 feet. In addition, the airport diagram depicted the levee and how it related to the runway.
Probable cause
The pilot's failure to maintain a proper glide path to the runway which resulted in the airplane contacting a 15-foot levee just short of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA232
- Event ID
- 20001212X21841
- Case number
- NYC00LA232
- 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: 8700aa3a3fa79f85d6e83217ff910761a596c1e9f9ec04a09638fa3e4d456fc7; retrieved 2026-09-21T10:29:41.569Z.