NTSB investigations: Learjet 25
8 cases on aircraft the registry lists as Learjet 25. 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
| 1972 | 1 |
|---|---|
| 1973 | 1 |
| 1983 | 1 |
| 1989 | 1 |
| 2001 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2012 | 1 |
Where
Open the mapLatest 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5170506'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5170506'))
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 DCA13RA025Accident · 7 fatalForeign investigationLearjet 25 · Monterrey, MexicoNTSB NYC07LA170Accident · No injuriesLimited investigationFinal reportLearjet 25 · St. Augustine, FLA loss of power on both engines for an undetermined reason.NTSB DFW05CA174Accident · No injuriesData collectionFinal reportLearjet 25 · Amarillo, TXThe pilot's failure to maintain directional control during the landing roll. A contributing factor was the prevailing crosswind.NTSB NYC01FA214Accident · 2 fatalField investigationFinal reportLearjet 25 · Ithaca, NYThe pilot's failure to maintain a proper climb rate while taking off at night, which was a result of spatial disorientation. Factors in the accident were the low visibility and cloud conditions, and the dark night.NTSB BFO89FA024Accident · No injuriesField investigationFinal reportLearjet 25 · Roanoke, VACo-pilots poorly planned approach which resulted in an overrun landing. A contributing factor was the captains poor supervision of the approach and landing.NTSB DCA83AA023Accident · 2 fatalFinal reportGates Learjet 25 · Newark, NJThe acft was on a ngt check courier flt. During arrival, the indicated airspeed was well above the legal limit of 250 ktfor flt below 10,000 ft. rwy 4R was selected for landing after the crew were advised that their original choice (rwy 11)was noise…NTSB MKC74AK012Accident · 3 fatalClosedGates Lear 25 · Lincoln, NENTSB FTW72AF044Accident · 9 fatalClosedGates Lear 25 · Victoria, TX