Lindsay Air Cessna 310R accident
Cessna 310R · Accident: loss of control on ground/water during takeoff
From John Glenn Columbus International Airport (CMH) to Cincinnati Municipal Airport Lunken Field (LUK)
Event
- NTSB case
- NYC95LA153
- 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
- Charter & commuter
- 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
Cessna 310R
- Aircraft type
- Cessna 310
- 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
- N1723E
- Operator
- Lindsay Air
- Onboard fatalities
- Unknown
- Route
- From John Glenn Columbus International Airport (CMH)To Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OH
- 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 135: Air Taxi & Commuter
- 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 · roll/run
- 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 on ground/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane yawed left as she was transitioning from an intersection takeoff roll to lift off at 85 knots. The takeoff was aborted. The airplane ran off the end of the runway, struck a fence, and came to a stop on a highway. The nose gear collapsed. Examination of the airplane and engines did not disclose evidence of malfunction. The runway is 3,908 feet long. The usable runway from the intersection is 2,800 feet. The accelerate-stop distance was computed to be 2,695 feet for 85 knots.
Probable cause
A loss of directional control during takeoff for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA153
- Event ID
- 20001207X04057
- Case number
- NYC95LA153
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-07-12.
- API snapshot SHA-256: 55705e5d15ae8a9f7f2b9bb190733256eeb37e69b1babeee99ed03abf519e9ab; retrieved 2026-09-18T17:59:23.455Z.
- The NTSB's operator name is blank for N1723E; the operator shown is the name the NTSB records it doing business as.