CHI90LA172 · Learjet LR-24D
Learjet LR-24D · Accident: overrun during landing
From South Bend International Airport (SBN) to an unrecorded destination
Event
- NTSB case
- CHI90LA172
- 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
Learjet LR-24D
- Aircraft type
- Learjet LR-24
- 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
- N45CP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Bend International Airport (SBN), South Bend, INTo 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
- Landing · landing roll
- 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
- Destroyed
Cause areas
- Pilot in command › Planned approach, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THAT AFTER REFUELING AT A NEARBY AIRPORT, HE AND HIS CO-PILOT RETURNED TO BENTON HARBOR, MICHIGAN TO POSITION THE AIRCRAFT FOR AN ORGAN TRANSPLANT FLIGHT. HE STATED THAT HE SHOT THE ILS APPROACH TO RUNWAY 27, AND BROKE OUT AT ABOUT 1100 FEET, WITH AN ESTIMATED 6 MILES VISIBILITY. HE REPORTED THAT THE 'HIGH INTENSITY APPROACH LIGHTS WERE ON FULL BRIGHT, DESTROYING MY NIGHT VISION....'HE STATED THAT ONCE THEY PASSED THE APPROACH LIGHTS HE WAS UNABLE TO SEE THE RUNWAY SURFACE, AND THE THE AIRCRAFT 'MUST HAVE FLOATED....'HE WAS UNABLE TO STOP BEFORE RUNNING OFF THE END OF THE RUNWAY. THE CO-PILOT'S STATEMENT CONCURS. THE PILOT-IN-COMMAND REPORTED A TOTAL FLIGHT TIME OF 8,300 HOURS, INCLUDING 2,100 HOURS IN THE ACCIDENT MAKE AND MODEL, AND 5,000 HOURS OF NIGHT FLIGHT EXPERIENCE.
Probable cause
PILOT-IN-COMMAND'S MISJUDGED APPROACH TO LANDING, WHICH RESULTED IN THE AIRCRAFT RUNNING OFF THE DEPARTURE END OF THE RUNWAY INTO A RAVINE. THE LATE, DARK NIGHT, IFR CONDITIONS CONTRIBUTED TO THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA172
- Event ID
- 20001212X23638
- Case number
- CHI90LA172
- 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: da1fc4abb2d7212e2bab58124ea73642975da19856af4bbd55c0b718d597115a; retrieved 2026-09-23T05:34:35.887Z.