NTSB investigations, FL

7 cases where the first occurrence was “Near collision between aircraft”.

Cases per year

19822026
NTSB investigations, FL per year, 1982–2026: 7 cases
19821
19851
19881
19891
19921
20051
20071

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\" = 'FL' 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.

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.Jul 11, 2007 · N6714Q · 2 aircraft · No damageNTSB OPS06IA001Incident · No injuriesIncident investigationFinal reportBoeing 737-400 · Fort Lauderdale, FLthe local controller's failure to monitor the operation and recognize a developing traffic conflict which resulted in a loss of separation between USA1251 and ComAir 5026. Contributing to the accident was the controller's incorrect prioritization of his…Nov 9, 2005 · UNKNO WN · No damageNTSB MIA92LA147Accident · Minor injuriesLimited investigationFinal reportMaule MX-7-180 · Okeechobee, FLThe failure of the pilot-in-command of N148DP to obtain NOTAM information concerning military routes along his route of flight, resulting in his encounter with a flight of F16 aircraft who were operating on a military route.Jul 7, 1992 · N148DP · Substantial damageNTSB MIA90IA039Incident · No injuriesIncident investigationFinal reportBoeing 727 · Ormond Beach, FLFailure of the pilot in command in the Beech 300 to comply with an ATC clearance in a timely manner, while diverting his attention, and failure of the ATC controller to assure that IFR separation was maintained.Dec 15, 1989 · N64339 · 2 aircraft · No damageNTSB 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…Feb 4, 1988 · N232BH · 2 aircraft · No damageNTSB MIA85IA208Incident · No injuriesIncident investigationFinal reportCessna 402 · West Palm Bch, FLA Learjet 35 was cleared on to runway 09L and hold, the Learjet crew confirmed with the air traffic control tower personnel that te transmission was intended for them and taxied into position and held. Personnel on duty in the control tower then cleared a…Jul 5, 1985 · N68368 · 2 aircraft · No damageNTSB MIA83LA003Accident · No injuriesLimited investigationFinal reportCessna 152 · Orlando, FLThe student pilot was practicing touch-and-go landings. After touching down on his first landing, he configured the aircraft for takeoff. Immediately after applying power, he observed another plane (unknown make & model) landing from the opposite direction.…Oct 3, 1982 · N93286 · Substantial damage