NTSB investigations: Lycoming LTS-101 series, CA
5 cases on aircraft whose registry engine model is Lycoming LTS-101 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
| 1986 | 1 |
|---|---|
| 2002 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2010 | 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.\"eventStateOrRegion\" = 'CA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41560'))
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."eventStateOrRegion" = 'CA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41560'))
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 WPR10LA200Accident · No injuriesLimited investigationFinal reportBell 222U · Santa Maria, CAThe pilot's inadequate preflight inspection to ensure that all tie-down straps were removed prior to flight. Contributing to the accident was the pilot's improper management of sleep opportunities during the preceding rest period, which likely contributed to…NTSB LAX04CA332Accident · No injuriesData collectionFinal reportBell 222U · Santa Rosa, CAthe pilot-in-command's (examinee's) incorrect collective control response to a simulated power loss of the number 1 engine.NTSB LAX03IA252Incident · No injuriesIncident investigationFinal reportBell 222 · Salinas, CAThe fatigue failure (fracture) of the right forward transmission lift link during cruise flight, which resulted in a severe vibration and an emergency landing.NTSB LAX02FA276Accident · 3 fatalField investigationFinal reportBell 222U · Nipton, CAThe main rotor blade separation while maneuvering for unknown reasons. A factor was the dark night condition.NTSB LAX86LA098Accident · Minor injuriesLimited investigationFinal reportBell 222UT · La Habra, CAOn January 26, 1986 a Bell 222UT collided with a 3/8 inch support cable. The pilot saw the lower of two of the three support cables about 75 feet AGL as he was transitioning to forward flight from a vertical max performance t/o. the pilot applied aft cyclic…