NTSB investigations, 1988
14 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
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 year(c.\"eventDate\") = 1988
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") = 1988 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 NYC89IA063Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-10 · Atlantic Ocean (Atlantic Ocean)American flt 1180 (McDonnell-douglas DC-10) was northbound ovr the Atlantic Ocean at flt lvl 350 as a british royal air force vickers VC10 was cruising east at the same alt (non-standard alt for the VC10'S drctn of flt). They were in a non-radar airspace…NTSB NYC89IA028Incident · No injuriesIncident investigationFinal reportBoeing 727-227 · Boston, MAFailure of the local controller to detect the red t on the departure strip on PRE659 when he cleared him into position and hold. Factors related to the accident were: darkness and the lack of positive coordination between the ground controller and local…NTSB FTW89IA016Incident · No injuriesIncident investigationFinal reportBoeing 727 · Houston, TXPoor planning/decision by the unidentified Cessna pilot by maneuvering in busy airspace near the arsa with no ATC coordination or transponder signal; no traffic advisory being issued by the approach controller; and inadequate visual lookout by the flight crew…NTSB ATL89MA012Incident · No injuriesMajor investigationFinal reportAerospatiale ATR-42-300 · Yardley, PABfr tkof, corrected flt plan was put in ATC computer for airforce 1 (AF1) to take nonstandard rte to newark. After tkof,AF1 was vctrd nw with handoff to NY ARTCC (zny), then east via Yardley (ard) to newark; 15 mi west of ard, zny initiatedhandoff to NY…NTSB DEN89FA010Accident · Serious injuriesField investigationFinal reportPiper PA-24-180 · Albuquerque, NMPlt-rated pax told plt, coronado arpt 'in sight'. Plt was suspicious because loran indicated arpt was 3 mi away but trusted former instrument student's judgment & landed at closed alameda arpt instead of coronado arpt. Coronado UNICOM had told plt 'multiple…NTSB CHI88IA217Incident · No injuriesIncident investigationFinal reportBell 206L · Indianapolis, INNTSB MIA88IA176Incident · No injuriesIncident investigationFinal reportAirbus Industrie A-300 · Near San Juan, PRPan am flt 217 (Airbus A300, N209PA) was clrd by new york center oceanic ctl area (oca) to proceed south on airway amber 300 at FL 290 over the atlantic ocean. As it was en route, American flt 902 departed san Juan (sju), PR for a northbound flt on the same…NTSB MIA88IA168Incident · No injuriesIncident investigationFinal reportPiper PA-42-720 · Chicago, ILCondor flt 610 (Mcdonnell Douglas DC-10, german registration: dadso) was aprx 2 hrs late as the flt crew members were preparing to takeoff. Subsequently, flt 610 was clrd for takeoff with instructions to cross the 5 DME (on the standard instrument…NTSB MIA88IA167Incident · No injuriesIncident investigationFinal reportBeech 200 · Chicago, ILMidway flt 172 (Mcdonnell Douglas DC-9, N1065T) was on an IFR departure from Chicago midway arpt at the same time that Beech 200, N981LL, was on an IFR arrival for a visual apch to merrill c meigs arpt, although both were in VMC. Previously, o'hare TRACON had…NTSB NYC88IA109Incident · No injuriesIncident investigationFinal reportBoeing 737 · Morristown, NJBoeing 737 (N69348) was depg newark intl arpt as a lear jet 24 (N500NH) was depg fm teterboro. Both were being ctld by new york TRACON (newark sector). The strip for the 737 was mismarked as a north departure rather than an east departure. The instructor/full…NTSB ATL88IA108Incident · No injuriesIncident investigationFinal reportBoeing 737 · Greensboro, NCContinental flt 458 (Boeing 737, N13331) was flying NE at FL370 as Continental flt 703 (Boeing 737, N432PE) was flying fm the opposite drctn at FL350. Both flts were on the same freq, being ctld by atlanta ARTCC (sector 47) ctlr, who had just come on duty. In…NTSB CHI88IA074Incident · No injuriesIncident investigationFinal reportSwearingen SA226T · Chicago, ILThe TRACON supervisor failed to comply with the established visual minima criteria and his incorrect issuance of a visual approach to an arriving aircraft.NTSB CHI88IA073Incident · No injuriesIncident investigationFinal reportBoeing 747-227B · Chicago, ILFailure of the tower cab supervisor to assure that coordination between the south local controller and north local controller had been completed. A factor is the failure of FAA tower management to insure there were personnel manning the cab coordinator…NTSB MIA88IA099Incident · No injuriesIncident investigationFinal reportBeech C-99 · Orlando, FLDrg a visual apch to Orlando intl arpt, bar harbor flt 3949 (Beech C-99, N232BH) contacted the tower (local controller) at 1817:07 & rprtd 5 mi north of the VOR for landing. The VOR was located 5.8 mi north of the rwy. About 20 sec later, the local controller…