SEA89LA020 · Gates Learjet 25B
Gates Learjet 25B · Accident: overrun during landing
From Rogue Valley International-Medford Airport (MFR) to S07 · Bend, OR
Event
- NTSB case
- SEA89LA020
- 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
Gates Learjet 25B
- Aircraft type
- Learjet 25
- 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
- N143CK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rogue Valley International-Medford Airport (MFR), Medford, ORTo S07 · Bend, OR
- 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
- 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
- Airport facilities, runway/landing area condition › Icy
- Copilot/second pilot › Air/ground communications, inadequate
- Pilot in command › In-flight planning/decision, improper
Approximate · Estimated position: the centre of Bend, OR, the place the record names. Not the accident site.
NTSB narrative
THE PILOT VISUALLY INSPECTED THE RUNWAY WHILE MAKING A LOW PASS. HE REPORTED AFTERWARD THAT HE SAW NO EVIDENCE OF ICE OR SNOW ON THE RUNWAY. THE COPILOT CALLED UNICOM BUT WAS TOLD, WHILE THE AIRCRAFT WAS ON SHORT FINAL, THAT THE WINDS WERE CALM AND THE FAVORED RUNWAY WAS 16. THE COPILOT DID NOT ASK UNICOM ABOUT THE EXISTING RUNWAY CONDITIONS. DURING LANDING ROLL, ABOUT 2,000 FEET BEYOND THE LANDING THRESHOLD, THE AIRCRAFT BEGAN TO FISH TAIL AND SKID. THE PILOT WAS UNABLE TO STOP THE AIRCRAFT AND AN OVERRUN OCCURRED. DURING THE OVERRUN, THE AIRCRAFT STRUCK A BARBED WIRE FENCE AND THEN CAME TO REST IN A DITCH. AFTER THE ACCIDENT, BLACK ICE WAS FOUND TO BE PRESENT ON THE LAST ONE HALF OF THE RUNWAY. THIS AIRCRAFT WAS NOT EQUIPPED WITH THRUST REVERSERS. THE DRAG CHUTE WAS PLACARDED INOPERATIVE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA89LA020
- Event ID
- 20001213X27357
- Case number
- SEA89LA020
- 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: a5d3ee9a930e55f3f933d559eb6f2130846428ada8c11ca80a8e9204e4e4199a; retrieved 2026-09-18T19:16:28.145Z.