MIA88LA027 · Learjet 35A
Jack Eckerd Learjet 35A · Accident: airframe, component or system failure while taxiing
From PBI · W. PALM BCH, FL to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- MIA88LA027
- 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
- Instrument Meteorological Cond
Learjet 35A Possible conflict
- 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
- N900JE
- Operator
- Jack Eckerd
- Onboard fatalities
- Unknown
- Route
- From PBI · W. PALM BCH, FLTo 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 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
- Taxi · from runway
- 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
- Brakes(emergency) › Not attained
- Brakes(normal) › Not possible
- Flt control syst, boost system › Failure, partial
- Fluid, hydraulic › Loss, total
- Landing gear, normal brake system › Loss, total
Approximate · Estimated position: the centre of Clearwater, FL, the place the record names. Not the accident site.
NTSB narrative
DURING TAXI UP TO HANGAR UNDER DIRECTION OF LINEMAN AFTER ARRIVAL THE FLT EXPERIENCED LOSS OF HYDRAULIC PRESSURE AND BRAKES. THE PLT COULD NOT ACTIVATE THE EMERGENCY BRAKES PRIOR TO ROLLING INTO THE HANGAR AND COLLIDING WITH TWO ACFT PRIOR TO COMING TO REST. EXAMINATION OF THE ACFT REVEALED THE SPOILERON CONTROL VALVE ASSEMBLY SUFFERED FRACTURE OF A NAS1351-4H-24P SCREW DUE TO HYDROGEN EMBRITTLEMENT CRACKING WHICH CAUSED THE SCREW HEAD TO SEPARATE FROM THE SCREW SHANK. THE SCREW IS ONE OF THREE WHICH RETAINS THE SELECTOR VALVE TO THE MANIFOLD ASSEMBLY. WHEN THE SCREW FAILED THE VALVE BODY SEPARATED ALLOWING LOSS OF ALL USABLE HYDRAULIC FLUID. THE SOURCE OF THE MIGRATING ELEMENTAL HYDROGEN INTO THE FRACTURE AREA COULD NOT BE DETERMINED. THE VALVE ASSEMBLY HAD BEEN INSTALLED IN THE ACFT SINCE MANUFACTURE IN 1977 AND HAD ACCUMULATED 5,642 HOURS. THE VALVE IS MAINTAINED ON CONDITION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA88LA027
- Event ID
- 20001213X32579
- Case number
- MIA88LA027
- 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: 57b2fea6e529b2e9b18ed1fd355993ed8edf4b4cacfdaebb4b24b23a8a6f28b9; retrieved 2026-09-23T11:40:39.144Z.