NTSB investigations: Rolls-Royce TAY-650-15
14 cases on aircraft whose registry engine model is Rolls-Royce TAY-650-15. 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
| 1993 | 2 |
|---|---|
| 1994 | 1 |
| 1997 | 1 |
| 1998 | 3 |
| 2000 | 2 |
| 2001 | 2 |
| 2002 | 2 |
| 2003 | 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 ('54557'))
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 ('54557'))
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 NYC03FA190Accident · No injuriesField investigationFinal reportFokker F.28 Mk 0100 · Flushing, NYAn in-flight collision with birds.NTSB CHI02IA270Incident · No injuriesIncident investigationFinal reportFokker 100 · Minneapolis, MNThe improper installation of the #2 main landing gear wheel, including the axle nut not being properly torqued and safetied, which resulted in the wheel separation during takeoff.NTSB FTW02LA088Accident · No injuriesLimited investigationFinal reportFokker F-28 MK-100 · Dallas, TXThe ground crew inadvertent application of deicing fluid in the auxiliary power unit resulting in an overspeed and turbine wheel burst. A contributing factor was the gusty wind.NTSB FTW01FA127Accident · No injuriesField investigationFinal reportFokker F28 Mk 0100 · DFW Airport, TXA forging fold that was introduced during the manufacture of the right main landing, which resulted in a fatigue crack in the right main landing gear cylinder, and its subsequent failure during landing.NTSB CHI01IA102Incident · No injuriesIncident investigationFinal reportFokker F28 MK 0100 · Montreal, Canadathe inaccurate aircraft deicing service the ground personnel performed alowing fluid injestion and the auxiliary power unit's turbine failure while standing. A factor was the auxiliary power unit's overspeed.NTSB NYC00IA231Incident · No injuriesIncident investigationFinal reportFokker F-100 · Norfolk, VAThe failure of the airplane's ground/flight switch and a malfunction of the thrust reverser deploy switch, which resulted in an in-flight thrust reverser deployment.NTSB CHI00LA076Accident · Serious injuriesLimited investigationFinal reportFokker F28 MK100 · Chicago, ILthe driver of the refueling truck fell asleep which resulted in him not maintaining clearance with the parked aircraft. Factors associated with the accident were severe obstructive sleep apnea and significant hypersomnolence which resulted in chronic fatigue.NTSB CHI98LA154Accident · Serious injuriesLimited investigationFinal reportFokker F-28 MK100 · Ft. Wayne, INIn-flight encounter with turbulence.NTSB NYC98LA075Accident · Serious injuriesLimited investigationFinal reportFokker F-100 · Philadelphia, PAThe driver's failure to maintain clearance from the parked airplane. Related factors were night conditions and the driver's diverted attention.NTSB MIA98FA089Accident · No injuriesField investigationFinal reportFokker F28 MK 0100 · Birmingham, ALWere the 1) the inoperative alternate anti-skid control valve due to the disconnected electrical connector on the parking brake shut-off valve, the area was inspected 2 days earlier 2) the total loss of the hydraulic system resulting in the inability of the…NTSB MIA98FA025Accident · No injuriesField investigationFinal reportFokker F100 · Charlotte, NCImproper written instructions (job/task card) by company maintenance personnel. The procedures did not reflect the correct manufactures maintenance manual servicing procedure, and did not ensure that the proper tool (replenishing gun) was available for the…NTSB ATL94IA088Incident · No injuriesIncident investigationFinal reportFokker F28 MK 0100 · Charlotte, NCThe improper rigging of the nose wheel steering system by company maintenance personnel.NTSB BFO93IA070Incident · Minor injuriesIncident investigationFinal reportFokker F28-MK-0100 · Pittsburgh, PAThe improper installation of the spacers by the mechanic and the unclear information supplied from the manufacturer and operator regarding the installation of the spacers.NTSB CHI93IA110Incident · No injuriesIncident investigationFinal reportFokker 100 · Chicago, ILFailure of the company station manager to follow proper dispatch procedures, and ice accumulation on the nose gear locking mechanism. Factors related to the incident were: wet snow (slush) on the runway at the departure airport, and inadequate design which…