NTSB investigations: Lake LA-4, FL
8 cases on aircraft the registry lists as Lake LA-4. 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
| 1967 | 1 |
|---|---|
| 1973 | 1 |
| 1974 | 1 |
| 1978 | 1 |
| 1983 | 2 |
| 1991 | 1 |
| 2000 | 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.aircraft_model_code IN ('5110302'))
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.aircraft_model_code IN ('5110302'))
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 MIA00LA240Accident · Serious injuriesLimited investigationFinal reportLake LA-4 · Pensacola, FLThe pilot receiving instruction failure to achieve the proper touch down point during a water landing, and the CFI's improper supervision and failure to initiate a go-around in sufficient time to avoid and in-flight collision with trees, water, and subsequent…NTSB MIA92LA009Accident · Minor injuriesLimited investigationFinal reportLake LA-4 · Panama City, FLLoss of power due to undetermined reasons. Contributing to the accident was the cfi's inadequate emergency procedures following the reported loss of power.NTSB MIA83LA193Accident · No injuriesLimited investigationFinal reportLake LA-4 · Gainesville, FLThe plt stated that during takeoff, the eng appeared to lose power at about 200 ft AGL, but the gauges showed no malfunction. The acft began to settle, so he elected to land on the rwy overrun area. Reportedly, the acft was landed successfully, however, while…NTSB MIA83LA167Accident · No injuriesLimited investigationFinal reportLake LA-4 · Jacksonville, FLThe acft collided with a tree and landed gear up on floats after an engine failure. The pilot was cruising at 1000 ft MSL when the oil pressure dropped to zero and the engine seized. The acft collided with the tops of pine trees while approaching a nearby…NTSB MIA78FA053Accident · 1 fatalClosedLake LA-4 · Pierson, FLNTSB MIA74FLA47Accident · No injuriesClosedLake LA-4 · Jacksonville, FLNTSB MIA73DKT78Accident · No injuriesClosedLake LA-4 · Key West, FLNTSB MIA68D0337Accident · No injuriesClosedLake LA-4 · Miami, FL