F/A-18 and Citation Near-Collision at Austin After a Clearance Misunderstanding

Accident Facts

On 23 September 2023, a flight of F/A-18s operating as SNAKE21 and a NetJets Cessna Citation came into close proximity while approaching Austin-Bergstrom International Airport. The event was not an accident, but it was a serious loss-of-separation event: the Citation crew took evasive action after receiving a traffic alert, and a preliminary FAA account reported that the aircraft came within about 200 feet vertically.

The central problem was not a single missed radio call. The military formation had requested an overhead break, a maneuver in which the fighters arrive at the airport at speed and then make a descending break to enter the landing pattern. The controller and military pilot did not appear to have the same understanding of how that request would be executed. Archived ATC audio later made the mismatch unusually clear.

The Citation had already been cleared to land. As SNAKE21 approached, the fighter pilot requested altitude and airspeed at his discretion for the break and received a clearance that he understood to authorize that profile. The controller, however, expected the fighter to begin its descent at a different point. The difference mattered because the two aircraft were converging on the same airport environment at very different speeds and on different assumptions about the fighter's path.

Within roughly half a minute of the relevant clearances, the Citation crew reported a proximity warning. The radio recording captured the reaction that became the defining line of the incident: an unidentified voice said, in effect, that it would have been useful to know what the fighter was about to do. The military pilot then explained that he had requested altitude and airspeed at his discretion for the break and believed that request had been cleared.

The FAA told The Washington Post that the private jet took evasive action and that the aircraft came within about 200 feet. The agency said it was investigating the incident. The report also noted that the fighter flew near a runway being used by a small propeller aircraft, making the event part of a broader concern about runway and airspace conflicts at a time when the FAA and NTSB were examining a series of serious near misses.

The radio exchange after the immediate conflict is important because it shows that the controller himself recognized a misunderstanding. After landing, the fighter pilot asked for a telephone number to discuss what had happened, and a controller said there had been a miscommunication. That does not, by itself, establish which participant was legally at fault. It does show that the clearance and the intended maneuver were not understood in the same way by both sides.

The event is therefore best understood as a breakdown in shared situational awareness during a complex military arrival into a busy civilian airport. The fighters' high-energy overhead-break profile required precise coordination, while the Citation was already established for landing. Once the two mental models diverged, the available margin disappeared quickly. The fact that the Citation received a traffic alert and avoided a collision is what turned a potentially catastrophic encounter into a near miss rather than an impact.

Sources

• The Washington Post — FAA account and archived ATC reconstruction
• PPRuNe discussion preserving contemporary reporting