Panther Aviation Learjet 24-B accident
Learjet 24-B · Accident: overrun during landing
From Miami International Airport (MIA) to Orlando Executive Airport (ORL)
Event
- NTSB case
- ATL98LA078
- 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
Learjet 24-B
- Aircraft type
- Learjet 24
- 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
- N100DL
- Operator
- Panther Aviation
- Onboard fatalities
- Unknown
- Route
- From Miami International Airport (MIA), Miami, FLTo Orlando Executive Airport (ORL)
- 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
- Copilot/second pilot › Procedure inadequate
- Landing gear, normal brake system › Failure
Approximate · Estimated position: the centre of Orlando, FL, the place the record names. Not the accident site.
NTSB narrative
During landing roll, the airplanes normal braking system failed as a result of hydraulic fluid leak(s). At the pilot's request, deployment of the drag chute and application of the emergency braking system was performed by the first officer. According to the first officer, application of the emergency brakes caused the airplane to yaw. The first officer then pulled up on the emergency brakes handle followed by re-application of braking pressure. This action took place several times during the landing roll. Gates' Learjet Flight Training Manual (Page 105) states, 'In using the emergency brake lever, slow steady downward pressure is required. Each time the lever is allowed to return upward to the normal position, nitrogen is evacuated overboard. Brace your hand so you will not allow the lever to move up and down inadvertently on a bumpy runway.' The airplane overran the end of the runway and collided with the Instrument Landing System back course antennae.
Probable cause
The first officer's failure to perform proper emergency braking procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL98LA078
- Event ID
- 20001211X09993
- Case number
- ATL98LA078
- 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: 7d2a512c1c35da21804b5c8f0d6d0b8fbb9dfb155c2d0e10cb70cb752b7b8985; retrieved 2026-09-18T17:08:56.413Z.