NTSB investigations: Rolls-Royce RB-211 series
4 cases on aircraft whose registry engine model is Rolls-Royce RB-211 series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1997 | 1 |
|---|---|
| 1999 | 1 |
| 2003 | 1 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('54555')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
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.engine_model_code IN ('54555')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
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 ENG08IA001IncidentIncident investigationFinal reportBoeing 757-225 · Charlotte, NCThe truck beam fracture initiated by fatigue and stress corrosion cracking from pits that were present on the ID surface of the truck beam, under the protective finishes. Crack propagation occurred by alternating modes of stress corrosion cracking and fatigue…NTSB MIA03IA168Incident · No injuriesIncident investigationFinal reportBoeing 757-223 · Miami, FLThe failure of maintenance personnel from the aircraft operator to identify a missing left main landing gear truck beam shield and damage to the left main landing gear truck beam which resulted in the fracture of the truck beam as a result of stress corrosion…NTSB LAX99FA315Accident · Serious injuriesField investigationFinal reportBoeing 757-2S7 · Agua Caliente, AZthe systemic failure of the airline's maintenance department to identify and correct the long standing history of intermittent faults, nuisance warnings, and erratic behavior in this airplane's GPWS system. Also causal is the airline's failure to perform the…NTSB LAX97FA276Accident · Serious injuriesField investigationFinal reportLockheed L-1011-385-1-15 · Honolulu, HIthe cumulative distance taxied immediately prior to takeoff that precipitated an excessive heat buildup in the tires and resulted in the bead separation of a single tire during the takeoff roll. The absence of cockpit procedures/directives or monitoring…