Flight Management Gates Learjet LEAR 25B accident
Gates Learjet LEAR 25B · Accident: overrun during landing
From Tulsa International Airport (TUL) to an unrecorded destination
Event
- NTSB case
- LAX92LA069
- 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 LEAR 25B
- Aircraft type
- Learjet LEAR 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
- N44PA
- Operator
- Flight Management
- Onboard fatalities
- Unknown
- Route
- From Tulsa International Airport (TUL), Tulsa, OKTo 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 › Airspeed(vref), excessive
- Pilot in command › Altitude, excessive
- Pilot in command › Go-around, not performed
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
3THE PILOT AND CO-PILOT REPORTED IN THEIR WRITTEN STATEMENTS THAT THE AIRPLANE WAS ABOVE GLIDESLOPE ON THE FINAL APPROACH. THEY SAID THE AIRPLANE TOUCHED DOWN ABOUT 1,500 FEET FROM THE APPROACH END OF THE 4,700 FEET LONG RUNWAY. THE PILOT SAID HE APPLIED THE BRAKES BUT COULD NOT STOP THE AIRPLANE ON THE RUNWAY. THE AIRPLANE DEPARTED THE END OF THE RUNWAY AND CONTINUED FORWARD OVER ROUGH AND UNEVEN TERRAIN. THE MAIN LANDING GEAR SHEARED OFF AND PENETRATED BOTH WINGS. THE AIRPLANE CAME TO A STOP IN A GULLY. OTHER WITTNESSES LOCATED ON THE GROUND AND IN THE AIR TRAFFIC CONTROL TOWER REPORTED THE AIRPLANE WAS 'HIGH AND FAST' AND TOUCHED DOWN AT ABOUT MIDFIELD OR AFTER.
Probable cause
THE PILOT NOT ATTAINING THE PROPER TOUCHDOWN POINT BECAUSE OF EXCESSIVE ALTITUDE AND AIRSPEED, AND THE PILOT'S FAILURE TO PERFORM A GO-AROUND. A FACTOR IN THIS ACCIDENT WAS THE ROUGH AND UNEVEN TERRAIN WHICH WAS ENCOUNTERED AFTER THE AIRCRAFT DEPARTED THE RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX92LA069
- Event ID
- 20001212X18623
- Case number
- LAX92LA069
- 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: 8fb18c2a2d3cfe7e1c078e9cbf8a200154de2375707b7be5754f03c3483b3cba; retrieved 2026-09-18T18:49:43.010Z.