What happened in the Delta and Air Force jet incident
On July 19, 2023, a Delta Air Lines Boeing 737 and a U.S. Air Force F-16 fighter jet came within 300 feet of each other near Savannah/Hilton Head International Airport in Georgia. The incident occurred when the F-16 was descending to land while the Delta flight was climbing after takeoff. Air traffic control had cleared both aircraft for their respective maneuvers, but a lapse in communication and radar monitoring created a situation where the two planes occupied nearly the same airspace at nearly the same time.
The National Transportation Safety Board (NTSB) investigated the incident and determined that neither pilot saw the other aircraft before the conflict was resolved. The F-16 pilot received a traffic alert from his onboard warning system and initiated an when ready climb, which increased the separation between the two planes. The Delta flight crew was not aware of the proximity until after the incident had been resolved.
This type of event is called a "loss of separation" incident in aviation. It means that two aircraft came closer together than the minimum safe distance required by air traffic control rules. The minimum safe distance varies depending on altitude and airspace type, but is typically 1,000 feet vertically or 3 miles horizontally.
Key Takeaways
- A Delta 737 and Air Force F-16 came within 300 feet of each other near Savannah in July 2023, a separation well below the required minimum distance.
- The incident resulted from a communication gap between air traffic control and the pilots, not from pilot error or mechanical failure.
- The F-16's onboard collision avoidance system detected the threat and alerted the pilot, who took when ready action to climb and increase separation.
- The NTSB investigation found that radar monitoring gaps and radio frequency congestion contributed to the loss of separation.
- This incident led to recommendations for improved radar coverage and communication protocols at regional airports.
How air traffic control prevents aircraft collisions
Air traffic controllers use radar, radio communication, and standardized flight paths to keep aircraft safely separated. When a pilot requests clearance to take off or land, the controller checks radar to see what other aircraft are in the area, then issues instructions that maintain the required separation. The controller continues to monitor both aircraft on radar and adjusts their paths if needed.
In the Delta-F-16 incident, the controller cleared the Delta flight to climb to a specific altitude and the F-16 to descend to a specific altitude. However, the timing of when each aircraft reached those altitudes created an overlap. The controller did not catch this conflict before it happened, and neither pilot received a warning in time to see the other aircraft visually.
Modern commercial aircraft carry their own collision avoidance systems called Traffic Collision Avoidance Systems (TCAS). These systems use radar to detect nearby aircraft and alert pilots if another plane is too close. If two TCAS-equipped aircraft are on a collision course, the system will tell one pilot to climb and the other to descend, ensuring they move apart. The F-16's system worked as designed in this incident.
Why regional airports face different challenges than major hubs
Savannah/Hilton Head is a regional airport, not a major hub like Atlanta or Charlotte. Regional airports handle fewer flights per hour than large hubs, but they often have less sophisticated radar equipment and smaller air traffic control teams. Controllers at regional airports may handle both civilian and military traffic, which adds complexity to their workload.
The NTSB found that the radar at Savannah had gaps in coverage—areas where the radar could not reliably detect aircraft. These gaps are more common at smaller airports because the equipment is older or less powerful. When an aircraft passes through a radar gap, the controller loses sight of it temporarily on the screen, even though the plane is still in the air.
Additionally, radio frequencies at busy times can become congested, meaning multiple pilots are trying to talk to the controller at once. If a controller is listening to one transmission, they may miss or not fully hear another. This congestion was a factor in the Delta-F-16 incident, according to the NTSB report.
What the NTSB recommended after this incident
The NTSB issued several recommendations to the Federal Aviation Administration (FAA) following the investigation. The first recommendation was to upgrade radar equipment at regional airports to eliminate coverage gaps. The second was to improve communication protocols when military and civilian traffic share the same airspace and frequencies.
A third recommendation focused on controller training. The NTSB suggested that controllers receive additional training on managing mixed military-civilian traffic during peak hours. The fourth recommendation asked the FAA to review the clearance procedures used when aircraft are climbing and descending through the same altitude block, to reduce the chance of timing conflicts.
The FAA has not yet implemented all of these recommendations, though it has begun a review of radar coverage at regional airports. Implementation of new radar systems can take years because of the cost and the need to coordinate with airport operators and the military.
How pilots and controllers work together to prevent incidents
Pilots are trained to follow air traffic control instructions precisely, but they are also trained to speak up if something does not seem right. If a pilot receives a clearance that they believe puts them in danger, they can request a different clearance or declare an emergency. This is called "pilot in command authority," and it is a fundamental safety principle in aviation.
Controllers, in turn, are trained to listen carefully to pilot readbacks of clearances. When a pilot repeats back the clearance they received, the controller listens to make sure the pilot understood correctly. If there is a misunderstanding, it should be caught at this point. In the Delta-F-16 incident, both the pilot and controller followed these procedures correctly, but the system still failed to prevent the loss of separation.
After an incident like this, both the pilot and controller are interviewed by the NTSB. Their actions are reviewed to see if they followed procedures and if those procedures were adequate. In this case, both the pilot and controller had done their jobs correctly according to the rules that existed at the time, but the rules themselves were found to be insufficient.
The difference between a near-miss and an accident
A near-miss incident is one in which two aircraft come closer together than they should, but no collision occurs. These incidents are valuable learning opportunities because they show where the system failed before anyone was hurt. Every near-miss is investigated and reported, and the information is used to improve procedures and equipment.
An accident, by contrast, is when a collision or other serious event actually occurs. The aviation industry treats near-miss incidents with the same seriousness as accidents because they reveal the same underlying problems. If a near-miss is not investigated and corrected, the same problem could eventually lead to an accident.
The Delta-F-16 incident was classified as a loss of separation incident, which is a specific type of near-miss. These incidents are tracked by the FAA and the NTSB, and they are used to identify trends. If a particular airport or controller facility has multiple loss of separation incidents, that is a signal that something needs to change.
What changed in aviation safety after this incident
The Delta-F-16 incident contributed to a broader conversation about radar modernization at regional airports. The FAA has been working to replace older radar systems with newer technology that provides better coverage and more accurate tracking. However, this process is slow because it requires funding, coordination with airport operators, and testing to may support the new systems work correctly.
The incident also highlighted the need for better communication between civilian air traffic control and military air traffic control. At many airports, civilian and military traffic share the same airspace but may use different radio frequencies or communication systems. Improving coordination between these two systems is an ongoing effort.
Additionally, the incident led to a review of how controllers manage traffic during peak hours at regional airports. Some airports have implemented new procedures to reduce the risk of loss of separation incidents, such as requiring larger vertical separation between climbing and descending aircraft, or staggering the times at which aircraft are cleared to climb or descend.
Frequently Asked Questions
How close do two planes have to be to be considered a near-miss?
The FAA defines a loss of separation as any time two aircraft come closer than the minimum required distance, which is typically 1,000 feet vertically or 3 miles horizontally. In the Delta-F-16 incident, the planes were 300 feet apart, which is well below the minimum. However, even aircraft that come within 2,000 feet of each other are investigated if they were supposed to be farther apart.
Do pilots always know when they are close to another aircraft?
No. In the Delta-F-16 incident, neither pilot saw the other aircraft. Pilots rely on air traffic control to keep them separated, and on their onboard collision avoidance systems to alert them if another aircraft is nearby. Visual detection of other aircraft is difficult, especially at night or in poor weather, and especially when aircraft are moving at high speed.
Why does the military share airspace with civilian aircraft?
Military aircraft need to train and transit between bases, and they often use the same airports and airspace as civilian aircraft. The FAA and the military coordinate to manage this shared airspace safely. At some airports, military and civilian traffic are separated by altitude or time of day. At others, they share the same frequencies and procedures.
Has anything like this happened before?
Yes. Loss of separation incidents occur regularly at airports across the United States. The FAA tracks these incidents and publishes data on how many occur each year. Most are resolved without incident because of the safety systems in place, but they all point to areas where procedures or equipment could be improved.
What happens to a controller if there is a loss of separation incident?
Controllers are not automatically blamed for loss of separation incidents. The NTSB investigates to determine whether the controller followed procedures correctly and whether the procedures themselves were adequate. If a controller made an error, they may receive additional training or counseling. If the procedures were inadequate, the FAA works to improve them. Controllers are protected by federal law from retaliation for reporting safety concerns.