CHI00LA192 · Creed LANCAIR 235 LANCAIR 23
Creed LANCAIR 235 LANCAIR 23 · Accident: overrun during takeoff
From Rajkot International Airport (HSR) to Huron Regional Airport (HON)
Event
- NTSB case
- CHI00LA192
- 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
Creed LANCAIR 235 LANCAIR 23
- Aircraft type
- Creed LANCAIR 235
- 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
- N235RC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rajkot International Airport (HSR)To Huron Regional Airport (HON), Huron, SD
- 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
- Overrun
- 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 › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was attempting to depart on runway 19, and the aircraft failed to achieve flight. The aircraft was substantially damaged when it overran the end of the runway. The pilot received two weather briefings in the 70 minutes prior to the attempted takeoff. According to a written statement by the pilot, he 'departed runway 19. Aircraft never developed lift and overran runway end. Wind had shifted 180 degrees in 20-30 minutes and pilot did not re-check wind before takeoff.' Winds were reported as 010 at 16 knots 75 minutes prior to the accident, 040 at 9 knots gusting 17 knots 15 minutes prior to the accident, and 340 at 8 knots 45 minutes after the accident. Density altitude was 4,613 feet at the airport at the time of the accident. There is a windsock directly across the runway from the parking ramp.
Probable cause
the failure of the pilot to select the correct runway for takeoff. Factors to the accident were the inadequate preflight planning/preparation, the aborted takeoff not performed, and the tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA192
- Event ID
- 20001212X21384
- Case number
- CHI00LA192
- 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: e34b709903f9398b7dfad146264b90d75d1bf0ffa8108df002f6f7db31262619; retrieved 2026-09-22T12:44:10.330Z.