CHI99LA093 · Mitsubishi 300
Mitsubishi 300 · Accident: overrun during landing
From Mineta San Jose International Airport (SJC) to Columbus Municipal Airport (OLU)
Event
- NTSB case
- CHI99LA093
- 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
- Instrument Meteorological Cond
Mitsubishi 300
- Aircraft type
- Mitsubishi 300
- 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
- N110DS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mineta San Jose International Airport (SJC), San Jose, CATo Columbus Municipal Airport (OLU)
- 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
- Substantial
Cause areas
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilots flew the VOR DME RWY 32 approach then circled over the runway to check conditions. The airplane overshot the turn onto final approach and witnesses recalled seeing the airplane in a steep left bank on final approach. Witnesses reported the airplane then touched down approximately 3,000 feet down the 5,682' long runway. The airplane traveled off the end of the runway into snow covered terrain where the nose gear and forward fuselage area were damaged. The runway was plowed just prior to the accident; however braking action was still reported as poor.
Probable cause
the pilot-in-command failed to attain the proper touchdown point during the landing. Factors associated with the accident were the rough, snow covered terrain encountered off the end of the runway, and the low ceiling at the time of the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA093
- Event ID
- 20001205X00136
- Case number
- CHI99LA093
- 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: 2b10fb02462dd277f2fd0fc43d96dfa2a2da9ddfc166fa5653a386cf94955f48; retrieved 2026-09-22T15:51:46.183Z.