# NTSB investigations, 2007: Near collision between aircraft

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB OPS08IA004](https://openairdocs.org/ntsb/OPS08IA004.md): Gulfstream American G5 · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Dec 27, 2007 · N90AM · 2 aircraft · No damage
  > The 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 OPS08IA002](https://openairdocs.org/ntsb/OPS08IA002.md): Bombardier CRJ1 · Baltimore, MD · Incident · No injuries · Incident investigation · Final report · Dec 3, 2007 · N781CA · 2 aircraft · No damage
  > The 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 OPS08IA001](https://openairdocs.org/ntsb/OPS08IA001.md): Cessna C 525 · Memphis, TN · Incident · No injuries · Incident investigation · Final report · Oct 12, 2007 · N241EP · No damage
  > The probable cause of this incident was the pilot's inadvertent departure from a taxiway instead of a runway.
- [NTSB OPS07IA009](https://openairdocs.org/ntsb/OPS07IA009.md): Boeing 737-700 · Los Angeles, CA · Incident · No injuries · Incident investigation · Final report · Aug 16, 2007 · C-FUWS · 2 aircraft · No damage
  > The 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 OPS07IA008](https://openairdocs.org/ntsb/OPS07IA008.md): Learjet 45 · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Aug 13, 2007 · N145AP · 2 aircraft · No damage
  > A 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 OPS07IA006](https://openairdocs.org/ntsb/OPS07IA006.md): Boeing 757-232 · Fort Lauderdale, FL · Incident · No injuries · Incident investigation · Final report · Jul 11, 2007 · N6714Q · 2 aircraft · No damage
  > The probable cause of this incident was the United flightcrews' inadvertant entry onto an active runway.
- [NTSB OPS07IA007](https://openairdocs.org/ntsb/OPS07IA007.md): Boeing 737 · New York City, NY · Incident · No injuries · Incident investigation · Final report · Jul 5, 2007 · N737DA · 2 aircraft · No damage
  > ATC - 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 OPS07IA005](https://openairdocs.org/ntsb/OPS07IA005.md): Piaggio Industrie P180 · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Jun 17, 2007 · N152SL · 2 aircraft · Minor damage
  > The TEB local controller's failure to ensure separation between two aircraft departing intersecting runways.
- [NTSB OPS07IA004](https://openairdocs.org/ntsb/OPS07IA004.md): Embraer 170 · San Francisco, CA · Incident · No injuries · Incident investigation · Final report · May 26, 2007 · N872RW · 2 aircraft · No damage
  > Failure of SFO tower local controller to provide adequate separation between two aircraft departing intersecting runways.
- [NTSB OPS07IA001](https://openairdocs.org/ntsb/OPS07IA001.md): Swearingen SW-4 · Denver, CO · Incident · No injuries · Incident investigation · Final report · Jan 5, 2007 · N425MA · 2 aircraft · No damage
  > The 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…

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
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
```

This list as a web page: https://openairdocs.org/ntsb?occurrence=280&year=2007

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.