NTSB investigations: Lycoming TI0-540 series
73 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “Loss of control - in flight”. 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, newest first
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 ('41533')
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\" = 250))
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 ('41533')
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" = 250))
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 FTW89FA089Accident · 1 fatalField investigationFinal reportSmith, Ted Aerostar 601 · New Iberia, LAThe pilot failed to maintain a proper climb immediately after takeoff. Contributing to the accident was excessive manifold pressure indications for the left engine. The pilot's diverted attention in dealing with that condition most probably resulted in the…NTSB LAX87FA281Accident · 4 fatalField investigationFinal reportPiper PA-32R-301T · Monterey, CALoss of control of the aircraft, by the pilot, while excuting a missed approach.NTSB NYC87FA172Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Nantucket, MAThe weather at the Nantucket airport was below the prescribed minima for the ILS approach to runway 24. A blanket broadcast had been made on the air traffic frequencies that the Nantucket weather was below the minima for most users and, thereafter, the…NTSB MKC87FA087Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Ogden, IAThe airplane was equipped for IFR flight. The pilot was not instrument rated. The pilot had been briefed earlier that VFR flight was not recommended. The pilot did not update the weather for this flight. The front of the airplane was buried seven feet in the…NTSB NYC87LA123Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Nantucket, MAThe Piper PA-23-250 attempted a go-around after crossing the threshold and observing the runway lights were not on during a night instrument approach. The pilot reported that he added full power and retracted the wing flaps. The procedure in the Piper manual…NTSB ANC86LA124Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Tyonek, AKThe pilot stated that during the initial climb, the aircraft started to settle. The pilot stalled and crashed into a wooded area at the departure end of the runway.NTSB ATL86LA161Accident · No injuriesLimited investigationFinal reportAero Commander 500-B · Guntersville, ALThe plt allowed the aircraft to settle back onto the runway shortly after liftoff from the runway after having already retracted the landing gear. The aircraft landed with the landing gear retracted.NTSB DEN86LA095Accident · Minor injuriesLimited investigationFinal reportSmith, Ted Aerostar 601P Aerostar · Dickinson, NDWhile enroute on an IFR flight plan, the plt changed destination to Dickinson, ND, which extended the length of the flt. He did not desiginate an alternate arpt or have an adequate fuel reserve as required. On arrival at the destination, he executed an…NTSB ATL86FA064Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Milwaukee, NCThe acft was observed to descend and level off at low alt. Witnesses indicated that it leveled off just above the trees, then rolled to the right and dove into wooded terrain. The eng was reported to be running loud and steady until impact. No preimpact part…NTSB LAX86LA033Accident · 3 fatalLimited investigationFinal reportPiper PA-32R-301T · San Diego, CAThe flt departed in VFR conditions after a wx briefing which indicated that clear skies and unrestricted visibilty existed and were forecasted at the destination airport. On arrival the plt requested and received clearance for an instrument apch. When the flt…NTSB BFO85FA067Accident · 2 fatalField investigationFinal reportBellanca 17-31A · Woodbridge, VAThe acft departed saratoga springs, NY, en route to manassas, VA. Wx was VFR and as the acft approached gaithersburg, MD, at 2132 LCL the plt contacted dulles apch for vectors through the area to manassas. The acft was issued a heading to manassas. Shortly…NTSB DEN85LA188Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Glen Canyon, UTThe plt said that during the takeoff roll at night from an unlit runway, he was distracted when the engine overboost light illuminated. The investigation revealed, however, that the plt was actually trying to avoid colliding with an airplane at the other end…NTSB ATL84MA208Accident · 5 fatalMajor investigationFinal reportPiper PA-32-300 · Canton, GAThe acft with a student plt at the controls had an in-flt breakup during a night x-country flt. During a preflt wx briefing, he was advised that VFR flt was not recommended. The plt terminated the conversation before the briefing was completed. While in flt,…NTSB LAX84IA353Incident · No injuriesIncident investigationFinal reportPiper PA-32-300 · Chowchilla, CAThe acft collided with VASI lights during an unscheduled landing when plt became ill & according to the passengers became unconscious. The passenger, a non-plt, landed the acft. The plt was transported by ambulence to a nearby hospitalwhere doctors stated…NTSB FTW84LA192Accident · No injuriesLimited investigationFinal reportRockwell A-9B · Lamont, OKThe plt reported that between swath runs, his attention was directed to swath marks on the ground, then he tried to determine how much chemical was remaining in the hopper. At about 100 ft AGL, while in a 50 deg left bank, he heard 'the eng slow down' & felt…NTSB ATL84FA093Accident · 4 fatalField investigationFinal reportPiper PA-32RT-300T · Bluefield, WVThe non-instrument rated plt began his takeoff during the hours of darkness, but in VMC wx. He stated that during the takeoff roll at about 65 to 75 KTS just prior to rotation, the landing light extinguished. Plt stated that 2 to 3 seconds later, he rotated &…NTSB CHI83FA279Accident · 1 fatalField investigationFinal reportSmith, Ted Aerostar 601A · Celina, OHWhen the plt arrived at the destination arpt, there was construction on the rwy, about 2500 ft from the apch end. He contacted UNICOM & was advised that the rwy was closed, but was told he could land on the grass beside the rwy. The plt responded that the…NTSB MIA83FA158Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Fort Lauderdale, FLDuring flt, the acft was observed flying from west to east across the beach & out over the ocean. Witnesses reported that over the ocean, the sky was dark & thunderstorms were approaching with heavy lightning. As the acft crossed the beach, a distinct eng…NTSB MIA83FA072Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · San Juan, PRShortly after takeoff the plt requested clearance to return to the arpt & land. According to witnesses the acft was having difficulty maintaining altitude & was flying with the nose 'up and down.' The tower controller stated that the acft didn't seem to get…NTSB LAX83FUJ04Accident · 1 fatalFinal reportPiper PA-32-300 · Douglas, AZThe plt was observed to crash shortly after takeoff. Witnesses stated it had been snowing off & on. The plt's blood alcohol level was 228 mg%.NTSB NYC83FA004Accident · 1 fatalField investigationFinal reportTed Smith 601P · Augusta, MEPilot lost control of his aircraft during low altitude maneuvers to align the aircraft for landing. The low ceiling and rising terrain around the airport influenced the pilots decisions to make tight turns at low altitude. The aircraft was stalled and rolled…NTSB MIA82FA120Accident · 1 fatalField investigationFinal reportPiper P-60-601P · Titusville, FLShortly after takeoff witnesses observed the acft in a steep left bank descending until it crashed approximately 1200 ftnw of the departure end of the rwy. According to the pax the initial climb distracting the attention of the plt who lostcontrol of the acft…NTSB FTW82FRG21Accident · 1 fatalFinal reportPiper PA-31 · Port Mansfield, TXThe aircraft crashed and burned about 1/2 mile from the approach end of runway 12. A witness reported that "the plane just fell" while the pilot was making a sharp turn. An estimated 1500 lbs of marijuana was on board.