NTSB CAROL · Event
Event OPS10IA132
Aircraft involved
Probable cause & findings
The failure of the local controller to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class B airspace.
Factual narrative
On Monday, April 28, 2010, at approximately 1225 central daylight time, a Boeing B737-700, N242WN, operating as Southwest Air Lines (SWA) flight 1322, and a Bell 207, N6YJ, operating as Sky2 were involved in a near mid-air collision at the William P. Hobby Airport (HOU), Houston, Texas. The B737 was departing from runway 12R, and the Bell 207 was departing from the south helipad on a north-bound departure route, when the aircraft came within approximately 125 feet vertically and 100 feet laterally at the departure end of runway 12R. The incident occurred during daytime visual meteorological conditions (VMC). The B737 was on a regularly scheduled passenger flight from HOU to Baltimore/Washington International Thurgood Marshall Airport (BWI), and was operating under the provisions of 14 Code of Federal Air Regulation Part 121. The B737 had 135 passengers and a crew of five onboard. The Bell 207 was departing from the south of the airport on an established departure route, and was operating under the provisions of 14 Code of Federal Regulations Part 91. The Bell 207 had one person onboard. No injuries were reported on either aircraft. At approximately 1224, the local controller issued takeoff clearance to the B737 on runway 12R, with departure instructions to turn left to the north. Approximately, twenty six seconds later the Bell 207 contacted the tower requesting a departure route to the north (cougar departure) from the south helipad. The local controller directed the Bell 207 to “use caution from the south pad, cougar departure is approved”. Approximately three seconds later, the local controller instructed the Bell 207 that he had “no restrictions”. The pilot immediately read back the “no restrictions” instructions and proceeded on the departure route. Approximately 20 seconds later the B737 reported to the tower “Hey tower that helicopter is going right across us” and “we made a pretty good duck to miss him”. Simultaneously the Bell 207 had conducted a sharp turn to the right to avoid overflying the departing B737. The aircraft came within an estimated 125 feet vertically and 100 feet laterally from each other, at approximately the 1,000-foot remaining section of runway 12R. The local controller did not issue traffic advisories to the B737 or the Bell 207. The B737 continued on the regularly scheduled flight to BWI, and the Bell 207 continued northbound to operate under visual flight rules (VFR). Radar Data Radar data for this report was obtained from the ASR-9 sensor located at HOU. A graphic showing a close-up view of the two aircraft and their minimum separation have been entered in the docket. The applicable separation standard between VFR and IFR aircraft in class B airspace is visual separation or 500 feet vertically and 1½ miles laterally. At the closest point the aircraft were separated by approximately 100 feet vertically and 125 feet laterally. The controller did not issue any traffic advisories or control instructions to establish and maintain visual separation. A Boeing 737 (B737) was departing from runway 12R and a Bell 207 was departing from the south helipad on a northbound departure route, when the aircraft came within approximately 125 feet vertically and 100 feet laterally at the departure end of runway 12R. The air traffic control tower controller did not issue traffic advisories to the B737 or the Bell 207. The incident occurred during daytime visual meteorological conditions. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Experience/knowledge-(general)-(general)-ATC personnel - C
- C Personnel issues-Experience/knowledge-(general)-(general)-ATC personnel - C
Verbatim from NTSB's published report. Source file
NTSB_2010_OPS10IA132.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (mid-air collision). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2025 · Journal article (IJAAA)
Invisible Aircraft in U.S. Airspace: Regulatory Gaps and Mid-Air Collision Risk for Part 121 Operators
Scheduled air carrier aircraft operate at large and small commercial airports across the U.S. National Airspace System. These turbine-powered aircraft fly at high speeds during departure and approach,…
- Semantic Scholar 2023 · Article (Reliability Engineering & System Safety)
Bayesian network model of aviation safety: Impact of new communication technologies on mid-air collisions
- Embry-Riddle Scholarly Commons 2022 · Faculty research project
Small UAS (sUAS) Mid-Air Collision (MAC) Likelihood
This research focuses on sUAS MAC likelihood analysis with general aviation (GA) and commercial aircraft. Because severity research varies based on where a collision occurred on a manned aircraft, thi…
- NASA NTRS 2019 · Conference Paper
Analyzing a Mid-Air Collision Over the Hudson River
On August 8, 2009, a private airplane collided with a sightseeing helicopter over the Hudson River near Hoboken, New Jersey.
- arXiv 2025 · arXiv preprint
Intent-Aware MPC for Aircraft Detect-and-Avoid with Response Delay: A Comparative Study with ACAS Xu
In this paper, we propose an intent-aware Model Predictive Control (MPC) approach for the remain-well-clear (RWC) functionality of a multi-agent aircraft detect-and-avoid (DAA) system and compare its …
- arXiv 2024 · arXiv preprint
Multi-Aircraft Scheduling Optimization in Urban Environments
With the increasing development of intelligent transportation systems and advancements in aviation technology, the concept of Advanced Air Mobility (AAM) is gaining attention.
Browse the full corpus — academia portal ↗