NTSB investigations: Cessna 170B
11 cases on aircraft the registry lists as Cessna 170B, where the first occurrence was “Nose over”. 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 | 1 |
|---|---|
| 1984 | 1 |
| 1991 | 2 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2006 | 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.aircraft_model_code IN ('2072306', '2072307')
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\" = 300))
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 ('2072306', '2072307')
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" = 300))
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 ANC06CA040Accident · No injuriesData collectionFinal reportCessna 170B · Palmer, AKThe pilot's selection of unsuitable terrain for landing, which resulted in the airplane nosing over during the landing roll. A factor associated with the accident was the snow covered terrain.NTSB LAX01LA132Accident · No injuriesLimited investigationFinal reportCessna 170B · Lincoln, CAThe certified flight instructor's inadequate supervision of his dual student who used excessive braking on landing resulting in the airplane's nose over.NTSB LAX01LA010Accident · No injuriesLimited investigationFinal reportCessna 170B · San Carlos, CAThe pilot's improper and excessive application of brakes resulting from his failure to maintain directional control during landing rollout.NTSB ANC98LA142Accident · No injuriesLimited investigationFinal reportCessna 170B · Port Alsworth, AKThe solo student pilot's excessive application of brakes during taxi from landing. Factors associated with the accident were the pilot's selection of unsuitable terrain for a precautionary landing, rough terrain, and the fuel leak from the fuel tank vent.NTSB SEA97LA053Accident · No injuriesLimited investigationFinal reportCessna 170B · Toledo, WAThe pilot's excessive application of the brakes on a tailwheel equipped aircraft. Factors include the pilot's inadequate compensation for wind conditions, and a crosswind blowing at the time of the landing.NTSB SEA97LA019Accident · No injuriesLimited investigationFinal reportCessna 170B · Utica, MTThe pilot's improper use of the brakes, while landing a tailwheel aircraft in crosswind conditions. The crosswind was a related factor.NTSB SEA96LA218Accident · No injuriesLimited investigationFinal reportCessna 170 · Enterprise, ORthe pilot's misjudgment of speed and distance during the approach/landing, his failure to attain a proper touchdown point during the landing, and his failure to go around (while there was sufficient runway remaining). The short runway was a related factor.NTSB ANC92LA004Accident · No injuriesLimited investigationFinal reportCessna 170B · Chugiak, AKThe student pilot's failure to maintain directional control during the takeoff run.NTSB ANC91LA083Accident · No injuriesLimited investigationFinal reportCessna 170B · Lake Louise, AKThe pilot not maintaining directional control during the takeoff roll. Contributing to the accident was the rough condition of the airstrip.NTSB ANC84LA048Accident · No injuriesLimited investigationFinal reportCessna 170B · Skwentna, AKThe plt elected to land on a snow covered strip that had a frozen snow crust & was rutted. He stated that during the touchdown, the acft bounced, then he elected to go around. However, the acft touched down again & broke thru the frozen crust, then nosed over.NTSB ANC82DA053Accident · No injuriesFinal reportCessna 170B · Near Anchorage, AKWhile on a fishing trip, the pilot landed on an abandoned oil exploration roadway. The pilot reported that he did not realize how narrow the roadway was until after he had landed and slowed the aircraft. He reported that he was not aware that the edges of the…