Final NTSB investigations
59 cases where the sequence of events included Air traffic event.
Cases per year
| 2008 | 6 |
|---|---|
| 2009 | 5 |
| 2010 | 7 |
| 2011 | 8 |
| 2012 | 4 |
| 2013 | 2 |
| 2014 | 4 |
| 2015 | 1 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 2 |
| 2019 | 1 |
| 2021 | 3 |
| 2022 | 2 |
| 2023 | 5 |
| 2024 | 1 |
| 2025 | 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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '100' 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 c."completionStatus" = 'Completed' AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '100' 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 CEN25LA370Accident · No injuriesClass 4 · LimitedFinal reportBoeing E75 · Benton, KSThe pilot's failure to maintain clearance from a moving vehicle during an evasive maneuver from a perceived conflict with another airplane. Contributing to the accident was the pilot of the other airplane’s non-standard phraseology and inaccurate position…NTSB CEN24LA144Accident · 1 fatalClass 3 · LimitedFinal reportPiper PA28 · Muncie, INThe pilot’s spatial disorientation and subsequent loss of control while maneuvering outside established instrument approach procedures in instrument meteorological conditions, which resulted in an impact with terrain. Contributing to the accident was the…NTSB OPS24LA011Incident · No injuriesClass 4 · LimitedFinal reportDiamond Aircraft Ind DA20-C1 · North Las Vegas, NVThe local controller’s loss of situational awareness, inadequate provision of traffic advisory or safety alert information, and lack of positive control, that resulted in a near-midair collision.NTSB OPS24LA004IncidentClass 4 · LimitedFinal reportAirbus A321-271N · Long Beach, CAThe local controller’s poor judgment in prioritization of their ground traffic ahead of their airborne traffic, that became a distraction and led to a loss of situational awareness resulting in a near midair collision. Contributing to the incident was the…NTSB OPS23FA010IncidentClass 4 · FieldFinal reportBoeing 737-7BD · San Diego, CAThe local control controller’s poor judgment in duty prioritization which distracted them from monitoring arriving and departing traffic and resulted in a runway incursion and loss of same runway separation. Contributing was the operations supervisor’s…NTSB DCA23LA395Accident · Serious injuriesClass 4 · LimitedFinal reportAirbus A320-214 · Fort Lauderdale, FLThe flight crew’s abrupt change in pitch in response to a traffic collision advisory system resolution advisory that resulted in a serious injury to a flight attendant.NTSB DCA23LA179Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-823 · Sarasota, FLThe local controller’s failure to prioritize and properly monitor the runway and airport environment along with his erroneous assumption that ROU 1633 would depart from runway 14 before AAL2172 arrived to land on the same runway, which resulted in a loss of…NTSB DCA22LA175Accident · No injuriesClass 4 · LimitedFinal reportBoeing 777 · Chicago, ILThe ground controller’s inappropriate routing of the B777 through a non-movement area, resulting in the airplane’s right wingtip contacting a light pole. Contributing to the accident was the lack of an appropriate display of taxiway BB2 as a restricted…NTSB ERA22FA318Accident · 4 fatalClass 3 · FieldFinal reportPiper PA-46-350P · North Las Vegas, NVThe low-wing airplane pilot’s failure to ensure that the airplane was aligned with the correct runway, which resulted in a collision with the high-wing airplane on final approach. Contributing to the accident was the controller’s failure to provide timely and…NTSB ERA22LA022Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Statesboro, GAThe student pilot’s failure reduce power and apply sufficient braking after landing, which resulted in a runway excursion and impact with objects and terrain.NTSB OPS21LA003Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-8H4 · San Diego, CAThe blocked go-around radio instruction from the air traffic control tower to the arrival aircraft which resulted in the arrival aircraft continuing the landing approach. This led to a loss of separation between the landing aircraft and the aircraft awaiting…NTSB OPS21LA002Incident · No injuriesClass 3 · LimitedFinal reportAirbus A319-112 · St Petersburg-Clearwater, FLThe air traffic controller’s failure to properly scan the runway and local area, and their general loss of situational awareness, resulting in a near midair collision. Contributing to the incident was the Cessna 337 pilot's poor decision making when he failed…NTSB CEN19CA227Accident · No injuriesData collectionFinal reportVans RV-8 · Oshkosh, WIThe pilot’s failure to maintain adequate spacing from the lead airplane while landing following revised landing instructions, which necessitated that the pilot conduct an improper landing flare and resulted in a hard landing.NTSB OPS18IA014IncidentClass 3 · IncidentFinal reportEmbraer EMB145 · Springfield, MOThe local controller failing to follow established facility directives and issuing a clearance for takeoff from a runway not under his control.NTSB ANC18LA030Accident · No injuriesLimited investigationFinal reportChampion 7GC · Anchorage, AKThe pilot's failure to maintain directional control during landing with a crosswind, which resulted in a loss of control and failure of the main landing gear. Contributing to the accident was the pilot's self-induced pressure to land.NTSB OPS18IA003IncidentClass 3 · IncidentFinal reportBombardier CL600 2D24 · Medford, ORThe incident was caused by the air traffic controller assigning an altitude below the published procedure altitude for the approach segment to be flown prior to the aircraft being established on a published portion of the approach. Contributing to the…NTSB DCA18LA024AccidentClass 3 · LimitedFinal reportBoeing 777 · Jamaica, NYThe air traffic controller's improper instruction to the Egypt Air airplane flight crew to pass in an area where passing is prohibited, which led to a ground collision.NTSB OPS17IA021IncidentClass 3 · IncidentFinal reportCessna 172S · New Orleans, LAThe air traffic controller not following Federal Aviation Administration directives to establish sequencing and spacing between aircraft operating to the same runway.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 OPS17IA010Incident · No injuriesIncident investigationFinal reportBoeing 777 · Mt. Wilson, CAThe incident was caused by the air traffic controller assigning the pilots a left turn instead of the required right turn after departure which placed the aircraft in an unsafe proximity with terrain and obstructions. Contributing to the incident was the air…NTSB OPS16IA010IncidentClass 3 · IncidentFinal reportMooney M20R · Jacksonville, FLThe air traffic controller's decision to issue climb instruction to one aircraft without ensuring the required separation with another could be maintained. Contributing to the incident was the air traffic controller's failure to issue a safety alert in a…NTSB OPS16IA009IncidentClass 3 · IncidentFinal reportCessna 172S · Honolulu, HIThe air traffic controller's decision to clear an aircraft to land on a runway occupied by another aircraft that had previously been instructed to line up and wait. Contributing to the runway incursion was the failure of the air traffic controller to visually…NTSB CEN16LA067Accident · No injuriesLimited investigationFinal reportHawker 400 · Telluride, COThe limitations of the air traffic control equipment that prevented the controller's timely recognition of NOTAM information that was effective immediately and resulted in the issuance of an approach clearance to a closed runway. Also causal was the pilots'…NTSB OPS14IA011Incident · No injuriesIncident investigationFinal reportBoeing 777 - 236 · Shemya, AKThe air traffic controller’s failure to identify a conflict between two aircraft and to issue an adequate clearance, which resulted in a loss of required separation. Contributing to the incident was the Federal Aviation Administration’s failure to provide…NTSB OPS14IA007Incident · Minor injuriesIncident investigationFinal reportBoeing 757 · Powhatan, VAThe air traffic controller’s failure to provide required advisories about significant radar-observed convective precipitation along both airplanes’ flight routes and the air route traffic control center’s lack of a program to ensure that air traffic…NTSB OPS14IA005Incident · No injuriesIncident investigationFinal reportEmbraer EMB 145XR · Newark, NJThe local controller’s failure to comply with Federal Aviation Administration separation requirements for aircraft operating on intersecting runways.NTSB DCA14IA037Incident · No injuriesIncident investigationFinal reportBoeing 737 7H4 · Branson, MOThe Flight crew's failure to properly identify the airport and runway of intended landing. Contributing to the incident was the flight crew's failure to comply with procedures for use of navigation information and visual cues to verify the airport and runway…NTSB OPS13IA071Incident · No injuriesIncident investigationFinal reportGulfstream GIV - Undesignat · Las Vegas, NVThe Federal Aviation Administration's (FAA) inadequate procedures, which did not require specific separation between aircraft operating on nonintersecting runways where flightpaths may intersect and led to an airborne conflict between two aircraft.…NTSB CEN13LA244Accident · 1 fatalLimited investigationFinal reportDean Leslie N Highlander · Bryan, OHThe pilot's failure to maintain sufficient airspeed during a go-around, which resulted in an aerodynamic stall and subsequent impact with terrain.NTSB ERA13LA042Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Sevierville, TNThe air traffic controller’s failure to comply with the required vectoring and safety alert procedures, which resulted in the airplane’s flight into rising terrain. Contributing to the accident was the Federal Aviation Administration’s continued practice of…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 OPS12IA535Incident · No injuriesIncident investigationFinal reportLas Vegas, NVFederal Aviation Administration procedures that do not ensure separation in the event of a go-around during simultaneous independent runway operations on runways that do not physically intersect but whose flight paths intersect.NTSB DCA12PA049Accident · 1 fatalFinal reportIsrael Aircraft Industries F21-C2 · Fallon, NVfuel exhaustion following missed approaches due to deficient ATC handling under weather conditions which were significantly lower than forecast. The second missed approach may have been initiated due to limited pilot instrument proficiency. Contributing to…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 OPS11IA653Incident · No injuriesIncident investigationFinal reportBeech 1900C · Fairbanks, AKInadequate air traffic control actions that failed to establish and maintain required separation between the two airplanes. Contributing to the incident was inexperience on the part of the local controller, inadequate oversight by the tower…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 OPS11IA499Incident · No injuriesIncident investigationFinal reportBoeing 737 · Camp Springs, MDThe misapplication of wake turbulence and instrument flight rules (IFR) separation criteria by air traffic controllers.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…NTSB CEN11CA166Accident · No injuriesData collectionFinal reportMcholland C L Solitare · Wellington, COThe glider pilot’s misjudgment while approaching to land, which resulted in an off-airport landing.NTSB OPS11IA173Incident · No injuriesIncident investigationFinal reportBoeing 737-832 · Covington, KYThe local controller's distraction with a helicopter south of the field.NTSB WPR11FA032Accident · 4 fatalField investigationFinal reportMooney M20J · Lander, WYThe pilot's decision to depart into known adverse weather conditions over mountainous terrain, which required operation near the limits of the airplane's performance capability and which resulted in a loss of airplane control and subsequent ground impact.…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 OPS10IA538Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Los Angeles, CAFailure of the air traffic controller to exercise positive control of the situation by issuing clear and timely control instructions to the helicopter pilot. Contributing to the incident was delay by the helicopter pilot in responding to instructions issued…NTSB OPS10IA196Incident · No injuriesIncident investigationFinal reportAirbus Industrie A319-132 · Anchorage, AKThe approach controller's delayed transfer of communications on the A319 to the tower controller and failure to account for the aircraft's speed when he directed the crew to turn north. Contributing to the incident was the 747 crew's transfer of radio…NTSB OPS10IA132Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Houston, TXThe failure of the local controller to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class B airspace.NTSB OPS10IA090Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Burbank, CAThe improper separation procedures by air traffic control.NTSB CEN10FA065Accident · 2 fatalField investigationFinal reportNew Piper PA-46-500TP · Mendoza, TX***This report was modified on May 22, 2014. Please see the docket for this accident to view the original report.*** The pilot's spatial disorientation, which resulted in his loss of airplane control. Contributing to the pilot's spatial disorientation was the…NTSB OPS10IA002Incident · No injuriesIncident investigationFinal reportAirbus A320 · Cortez, COThe failure of the ACA795 flight crew to monitor and/or switch to the appropriate air traffic control frequency.