NTSB investigations
25 cases where NTSB found Accuracy of communication.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 2 |
| 2010 | 2 |
| 2011 | 2 |
| 2012 | 2 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 4 |
| 2019 | 1 |
| 2022 | 1 |
| 2023 | 3 |
| 2024 | 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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '02063515')) 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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '02063515')) 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 CEN24LA219Accident · Serious injuriesClass 4 · LimitedFinal reportSchweizer SGS 1-23H-15 · Chouteau, OKThe student pilot’s failure to maintain control of the glider while landing. Contributing to the accident was the unclear communications between the student pilot and instructor.NTSB ERA24LA062Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Miami, FLThe business jet flight crew’s failure to appropriately position their airplane to mitigate the impact of their extended duration, high-power engine run, and their failure to adequately communicate these factors to air traffic control, which resulted in the…NTSB DCA24LA043Incident · No injuriesClass 4 · LimitedFinal reportBoeing 787 · Chicago, ILThe flight crew’s misperception of the distance required to safely pass the hangar and failure to request additional ground handling support while taxiing, which resulted in a collision with a hangar. Contributing to the accident was United Airlines…NTSB CEN23LA198Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Wichita, KSThe pilot’s failure to maintain a safe taxi distance from a turbine-powered airplane, resulting in an encounter of the turbine-powered airplane’s jet blast while taxiing.NTSB WPR22LA368Accident · Serious injuriesClass 4 · LimitedFinal reportFirefly Balloons Firefly 8B-15 · Las Cruces, NMThe pilot’s failure to maintain the proper descent rate during the balloon’s approach to landing, which resulted in a hard landing and serious passenger injury.NTSB GAA19CA582Accident · No injuriesData collectionFinal reportDiamond DA 40 · Mesa, AZThe pilot's decision to abort a go-around with insufficient runway remaining to safely stop the airplane, which resulted in a loss of control, runway excursion and impact with a concrete barrier.NTSB GAA18CA017Accident · Serious injuriesData collectionFinal reportYoung David E Pitts S1 C · Farmville, VAThe pilot’s failure to see and avoid the other airplane landing in the opposite direction on the runway. Contributing to the accident was the pilot’s failure to use the correct runway call sign in his radio communications.NTSB GAA17CA450Accident · Minor injuriesData collectionFinal reportRobinson Helicopter R44 · Dunlap, ILThe pilot’s failure to visually confirm that the helicopter was disconnected from hoses during refueling operations. Contributing to the accident was the pilot’s and ground crew’s misunderstanding of the hand signals.NTSB GAA17CA398Accident · No injuriesData collectionFinal reportRobinson Helicopter R44 II · Pocahontas, ILThe helicopter pilot’s miscommunication with the ground crewmember during reloading operations, which resulted in a takeoff with the filler hose attached to the helicopter and subsequent impact with a truck.NTSB OPS17IA014IncidentClass 3 · IncidentFinal reportEmbraer S A ERJ 170-200 LR · San Francisco, CAThe local controller's issuance of a landing clearance for runway 28L to the ERJ170, and the subsequent issuance of line up and wait instructions to the A320 for runway 28L, resulting in a runway incursion.NTSB WPR16FA172Accident · 2 fatalField investigationFinal reportBeech A36 · Sparks, NVThe pilot's selection of a landing runway which, given the wind and traffic conditions, was susceptible to high crosswinds and the translation of wake turbulence across its approach path, and the controller's and pilot's failure to ensure separation from the…NTSB WPR15MA243Accident · 5 fatalMajor investigationFinal reportCessna 172M · San Diego, CAThe local controller's (LC) failure to properly identify the aircraft in the pattern and to ensure control instructions provided to the intended Cessna on downwind were being performed before turning Eagle1 into its path for landing. Contributing to the LC's…NTSB ERA15FA313Accident · 1 fatalField investigationFinal reportBeech C35 · Hicksville, NYThe pilot's improper decision to delay turning toward a suitable runway once he realized that an engine failure had occurred, which resulted in his having inadequate altitude to glide to a suitable runway, and the New York terminal radar approach control…NTSB CEN15FA316Accident · 2 fatalField investigationFinal reportBeech V35B · Colbert, OKThe pilot's failure to properly position the fuel selector, which resulted in a total loss of engine power due to fuel starvation. Contributing to the severity of the accident was the pilot's failure to select an appropriate location for a forced landing,…NTSB WPR14FA349Accident · 1 fatalField investigationFinal reportBeech V35B · Novato, CAThe instrument-rated pilot's decision to conduct a visual approach to the airport in night, instrument meteorological conditions, which resulted in controlled flight into terrain. Contributing to the accident was the pilot's loss of situational awareness, the…NTSB DCA13LA039Accident · No injuriesLimited investigationFinal reportBoeing 777 - 300 · Miami, FLLV-BMT flight crew's incorrect evaluation of the clearance between the two aircraft, leading to the inadvertent collision of the left winglet with the horizontal stabilizer and elevator of F-GNZI. Contributing to the accident were the incorrect instructions…NTSB OPS12IA849Incident · No injuriesIncident investigationFinal reportArlington, VAA hearback/readback error on the part of the tower traffic management coordinator, who did not understand the request being made by the approach control area supervisor and then communicated that misunderstanding to the local controllers. Contributing to the…NTSB OPS12WA430Incident · No injuriesForeign investigationGulfstream Aerospace GV SP (G550) · Ontario, CanadaN217AL, a private Cessna 750, was en route between San Jose, California (KSJC), and Bedford, Massachusetts (KBED) at FL430. N128GV, a private Gulfstream V, was en route between Bradley/Windsor Locks, Connecticut (KBDL), and San Francisco, California (KSFO),…NTSB ERA11FA401Accident · 1 fatalField investigationFinal reportSlingsby Capstan Type 49B · Hollywood, MDThe glider pilot’s improper response to the “check spoilers” signal from the tow pilot. Contributing to the accident was the glider pilot’s failure to confirm that the spoilers were closed and locked before takeoff, and the glider copilot’s improper crew…NTSB OPS11IA246Incident · No injuriesIncident investigationFinal reportBoeing 777 · 80 SE of JFK (Atlantic Ocean), NYIncomplete and incorrect coordination between air traffic controllers that resulted in the 777 and the two C17s being cleared to maintain the same altitude. Contributing to the incident was the controllers’ non-adherence to established communications…NTSB OPS11IA054Incident · No injuriesIncident investigationFinal reportDassault FALCON900EX · Teterboro, NJThe pilot of the F900 overshooting of the final approach course, which conflicted with traffic in the pattern. Contributing to the accident was the lack of appropriate coordination between the tower controller and the approach controller.NTSB CEN11LA023Accident · Serious injuriesLimited investigationFinal reportBell 206B · Newton, TXThe pilot’s attempted takeoff with the fuel hose attached to the helicopter and the pilot and ground crew’s failure to accurately communicate.NTSB OPS10IA003Incident · No injuriesIncident investigationFinal reportDetroit, MIThe ground controller did not monitor the progress of the fire truck to ensure that the driver followed the expected route. A contributing factor was the ground controller's misunderstanding of the fire truck driver's requested destination on the airport.NTSB OPS09IA002Incident · No injuriesIncident investigationFinal reportTampa, FLThe controller's issuance of an improper climb clearance to the pilot of Berry Aviation flight 510. Contributing to the incident was the controller's distraction while he searched for a misplaced flight progress strip.NTSB NYC08CA309Accident · No injuriesData collectionFinal reportBell 206B · Eutaw, ALThe pilot's inadequate preflight inspection.