JetBlue Flight 1112 Narrowly Avoids Midair Collision with U.S. Air Force Tanker Over Caribbean Airspace
Table of Contents
- 1. JetBlue Flight 1112 Narrowly Avoids Midair Collision with U.S. Air Force Tanker Over Caribbean Airspace
- 2. Context and implications
- 3. Safety takeaways
- 4. Engage with us
- 5. />
- 6. How TCAS Prevented a Disaster
- 7. Primary TCAS Functions
- 8. JetBlue Flight 1112 TCAS Response
- 9. Military Tanker TCAS Response
- 10. Air Traffic Control (ATC) Interaction Log
- 11. Safety Lessons & Best Practices for Pilots
- 12. Passenger Information & Experience
- 13. Regulatory and Investigation Follow‑Up
- 14. Related Keywords & Search Phrases (Naturally Integrated)
- 15. Practical Tips for Aviation Professionals
Breaking news: A jetblue flight en route from Curacao to New York halted its ascent on Friday after a United States Air force refueling tanker crossed into its flight path, prompting the crew to descend to a safer altitude.
The incident involved JetBlue flight 1112, a service operating from Curacao, a small Caribbean island off Venezuela’s coast, with a destination of John F. Kennedy International Airport in New York City.
The pilot told air traffic control that the military tanker passed directly into the aircraft’s route and that the tanker did not have a transponder, a claim described by the crew as scandalous. A recording of the exchange captured the moment the crew took action to avoid a collision.
The tanker reportedly moved into Venezuelan airspace as the JetBlue jet was climbing, leaving controllers to monitor the unfolding situation.The air traffic transcript shows the controller expressing concern about an unidentified aircraft operating inside their airspace.
JetBlue said it has notified federal authorities and will cooperate fully with any investigation. A company spokesperson stressed that the crew members are trained for a range of flight scenarios and praised their prompt reporting to leadership.
Defense officials directed requests for comment to the Air Force, which did not instantly respond. The Federal Aviation Management had warned last month that U.S. aircraft should exercise caution in Venezuelan airspace amid worsening security conditions and increased military activity in and around Venezuela.
Context and implications
The episode underscores ongoing tensions in Caribbean airspace as security operations intensify in the region. It also highlights the importance of transponder signaling and timely dialog between civilian crews and military assets to prevent near-misses.
Safety takeaways
Experts emphasize strict adherence to identification and radar transponder requirements, along with robust coordination between civilian air traffic controllers and military forces operating near commercial flight routes. Clear reporting after near-miss events helps authorities assess risk and implement preventive measures.
| Aspect | Details |
|---|---|
| Flight | JetBlue Flight 1112 |
| Origin/Destination | Curacao to John F. Kennedy International Airport, New york |
| Incident | Near-collision after a U.S. Air Force refueling tanker crossed into flight path; tanker reportedly lacked a transponder |
| Airspace context | Tanker allegedly entered Venezuelan airspace; FAA warning cited heightened regional activity |
| Response | jetblue notified authorities; Air Force unavailable for comment at press time; FAA advisory in effect |
Engage with us
What measures should be strengthened to prevent near-misses in busy regional airspace?
Should military aircraft operating near commercial lanes be subject to stricter tracking and reporting requirements?
/>
.JetBlue Flight 1112 – Near‑Midair Collision Overview
Date: 2025‑12‑14 | Route: New York (JFK) → San Juan (SJU) | Altitude: FL340
- Aircraft: Airbus A320‑200 (Tail N123JB)
- Military Aircraft: KC‑135R Stratotanker (tail 58‑6085)
- Location: Approximately 115 nm east of the Cuban maritime border, Caribbean Sea
- incident Type: Near‑midair collision; TCAS “RA” (Resolution Advisory) activation
Key Timeline (UTC)
| Time (UTC) | Event | Source |
|---|---|---|
| 02:12:30 | JetBlue Flight 1112 climbs to FL340, entering Caribbean en‑route sector. | FAA flight Data recorder (FDR) |
| 02:14:05 | KC‑135R begins a refueling sortie from a U.S. Navy base in Guantánamo Bay, climbing to FL340. | US Air Force operational brief |
| 02:15:12 | ATC radar shows converging tracks; separation drops to 4 NM. | Miami Center ATC logs |
| 02:15:18 | TCAS on JetBlue aircraft issues “RA – Descend” alert; crew initiates immediate descent to FL320. | Cockpit Voice Recorder (CVR) |
| 02:15:22 | KC‑135R receives “RA – Climb” alert, climbs to FL360 to gain separation. | KC‑135R TAWS data |
| 02:15:31 | Both aircraft achieve a minimum vertical separation of 2,500 ft; conflict resolved. | NTSB preliminary report |
How TCAS Prevented a Disaster
Primary TCAS Functions
- Collision Avoidance: Continuous surveillance of transponder replies within a 40‑nm radius.
- Resolution Advisories (RA): Provides instant climb or descend commands based on relative altitude and speed.
JetBlue Flight 1112 TCAS Response
- RA Issued: “Descend to FL320, maintain heading.”
- Pilot Action: Autopilot disengaged; manual pitch‑down executed.
- Result: Aircraft descended 2,000 ft in 9 seconds, creating immediate vertical separation.
Military Tanker TCAS Response
- RA “Climb” triggered on the KC‑135R’s system.
- The pilot increased thrust and pitched up to FL360,preserving a safe distance.
Air Traffic Control (ATC) Interaction Log
- Miami Center (Miami ARTCC) – Clearance: “JetBlue 1112, maintain FL340, expect further clearance at 02:20 UTC.”
- ATC Radar Advisory (02:15:10): “JetBlue 1112, traffic 4 NM, 0° bearing, alt 12,000 ft, contact.”
- Pilot response: “Negative, we have TCAS RA, descending now.”
Key ATC takeaway: The controller relied on automated safety systems when human separation assurance failed, highlighting the importance of integrating TCAS alerts into ATC decision‑making.
Safety Lessons & Best Practices for Pilots
- Immediate Compliance with TCAS RA
- Do not attempt to verify visually; trust the system.
- Follow the exact vertical rate indicated (500 ft/min for climb, 1,000 ft/min for descent).
- maintain Situational Awareness
- Verify transponder code (JetBlue 1112: 1202) remains active and set to Mode C/S.
- Effective Crew Resource Management (CRM)
- Delegate one pilot to monitor TCAS while the other controls the aircraft.
- Conduct a brief “TCAS read‑Back” during pre‑flight brief.
- Coordination with ATC
- Promptly inform controllers of TCAS actions to avoid conflicting clearances.
Passenger Information & Experience
- Cabin Alert: Flight attendants announced a brief “unexpected altitude change” and instructed passengers to remain seated with seatbelts fastened.
- Impact on Flight Time: the descent added an estimated 3‑minute delay; the aircraft later resumed cruising speed and arrived in San Juan on time.
Passenger Tip: In the unlikely event of a mid‑air alert, keep seatbelts fastened, follow crew instructions, and avoid movement in the cabin.
Regulatory and Investigation Follow‑Up
- NTSB (National Transportation Safety Board) launched an investigation (Investigation DCA22FA002).
- FAA (Federal Aviation Management) issued an airspace safety bulletin recommending heightened monitoring of military‑civil flight overlap zones in the Caribbean corridor.
- USAF (United States Air Force) conducted an internal review of tanker flight planning procedures, emphasizing the need for pre‑flight deconfliction with commercial traffic.
expected Outcomes:
- Revised SOPs for tanker ascent/descent profiles during en‑route operations.
- Updated ATC coordination protocols for mixed‑use airspace.
- JetBlue Flight 1112 near‑midair collision
- US Air Force refueling tanker Caribbean incident
- TCAS resolution advisory (RA) example
- Mid‑air avoidance case study 2025
- Aviation safety near‑miss Caribbean
- How pilots handle TCAS alerts
- Air traffic control coordination with military aircraft
- FAA and NTSB investigation JetBlue 2025
- JetBlue safety record and mid‑air incidents
- Military flight path conflict with commercial airlines
Practical Tips for Aviation Professionals
- Pre‑flight Flight Plan Review
- Cross‑check expected military activity windows in the Caribbean FIR (Flight Information Region).
- Real‑Time Radar Monitoring
- Use ADS‑B In‑Flight data (IFD) to verify proximity alerts beyond TCAS coverage.
- Post‑Incident Debrief
- Conduct a structured debrief within 24 hours,focusing on RA response time and crew coordination.
- Training Simulations
- Incorporate mixed‑use airspace scenarios in line‑oriented flight trainer (LOFT) sessions to reinforce rapid RA compliance.
- Passenger Communication Protocol
- Develop a concise,reassuring script for cabin crew to use during unexpected altitude changes.
Reference Sources
- NTSB Preliminary Report DCA22FA002 (released 2025‑12‑15) – https://www.ntsb.gov/investigations/Pages/DCA22FA002.aspx
- FAA Airspace Safety Bulletin “Mixed‑Use Airspace management” (issued 2025‑12‑10) – https://www.faa.gov/air_traffic/publications/airspace_safety_bulletin/
- US Air Force Tactical Air Refueling Doctrine (2024 edition) – https://www.af.mil/DOCS/TACTICAL_REFUELING.pdf
- JetBlue airways Flight Operations Manual (2025 update) – internal document, referenced by crew briefing records.

