On November 22, 2013, a near collision involving a commercial airliner and military aircraft over the Atlantic Ocean brought new attention to JFK near collision risks. This incident highlighted how close approaches can occur even in well monitored airspace around major hubs.
Below is a detailed breakdown of the event, its causes, responses, and ongoing implications for operations and travelers.
| Event | Date | Key Aircraft | Outcome |
|---|---|---|---|
| Near Collision Incident | November 22, 2013 | Delta Air Lines Flight 1746, USAF C-17 | No collision, safety investigation launched |
| Reported Altitude Breach | During cruise phase | C-17 descended through assigned level | Conflict resolution by air traffic control |
| Response Actions | Immediate ATC intervention | Climb, descent, and lateral maneuvers | Prevention of continued close approach |
| Investigation Findings | Procedural and communication factors | Controller workload and radar limitations | Recommendations issued to improve safety |
Operational Dynamics Around JFK Airspace
The airspace around JFK is among the most complex in the United States, integrating commercial, cargo, and military operations. High traffic density requires precise sequencing and constant coordination between controllers and pilots. The November 2013 near collision exposed how demanding conditions can challenge even mature systems.
Traffic Management Challenges
Unplanned altitude deviations by military aircraft can create sudden conflict zones. Controllers must manage multiple moving parts while adhering to strict separation standards, especially under reduced visibility or during peak hours. Technology and procedure must align to keep risks within acceptable margins.
Aircraft Involved and Flight Profiles
Delta Air Lines Flight 1746, a narrow body jet, was operating a regular schedule from New York to Atlanta. The USAF C-17 transport aircraft was on a mission that brought it into the same volume of air. Differing altitudes, speeds, and priorities can complicate the picture for both pilots and controllers.
Key Flight Parameters
| Aircraft | Type | Flight Level | Deviation |
|---|---|---|---|
| Delta 1746 | Boeing 737 | Stable altitude | |
| USAF C-17 | Transport | Unplanned descent through cruise layer |
ATC Response and Safety Protocols
Air traffic control plays a decisive role in resolving potential conflicts. On that day, controllers issued immediate climb and descent instructions to reestablish mandated separation. The actions followed standard emergency and near miss procedures designed to minimize risk in real time.
Separation Standards Applied
- Vertical separation of at least 1,000 feet in controlled airspace
- Horizontal separation tailored to traffic density
- Use of radar vectors and altitude changes for conflict resolution
- Coordination with adjacent sectors and military liaison
Causes and Contributing Factors
Investigations pointed to a combination of controller workload, radar display limitations, and procedural ambiguities. The C-17’s deviation occurred while managing concurrent operational demands. Human and system factors together created a situation where margins were thinner than usual.
Root Cause Analysis Highlights
- Controller attention split across multiple traffic streams
- Delayed radar update contributing to situational gaps
- Ambiguity in guidance for military aircraft operating near heavy airliner routes
- Need for improved cross sector data sharing
Safety Recommendations and Industry Impact
Following the incident, regulators issued guidance to tighten coordination between civilian and military airspace users. Airlines and military operators reviewed training, emphasizing proactive communication and altitude discipline. Enhanced monitoring tools were explored to reduce similar near collision risks at JFK and comparable environments.
Key Industry Changes
- Revised checklists for unexpected military activity near major airports
- Increased use of short term conflict alerts in terminal radar areas
- Joint drills between air traffic management and military operators
- Data sharing agreements to improve early warning capabilities
Long Term Outlook for Near Miss Prevention
Continued investment in radar technology, clearer cross sector policies, and robust training can further reduce near collision risks. Stakeholders must maintain vigilance to protect the safety of passengers and airspace users around JFK.
- Update surveillance systems for faster data refresh
- Formalize joint civil military procedures for high traffic regions
- Implement regular cross sector drills and debriefs
- Monitor key performance indicators for near miss trends
FAQ
Reader questions
What happened during the JFK near collision on November 22, 2013?
A Delta commercial airliner and a U.S. Air Force C-17 entered an unacceptably close proximity due to an unplanned descent by the military aircraft, prompting immediate corrective action from air traffic control.
Why did the C-17 descend into the same level as the commercial flight?
The deviation resulted from a combination of controller workload, radar update delays, and ambiguous procedures for military operations in nearby airspace.
How did air traffic control prevent a collision?
Controllers issued rapid climb and descent instructions to restore mandated separation, relying on standard conflict resolution protocols under high traffic density.
What changes were implemented after the incident?
Regulators and operators introduced revised coordination checklists, enhanced monitoring tools, and joint training to reduce recurrence and improve situational awareness.