CHI90LA189 · Mitsubishi MU-300
Mitsubishi MU-300 · Accident: overrun during landing
From Millard Airport (MLE) to an unrecorded destination
Event
- NTSB case
- CHI90LA189
- 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
Mitsubishi MU-300
- Aircraft type
- Mitsubishi MU-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
- N800TJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Millard Airport (MLE), Omaha, NETo 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
- Substantial
Cause areas
- Pilot in command › Brakes(normal), delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATES HE LANDED SOFTLY, COMMENCED AERODYNAMIC BRAKING, THEN LOWERED THE NOSEWHEEL TO THE RUNWAY AND APPLIED WHEEL BRAKES WITH ANTI-SKID ENGAGED. HE STATES THERE WAS NO RESPONSE TO BRAKES. THE AIRPLANE OVERRAN THE RUNWAY, SUSTAINING SUBSTANTIAL DAMAGE. TEST OF THE BRAKE SYSTEM REVEALED NO DISCREPANCY. MAIN LANDING GEAR STRUTS WERE FOUND OVERPRESSURIZED. AN ANTI-SKID LOGIC CIRCUIT INTERRUPTS BRAKE ACTIVATION UNTIL LOAD SWITCHES ON THE MAIN STRUTS SENSE WEIGHT ON THE WHEELS (STRUTS LESS THAN FULLY EXTENDED). THERE WERE THUNDERSTORMS AND RAIN IN THE VICINITY AND THE RUNWAY WAS WET. THE RIGHT MAIN TIRE TRACK WAS IDENTIFIABLE AS A CLEAN STRIP ACROSS THE ASPHALT AND WHITE PAINT MARKINGS AT RUNWAY DEPARTURE END.
Probable cause
THE PILOT'S DELAYED DETERMINATION OF TRACTION OR BRAKING ACTION UNTIL TOO LITTLE RUNWAY REMAINED TO GO AROUND OR TO EMPLOY ALTERNATE MEANS OF ACTIVIATING THE BRAKES. CONTRIBUTING TO THE ACCIDENT WAS THE OVERSERVICING OF THE MAIN GEAR STRUTS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA189
- Event ID
- 20001212X23650
- Case number
- CHI90LA189
- 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: 16a7e4d7e67b05180110cb7b3318a8fba7a8f58345cd174a3af0a1091436380b; retrieved 2026-09-23T05:33:36.186Z.