NTSB investigations, 2011
6 cases where the defining event was Air traffic event.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 3 |
| 2010 | 6 |
| 2011 | 6 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 4 |
| 2017 | 4 |
| 2018 | 7 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 2 |
| 2022 | 4 |
| 2023 | 7 |
| 2024 | 7 |
| 2025 | 4 |
| 2026 | 14 |
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 year(c.\"eventDate\") = 2011
AND c.\"mKey\" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.\"isDefiningEvent\" AND e.\"tier2Number\" = '100')
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 year(c."eventDate") = 2011 AND c."mKey" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e."isDefiningEvent" AND e."tier2Number" = '100') 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 OPS11IA819Incident · No injuriesIncident investigationFinal reportEmbraer EMB-135KL · Chicago, ILThe improper air traffic control takeoff clearance issued by the local controller because of his lack of monitoring and lack of awareness of the conflicting arrival airplane.NTSB OPS11IA673Incident · No injuriesIncident investigationFinal reportEmbraer EMB-145EP · Gulfport, MSthe Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff.NTSB OPS11IA552Incident · No injuriesIncident investigationFinal reportEmbraer EMB-145LR · Chicago, ILThe air traffic controller’s failure to adhere to runway separation requirements and his issuance of an improper takeoff clearance. Contributing to the incident was the controller's failure to recall that there was an arrival inbound to a crossing runway.NTSB DCA11WA054Incident · No injuriesForeign investigationBoeing 767 · Fukuoka, JapanThe Japan Transport Safety Board (JTSB) has notified the NTSB of an incident involving a B767-300 and a DHC-8-402 that occurred on May 10, 2011. The NTSB has appointed a U.S. Accredited Representative to assist the JTSB investigation under the provisions of…NTSB OPS11IA401Incident · No injuriesIncident investigationFinal reportArlington, VAThe tower controller's loss of consciousness induced by lack of sleep, fatigue resulting from working successive midnight shifts, and air traffic control scheduling practices.NTSB OPS11IA410Incident · No injuriesIncident investigationFinal reportBoeing 757-232 · Atlanta, GAThe air traffic controllers’ failure to adhere to required radar identification procedures, which resulted in loss of separation between the departing Boeing 757 and three other airplanes. Contributing to the incident was the pilots’ inadequate preflight…