NTSB investigations, TX
8 cases where the first occurrence was “Vortex turbulence encountered”.
Cases per year
| 1984 | 1 |
|---|---|
| 1985 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1995 | 2 |
| 2002 | 1 |
| 2003 | 1 |
Where
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\" = 'TX' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 410)
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."eventStateOrRegion" = 'TX' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 410) 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 FTW03LA179Accident · No injuriesLimited investigationFinal reportGrumman AA-5B · Spring, TXThe failure of the pilot to maintain aircraft control due to wake turbulence.NTSB FTW02LA139Accident · Minor injuriesLimited investigationFinal reportBoeing A75SN1 · Georgetown, TXThe pilot's inadequate planning/decision resulting in the wake turbulence encounter during the takeoff/initial climb of the formation flight. A contributing factor was the partial loss of engine power for an undetermined reason.NTSB FTW95LA223Accident · No injuriesLimited investigationFinal reportCessna 120 · College Station, TXThe pilot's inability to maintain directional control after encountering wake turbulence from a landing airplane. A factor was the tailwind.NTSB FTW95IA083Incident · No injuriesIncident investigationFinal reportBoeing 737-3A4 · Houston, TXEncounter with wake turbulence.NTSB FTW92LA117Accident · No injuriesLimited investigationFinal reportCessna 310P · Austin, TXThe approach controller's failure to properly sequence arriving traffic, and the tower controller's failure to sequence and separate landing traffic. Factors in the accident were: the pilot's failure to obtain a landing clearance and the night light…NTSB DEN91LA117Accident · Minor injuriesLimited investigationFinal reportPiper PA-25-150 · Seagraves, TXThe pilot's improper inflight planning which resulted in loss of aircraft control due to wake turbulence.NTSB FTW85IA149Incident · No injuriesIncident investigationFinal reportBeech A36 · Dfw Airport, TXDrg arr, a Beech A36, N2057A, was vectored for an ILS rwy 17L apch while a hvy Boeing 747 was being vectored for an ILS rwy 18R apch. The ATC arrival controller (ctlr) stated he had 'staggered' the A36 bhnd the 747 with at least 3 mi sepn. After the A36 was…NTSB FTW84LA234Accident · Serious injuriesLimited investigationFinal reportCanadair CL-600 · Clarksville, TXCruising at FL350, N215RL encountered wake turbulance from a descending 'heavy' Boeing 767. The resultant upset caused an uncontrolled loss of 11,000 ft in 10 to 15 seconds before the crew was able to recover. The acft was not damaged but an unrestrained pax…