MIA99FA267 · Learjet 24
Learjet 24 · Accident: airframe, component or system failure during landing
From Sarasota Bradenton International Airport (SRQ) to Lee Gilmer Memorial Airport (GVL)
Event
- NTSB case
- MIA99FA267
- 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
- General aviation
- 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
- 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
- N224SC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sarasota Bradenton International Airport (SRQ), Sarasota, FLTo Lee Gilmer Memorial Airport (GVL)
- 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 91: General Aviation
- 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
- Airframe, component or system failure
- 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
- Other maintenance personnel › Maintenance, inspection, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilots stated that approach and landing were normal. During landing rollout, about 2,000 feet down the runway, the brakes became ineffective. The aircraft continued to roll off the end of the runway, down an embankment, across a 4 lane road, and came to rest in a drainage ditch. Post-crash examination of the main landing gear brakes showed that 3 out of the 4 brake assemblies were worn beyond allowable limits and all 4 antiskid wheel generators were not producing voltage within the allowable limits. The outboard right main tire had failed during landing roll do to the antiskid becoming inoperative due to the low voltage of the wheel generator. The airplane had received an A-1 through A-6 inspection 2 days before the accident and this was the first flight since the inspection. The A-5 inspection requires inspection of the landing gear brake assemblies for wear, cracks, hydraulic leaks, and release.
Probable cause
The inadequate inspection of the main landing gear brake assemblies, which lead to operation of the aircraft with worn brakes that failed during the landing roll. Contributing factors were the descending terrain, roadway and ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99FA267
- Event ID
- 20001212X19824
- Case number
- MIA99FA267
- 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: 1a40ecb9179946bbf4a38413d543e973952feb7c4447614498bc37a764b7c702; retrieved 2026-09-21T10:49:44.005Z.