NTSB investigations: Continental IO-520 series, MD
19 cases on aircraft whose registry engine model is Continental IO-520 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
| 1966 | 1 |
|---|---|
| 1967 | 2 |
| 1981 | 1 |
| 1984 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2006 | 1 |
| 2008 | 1 |
| 2011 | 1 |
| 2019 | 1 |
| 2023 | 2 |
| 2024 | 1 |
| 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\" = 'MD' 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 ('17032'))
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" = 'MD' 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 ('17032'))
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 ERA26LA173Accident · No injuriesClass 4 · LimitedFinal reportBeech 58 · Stevensville, MDThe pilot’s inadvertent retraction of the landing gear lever during the landing roll, which resulted in a gear collapse and runway excursion.NTSB ERA24LA112Accident · No injuriesClass 4 · LimitedFinal reportBellanca 17-30 · Stevensville, MDThe pilot’s failure to maintain directional control of the airplane while landing with a crosswind.NTSB ERA23LA389Accident · No injuriesClass 4 · LimitedFinal reportBellanca 17-30A · Baltimore, MDThe pilot’s failure to maintain control of the airplane during the aborted landing, which resulted in a collision with a taxiway light.NTSB ERA23LA349Accident · No injuriesClass 3 · LimitedFinal reportCessna A185F · Leonardtown, MDA loss of engine power during an approach to landing for undetermined reasons.NTSB GAA19CA358Accident · No injuriesData collectionFinal reportBeech 35 · Bowie, MDThe pilot's failure to extend the landing gear before landing.NTSB ERA12CA080Accident · Serious injuriesData collectionFinal reportBeech V35 · Lusby, MDThe pilot did not maintain clearance from trees during a night approach.NTSB NYC08FA109Accident · 2 fatalField investigationFinal reportBeech A36 · Cumberland, MDThe pilot's failure to maintain the proper approach course for undetermined reasons.NTSB NYC07FA042Accident · 2 fatalField investigationFinal reportCessna 210K · Edgewater, MDThe pilot's failure to maintain the proper altitude/clearance will on approach, which resulted in an in-flight collision with trees. Contributing to the accident was the night-light conditions, an obstruction light that was not illuminated, and trees that had…NTSB NYC03LA128Accident · Minor injuriesLimited investigationFinal reportCessna 210L · Crisfield, MDThe pilot's inadequate recovery from a bounced landing and his improper flare which resulted in a hard landing. Contributing factors were the windshear and the crosswind.NTSB IAD02FA075Accident · 1 fatalField investigationFinal reportBeech S-35 · Clear Spring, MDThe pilot's continued visual flight into instrument meteorological conditions, which resulted in an in-flight collision with rising terrain. Factors included dense fog and mountainous terrain.NTSB IAD00LA058Accident · Serious injuriesLimited investigationFinal reportCessna 206 · Annapolis, MDThe pilot's failure to attain the proper touchdown point, and his failure to perform a go-around.NTSB IAD96LA092Accident · No injuriesLimited investigationFinal reportBeech V35B · Westminster, MDThe fracture of the engine crankshaft which had a subsurface origin and progressed in fatigue until overload and separation occurred.NTSB BFO96LA033Accident · No injuriesLimited investigationFinal reportCessna 210 · Baltimore, MDfailure of the pilot to ensure that the landing gear was fully down and locked before landing.NTSB BFO94FA160Accident · 1 fatalField investigationFinal reportBeech A36 · Barstow, MDThe pilot's failure to maintain clearance from the tower.NTSB NYC84FA178Accident · 1 fatalField investigationFinal reportCessna 210E · Glen Burnie, MDBefore the flt, the plt was observed performing maintenance in the eng compartment. He was known to do some of his own maintenance which included stopping an oil gasket leak by using a sealer. While climbing after takeoff, he turned back to the departure…NTSB ATL81FIG11Accident · Minor injuriesClosedBellanca 17-30 · Royal Oak, MDNTSB DIA67D0111Accident · No injuriesClosedBeech 35C · Cecilton, MDNTSB DIA68D0018Accident · No injuriesClosedCessna U206B · Friendship, MDNTSB NYC67F0315Accident · No injuriesClosedCessna 210E · Newburg, MD