NTSB investigations: Lycoming O-360-A4M, FL
7 cases on aircraft whose registry engine model is Lycoming O-360-A4M. 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
| 2016 | 1 |
|---|---|
| 2021 | 1 |
| 2024 | 2 |
| 2025 | 2 |
| 2026 | 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\" = 'FL' 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 ('42276'))
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" = 'FL' 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 ('42276'))
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 ERA26LA180Accident · No injuriesClass 3 · LimitedPreliminary reportPiper PA-28-181 · Indiantown, FLOn April 18, 2026, about 2115 eastern daylight time, a Piper PA-28-181, N643FT, was substantially damaged when it was involved in an accident near Indiantown, Florida. The private pilot was not injured. The airplane was operated as a Title 14 Code of Federal…NTSB ERA26LA074Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-28-181 · Fort Lauderdale, FLThe student pilot’s improper landing flare and the flight instructor’s inadequate remedial action, which resulted in a hard landing and subsequent nose landing gear collapse.NTSB ERA26LA068Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-28-181 · Fort Pierce, FLThe pilot’s inadequate visual lookout while taxing, which resulted in the airplane striking a light pole.NTSB ERA24LA295Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-28-181 · Clearwater, FLAn in-flight collision with a bird while flying in the airport traffic pattern.NTSB ERA24LA113Accident · No injuriesClass 4 · LimitedFinal reportPiper PA28 · Melbourne, FLThe pilot receiving instruction’s failure to correctly identify the runway centerline prior to initiating the nighttime takeoff, which resulted in a collision with a runway edge light and subsequent runway excursion. Contributing to the accident was the…NTSB ERA21LA139Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-28-181 · Fort Pierce, FLThe pilot under instruction’s improper landing flare and attempted go-around which resulted in an aerodynamic stall, and subsequent loss of control. Contributing to the accident was the flight instructor’s delayed remedial action.NTSB GAA16CA243Accident · No injuriesData collectionFinal reportPiper PA-28 · Crystal River, FLThe student pilot's failure to maintain directional control during the takeoff, which resulted in runway excursion and collision with a ditch. Contributing to the accident was the improper flap retraction procedure employed by the pilot during takeoff.