Connect with us

Regulations & Safety

JetBlue Flight Avoids Collision with Dark US Military Tanker Near Curaçao

A JetBlue Airbus A320 flight avoided collision with a US military tanker flying without an active transponder near Curaçao, raising safety concerns.

Published

on

This article summarizes reporting by NBC News and Yamiche Alcindor.

JetBlue Flight Takes Evasive Action Near Venezuela After Encounter with “Dark” Military Jet

New details have emerged regarding a significant safety incident involving a commercial JetBlue flight and a U.S. military aircraft operating in international airspace near Venezuela. According to reporting by NBC News, the incident occurred on Friday, December 12, 2025, when a JetBlue Airbus A320 was forced to halt its climb to avoid a potential collision with a U.S. Air Force refueling tanker that was not broadcasting its location.

The encounter, which took place near Curaçao, highlights the growing friction between civilian air traffic and increased military operations in the Caribbean. Audio recordings from the cockpit, obtained and released by NBC News, reveal a tense exchange between the commercial pilots and air traffic control immediately following the near-miss.

At AirPro News, we are tracking the implications of this event, particularly regarding the safety protocols for military aircraft operating in busy civilian corridors without active transponders.

“Harrowing Moments” in the Cockpit

JetBlue Flight 1112 had departed from Curaçao (CUR) and was en route to New York (JFK). Approximately 20 minutes after takeoff, while the aircraft was climbing through 33,000 feet, the flight crew visually identified a large military aircraft directly in their path at the same altitude.

According to the data summarized by NBC News, the military aircraft, identified as a U.S. Air Force refueling tanker, had its transponder turned off. This rendered the tanker invisible to the JetBlue aircraft’s automated collision avoidance systems until the pilots made visual contact. The commercial crew immediately stopped their climb to maintain vertical separation.

In the air traffic control audio released by NBC News, the JetBlue pilot expressed immediate frustration regarding the lack of electronic visibility:

“We almost had a midair collision up here. They passed directly in our flight path… They don’t have their transponder turned on, it’s outrageous.”

The pilot estimated that the military jet passed within two to three miles of the commercial airliner’s nose. While this distance may sound substantial to a layperson, at cruising speeds, it represents a margin of seconds. The controller on duty in Curaçao reportedly agreed with the pilot’s assessment, noting that the situation with unidentified aircraft in the region had become “outrageous.”

The Risks of “Dark” Military Operations

The primary safety failure in this incident stems from the military aircraft operating “dark”, flying without an active transponder. Transponders are essential for modern aviation safety, as they broadcast an aircraft’s altitude and position to both ground radar and other aircraft equipped with Traffic Collision Avoidance Systems (TCAS).

According to the report, the U.S. military has increased its presence in the region for drug interdiction operations and to apply pressure on the Venezuelan government. While military aircraft often disable transponders during sensitive combat or stealth operations to avoid detection by adversaries, doing so in a standard civilian flight corridor poses severe risks.

The Federal Aviation Administration (FAA) has previously issued warnings to U.S. carriers regarding the “worsening security situations” near Venezuelan airspace, advising extreme caution. However, this incident suggests that the danger may not only come from foreign actors but also from coordination failures involving U.S. assets.

AirPro News Analysis

The Failure of De-confliction: While military necessity sometimes dictates stealth, the proximity of this incident to a major civilian airport (Curaçao) suggests a breakdown in “de-confliction”, the process of ensuring military and civilian flights do not occupy the same airspace simultaneously. The fact that the Curaçao air traffic controller was unaware of the tanker’s presence until the JetBlue pilot reported it indicates a lack of communication between military command and civilian air traffic authorities.

Systemic Risk: This is not an isolated technical glitch but a systemic risk inherent in mixed-use airspace. When “dark” targets operate near commercial lanes, the safety of passengers relies entirely on the “see and avoid” principle, which is less reliable at high altitudes and high speeds than automated radar systems.

Official Responses

Following the release of the details, the involved parties issued statements regarding the event:

  • JetBlue: The airline confirmed the incident and stated they have reported the matter to federal authorities. They emphasized that their crew is trained for various flight situations and will participate fully in the investigation.
  • U.S. Air Force: A spokesperson acknowledged the report, stating that safety is a top priority and that they are currently reviewing the facts of the encounter.

Frequently Asked Questions

Was anyone injured on JetBlue Flight 1112?
No injuries were reported. The aircraft took evasive action by halting its climb, but there were no reports of violent maneuvers that caused passenger injury.

Why do military planes turn off their transponders?
Military aircraft may disable transponders to avoid detection by adversarial radar systems during sensitive operations. In this case, it was likely to avoid tracking by Venezuelan military radar.

How close did the planes actually get?
The pilots estimated the horizontal separation was between 2 and 3 miles. Vertically, they were at the same altitude before the JetBlue crew halted their climb.

Sources

Photo Credit: Reuters

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure

NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

Published

on

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.

The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.

Mechanical sequence and rejected takeoff

The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.

During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.

The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.

Emergency evacuation and passenger behavior

Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.

The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.

The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.

AirPro News analysis

The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).

When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.

Sources: National Transportation Safety Board

Photo Credit: National Transportation Safety Board

Continue Reading

Regulations & Safety

Marine One Loss of Separation at DCA: NTSB Preliminary Report

NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

Published

on

This is a developing story. Information may change as official details are released.

This is original reporting and analysis by AirPro News.

A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.

According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.

Incident timeline and separation data

The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.

President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.

Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.

No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.

Communication failure and FAA response

The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.

Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.

CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.

Regulatory context and prior airspace changes

The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.

Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.

Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.

AirPro News analysis

The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.

Sources: National Transportation Safety Board

Photo Credit: National Transportation Safety Board

Continue Reading

Regulations & Safety

FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision

FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.

The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.

The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”

Disciplinary actions and union response

The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.

The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.

The March 22 collision and investigation

The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.

Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.

It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.

Regulatory response to surface safety

Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.

These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.

AirPro News analysis

We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.

Sources: Reuters, NTSB

Photo Credit: Mike Segar – Reuters

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News