NTSB investigations: Lycoming 0-290 series
22 cases on aircraft whose registry engine model is Lycoming 0-290 series, where the first occurrence was “In flight collision with object”. 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
| 1982 | 1 |
|---|---|
| 1983 | 2 |
| 1984 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2001 | 1 |
| 2002 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2007 | 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 ('41506')
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\" = 220))
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 ('41506')
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" = 220))
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 CHI07CA119Accident · No injuriesData collectionFinal reportJohnson-Whittman Tailwind JW9L · Saginaw, MIThe pilot's failure to maintain the proper glidepath and clearance from a fence while on final approach.NTSB DFW06CA107Accident · No injuriesData collectionFinal reportPiper PA-22 · Tecumseh, OKThe pilot's failure to maintain clearance from the trees. Contributing factors were the pilot's inadequate preflight planning/preparation and the high-density altitude.NTSB DEN05FA124Accident · 2 fatalField investigationFinal reportPiper PA-22-135 · Kremmling, COthe pilot's failure to maintain clearance from terrain.NTSB CHI02LA229Accident · Minor injuriesLimited investigationFinal reportPiper PA22-135 · Lyons, WIFailure of the pilot to maintain a sufficient rate-of-climb and to obtain a safe altitude/clearance from the tree line at end of the runway. Contributing factors were the uphill runway gradient and the trees.NTSB ANC01LA123Accident · No injuriesLimited investigationFinal reportPiper PA-12 · Nenana, AKThe pilot's selection of an unsuitable landing area. A factor associated with the accident was trees.NTSB FTW00LA015Accident · 2 fatalLimited investigationFinal reportSturges Spezio Sport · Mathis, TXthe pilot's failure to maintain clearance with the power lines while maneuvering.NTSB FTW99FA171Accident · 1 fatalField investigationFinal reportHeilig-Reading Emeraude CP 301A · Altus, ARThe pilot's failure to maintain clearance with a wire, during an approach to a private airstrip.NTSB FTW98FA101Accident · 1 fatalField investigationFinal reportPiper PA-18-135 · Wooster, ARthe pilot's failure to maintain clearance with trees during an aborted landing. A contributing factor was the pilot's delayed decision to abort the long landing.NTSB SEA96LA216Accident · 1 fatalLimited investigationFinal reportPiper PA-18 · Gillette, WYfailure of the pilot to see-and-avoid the obstruction (power line). The powerline was a related factor.NTSB LAX96LA018Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Battle Mountain, NVthe pilot's failure to see and avoid utility transmission wires suspended across the final approach flight path.NTSB SEA94FA208Accident · 2 fatalField investigationFinal reportPiper PA-22 · Butte Falls, ORThe pilot-in-command's failure to maintain adequate altitude and clearance from trees while maneuvering.NTSB NYC92LA142Accident · Minor injuriesLimited investigationFinal reportPiper PA-12 · Green Creek, NJThe pilot diverted his attention from flying the airplane and did not maintain a visual lookout, which resulted in a collision with trees.NTSB SEA91LA182Accident · 2 fatalLimited investigationFinal reportPiper PA-20 · Ione, WAInadequate clearance. A factor to the accident was: poor inflight planning.NTSB SEA90LA076Accident · 1 fatalLimited investigationFinal reportPiper PA-18-125 · Rogerson, IDThe pilot's intentional flight below safe altitudes while engaged in low-altitude 'buzzing' activities.NTSB ATL89LA153Accident · Serious injuriesLimited investigationFinal reportPiper PA-22-135 · Medina, OHFailure of airport management to establish a displaced threshold which would provide adequate obstruction clearance. Factors contributing to the accident were the power lines, the utility pole and the dusk light conditions.NTSB DEN88LA169Accident · Minor injuriesLimited investigationFinal reportPiper PA-18 · Forsyth, MTNTSB MIA88FA063Accident · 1 fatalField investigationFinal reportPiper PA-22-135 · Geneva, ALPrior to the acdnt, a witness saw the acft flying across an open field at a very low alt. Subsequently, it collided with the tops of several pine trees at about 90 to 95 ft AGL, then it crashed to the ground. No preimpact part failure or malfunction was…NTSB NYC86FNC08Accident · 2 fatalFinal reportChampion 7HC · Epsom, NHA student pilot and passenger on a local flight collided with a tree, crashed and burned. No malfunction was found with the aircraft and engine. The plts flt time was not reported or available.NTSB BFO84FA003Accident · 2 fatalField investigationFinal reportPiper L-21-A · Selbyville, DEAt the conclusion of towing banners with no pax on board, the acft was landed and topped off with fuel. The plt then reentered the acft and an additional employee got in the rear seat with the intension of flying to a nearby airport for a plt exchange. During…NTSB DEN83LA194Accident · No injuriesLimited investigationFinal reportPiper PA-12 · St. Xavier, MTThe acft collided with a fence during an attempted go-around in a field which was estimated to be 500 ft long. The wind was calm and the density alt was calculated to be 4900 ft. after landing and rolling 300 ft the plt decided he would not be able to stop.…NTSB DEN83LA097Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Hulett, WYThe acft struck a deer while landing into the sun at a private ranch strip. The animal was seen just before touchdown but not in time to avoid hitting it.NTSB NYC82DA168Accident · No injuriesFinal reportPiper PA-18S · Moultonboro, NHAccording to the pilot, he taxied to a takeoff point farther out than normal and it took longer to get the plane "on the step" due to very heavy air. When the pilot reached the abort point he used control back pressure to "pop off" the water. However, he was…