NTSB investigations: Lycoming TI0-540 series, 2000

36 cases on aircraft whose registry engine model is Lycoming TI0-540 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

19642026
NTSB investigations: Lycoming TI0-540 series, 2000 per year, 1964–2026: 2,259 cases
19649
196527
196632
196749
196848
196947
197048
197163
197245
197351
197462
197546
197652
197758
197868
197965
198057
198155
198247
198340
198446
198543
198643
198735
198833
198932
199016
199130
199230
199325
199426
199527
199631
199723
199822
199926
200036
200143
200246
200337
200441
200544
200649
200732
200833
200928
201034
201123
201231
201327
201425
201531
201621
201721
201822
201920
202029
202118
202228
202331
202415
202518
202619

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 year(c.\"eventDate\") = 2000
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41533'))
  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 ANC01LA027Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Deadhorse, AKThe pilot's continued VFR flight into instrument meteorological conditions. Factors associated with the accident were clouds, fog, dusk light conditions, and the pilot's self-induced pressure to complete the flight prior to nightfall.Dec 22, 2000 · N63MB · Substantial damageNTSB MIA01FA043Accident · 1 fatalField investigationFinal reportPiper PA-31-325 · Belvidere, NCThe pilot's failure to maintain airplane control due to spatial disorientation while maneuvering in instrument meteorological conditions resulting in the airplane entering a descending turn and crashing into terrain.Dec 14, 2000 · N120JB · DestroyedNTSB CHI01LA042Accident · No injuriesLimited investigationFinal reportAerostar PA-60-601P · Preston, MNaltitude/clearance from the trees not being obtained/maintained by the pilot. Factors to the accident were the trees and the contamination of the pitot/static system.Nov 26, 2000 · N713HM · Substantial damageNTSB CHI01LA010Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Tecumseh, MIThe pilot was unable to rotate the aircraft during takeoff for undetermined reasons. A factor associated with the accident was the soft terrain, which the airplane encountered during the aborted takeoff.Oct 15, 2000 · N289JG · Substantial damageNTSB DEN01LA023Accident · No injuriesLimited investigationFinal reportCessna 310N · Montrose, COthe pilot's inadequate airspeed on final approach which resulted in a hard landing. A contributing factor was wind shear.Oct 14, 2000 · N111KC · Substantial damageNTSB DEN01LA005Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Grand Junction, COTotal failure of the right forward inboard landing gear door hinge pin for undetermined reasons.Sep 27, 2000 · N159SW · Substantial damageNTSB DEN00LA179Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Blanding, UTThe pilot's failure to follow the checklist and lower the landing gear for landing. A factor was diverted attention.Sep 27, 2000 · N114SA · Substantial damageNTSB CHI00LA303Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-325 · Jeffersonville, INthe pilot's inadequate normal braking and the pilot's inability to stop the airplane on the runway. Factors relating to this accident were the hydroplaning conditions, wet runway, the tailwind, the trees, and the ravine.Sep 20, 2000 · N63706 · Substantial damageNTSB ANC00LA133Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Emmonak, AKThe pilot's continued operation of the airplane on unsuitable terrain, and the subsequent failure of the main landing gear torque link. Factors in the accident were rough and uneven runways, and inadequate surveillance of airport facilities/runway conditions…Sep 15, 2000 · N4105D · Substantial damageNTSB NYC00LA254Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Factoryville, PAThe pilot's failure to attain the proper touchdown point.Sep 7, 2000 · N8704P · Substantial damageNTSB CHI00LA286Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Mason City, IAthe unsuitable terrain for landing encountered by the pilot and the failure of the oil filter converter plate gasket. Factors to the accident were the total loss of oil and the soft terrain condition.Sep 1, 2000 · N8304C · Substantial damageNTSB LAX00LA339Accident · No injuriesLimited investigationFinal reportCessna 210E · Holbrook, AZThe lack of elevator control during final approach, for undetermined reasons, that resulted in a hard landing.Aug 28, 2000 · N210DL · Substantial damageNTSB LAX00FA310Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Hilo, HIDeterioration and failure of the oil filter converter plate gasket, which resulted in a loss of engine power and a subsequent in-flight fire.Aug 26, 2000 · N923BA · Substantial damageNTSB ATL00FA081Accident · 3 fatalField investigationFinal reportPiper PA-31-350 · Lumber City, GAPilot's failure to follow instrument procedures and descended below approach minimums and collided with trees. A factor was low clouds.Aug 15, 2000 · N801MW · DestroyedNTSB CHI00LA255Accident · No injuriesLimited investigationFinal reportPiper PA-31-325 · Omaha, NEthe landing gear not deployed, the checklist not followed, the lack of familiarity with the airplane, the landing gear warning system not understood, and the landing gear warning disregarded by the pilot.Aug 10, 2000 · N10QB · Substantial damageNTSB DCA00MA080Accident · 11 fatalMajor investigationFinal reportPiper PA-31 Navajo · Burlington Twp., NJthe failure of the pilots of the two airplanes to see and avoid each other and maintain proper airspace separation during visual flight rules flight.Aug 9, 2000 · N27944 · 2 aircraft · DestroyedNTSB ATL00FA075Accident · 3 fatalField investigationFinal reportPiper PA-46-350P · Augusta, GAImproper preflight planning/preparation by the pilot, which resulted in taking off with the airplane exceeding the weight and balance limitations. Factors to the accident were the improper loading of the airplane, taking off from a short, up sloping runway…Aug 4, 2000 · N198PM · DestroyedNTSB SEA00LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Birkenfeld, ORThe pilot's delayed go-around, which resulted in the aircraft not clearing the fence posts. A contributing factor was the fence posts.Jul 29, 2000 · N934PH · Substantial damageNTSB LAX00LA277Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Boulder City, NVThe fatigue fracture and separation of the No. 6 cylinder fuel injector line due to the company maintenance personnel's failure to comply with an Airworthiness Directive. A factor in the accident was the company's decision to operate the aircraft in…Jul 23, 2000 · N600EE · Substantial damageNTSB MIA00LA218Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Immokalee, FLThe inadequate supervision of the pilot rated student by the CFI for her failure to note that the fuel selector was positioned to an empty fuel tank. Also, failure of the CFI to attain the proper rate of descent at touchdown resulting in a hard landing.…Jul 16, 2000 · N980AC · Substantial damageNTSB MIA00WA209Accident · Serious injuriesForeign investigationPiper PA32-300 · Staniel Cay, BahamasJul 8, 2000 · N7638F · Substantial damageNTSB DEN00LA120Accident · No injuriesLimited investigationFinal reportNew Piper PA-46-350P · Spanish Fork, UTFailure by the pilot to maintain control of the aircraft during initial climb following takeoff.Jun 26, 2000 · N9246D · Substantial damageNTSB NYC00LA158Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Wauseon, OHThe pilot's failure to maintain airspeed, which resulted in an inadvertent stall.Jun 12, 2000 · N8197W · Substantial damageNTSB FTW00LA176Accident · No injuriesLimited investigationFinal reportBellanca 17-31ATC · Del Rio, TXThe separation of the #3 connecting rod, piston, and cylinder. A factor was the lack of suitable terrain for the forced landing.Jun 7, 2000 · N39827 · Substantial damageNTSB FTW00LA170Accident · No injuriesLimited investigationFinal reportAero Commander 700 · Breckenridge, TXFuel exhaustion as a result of an inaccurate fuel quantity indicating system. A factor was the lack of suitable terrain for the forced landing.Jun 5, 2000 · N700AF · Substantial damageNTSB ANC00IA063Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Tanana, AKAn in-flight oil leak due to the deterioration of oil filter adapter plate gasket material, and the supplier's distribution of inadequate material. A factor associated with the accident was the engine manufacturer's inadequate quality control.Jun 1, 2000 · N3536B · Minor damageNTSB DEN00IA093Incident · No injuriesIncident investigationFinal reportPiper PA-32R-300 · Erie, COImproper installation of cylinders by unknown maintenance personnel who failed to torque the cylinder stud nuts sufficiently.May 22, 2000 · N424TP · Minor damageNTSB DEN00FA086Accident · 2 fatalField investigationFinal reportSmith, Ted Aerostar Aerostar 601 · Estes Park, COA descent below the surrounding terrain, by the pilot, in IMC conditions. Factors were high mountainous terrain, clouds, inaccurate weather evaluation by the pilot, and the pilot's flight into IMC conditions.Apr 30, 2000 · N7421S · DestroyedNTSB ATL00LA053Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-200 · Mt. Pleasant, SCThe airplane collision with a deer during a night landing.Apr 30, 2000 · N9385C · Substantial damageNTSB MIA00LA140Accident · No injuriesLimited investigationFinal reportSmith, Ted Aerostar Aerostar 600 · Vieques, PRThe pilot's improper compensation for wind conditions during approach to landing resulting in the aircraft touching down hard, short of the runway, and receiving substantial damage.Apr 20, 2000 · N7528S · Substantial damageNTSB ANC00LA038Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Fairbanks, AKThe pilot's misjudgment of distance/altitude, and subsequent undershoot during landing. Factors in the accident were light snow precipitation, flat light conditions, snow-covered terrain, and the absence of a visual approach slope indicator.Mar 27, 2000 · N8540F · Substantial damageNTSB LAX00LA112Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Coalinga, CAThe failure of the landing gear for undetermined reasons to go into the locked position after the pilot conducted a manual and emergency gear extension. A factor in the accident was the undetermined failure of the electrical system.Mar 2, 2000 · N8170S · Substantial damageNTSB MIA00LA077Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · W. Columbia, SCThe inadequate wording of the NOTAM for failure to identify that the usable width of the runway was reduced and the inadequate snow removal by airport personnel for failure to remove the snow from the runway resulting in the on-ground collision with a snow…Jan 28, 2000 · N42Y · Substantial damageNTSB NYC00LA069Accident · No injuriesLimited investigationFinal reportMooney M20M · Montpelier, VTA blocked crankcase breather line due to ice and improper maintenance which resulted in further restricting the line. A factor in this accident was the below freezing outside air temperature.Jan 21, 2000 · N223KT · Substantial damageNTSB FTW00LA059Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Sweeney, TXThe pilot's excessive flare resulting in a hard landing. Factors were the loss of engine power for undetermined reasons, the power lines on final approach and the dark night conditions.Jan 10, 2000 · N8954N · Substantial damageNTSB NYC00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Harpswell, MEwas the improper decision of the pilot to depart at night, from an unlighted runway with no visual references to obstructions on the sides of the runway. Factors were the dark night conditions, and the lack of runway side lights.Jan 9, 2000 · N8463X · Substantial damage