NTSB investigations, 2007
10 cases where the first occurrence was “Near collision between aircraft”.
Cases per year
| 1982 | 4 |
|---|---|
| 1984 | 8 |
| 1985 | 3 |
| 1986 | 10 |
| 1987 | 18 |
| 1988 | 14 |
| 1989 | 12 |
| 1990 | 1 |
| 1991 | 3 |
| 1992 | 5 |
| 1993 | 2 |
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 3 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 3 |
| 2001 | 2 |
| 2002 | 2 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 5 |
| 2007 | 10 |
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\") = 2007
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\" = 280)
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") = 2007 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" = 280) 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 OPS08IA004Incident · No injuriesIncident investigationFinal reportGulfstream American G5 · Teterboro, NJThe probable cause of this incident was the TEB tower local controller's failure to ensure that the runway was free of all known ground vehicles, equipment, and personnel before permitting a departing aircraft to start takeoff roll.NTSB OPS08IA002Incident · No injuriesIncident investigationFinal reportBombardier CRJ1 · Baltimore, MDThe probable cause of this incident is local controller's failure of maintaining awareness of the situation and failing to provide the appropriate separation between the two aircraft operating on intersecting runways. Providing separation between aircraft is…NTSB OPS08IA001Incident · No injuriesIncident investigationFinal reportCessna C 525 · Memphis, TNThe probable cause of this incident was the pilot's inadvertent departure from a taxiway instead of a runway.NTSB OPS07IA009Incident · No injuriesIncident investigationFinal reportBoeing 737-700 · Los Angeles, CAThe LAX north ground controller's failure to properly coordinate with the tower local controller prior to providing taxi instructions that permitted an aircraft to cross an active runway while another aircraft was departing. **This report was modified on…NTSB OPS07IA008Incident · No injuriesIncident investigationFinal reportLearjet 45 · Teterboro, NJA runway incursion occurred when the local controller did not ensure that N145AP has passed the intersection of runways 1 and 6 prior to authorizing N336FX to depart runway 1.NTSB OPS07IA006Incident · No injuriesIncident investigationFinal reportBoeing 757-232 · Fort Lauderdale, FLThe probable cause of this incident was the United flightcrews' inadvertant entry onto an active runway.NTSB OPS07IA007Incident · No injuriesIncident investigationFinal reportBoeing 737 · New York City, NYATC - The incident occurred because the ground controller instructed COM5196 to cross runway 22, without approval from the local controller, resulting in a loss of separation with DAL1238 that was landing on the same runway.NTSB OPS07IA005Incident · No injuriesIncident investigationFinal reportPiaggio Industrie P180 · Teterboro, NJThe TEB local controller's failure to ensure separation between two aircraft departing intersecting runways.NTSB OPS07IA004Incident · No injuriesIncident investigationFinal reportEmbraer 170 · San Francisco, CAFailure of SFO tower local controller to provide adequate separation between two aircraft departing intersecting runways.NTSB OPS07IA001Incident · No injuriesIncident investigationFinal reportSwearingen SW-4 · Denver, COThe probable cause of the incident was the Key Lime Air flight 4216 pilot's inadvertant entry onto the active runway. A contributing factor to the incident was the failure of the Denver tower ground and local controllers to detect the aircraft on the airport…