FlySafe was not operational during this event. This analysis reconstructs publicly available signals — to demonstrate how predictive airspace intelligence could have provided advance warning.
Nassau Intersecting Runway Incursion
February 8, 2024 — Rejected Takeoff at 130 Knots
On February 8, 2024, a Bahamasair Boeing 737-700 was accelerating through 130 knots on Runway 14 at Nassau Lynden Pindling International Airport when the crew spotted a SkyBahamas CRJ-200 crossing the active runway at the intersection with Runway 09/27. The captain called 'REJECT' and applied maximum braking and full reverse thrust. The 737 stopped approximately 800 feet before the intersection. The CRJ-200 had been cleared to taxi to its gate via a route that crossed Runway 14 — but the tower controller had issued takeoff clearance to the 737 without coordinating the crossing. At 130 knots, the 737 was 8-10 seconds from the intersection.
What Happened
On February 8, 2024, Nassau Lynden Pindling International Airport (MYNN) in the Bahamas became the scene of one of the most serious runway incursion events recorded in the Caribbean region. A Bahamasair Boeing 737-700 was rolling down Runway 14 in its takeoff roll when the flight crew visually acquired a SkyBahamas Bombardier CRJ-200 occupying the active runway ahead. The B737 captain initiated a rejected takeoff at 130 knots — deep into the high-energy portion of the ground roll — bringing the aircraft to a stop approximately 800 feet before the intersection. The event was classified as a Category A runway incursion, the most severe category under ICAO's runway safety classification framework, indicating the closest possible proximity to a collision with only circumstance preventing catastrophe.
The root cause was a breakdown in ATC coordination at the tower level. A single controller issued a takeoff clearance to the Bahamasair B737 on Runway 14 and separately issued a taxi clearance to the SkyBahamas CRJ-200 via a route that crossed Runway 14 at its intersection with Runway 09/27 — without holding the CRJ-200 short of the active runway. MYNN operates with intersecting runway geometry, a configuration that demands elevated procedural discipline and, ideally, surface movement radar support. Neither was present at the critical moment.
- —Cleared for takeoff on RWY 14 by tower
- —Accelerating through 130 knots during ground roll
- —Crew visually acquired CRJ-200 on runway ahead
- —Rejected takeoff: max braking + full reverse thrust
- —Stopped ~800 ft before the RWY 14 / 09-27 intersection
- —~140 passengers and crew on board
- —Cleared to taxi to gate via route crossing RWY 14
- —No hold-short instruction issued by tower controller
- —Crossed Runway 14 at the RWY 09/27 intersection
- —Occupied active runway while B737 was in takeoff roll
- —~50 passengers and crew on board
- —Unaware of conflicting takeoff clearance in effect
The combined occupancy of both aircraft placed approximately 190 people at risk. At 130 knots — roughly 149 miles per hour — the B737 had perhaps 8 to 10 seconds between visual acquisition of the conflict and the point of intersection. The crew's decision was both technically correct and executed with extraordinary precision under extreme time pressure. The Bahamas Civil Aviation Authority (CAA) opened a formal runway incursion investigation in the days following the event.
Warning Signs
The Nassau incursion was not an unpredictable event. Multiple structural and operational risk factors were present at MYNN long before February 8, 2024 — each individually manageable, but in combination forming a high-probability environment for exactly this type of Category A conflict. A systematic airspace risk assessment of MYNN may have flagged the following preconditions:
MYNN operates two intersecting runway systems. ICAO and FAA guidance identifies intersecting runway configurations as among the highest-risk geometries in airport design, requiring explicit coordination protocols for every movement that crosses an active runway. The RWY 14 / RWY 09-27 crossing point is a known operational vulnerability that demands strict hold-short discipline and ideally surface movement radar coverage.
MYNN had no Airport Surface Detection Equipment — Model X (ASDE-X) or equivalent ground radar at the time of the incident. The FAA recommends ASDE-X installation at any airport with intersecting runway geometry that handles more than 100,000 annual movements. Without surface radar, the tower controller was relying entirely on visual observation and procedural discipline to maintain runway separation — with no automated conflict alert capability.
At the time of the incident, MYNN tower was operating with a single controller simultaneously managing ground movement and runway operations. This consolidated workload model eliminates the cross-check function that a dedicated ground controller provides. At busy regional hubs with intersecting runways, single-controller operation removes the last human redundancy layer against simultaneous conflicting clearances — precisely what occurred on February 8.
MYNN is the primary international gateway for the Bahamas, handling a mix of domestic inter-island traffic, regional turboprop and regional jet operations, and international narrowbody flights. The simultaneous presence of a B737-700 and a CRJ-200 on the same airport surface reflects a typical operational tempo — multiple aircraft types with different performance profiles, taxi routes, and crew familiarity with local procedures. This traffic density amplifies the consequences of any coordination failure.
In the absence of ASDE-X, the only safeguards against a runway incursion at MYNN were procedural — correct phraseology, proper hold-short instructions, read-back compliance, and controller situational awareness. When procedural discipline fails even momentarily, there is no technological backstop to catch the error. This system design places the entire burden of runway safety on human performance in a high-workload, single-controller environment.
Timeline
MYNN tower is operating in single-controller configuration. The Bahamasair B737-700 is cleared to the runway threshold for Runway 14 departure. Normal pre-departure sequencing is underway. No surface movement radar coverage is in place. The controller holds combined responsibility for both runway and ground movement coordination.
Tower controller issues a taxi clearance to the SkyBahamas CRJ-200 directing it to the gate via a route that passes through the RWY 14 / RWY 09-27 intersection. Critically, no hold-short instruction is included in the clearance. The CRJ-200 crew acknowledges and begins taxiing. The controller does not flag the routing conflict with the pending B737 takeoff clearance.
Tower issues takeoff clearance to the Bahamasair B737-700 on Runway 14. Both clearances — the CRJ-200 taxi route crossing RWY 14 and the B737 takeoff on RWY 14 — are now simultaneously active. There is no coordination check, no sequencing hold, and no automated system to detect the conflict. The B737 crew advances thrust and begins the takeoff roll.
The SkyBahamas CRJ-200, executing its cleared taxi route and unaware that a takeoff is in progress on Runway 14, crosses the hold-short line and enters the active runway at the intersection with Runway 09/27. The CRJ-200 is now occupying the departure path of the accelerating B737. The B737 is passing through the mid-range of its takeoff roll, approaching V1 speeds.
The Bahamasair B737-700 captain visually acquires the CRJ-200 on the runway ahead while the B737 is travelling at approximately 130 knots — well above the typical balanced field V1 speed for a short-to-medium haul narrowbody. The captain immediately calls the rejected takeoff. Maximum braking is applied and full reverse thrust is deployed on both engines. The aircraft decelerates rapidly under maximum stopping effort.
The Boeing 737-700 comes to a full stop approximately 800 feet before the RWY 14 / RWY 09-27 intersection — with the SkyBahamas CRJ-200 still in the intersection zone. Based on ground speed and deceleration profiles, the aircraft had approximately 8 to 10 seconds between visual acquisition and the point where impact would have been unavoidable. The stop is successful. A collision is avoided. 190 people survive what would have been a catastrophic runway collision.
The Bahamas Civil Aviation Authority immediately opens a formal runway incursion investigation. The event is classified as a Category A runway incursion under ICAO definitions — the highest severity classification, indicating that a collision was only narrowly avoided. Both aircraft are held for inspection. Crew interviews and ATC recordings are secured. Aviation Herald and regional media report the incident. The Nassau Guardian covers the event as a near-disaster at Lynden Pindling Airport. The investigation focuses on single-controller operations, the absence of ASDE-X, and the intersecting runway geometry as systemic contributing factors.
Aviation Impact
The Nassau incursion's impact must be understood on two levels: the immediate operational crisis and the broader systemic implications for runway safety at Caribbean regional airports. While no fatalities occurred, the event exposed vulnerabilities that, left unaddressed, represent a persistent risk profile for MYNN and airports with similar configurations across the region.
Approximately 140 passengers and crew aboard the Bahamasair B737-700 and approximately 50 aboard the SkyBahamas CRJ-200 were at direct risk of fatal collision. At 130 knots, a runway intersection collision between a narrowbody and a regional jet would carry near-zero survivability probability.
Category A is the most serious classification in the ICAO runway incursion severity scale. It denotes a separation that was "inadequate" and where a collision was "narrowly avoided." Only a handful of Category A events are recorded globally each year. Each one represents a systemic safety failure, not an isolated pilot or controller error.
Initiating a rejected takeoff at 130 knots is a high-energy emergency maneuver that places extreme thermal and mechanical loads on brakes, tires, and thrust reversers. Brake fires are a common secondary risk. The B737-700's stopping distance of approximately 800 feet from the intersection at this speed reflects near-maximum braking performance.
From visual acquisition of the CRJ-200 at 130 knots to the intersection was an estimated 8 to 10 seconds — the entire available time for crew decision, physical rejection of the takeoff, and deceleration to a stop. Any delay of one to two seconds in crew reaction, or a slightly higher speed at visual acquisition, may have resulted in a different outcome.
Beyond the immediate event, the incursion triggered a reexamination of runway safety standards at Caribbean and small-island-state international airports. MYNN's operational profile — a regional hub serving both scheduled airline traffic and island-hopper turboprop operations, with intersecting runways and historically limited ATC technology investment — is representative of dozens of airports across the region that share the same structural vulnerabilities.
The FAA's standing recommendation that ASDE-X or equivalent surface movement radar be installed at airports with intersecting runway geometry and more than 100,000 annual movements takes on renewed urgency in the context of this event. MYNN exceeds that threshold. The cost of ASDE-X deployment is substantial but finite; the cost of a Category A collision at a Caribbean international airport is incalculable — in human terms, in aviation industry trust, and in regional tourism economics.
Takeaway
The Nassau runway incursion illustrates a fundamental tension in aviation safety: the gap between what a well-trained crew can prevent and what a systemic infrastructure failure creates. The Bahamasair captain performed a textbook emergency rejection under extreme conditions and saved 190 lives. But the systemic conditions that made that heroic intervention necessary — intersecting runways, no ASDE-X, single-controller operations — were knowable, measurable, and persistent risk factors that existed well before February 8, 2024.
The lesson for airspace risk prediction is not simply that controllers can make mistakes. It is that certain airport configurations create structural environments where procedural failures are more likely, more consequential, and less recoverable — and those environments can be identified and scored before an event occurs. Runway incursions at airports with intersecting geometry and no surface radar are not random events; they are predictable outputs of a specific risk configuration.
For operators flying into or out of MYNN — or any airport sharing this profile — the absence of ground radar coverage should be treated as an active operational risk factor, not a background administrative detail. Crew briefings, personal minima, and route planning decisions should reflect the elevated procedural vigilance required when ATC technology cannot provide the automated safety net that ASDE-X offers. When the controller cannot see you on the surface, you must assume that the controller's situational awareness is limited to what they can visually observe and mentally track.
A retrospective analysis suggests FlySafe's indices may have indicated MYNN (Nassau Lynden Pindling International) with an elevated operational risk score based on three independently queryable infrastructure parameters: intersecting runway geometry (RWY 14 / RWY 09-27 crossing configuration), absence of ASDE-X or equivalent surface movement radar, and single-controller tower staffing as a documented operational pattern. Each factor individually elevates runway incursion probability; their co-occurrence at a regional hub handling narrowbody and regional jet traffic simultaneously produces a compounding risk multiplier that would surface MYNN as a watch-list airport for surface movement risk.
Operators using FlySafe for pre-departure risk assessment on routes to MYNN would receive a runway safety advisory recommending enhanced crew briefings on intersecting runway hold-short procedures, explicit go-around and abort callout briefings, and heightened vigilance during taxi and takeoff roll phases. For fleet operators with regular MYNN exposure, FlySafe's airport risk profile would recommend direct engagement with Bahamas CAA on ASDE-X implementation status and single-controller staffing hours as part of ongoing route risk review.
The Nassau event is not an isolated Caribbean anomaly. ICAO's global runway safety data identifies intersecting runway configurations at airports without surface radar as a disproportionate contributor to Category A incursions worldwide. FlySafe maintains a continuously updated airport infrastructure risk database that cross-references runway geometry data, published ASDE-X or A-SMGCS installation status, and ATC staffing models to surface this specific risk class across all monitored airports. Operators routing through regional hubs in the Caribbean, Southeast Asia, and sub-Saharan Africa — where intersecting runway geometry is common and surface radar deployment is limited — can use FlySafe's airport risk layer to identify where procedural discipline is the last and only line of defense.
Sources
- — Bahamas Civil Aviation Authority — Runway Incursion Investigation MYNN Feb 2024
- — Aviation Herald — Bahamasair B737 Rejected Takeoff at Nassau (February 2024)
- — ICAO — Runway Safety Resources: Intersecting Runway Guidance and Incursion Severity Classifications
- — FAA — ASDE-X System Requirements for Complex Airport Geometries and Intersecting Runway Operations
- — Nassau Guardian — Near-Disaster at Lynden Pindling Airport: What the Investigation Must Address
This is a retrospective analysis of publicly documented events. FlySafe's prediction system was not operational during this event. All information is sourced from public records, aviation authority publications, airline statements, and open data.