NTSB investigations, 2010
8 cases where the sequence of events included Near midair/TCAS alert/loss of separation.
Cases per year
| 2008 | 3 |
|---|---|
| 2009 | 1 |
| 2010 | 8 |
| 2011 | 7 |
| 2012 | 1 |
| 2014 | 2 |
| 2015 | 2 |
| 2016 | 2 |
| 2017 | 4 |
| 2018 | 6 |
| 2021 | 5 |
| 2022 | 7 |
| 2023 | 6 |
| 2024 | 18 |
| 2025 | 15 |
| 2026 | 9 |
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\") = 2010
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '260' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\"))
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") = 2010 AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '260' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) 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 OPS11IA101Incident · No injuriesIncident investigationFinal reportBoeing 737-832 · 66 NM East of Hobe Sound, FLAir traffic controllers did not maintain required awareness of available flight data and aircraft positions, resulting in issuance of an incorrect altitude clearance that caused a loss of standard instrument flight rules separation between the two aircraft.NTSB OPS10IA574Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-214 · Minneapolis, MNThe Local North Controller's issuance of a left-turn heading to the Airbus without establishing the position and heading of the Beech. Contributing to the incident was the Local South Controller's distraction with a ground movement operation and lack of…NTSB DCA10LA083Accident · Serious injuriesLimited investigationFinal reportEmbraer ERJ 170 100 SE · Summit, MSthe abrupt maneuver that was appropriately initiated to comply with the TCAS resolution advisory caused by the momentary projected loss of separation from converging traffic. Contributing to the accident was a passenger's decision to disregard the seatbelt…NTSB OPS10IA163Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B19 · Burbank, CAThe local controller’s failure to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class C airspace.NTSB OPS10IA155Incident · No injuriesIncident investigationFinal reportEmbraer EMB-135KL · Chicago, ILThe air traffic controller's issuance of an improper takeoff clearance to the pilot of the Embraer. Contributing to the incident was the instructor’s inadequate monitoring of the trainee local controller.NTSB OPS10IA020Incident · No injuriesIncident investigationFinal reportBoeing 777-222 · San Francisco, CAThe local controller's issuance of a takeoff clearance to the Boeing 777 without ensuring that approved separation would exist with the Cessna 182. Contributing to the incident were tower procedures that permitted transitioning aircraft to cross the runway 28…NTSB OPS10IA014Incident · No injuriesIncident investigationFinal reportBoeing 737 · Worton, MDThe R10/12 controller issued an improper vector and descent clearance to the GII that put the airplane on a coverging flight path with the B737. Contributing to the incident was the failure of the FAA's training program to correct ongoing controller…NTSB OPS10IA015Incident · No injuriesIncident investigationFinal reportCessna 208B · Phoenix, AZThe Cessna 208 pilot’s failure to identify the correct landing runway.