NTSB investigations: IAE V2500SERIES
5 cases on aircraft whose registry engine model is IAE V2500SERIES, 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
| 2002 | 1 |
|---|---|
| 2005 | 1 |
| 2006 | 2 |
| 2007 | 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.engine_model_code IN ('34601')
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 ('34601')
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 CHI08IA026Incident · Minor injuriesIncident investigationFinal reportAirbus Industrie A320-232 · Chicago, ILThe misrouted and reversed antiskid wiring by vendor maintenance personnel leading to the runway excursion. Contributing to the incident were the runway sign, the vendor's maintenance personnel not understanding the entire maintenance procedures in the dual…NTSB DEN07FA008Accident · No injuriesField investigationFinal reportMcDonnell Douglas MD-90-30 · Denver, COA fractured nose gear assembly spray deflector that blocked the nose gear from extending during landing, and resulted in an intentional nose gear up landing.NTSB DEN06IA083Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas MD-90-30 · Denver, COa brake fire for reasons undetermined. A contributing factor was the inadequate inspection by the maintenance crew.NTSB LAX05IA312Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 · Los Angeles, CAThe fatigue failure of two anti-rotation lugs due to repeated cyclic pre-landing tests, which allowed the nosewheels to deviate from the 0-degree position on landing gear retraction. A contributing factor was the design of the Brake Steering Control Unit…NTSB CHI03IA027Incident · No injuriesIncident investigationFinal reportAirbus Industrie A319-131 · Chicago, ILThe maintenance facililty improperly assembled and installed the nose landing gear shock absorber assembly. Factors were the improper assembly which allowed the nose gear to turn 90 degrees to the direction of travel.