FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Med Flight Air Ambulance Learjet 35 A accident

2 Jan 2024 · San Marcos, TX, United States

Learjet 35 A · Accident: runway excursion during landing

From Albuquerque International Sunport (ABQ) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24LA085
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 35 A

Aircraft type
Learjet 35
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
N46MF
Onboard fatalities
Unknown
Route
From Albuquerque International Sunport (ABQ), Albuquerque, NMTo not recorded
Aircraft age
About 43 years (built 1981)
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
Defining eventThe 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
Runway excursion
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

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While in cruise flight approaching the descent for landing, the crew received automated weather information that was about an hour old that reported wind from the northeast. The crew selected the precision approach to the airport, which landed toward the southeast. Unknown to the crew, the wind had shifted from the northeast to a tailwind from the northwest and had increased in velocity with gusts. They did not request current weather during the descent, and no weather information was provided by the tower controller. Recorded data for the approach revealed that the airplane had a 15-knot tailwind and a steep descent rate before the landing, which exceeded the company’s general operation manual’s criteria for a stabilized approach. Data showed the airplane touched down at 124 knots about halfway down runway 13, which was wet, with about 2,600 ft remaining. The captain applied the brakes and reported that they were unresponsive. The airplane overran the runway and traveled into a grass field. The nose landing gear separated from the airplane, resulting in substantial damage to the fuselage. The first officer (FO) stated that he perceived that the airplane had hydroplaned on landing. A performance study conducted for the accident flight using available airplane and weather information revealed the landing distance for the airplane on a wet/contaminated runway was 4,550 ft; runway 13 was 5,601 ft. The calculated landing reference speed to included “half the gust factor” was 125 knots. The manufacturer’s flight manual lists the maximum tailwind component as 10 knots. The landing data for the flight could not be calculated since the actual tailwind component at the time of the landing exceeded 10 knots.

Probable cause

The captain’s failure to perform a go-around following an unstable approach while landing with a gusty tailwind, which resulted in the airplane touching down long on the wet runway with insufficient distance to stop. Contributing to the accident was the crew’s unawareness of the prevailing winds and first officer’s decision to not call a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA085
Event ID
20240108193628
Case number
CEN24LA085
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: b686038d15e9b484f9e9118dda68c05c175d85bf421a0b570258b870c6c376cd; retrieved 2026-09-16T18:25:20.515Z.