NTSB investigations, CA
12 cases where the first occurrence was “Near collision between aircraft”.
Cases per year
| 1984 | 1 |
|---|---|
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 2 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 1 |
| 2004 | 1 |
| 2007 | 2 |
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.\"eventStateOrRegion\" = 'CA' 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\" = 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 c."eventStateOrRegion" = 'CA' 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" = 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 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 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 LAX04IA302Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Los Angeles, CAa loss of separation between Southwest flight 440 and Asiana flight 204 due to the LC2 relief controller's failure to appropriately monitor the operation and recognize a developing traffic conflict. Contributing factors included the FAA's position relief…NTSB LAX91IA297Incident · No injuriesIncident investigationFinal reportBoeing 747-200 · Los Angeles, CAThe inadequate runway safety area inherent in the airport design, and, the ATC clearance procedures in use which failed to take into consideration the substandard runway safety area. Factors in the incident were the dark night time conditions and the…NTSB LAX90FA233Accident · Minor injuriesField investigationFinal reportBellanca 17-30A · Ojai, CAStructural damage sustained by the Bellanca, N39843, as a result of encountering wake turbulence during a near-collision with a navy F-14A.NTSB LAX89IA184Incident · Minor injuriesIncident investigationFinal reportBoeing 747 · Los Angeles, CAInadequate visual look-out by the pilot of the other (small twin engine) aircraft. A factor related to the incident was: a delay of the 747 crew to see-and-avoid the other aircraft.NTSB LAX89IA112Incident · No injuriesIncident investigationFinal reportBritish Aerospace BAE 146-200A · Los Alamitos, CAInadequate coordination among the ATC controllers which resulted in their failure to maintain adequate radar separation of the two aircraft.NTSB LAX88IA009Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-82 · Ontario, CAFailure of the general aviation aircraft to visually identify the transport aircraft. Factures contributing to the incident were: failure of the general aviaiton aircraft to establish communications with ATC prior to entering the arsa and maintaining a poor…NTSB LAX87IA304Incident · No injuriesIncident investigationFinal reportBoeing 737 · Santa Monica, CAThe plts of a Boeing 737 reported that a near-collision occurred aprx 2.5 miles east of the Santa Monica VOR while they were descending through an altitude of about 7400 ft MSL. The coplt saw the other acft first & took immediate evasive action. He estimated…NTSB LAX87IA027Incident · No injuriesIncident investigationFinal reportBoeing 727-222 · Los Angeles, CADrg arr, united flt 282 (Boeing 727, N7255U) was vectored by Los Angeles (lax) TRACON for an ILS rwy 25L apch. While in a dscndg turn at 2100' MSL to intercept the ILS LOC at 2000', the capt saw a helicopter (hel) ahead & pulled up. He estdhis acft passed w/i…NTSB LAX85IA175Incident · No injuriesIncident investigationFinal reportPiper PA-44-180 · San Jose, CAA Piper seminule was vectored to the final apch course & cleared for an ILS apch at 3000FT MSL. A DC-9, in trail at 5000FT MSL, was overtaking the seminule. The controller elected to change their sequence & cleared the seminule to climb to 4000FT MSL due to…NTSB LAX84IA219Incident · No injuriesIncident investigationFinal reportBeech C-45G · Ontario, CAA Beech E18S, N3657G, operating as federal express flt 954L, was cleared for takeoff on rwy 8L after a Boeing 747, N8172G, operating as interflight 429, was cleared to cross the same rwy. The Boeing 747'S cargo included race horses. The Boeing crew were…