NTSB investigations: Continental 0-300 series, MD
44 cases on aircraft whose registry engine model is Continental 0-300 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
| 1964 | 3 |
|---|---|
| 1965 | 7 |
| 1966 | 2 |
| 1967 | 3 |
| 1968 | 2 |
| 1969 | 3 |
| 1970 | 2 |
| 1971 | 2 |
| 1973 | 2 |
| 1974 | 2 |
| 1976 | 1 |
| 1977 | 2 |
| 1983 | 1 |
| 1984 | 1 |
| 1986 | 1 |
| 1988 | 3 |
| 1989 | 1 |
| 1990 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2009 | 1 |
Where
Latest 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 ('17022'))
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 ('17022'))
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 ERA09CA297Accident · No injuriesData collectionFinal reportCessna 172 · Perryville, MDA total loss of engine power due to fuel exhaustion as a result of the pilot’s inadequate preflight planning.NTSB IAD00LA061Accident · No injuriesLimited investigationFinal reportCessna 172H · Friendly, MDthe student pilot's inadequate compensation for winds that resulted in his failure to maintain runway alignment and a hard landing.NTSB IAD99LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Essex, MDA loss of engine power for undetermined reasons. Factors were the lack of suitable terrain for a forced landing and dark night conditions.NTSB IAD97LA072Accident · No injuriesLimited investigationFinal reportCessna 172H · Westminister, MDThe pilot misjudged landing distance on the runway and his failure to perform a go-around.NTSB BFO90FA067Accident · No injuriesField investigationFinal reportCessna 150K · Clinton, MDImproper planning/decision by the instructor pilot (CFI), which resulted in fuel exhaustion due to an inadequate supply of fuel.NTSB BFO90LA044Accident · No injuriesLimited investigationFinal reportCessna 172A · Pocomoke, MDThe pilot's misjudgement of distance and speed during the approach to land, and his failure to attain the proper touchdowwn point during the landing. The ditch was a related factor.NTSB BFO89LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Odenton, MDThe inflight collision with birds.NTSB BFO88LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Oakland, MDAccording to the pilot the landing approach for runway 22 was made over power lines. He stated that during the approach the stall warning horn activated and he increased power to maintain 60 mph with 20 degs of flaps. Once estimating that his intended point…NTSB BFO88LA042Accident · Minor injuriesLimited investigationFinal reportCessna 170 · Mechanicsville, MDThe acft was flown with the engine cowling plugs installed. The engine overheated and it lost power. The plt said he forgot to remove the plugs during the preflight. During the forced landing roll the acft collided with a berm and the rt main lndg gear was…NTSB BFO88LA035Accident · No injuriesLimited investigationFinal reportCessna 172 · Elkton, MDDuring cruise flt at an alt of 1500 ft, the engine suddenly stopped producing power. The acft was landed on railroad tracks in order to avoid trees. The acft nosed over during the landing. Plt stated that the right fuel tank gauge indicated 1/4 tank and the…NTSB BFO86FA020Accident · No injuriesField investigationFinal reportCessna 172H · Upper Marlboro, MDSince the fuel gages in the acft were known not to be accurate, the plt measured the amount of fuel in each tank with a dipstick before departing. He determined that he had 18 gallons for the 2 hours of flying he planned to do and based on a fuel consumption…NTSB NYC84LA126Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Hagerstown, MDThe plt initiated a 5 mi straight-in approach. When the acft was within 2 mi of the arpt, the plt reduced power, appliedcarb heat & slowed the acft. When it appeared he was going to land short, he added power, but the eng would not respond. The acft was…NTSB ATL83FIG03Accident · 1 fatalFinal reportCessna 172F · Hancock, MDThe aircraft collided with the top two wires of a powerline during a low altitude sight-seeing flight along the potomac river. The pilot stated he was maintaining visual contact with the ground should an emergency landing become necessary. He was staying high…NTSB IAD77FIG27Accident · Minor injuriesClosedCessna 172C · Stevensville, MDNTSB IAD77FIG21Accident · Minor injuriesClosedCessna 172 · College Park, MDNTSB IAD76FIG19Accident · Minor injuriesClosedCessna 172 · Laurel, MDNTSB IAD75FIG05Accident · No injuriesClosedMaule M-4C · Easton, MDNTSB IAD75FIA06Accident · No injuriesClosedCessna 172B · Clinton, MDNTSB IAD74AI003Accident · No injuriesClosedLuscombe 8E · Pasadena, MDNTSB IAD73FIG25Accident · No injuriesClosedCessna 172A · Essex, MDNTSB IAD71DIA22Accident · No injuriesClosedCessna 170B · Cobb Island, MDNTSB IAD71FIG26Accident · Serious injuriesClosedCessna 172 · College Park, MDNTSB IAD71FIG21Accident · Minor injuriesClosedCessna 172 · Reistertown, MDNTSB IAD70DIG14Accident · No injuriesClosedCessna 172 · Friendsville, MDNTSB IAD70D0070Accident · No injuriesClosedCessna 172 · Nanjemoy, MDNTSB DIA70F0002Accident · Minor injuriesClosedCessna 172E · Laurel, MDNTSB DIA69F0175Accident · Minor injuriesClosedCessna 172F · Gaithersburg, MDNTSB DIA68D0236Accident · Minor injuriesClosedCessna 172 · Sykesville, MDNTSB DIA68F0206Accident · Minor injuriesClosedCessna 172 · Queenstown, MDNTSB DIA68F0027Accident · No injuriesClosedCessna 172G · Clinton, MDNTSB DIA67D0083Accident · No injuriesClosedCessna 172 · Cambridge, MDNTSB DIA67D0081Accident · No injuriesClosedCessna 172 · Pittsville, MDNTSB NYC66F0598Accident · No injuriesClosedCessna 170B · Friendly, MDNTSB NYC66F0440Accident · No injuriesClosedCessna 172F · Baltimore, MDNTSB NYC66F0398Accident · No injuriesClosedCessna 172 · Gaithersburg, MDNTSB NYC66F0388Accident · Serious injuriesClosedCessna 172 · Stevensville, MDNTSB NYC66D0342Accident · No injuriesClosedCessna 172 · College Park, MDNTSB NYC66D0316Accident · No injuriesClosedCessna 170B · Baltimore, MDNTSB NYC66D0149Accident · No injuriesClosedCessna 172 · Essex, MDNTSB NYC65F0131Accident · No injuriesClosedCessna 172A · Westminster, MDNTSB NYC65F0034Accident · Minor injuriesClosedCessna 172 · Mitchellville, MDNTSB UNK64X4047Accident · Minor injuriesClosedCessna 172 · Hagerstown, MDNTSB UNK64X2913Accident · No injuriesClosedCessna 172 · Beltsville, MDNTSB UNK64X2593Accident · Minor injuriesClosedCessna 172B · Ocean City, MD