NTSB investigations: Pratt & Whitney JT8D-9 series
74 cases on aircraft whose registry engine model is Pratt & Whitney JT8D-9 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
| 1969 | 1 |
|---|---|
| 1971 | 1 |
| 1973 | 2 |
| 1974 | 1 |
| 1976 | 1 |
| 1977 | 4 |
| 1979 | 2 |
| 1980 | 1 |
| 1981 | 3 |
| 1982 | 2 |
| 1983 | 5 |
| 1984 | 5 |
| 1985 | 1 |
| 1986 | 5 |
| 1987 | 3 |
| 1988 | 2 |
| 1989 | 4 |
| 1990 | 5 |
| 1992 | 3 |
| 1993 | 2 |
| 1994 | 2 |
| 1995 | 1 |
| 1996 | 2 |
| 1997 | 5 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 3 |
| 2002 | 2 |
| 2005 | 1 |
| 2008 | 1 |
| 2017 | 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 ('52048'))
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 ('52048'))
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 DCA18CA056Accident · No injuriesData collectionFinal reportMcdonnell Douglas DC 9 33F · Bethel, AKfailure of a cargo tie-down fastener, resulting in unsecured cargo striking the pressure bulkhead.NTSB DCA08RA077Accident · 1 fatalForeign investigationMcdonnell Douglas DC-9-15 · Saltillo, MexicoimportNTSB CHI05MA111Accident · Serious injuriesMajor investigationFinal reportMcDonnell Douglas DC-9-51 · Minneapolis, MNthe Captain of the other aircraft's decision to shutdown the left engine during taxi with no hydraulic pressure on the right side hydraulic system to effectively operate the brakes, steering, or thrust reversers. A factor was the fatigue fracture of the…NTSB NYC02LA056Accident · No injuriesLimited investigationFinal reportMcDonnell Douglas DC-9-32 · Dulles, VAThe lack of direction from the operator on how to perform pushbacks on an icy ramp, which led to the tug driver positioning the tug at an angle to the nose of the airplane that allowed the airplane to move forward and strike the tug. Factors were the…NTSB ATL02LA029Accident · No injuriesLimited investigationFinal reportBoeing 727-200 · Greenville, SCThe tug driver's failure to maintain control of the airplane during pushback resulting in the tug colliding with the airplane. A factor was ice on the ramp.NTSB NYC01FA062Accident · No injuriesField investigationFinal reportMcDonnell Douglas DC-9-51 · Jamaica, NYThe low cycle fatigue fracturing of the approach lighting cover securing bolts.NTSB LAX00IA127Incident · No injuriesIncident investigationFinal reportBoeing 727-232 · San Francisco, CAfailure of the right main landing gear to fully extend for undetermined reasons.NTSB CHI00IA087Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC9-32 · Milwaukee, WIthe chafing of the internal water heater wire. A factor was the missing ground strap.NTSB CHI00IA009Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-9-51 · Chicago, ILThe landing gear's wheel separation due to the improper installation of the wheel by company maintenance personnel using incomplete maintenance steps, and the maintenance steps not listed in the manufacturer's manual. Factors were the airport perimeter wall…NTSB CHI99FA102Accident · No injuriesField investigationFinal reportDouglas DC-9-15F · Kansas City, MOingestion of birds into both engines, resulting in foreign object damage and the subsequent partial power loss to both engines. A factor relating to this accident was the dark night.NTSB NYC98LA177Accident · No injuriesLimited investigationFinal reportDouglas DC-9-30 · Philadelphia, PAthe failure of the fuel truck driver to follow airport operating procedures, and yield the right-of-way to the airplane. Factors were the stopped airplane, which obscured the fuel truck from the approaching airplane and the approaching airplane from the fuel…NTSB CHI98LA053Accident · No injuriesLimited investigationFinal reportMcDonnell Douglas DC-9-15 · Syracuse, NYThe pilot's inadequate preflight to ensure that the cargo pallets were properly secured. Also causal was the the improper securing of the pallets.NTSB CHI97IA212Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-9-15 · Memphis, TNthe spoiler cable was misrouted by unknown maintenance personnel.NTSB FTW97LA215Accident · Serious injuriesLimited investigationFinal reportBoeing 737-291A · Albuquerque, NMthe sudden encounter with clear air turbulence.NTSB DCA97IA030Incident · No injuriesIncident investigationFinal reportBoeing 727F · Atlanta, GAA jammed elevator resulting from a backed-off elevator trim tab nut.NTSB CHI97LA060Accident · Serious injuriesLimited investigationFinal reportMcDonnell Douglas DC-9-51 · Cape Girardeau, MOclear air turbulence encountered by the flight.NTSB LAX96IA300Incident · No injuriesIncident investigationFinal reportDouglas DC-9-51 · Honolulu, HIImproper installation of a flexible hydraulic hose by company maintenance personnel and inadequate inspection of the work by company inspectors which resulted in the loose hose becoming entangled in the nose gear linkage, preventing complete extension of the…NTSB MIA96LA107Accident · No injuriesLimited investigationFinal reportBoeing 727-225 · Memphis, TNfailure of the flightcrew to maintain clearance from construction equipment while taxiing after landing. Factors relating to the accident were: failure of operator personnel to supply the flightcrew with current NOTAM information, failure of ATC personnel to…NTSB LAX95IA229Incident · No injuriesIncident investigationFinal reportBoeing 737-200 · Elko, NVin-flight separation of the aileron as a result of inadequate bonding.NTSB FTW94LA229Accident · Serious injuriesLimited investigationFinal reportBoeing 737-2H4 · South Bend, INThe encounter with unforcasted and unreported turbulence.NTSB LAX94IA206Incident · Minor injuriesIncident investigationFinal reportBoeing 737-209 · Honolulu, HIThe failure of the battery transfer relay resulting in multiple system failures.NTSB FTW93WA107Accident · No injuriesForeign investigationBoeing 727-232 · Guadalajara, MexicoNTSB NYC93IA064Incident · No injuriesIncident investigationFinal reportBoeing 727-200 · Newark, NJThe pilot's disorientation while taxiing, resulting in a runway incursion. Factors contributing to the incident were: the failure of the flight crew to communicate with the ATC ground controller to verify their position; the inadequate crew coordination; and…NTSB CHI93LA043Accident · Serious injuriesLimited investigationFinal reportBoeing 727-232 · Chicago, ILThe captain's inadequate coordination with the ground and flight crew. Factors related to the accident were: the passenger's perception that the APU exhaust was a fire, which resulted in action that initiated an evacuation.NTSB FTW92LA142Accident · Serious injuriesLimited investigationFinal reportBoeing 737-200 · Palacios, TXThe flight's unexpected encounter with moderate turbulence.NTSB NYC92LA076Accident · 1 fatalLimited investigationFinal reportMcdonnell Douglas DC-9-32 · Dayton, OHA failed wheel rim following an inadvertent over inflation by the mechanic. Additional causes were the failure of the mechanic to be aware of the pressure being used and his failure to follow procedures. A factor related to the accident was the failure of the…NTSB DEN90IA189Incident · Minor injuriesIncident investigationFinal reportBoeing 737-222 · Denver, COThe failure of the flight crew to follow emergency procedures/directives. Factors were the failure of the aircraft electrical system (relays) and the failure of the company to provide a jetway operator.NTSB SEA90IA161Incident · No injuriesIncident investigationFinal reportBoeing 727-224 · Belgrade, MTThe malfunction of the starter control valve.NTSB MIA90LA155Accident · Serious injuriesLimited investigationFinal reportBoeing 727-223 · Fort Myers, FLUnforecasted encounter with weather. The airplane encountered severe turblence during enroute descent, resulting in one flight attendant sustaining serious injury, and one passenger sustaining minor injury.NTSB CHI90IA166Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-32 · Chicago, ILThe pilot-in-command's inadequate weather evaluation. Factors in the incident were the weather and artcc's failure to issue a weather advisory.NTSB DCA90MA017Accident · 1 fatalClass 1 · MajorFinal reportBeech A100 · Atlanta, GA(1) Failure of the federal aviation administration to provide air traffic control procedures that adequately take into consideration human performance factors such as those which resulted in the failure of the north local controller to detect the developing…NTSB ATL89LA172Accident · Serious injuriesLimited investigationFinal reportBoeing 737-291 · Atlanta, GAFailure of the ground employee to follow normal safety procedures. His lack of familiarity with the operation was a related factor.NTSB DCA89MA035Accident · 2 fatalClass 1 · MajorFinal reportMcDonnell Douglas DC-9-33F · Saginaw, TXThe loss of control of the airplane for undetermined reasons following the inflight opening of the improperly latched cargo door. Contributing to the accident were: inadequate procedures used by evergreen airlines and approved by the FAA for preflight…NTSB FTW89IA067Incident · Minor injuriesIncident investigationFinal reportBoeing 727-232 · Greenville, TXFalse fire warning, which resulted from (1) contaminants on hardware at one end of the fire detection loop; and (2) an electrical short on both elements of the loop.NTSB CHI89MA046Accident · No injuriesMajor investigationFinal reportBoeing 737-201 · Chicago, ILPrevious damage to the aft cone (engine mounting) bolt, which resulted in mismatched surfaces between the bolt and isolation mount, loss of torque during cyclic loading of the mounting bolt, and subsequent fatigue failure of the bolt.NTSB CHI88IA111Incident · No injuriesIncident investigationFinal reportBoeing 737-222 · Detroit, MINTSB SEA88IA065Incident · No injuriesIncident investigationFinal reportBoeing 727-232 · Portland, ORCrew was unable to lower the left main lndg gear. Crew then executed an emergency landing on the right main and nose gear with minor damage to the acft. The investigation revealed that the left main gear door attach fitting had a fatigue fracture.NTSB MIA88IA072Incident · No injuriesIncident investigationFinal reportBoeing 727-231 · Miami, FLPlt was instructed to turn the tail to the right as viewed by the signal man during power back. As power back started the tail was turned to the left as viewed by the signal man. The signal man corrected this turn but the acft was now making a much larger arc…NTSB FTW88IA037Incident · No injuriesIncident investigationFinal reportBoeing 727-243 · Houston, TXImproper drilling of the cross hole in the slat track bearing bolt, which led to its failure from fatigue cracking.NTSB DEN87IA145Incident · No injuriesIncident investigationFinal reportBoeing 727-251 · Casper, WYBoeing 727 (northwest flt 354) & USAF EC-135 (slum 51) were involved in a nr collision at FL 330. The mishap occurred asflt 354 was ene bnd on J-158 & slum 51 was flying on a radial-distance (r/d) flt pln, flying btn r/d pts south of J-158.as slum 51 apchd…NTSB LAX87IA027Incident · No injuriesIncident investigationFinal reportBoeing 727-222 · Los Angeles, CADrg arr, united flt 282 (Boeing 727, N7255U) was vectored by Los Angeles (lax) TRACON for an ILS rwy 25L apch. While in a dscndg turn at 2100' MSL to intercept the ILS LOC at 2000', the capt saw a helicopter (hel) ahead & pulled up. He estdhis acft passed w/i…NTSB ANC87IA003Incident · No injuriesIncident investigationFinal reportBoeing 727-22C · Anchorage, AKAfter departure, the flight crew retracted the landing gear and noticed a nose gear disagreement light. Upon arriving at Anchorage, the flight crew could not lower the nose gear through normal or manual means. The airplane landed with main gear extended and…NTSB CHI86MA142Incident · No injuriesMajor investigationFinal reportMcdonnell Douglas DC-9-31 · Chicago, ILU.S. Air flight 373 passed over American airlines flight 695 at the intersection of runways 32R and 4L while both aircraft were taking off. Both aircraft had been cleared for takeoff by the local controller at o'hare tower. The aircraft came within twenty…NTSB ATL86LA090Accident · Serious injuriesLimited investigationFinal reportBoeing 727-223 · Memphis, TNAmerican airlines flight 502 experienced a fire warning light illumination on no. 1 engine as the aircraft was climbing through 6000 feet. The pilot declared an emergency and returned to Memphis. Following the landing the pilot ordered a passenger emergency…NTSB DCA86IA017Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Harlingen, TXWhile en route, the company dispatcher notified American flt 844 (via acars) that Harlingen (hrl) had unforecast fog & was 300' obscd with 1/2 mi vis. At 2335, as the flt bgn a dscnt fm FL 310, the same ceiling & vis were rprtd. However, as the flt was clrd…NTSB BFO85IA065Incident · No injuriesIncident investigationFinal reportBoeing 727-225 · Richmond, VAThe flt was in cruise at FL 350 when the cabin crew reported a cabin fire in the vicinity of seat 28A. Shortly after, a lower aft body overheat warning was recvd. The flt diverted to Richmond, VA. During descent, the flt crew performed the appropriate…NTSB MIA84IA242Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-51 · Orlando, FLJust prior to V1 and rotation both left main landing gear tires failed. Takeoff was aborted and acft was stopped on rwy. Pax & crew deplaned without injury. Cause of tire failure could not be determined.NTSB ATL84IA246Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-30 · Nashville, TNDuring the climb-out, a 15% decrease in the right eng epr was noted by the flt crew. This was followed by a loud bang & failure of the #2 eng. The #2 eng was shut down & the acft was flown back to the departure arpt. An initial exam revealed that the right…NTSB CHI84IA314Incident · No injuriesIncident investigationFinal reportBoeing 727-2M7 · Minneapolis, MNThe crew reported that they noticed a decrease in climb rate while over rapid city, SD, en route from msp to sfo at flt level 310. The plt noted fuel burn was aprx 1400 lbs ahead of schedule. In-flt inspection revealed that the inboard trailing edge flaps had…NTSB MIA84IA064Incident · No injuriesIncident investigationFinal reportDouglas DC-9-51 · Tampa, FLWhile climbing after takeoff thru about 3000 ft, the crew noted that the #2 epr had dropped about .08, from aprx 1.82 to 1.74 epr. Shortly after that, the 1st officer noted that the avm on the #2 eng was at the max indication. At about 4000 ft, there was a…