Flight Operations Learjet 25B accident
Learjet 25B · Accident: overrun during landing
From Cincinnati Municipal Airport Lunken Field (LUK) to an unrecorded destination
Event
- NTSB case
- BFO93LA012
- 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
- Instrument Meteorological Cond
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
- N893WA
- Operator
- Flight Operations
- Onboard fatalities
- Unknown
- Route
- From Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OHTo 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 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
- Pilot in command › Distance, misjudged
- Pilot in command › Missed approach, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS ON AN ILS APPROACH TO RUNWAY 28 WHEN HE REPORTED THAT HE TOUCHED DOWN BEYOND THE POINT AT WHICH HE INTENDED TO LAND. THE PILOT WAS LANDING WITH A TAILWIND. THE PILOT REPORTED HEAVY RAIN AT THE TIME AND HE ADDED POWER TO CUSHION THE LANDING, WHICH CONTRIBUTED TO THE LOCATION OF THE TOUCHDOWN POINT. THE COPILOT STATED THAT HE EXPECTED THE PILOT TO DO A GO AROUND. ACCORDING TO WITNESSES THE AIRPLANE LANDED AT A LOCATION WITH ABOUT 2000 TO 2800 FEET OF RUNWAY DISTANCE REMAINING. THE AIRPLANE WENT OFF THE END OF THE RUNWAY AND COLLIDED WITH THE LOCALIZER TRANSMITTER FACILITY AND A FENCE. THE LANDING GEAR COLLAPSED DURING THE IMPACT SEQUENCE. THE RUNWAY IS 6015 FEET LONG AND THE LAST 2000 FEET DOWNSLOPES AT ABOUT A 0.85% GRADIENT. ACCORDING TO LEAR JET, THE LANDING DISTANCES BASED ON THE PREVAILING CONDITIONS, RESPECTIVELY, FOR A DRY AND WET RUNWAY ARE ABOUT 3350 AND 4690 FEET.
Probable cause
THE PILOT MISJUDGED DISTANCE AND ALTITUDE WHICH RESULTED IN A LANDING TOUCHDOWN WITH INSUFFICIENT RUNWAY LENGTH REMAINING AND A SUBSEQUENT LANDING OVERRUN. CONTRIBUTING WAS THE PILOT'S FAILURE TO INITIATE A GO AROUND, A TAILWIND, AND A DOWNSLOPING RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA012
- Event ID
- 20001211X16001
- Case number
- BFO93LA012
- 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: 4ab415e8b08eb8ac279dd421b6227828e5bfaa188b05e1f68f3705be81bd62a1; retrieved 2026-09-18T18:42:48.578Z.