Final NTSB investigations: Learjet 24
8 cases on aircraft the registry lists as Learjet 24. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1973 | 2 |
|---|---|
| 1978 | 1 |
| 1981 | 1 |
| 1984 | 1 |
| 1986 | 1 |
| 1990 | 1 |
| 1997 | 1 |
Where
Latest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5170302'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5170302'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB CHI97LA053Accident · No injuriesLimited investigationFinal reportLearjet 24 · Muscatine, IAthe pilot's failure to maintain directional control. A factor was the snow covered runway edge.NTSB ATL90LA080Accident · Serious injuriesLimited investigationFinal reportLearjet 24 · Anderson, SCElectrical arcing which resulted from a short in the pilot's map light circuit; a chafted wire contacted the oxygen supply line at the oxygen control panel in the cockpit. A factor in the accident was the inadequate design of the oxygen panel plumbing and…NTSB MIA86LA149Accident · Minor injuriesLimited investigationFinal reportLearjet 24 · Hollywood, FLThe plt stated he made a normal apch and landing but on rollout discovered he had no brakes. The acft traveled off the left side of the rwy and collided with a fence surrounding a ballpark. Post crash examination of the hydraulic system revealed that the…NTSB LAX85MA008Accident · 3 fatalMajor investigationFinal reportGates Learjet 24B · San Francisco, CAThe acft, a Gates lear jet 24B, modified by a howard/raisebach mark ii conversion, was cleared for takeoff on rwy 28L. Tower psnl estimated that the acft rotated for takeoff at 3200' down the rwy & was at aprx 200' AGL when the plt was instructed to contact…NTSB DCA82AA001Accident · 3 fatalClosedLearjet 24 · Felt, OKNTSB LAX79FA004Accident · 1 fatalClosedLear Jet 24 · Lancaster, CANTSB MIA73AM087Accident · 7 fatalClosedGates Lear 24 · Atlanta, GANTSB CHI73AC072Accident · 2 fatalClosedLear 24 · Belleville, MI