NTSB investigations: Continental 0-300 series
42 cases on aircraft whose registry engine model is Continental 0-300 series, where the first occurrence was “Hard landing”. 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 | 3 |
|---|---|
| 1983 | 3 |
| 1984 | 3 |
| 1985 | 2 |
| 1987 | 2 |
| 1988 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1994 | 2 |
| 1995 | 1 |
| 1996 | 4 |
| 1998 | 3 |
| 1999 | 1 |
| 2000 | 4 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 2 |
| 2004 | 3 |
| 2005 | 2 |
| 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 ('17022')
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\" = 200))
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 ('17022')
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" = 200))
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 DFW07CA140Accident · No injuriesData collectionFinal reportCessna 172G · Katy, TXThe student pilot's improper flare and his failure to recover from a bounced landing.NTSB ATL06CA033Accident · No injuriesData collectionFinal reportCessna 172H · Waycross, GAThe student pilot's improper landing flare and the CFI's inadequate supervision resulting in a hard landing.NTSB MIA05CA067Accident · No injuriesData collectionFinal reportCessna 172 · Jacksonville, FLThe pilot's improper landing flare which resulted in a hard landing.NTSB MIA05LA027Accident · No injuriesLimited investigationFinal reportCessna 170A · Opa Locka, FLThe pilot's improper landing flare/touchdown, which resulted in a hard landing.NTSB CHI04CA121Accident · No injuriesData collectionFinal reportCessna 172C · Fort Leavenwort, KSThe inadequate flare by the pilot.NTSB CHI04CA088Accident · Minor injuriesData collectionFinal reportCessna 172A · Springfield, MOThe pilot failed to initiate a go-around and the airplane porpoised during the hard landing. Factors associated with the accident were the excessive groundspeed and the overload failure of the nose gear.NTSB NYC03CA185Accident · Minor injuriesData collectionFinal reportCessna 172E · Lemont Furnace, PAThe pilot's improper bounced landing recovery. A factor was the pilot's inadequate flare during the initial touchdown.NTSB CHI03LA166Accident · No injuriesLimited investigationFinal reportCessna 172H · Council Bluffs, IAMisjudgment of the landing flare by the pilot in command resulting in a hard landing.NTSB LAX02LA168Accident · No injuriesLimited investigationFinal reportCessna 170B · Show Low, AZThe pilot's improper recovery from a bounced landing resulted in a loss of aircraft control. A factor was a sudden wind shift on final approach.NTSB CHI02LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Manito, ILThe pilot's improper planning and decision and his failure to maintain adequate airspeed, which resulted in a stall and hard landing. The gusting crosswind conditions were a contributing factor.NTSB ATL01LA101Accident · No injuriesLimited investigationFinal reportCessna 172 · Mobile, ALThe pilot's improper landing flare that resulted in a hard landing. A factor was the pilot induced porpoise.NTSB ATL01LA018Accident · No injuriesLimited investigationFinal reportCessna 172 · Mobile, ALThe pilot's improper flare during landing that resulted in a hard landing and the subsequent overload failure of the nose gear assembly.NTSB LAX01LA008Accident · No injuriesLimited investigationFinal reportCessna 172H · Hilo, HIAn inadvertent pilot-induced porpoise resulting from the pilot's improper landing flare and inadequate power management.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 FTW00LA148Accident · No injuriesLimited investigationFinal reportCessna 172H · Mesquite, TXThe flight instructor's inadequate supervision of the student pilot during the landing.NTSB FTW00LA049Accident · No injuriesLimited investigationFinal reportCessna 172 · Fort Worth, TXThe student pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise.NTSB CHI99LA030Accident · No injuriesLimited investigationFinal reportCessna 172C · Falls City, NEthe flight instructor (on the ground)'s conducting inadequate initial training of the student pilot. Factors were the student pilot's misjudging the flare and his lack of total experience in the type of operation.NTSB LAX98LA301Accident · No injuriesLimited investigationFinal reportCessna 172F · Long Beach, CAThe pilot's misjudging the flare point and failure to maintain an adequate airspeed margin, which resulted in a stall/mush and hard landing. A contributing factor was the dark night conditions.NTSB FTW98LA166Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Collins, COthe pilot's improper in flight planning/decision in electing to land with a known 30 knot tailwind. Factors were high winds and a tailwind.NTSB NYC97LA002Accident · No injuriesLimited investigationFinal reportCessna 172H · Chatham, MAthe pilot's improper flare, which resulted in a hard landing. A factor relating to the accident was: the pilot's lack of experience in the make and model of airplane.NTSB FTW96LA362Accident · No injuriesLimited investigationFinal reportCessna 172H · Durango, COthe pilot's improper flaring of the airplane at too high an altitude, resulting in a hard landing.NTSB LAX96LA209Accident · No injuriesLimited investigationFinal reportCessna 172 · Marana, AZthe pilot's improper flare and improper recovery from a bounced landing.NTSB ANC96LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Fairbanks, AKThe student pilot's premature flare and the flight instructor's failure to perform remedial action prior to the hard landing.NTSB CHI95LA220Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Cedar Rapids, IAthe pilot's lack of experience in flying from the right seat. A factor was the steep final approach.NTSB MIA95LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Indiantown, FLThe improper landing flare by the pilot resulting in the hard landing.NTSB CHI94LA338Accident · No injuriesLimited investigationFinal reportCessna 172 · Mora, MNwas an improper touchdown by the pilot-in-command. Factor's associated with this accident were the pilot's diverted attention due to his perception of a crosswind condition and the pilot not performing a recovery from a bounced landing.NTSB SEA91LA080Accident · No injuriesLimited investigationFinal reportCessna 172A · Hood River, ORAn inadequately planned approach which resulted in a hard landing. Factors to the accident were rough water landing conditions, poor supervision by the CFI, and the overload condition to the float assembly.NTSB DEN91LA011Accident · No injuriesLimited investigationFinal reportCessna 172H · Buena Vista, COThe failure of the pilot to flare properly during landing. The pilot's total lack of experience is a factor.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 CHI87LA169Accident · No injuriesLimited investigationFinal reportCessna 172 · Madison, WIThe instructor (CFI) & pvt plt (student) were on a renter's check-out flt to familiarize the student with a Cessna 172. While practicing landings, tower psnl provided a windshear alert. Drg an apch to land, the acft went into a high sink rate over the apch…NTSB FTW87LA167Accident · Serious injuriesLimited investigationFinal reportCessna 172E · Quitman, TXDuring final approach for landing, the pilot allowed the airspeed to drop. The aircraft stalled at approximately 30 to 40 feet AGL. Substantial damage occurred when the aircraft bounced, cartwheeled and slid to a stop backwards 300 feetbeyond the threshold.NTSB FTW85LA334Accident · No injuriesLimited investigationFinal reportCessna 172B · Ada, OKThe student plt, who had been executing touch and go landings, stated that the acft bounced on touchdown and began porpoising. The student over-corrected and the acft subsequently impacted the runway in a nose low attitude damaging the prop, nose gear and the…NTSB ATL85LA116Accident · No injuriesLimited investigationFinal reportCessna 172H · Buena Vista, GAAcft slipped on final due to being high. Landed hard and bounced. On second touchdown rudder was still applied and acft veered off runway colliding with ditch bank.NTSB LAX85LA009Accident · No injuriesLimited investigationFinal reportCessna 172H · Long Beach, CAThe plt said that after he returned to the arpt for a night landing, he applied back pressure during the flare, then heard the stall warning horn. Subsequently, the acft was damaged when it landed hard & bounced. However, the plt was able to taxi to the…NTSB ATL84FLT08Accident · No injuriesFinal reportCessna 172 · Walls, MSThe plt stated that he stalled the acft about 15 ft AGL. When the acft hit the rwy it flipped over.NTSB CHI84LA100Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Lk In The Hills, ILThe plt made a hard landing which damaged the nose gear making it impossible for the plt to avoid a collision with a snowbank during a subsequent landing.NTSB SEA83LA091Accident · No injuriesLimited investigationFinal reportSwift GC-1B · Everett, WAThe acfts left main landing gear sheared and the acft came to rest off the runway in the grass. The pilot said that eventhough the landing gear light indicated down and locked he does not believe the rt main gear was down and locked. Duringan attempted…NTSB FTW83LA344Accident · No injuriesLimited investigationFinal reportCessna 172D · New Braunfels, TXThe acft made a hard landing which was hard enough to blow the nose gear tire and collapse the nose gear assembly.NTSB SEA83LA047Accident · No injuriesLimited investigationFinal reportCessna 172 · Payette, IDThe acft bounced after a hard landing and drifted off the runway into a tree. The acft then stopped in the mud and nosedover. The landing was on runway 31 and the wind was 360 degrees at 8 KTS.NTSB FTW82DA333Accident · No injuriesFinal reportCessna 172F · Springlake, TXThe student pilot reported that during a landing, he flared too high. The aircraft then stalled onto the runway and was substantially damaged. Reportedly, he had a 3 kt tail wind and the density altitude was about 6000 ft.NTSB FTW82DA224Accident · No injuriesFinal reportCessna 172 · Duncan, OKThe student pilot was practicing touch-and-go landings in winds from the southeast at 10 gusting 15 KTS. Just prior to landing, the aircraft encountered a gust of wind, then touched down hard. The engine fire wall was buckled and two tires blew out.NTSB ATL82IA076Incident · No injuriesIncident investigationFinal reportCessna 172F · Mobile, ALUpon arrival at the aircraft, the pilot noted that the nose gear strut was under inflated. The pilot, who is training to be an A&P mechanic, diagnosed the problem as an oil leak. However, to avoid aborting the flight, he inflated the strut with air only and…