NTSB investigations: Pratt & Whitney JT9D series
28 cases on aircraft whose registry engine model is Pratt & Whitney JT9D series. 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
| 1970 | 1 |
|---|---|
| 1983 | 2 |
| 1984 | 1 |
| 1989 | 1 |
| 1993 | 2 |
| 1994 | 1 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 3 |
| 2001 | 2 |
| 2003 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2008 | 4 |
| 2010 | 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 ('52054'))
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 ('52054'))
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 ENG11WA005Incident · No injuriesForeign investigationBoeing 747 · Chubu, Japan, JapanOn November 28, 2010, at about 06:00 Japan Standard Time (JST), after taking off from Chubu Centrair International Airport, operating as flight EIA238, the crew of an Evergreen International Airlines Boeing 747-200F airplane, registration number N482EV,…NTSB CEN09LA114Accident · No injuriesLimited investigationFinal reportBoeing 747-212B · Rockford, ILThe ground crew's failure to maintain clearance from the light pole while directing the airplane to parking.NTSB DCA08RA078Accident · 2 fatalForeign investigationBoeing 747-200FM · Madrid, ColombiaOn July 7, 2008, at 0357 local time, a Boeing 747-200FM, N714CK, operated by Kalitta Air as Centurion Airlines flight 164, was destroyed during a forced landing in Madrid, Cundinamarca, Colombia, shortly after taking off from El Dorado International Airport…NTSB DCA08RA063Accident · No injuriesForeign investigationBoeing B747-200 · Brussels, BelgiumimportNTSB ENG08IA022Incident · No injuriesIncident investigationFinal reportBoeing 747 · Newark, NJAn engine fire in the No. 3 engine due to the failure of, and subsequent flammable fluid leak from, one of three fuel or hydraulic lines located in the engine's accessory raceway that ignited when the fluid came in contact with the hot engine cases.…NTSB DCA06WA049Accident · No injuriesForeign investigationBoeing 747-200 · Rio Negro, ColombiaNTSB ENG05RA021Incident · No injuriesForeign investigationBoeing 747-200B · Sapporo, JapanNTSB SEA04IA010Incident · No injuriesIncident investigationFinal reportBoeing 747-100 · Lyon, FranceAn undetermined malfunction in an aircraft system while in cruise flight leading to a fire in the engine number four B Loop portion (Card A16) of the fire detection controls cardfile.NTSB ANC02LA008Accident · No injuriesLimited investigationFinal reportBoeing 747-128 · Anchorage, AKThe flight crew's inadequate preflight planning, and failure to calculate the airplane weight and balance prior to departure.NTSB DCA01MA063Accident · 65 fatalMajor investigationFinal reportBoeing 767-200ER · New York City, NYThe Safety Board did not determine the probable cause and does not plan to issue a report or open a public docket. The terrorist attacks of September 11, 2001 are under the jurisdiction of the Federal Bureau of Investigation. The Safety Board provided…NTSB ANC01IA007Incident · No injuriesIncident investigationFinal reportBoeing 747-251F · Anchorage, AKRupture and disintegration of main landing gear tires during the takeoff roll, and subsequent damage to the right main gear hydraulic brake system.NTSB CHI00IA152Incident · No injuriesIncident investigationFinal reportBoeing 767-222 · Lafayette, INThe blocked drain lines in the canted pressure deck and the frozen aileron cable.NTSB DCA00WA049Incident · No injuriesForeign investigationBoeing 747-200 · IrelandNTSB DCA99WA064Accident · No injuriesForeign investigationAirbus Industrie A310 · Manila, PhilippinesNTSB SEA99IA032Incident · Minor injuriesIncident investigationFinal reportBoeing 747-238B · Pacific Ocean (Pacific Ocean)An encounter with Clear Air Turbulence at Flight Level 330.NTSB DCA98WA069Incident · No injuriesForeign investigationBoeing 747 · Amsterdam, NetherlandsNTSB MIA97IA147Incident · No injuriesIncident investigationFinal reportBoeing 747-2R7F · Miami, FLdisbonding and separation of the right inboard wing fixed trailing edge panel during cruise flight, which resulted in damage to the inboard fore flap and inboard mid flap, and a subsequent precautionary landing at the departure airport.NTSB IAD96IA098Incident · No injuriesIncident investigationFinal reportBoeing 747-136 · Jamaica, NYfailure of the constant speed drive (CSD) to disconnect from the generator. Contributing to the cause was the failure of the FAA approved overhaul facility to follow the manufacturer's overhaul manual.NTSB MIA95WA143Accident · No injuriesForeign investigationBoeing B-747-238 · Panama City, PanamaNTSB CHI95LA078Accident · No injuriesLimited investigationFinal reportBoeing 747-238B · Belleville, MIthe failure of company maintenance personnel to adequately secure the cargo pallets, and the failure of the flightcrew to detect the deficiency during their preflight inspection.NTSB DCA94RA037Accident · No injuriesForeign investigationBoeing 747 · Narita, JapanNTSB ANC93IA188Incident · No injuriesIncident investigationFinal reportBoeing 747-200 · Anchorage, AKForeign object damage to the compressor forward fan assembly as a result of the ingestion of a bird.NTSB NYC93IA184Incident · No injuriesIncident investigationFinal reportBoeing 747-200 · New York, NYThe improper installation of the fairing by company maintenance personnel, resulting in the infligh separation of the fairing in flight.NTSB NYC89IA123Incident · No injuriesIncident investigationFinal reportFairchild Swearingen SA-227AC · New York, NYThe failure of the swearingen flight crew to properly identify the airplane they were to follow, prior to accepting the visual approach to runway 31R.NTSB DCA84AA025Accident · No injuriesFinal reportBoeing 727-222 · Denver, COBefore takeoff, the crew of N7647U (ua flt 663) noted cumulus clouds & virga in the area. At 1327, a Dehavilland dash 7 crew rprtd a 25 kt loss of airspeed, but svrl other acft then took off without rprtg a problem. Due to radio conjestion,the captain did not…NTSB DEN84IA041Incident · No injuriesIncident investigationFinal reportBoeing 767 · Denver, COOn takeoff roll the no 3 wheel on the right main landing gear fell off the acft. The acft returned and landed without further incident. The wheel bearing was found faileddue to cosmoline contamination.NTSB LAX84IA040Incident · No injuriesIncident investigationFinal reportBoeing 767 · San Francisco, CADuring pushback the right wingtip of the Boeing 767 struck the rudder of a Douglas DC-9 parked at the adjacent gate. The B-767 was being pushed back by two mechanics, one on thetug & one under the left wing.NTSB SEA70IS044Incident · No injuriesClosedBoeing 747 · Moses Lake, WA