NTSB investigations, MD

4 cases where NTSB found Communication (personnel).

Cases per year

20082026
NTSB investigations, MD per year, 2008–2026: 4 cases
20081
20091
20111
20121

Latest 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\" = 'MD' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '020635'))
  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.

NTSB ERA12IA166Incident · No injuriesIncident investigationFinal reportGulfstream G150 · Baltimore, MDThe pilot-in-command's failure to obtain the proper touchdown point or landing reference speed and failure to initiate a go-around when it became evident that the airplane was landing long and fast. Contributing to the incident was a lack of effective flight…Jan 30, 2012 · N272CB · Minor damageNTSB 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…Jul 15, 2011 · N7475 · Substantial damageNTSB OPS09IA004Incident · No injuriesIncident investigationFinal reportBE20 · Camp Springs, MDThe failure of the ground controller to coordinate the runway crossings with the local controller and her failure to scan the runway prior to issuing the crossing instructions. Contributing to the incident was the combination of the front line manager/tower…May 13, 2009 · VM206 · No damageNTSB ERA09CA041Accident · Serious injuriesData collectionFinal reportCessna 172 · Frederick, MDThe passenger’s failure to avoid the rotating propeller after exiting the airplane. Contributing to the accident was the pilot’s failure to include deplaning procedures as part of the passenger safety briefing.Nov 7, 2008 · N1242C · No damage