NTSB investigations: Taylorcraft F19
5 cases on aircraft the registry lists as Taylorcraft F19, 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
| 1983 | 1 |
|---|---|
| 1984 | 1 |
| 1999 | 1 |
| 2003 | 1 |
| 2005 | 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 ('8850904')
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 ('8850904')
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 ANC06LA014Accident · Minor injuriesLimited investigationFinal reportTaylorcraft F-19 · Chenga Bay, AKThe pilot's failure to maintain adequate altitude/clearance during takeoff initial climb, which resulted in an in-flight collision with trees, and subsequent collision with the ground.NTSB ANC03CA078Accident · No injuriesData collectionFinal reportTaylorcraft F-19 · Aniak, AKThe pilot's inadvertent touchdown, and failure to maintain clearance from trees during an aborted landing, which resulted in the nose over of the airplane. A factor associated with the accident was the soft terrain.NTSB ANC00LA016Accident · Serious injuriesLimited investigationFinal reportTaylorcraft F-19 · Skwentna, AKThe pilot's selection of an unsuitable landing/takeoff area. Factors associated with the accident were snow-covered terrain, and a tree.NTSB ANC84LA096Accident · No injuriesLimited investigationFinal reportTaylorcraft F19 · Rainbow Lake, AKThe plt stated that the acft 'was sluggish getting on the step. After lift-off it still performed under par. We cleared the hills and trees. On the downside of the hill we hit a downdraft. We hit the trees nose high; climb power.' The reported wind was calm.…NTSB MIA83FA173Accident · 1 fatalField investigationFinal reportTaylorcraft TC-19 · Lorida, FLWitnesses along a highway observed the acft flying at low altitude. One witness saw the acft hit a powerline, climb a little, then crash nose first.