NTSB investigations: Great Lakes 2T-1A-2
5 cases on aircraft the registry lists as Great Lakes 2T-1A-2, where the first occurrence was “Loss of control - on ground/water”. 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 |
|---|---|
| 1985 | 1 |
| 1987 | 2 |
| 1989 | 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 ('3910101')
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\" = 260))
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 ('3910101')
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" = 260))
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 NYC90LA022Accident · Minor injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Pittstown, NJThe pilot's failure to maintain directional control during landing.NTSB FTW87LA154Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Baytown, TXDrg the lndg roll, the acft started to drift to the left, so the plt corrected with right rudder. He said he over- controlled, then applied left rudder & brake, followed by right rudder & brake. Subsequently, the situation became aggravated until both main…NTSB LAX87LA211Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Tucson, AZA Great Lakes 2T-1A-2 nosed over during landing. The pilot indicated that he had contacted the airport on the UNICOM frequency and was informed that the winds were favoring runway 30. On short final approach to runway 30 the pilot glanced a wind sock located…NTSB LAX85LA295Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Angwin, CADuring a VFR cross country flt, wx conditions along the route induced the plt to divert to the Angwin arpt. After an overflt to obtain wind information from the wind sock, the plt said he entered the pattern and completed a normal approach and touchdown.…NTSB MIA85LA062Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Naples, FLAfter making a three point landing on the paved runway the pilot lost control of the acft, it veered left and ran off the rwy. The acft then struck a mound of sandy soil and nosed over.