NTSB investigations: Cessna 177B
11 cases on aircraft the registry lists as Cessna 177B, where the first occurrence was “In flight collision with object”. 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
| 1984 | 1 |
|---|---|
| 1988 | 1 |
| 1989 | 2 |
| 1990 | 2 |
| 1991 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 2006 | 1 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073708')
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\" = 220))
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.aircraft_model_code IN ('2073708')
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" = 220))
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 SEA07LA249Accident · 1 fatalLimited investigationFinal reportCessna 177 · Pinecliff, WAThe pilot's failure to maintain clearance from the trees while maneuvering in mountainous terrain. Factors include the mountainous terrain, low ceilings, and trees in the area where the pilot was maneuvering.NTSB CHI06LA105Accident · 1 fatalLimited investigationFinal reportCessna 177 · Blackburn, MOThe pilot's failure to maintain obstacle clearance from the power line during low altitude maneuvering. A factor was the power line.NTSB CHI96LA130Accident · 3 fatalLimited investigationFinal reportCessna 177B · Perry, MOthe pilot's impairment of judgment and performance due to alcohol, and his failure to maintain altitude/clearance from the power transmission wires. Darkness, restricting the pilot's ability to see-and-avoid the transmission line, was a related factor.NTSB FTW95LA194Accident · Serious injuriesLimited investigationFinal reportCessna 177B · Casa, ARThe pilot's failure to maintain obstacle clearance.NTSB NYC92LA043Accident · No injuriesLimited investigationFinal reportCessna 177B · Dalmatia, PAThe pilot's failure to maintain proper altitude and object clearance which resulted in a collision with power lines.NTSB CHI91LA030Accident · No injuriesLimited investigationFinal reportCessna 177 · Mount Ayr, IAProper touch-down point not attained and go-around delayed by the PIC. Contributing factors were a downwind, crosswind, weather evaluation misjudged, wrong runway selected and lack of total experience by the PIC.NTSB CHI90LA173Accident · No injuriesLimited investigationFinal reportCessna C177B · Northport, MIPilot's delayed decision to abort the landing, and the aircraft's resultant inadequate clearance/altitude and impact with trees.NTSB ATL89LA191Accident · No injuriesLimited investigationFinal reportCessna 177B · Fort Gaines, GAThe pilot failed to maintain directional control of the airplane during takeoff, which resulted in a collision with trees adjacent to the runway.NTSB ATL89LA152Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Indian Trail, NCThe pilot's delay in aborting the landing after a bounced landing. Contributing factors were: improper flare by the pilot and the transmissions lines.NTSB BFO88LA052Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Milford, DEThe plt stated the landing apch was too fast and the acft bounced on touchdown. The plt stabilized the acft and attempted another touchdown, however, the acft bounced again. Having used over half the rwy by this time, the plt elected to abort the landing by…NTSB NYC84LA181Accident · No injuriesLimited investigationFinal reportCessna 177B · Spring Valley, NYSufficient alt was not obtained to clear trees located aprx 100 ft off the departure end of the rwy during an aborted landing to avoid an overrun.