OpenAirDocs.org

NTSB investigations: AiResearch TPE331 series

13 cases on aircraft whose registry engine model is AiResearch TPE331 series, where the first occurrence was “In flight collision with terrain/water”. 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

19822026

Where

Open the map

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 ('01514', '01517')
      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\" = 230))
  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.

NTSB CHI05CA246Accident · No injuriesData collectionFinal reportAyres S2R-G10 · Davenport, NDThe pilot failed to gain suffient altitude during takeoff in order to clear the corn crop at the end of the runway. A factor associated with the accident was the corn crop.Aug 29, 2005 · N3024U · Substantial damageNTSB DFW05FA202Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Parker, COThe pilot’s failure to fly a stabilized instrument approach at night which resulted in controlled flight into terrain. Contributing factors were; the dark night, low clouds, the inadequate design and function of the airport facility’s Minimum Safe Altitude…Aug 4, 2005 · N454MA · DestroyedNTSB SEA05LA146Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Jerome, IDFailure to maintain clearance from terrain during takeoff and initial climb. A high density altitude was a factor.Jul 19, 2005 · N6702Q · Substantial damageNTSB IAD05FA023Accident · 6 fatalClass 1 · FieldFinal reportCASA 212-200-CC · Bamiyan, Afghanistanthe captain's inappropriate decision to fly a nonstandard route and his failure to maintain adequate terrain clearance, which resulted in the inflight collision with mountainous terrain. Factors were the operator's failure to require its flight crews to file…Nov 27, 2004 · N960BW · DestroyedNTSB CHI01LA302Accident · No injuriesLimited investigationFinal reportSwearingen SA226-T · West Chicago, ILthe checklist not followed and the directional control not maintained by the pilot. A contributing factor was the left propeller’s start locks being engaged.Aug 28, 2001 · N104BR · Substantial damageNTSB MIA00LA123Accident · Minor injuriesLimited investigationFinal reportAyres S2R-G10 · Leesburg, GAThe failure of the pilot to maintain clearance during a spray pass resulting in the in-flight collision with the raised rows of the field.Mar 29, 2000 · N4089Q · Substantial damageNTSB LAX95FA338Accident · Minor injuriesField investigationFinal reportSwearingen SA-226T · Chino, CAThe pilot's improper IFR procedure by not initiating a missed approach at the outer marker, by attempting to intercept the glideslope from above after passing the outer marker, and by allowing the airplane to continue descending after reaching the decision…Sep 18, 1995 · N693PG · DestroyedNTSB CHI92LA038Accident · No injuriesLimited investigationFinal reportSwearingen SA-226T · Iowa, IAThe pilot's failure to extend the landing gear which resulted in the propeller blades contacting the runway during the landing. A factor related to the accident was the pilot's failure to follow a checklist during the approach.Dec 3, 1991 · N14TP · Substantial damageNTSB DEN90FA042Accident · Serious injuriesField investigationFinal reportFairchild SA227-AC · Elko, NVImproper IFR procedure by the captain, and inadequate monitoring of the approach by the first officer, which resulted in a failure to maintain proper altitude during the approach. Factors related to the accident were: the terrain and weather conditions at the…Jan 15, 1990 · N2721M · Substantial damageNTSB CHI86MA025Accident · 5 fatalMajor investigationFinal reportCessna 441 · Derry, PADrg arrival, the plt was advised the destn wx was: estd 500' overcast, vis 1 mi with fog, arpt blo mins. The plt electedto make an NDB rwy 23 apch, but said he would divert if a missed apch was made. He was provided radar vectors & was clrdfor the apch. At…Nov 11, 1985 · N59MD · DestroyedNTSB FTW85FA086Accident · 1 fatalField investigationFinal reportCessna 441 · Marble Falls, TXThe acft crashed aprx 1.5 miles south of the departure end of rwy 17 during an attempted rwy 17 NDB apch. The acft was cleared for the apch at 2012 CST and the plt canceled IFR reporting the arpt in sight at 2014. A witness located aprx 1 mile south of the…Dec 26, 1984 · N441CM · DestroyedNTSB LAX82DUJ45Accident · No injuriesFinal reportAyres S2R · Goodyear, AZThe aircraft had just been loaded with spray material. The pilot stated that after taking off, he leveled off over cotton at the end of the strip and made a power reduction. At about that time, the aircraft settled into the cotton and hit an embankment. The…Sep 1, 1982 · N5611X · Substantial damageNTSB FTW82FA173Accident · 2 fatalField investigationFinal reportGulfstream American 980(695) · Carlsbad, NMThe acft crashed about 1/2 mi sw of the departure end of rwy 32L. The rwy had been illuminated at the time of takeoff with the acft making a left turn into an area that was not illuminated toward the mountains. It was a very dark night with an…May 13, 1982 · N9789S · Destroyed