NTSB investigations, GA
6 cases where the first occurrence was “Midair collision”.
Cases per year
| 1984 | 1 |
|---|---|
| 1987 | 1 |
| 1991 | 1 |
| 1993 | 2 |
| 1998 | 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.\"eventStateOrRegion\" = 'GA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 270)
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."eventStateOrRegion" = 'GA' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 270) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 ATL98FA060Accident · 5 fatalField investigationFinal reportCessna 525 · Marietta, GAThe failure of both pilots to see and avoid conflicting traffic, and the failure of the 172 pilot to operate the transponder as required by current regulations. Factors were the controller's failure to observe the traffic conflict, the lack of radar conflict…NTSB ATL93FA082Accident · 2 fatalField investigationFinal reportAmerican AA-1A · Statesboro, GAInadequate visual lookout by the pilots of both aircraft. Factors related to the accident were: failure of the pilot of N9317L to illuminate his aircraft navigation lights, and improper radio communications by the pilot of N47WD by selecting the wrong UNICOM…NTSB ATL93FA061Accident · 4 fatalField investigationFinal reportRobinson R22B · Atlanta, GAThe failure of the pilot/applicant of the R22B, N621SG, to follow low approach procedures, and the failure of the designated examiner/observer in the R22B to maintain visual separation from the Cessna 152, N5532Q. Contributing factors to the accident were:…NTSB ATL91FA108Accident · 2 fatalField investigationFinal reportCessna T37B · Chickamauga, GAThe T-37 pilot misjudged the clearance between his aircraft and the A-26.NTSB ATL87FA130Accident · 2 fatalField investigationFinal reportCessna 182R · Kennesaw, GAN5511N was in the traffic pattern at cobb county airport-mc collum field and was near the turning point from crosswind to dwnd when it was struck by N52995. N52995 was making a straight-in entry into the downwind leg of the traffic pattern from the west with…NTSB MIA84FA241Accident · 4 fatalField investigationFinal reportCessna 152 · Valdosta, GAThe two acft collided about a mile east of the arpt on the downwind leg of the traffic pattern. One of the acft, N25853,called Valdosta radio and reported left downwind for rwy 17.Valdosta advised that another acft had just departed rwy 17 2 minutes prior.…