A near-midair collision incident in the Colorado Springs terminal area has highlighted persistent risks at the intersection of IFR and uncoordinated VFR formation operations in Class E and transitional airspace. The event unfolded during an IFR departure from KCOS (Colorado Springs Regional) routing northbound toward KCFO (Meadow Lake Airport), with the crew receiving radar vectors and eventually a direct clearance. In the vicinity of KFLY (Fremont County Airport), the crew identified a flight of two VFR aircraft on a converging course. One of the aircraft was broadcasting ADS-B Out but with no callsign, appearing only as an anonymous "VFR" target on traffic displays and verified on the Global ADS-B Exchange. The aircraft closed to within approximately 400–500 feet before the pilot disconnected the autopilot and initiated a manual right deviation. ATC simultaneously issued a collision alert and directed an immediate right turn — a near-simultaneous recognition that underscores the system very nearly failed before either layer caught the conflict.
The behavior of the VFR pair following the initial encounter is the more troubling operational detail. Rather than deconflicting, the aircraft continued to circle the IFR traffic for approximately five minutes, then reportedly repeated the behavior against subsequent IFR arrivals and departures at KCOS. This pattern strongly suggests either deliberate airspace provocation or an extraordinary lapse in situational awareness — and in either case, it represents a direct threat to separation standards that ATC cannot fully mitigate in Class E airspace where VFR operations require no clearance. The anonymous ADS-B target, transmitting position without a callsign, creates a significant gap in both ATC coordination and crew situational awareness: while the traffic was technically visible on TIS-B and EFB displays, the absence of an identifiable callsign or transponder code severely limited ATC's ability to issue traffic advisories, coordinate with the aircraft, or take enforcement action in real time.
For IFR crews operating in and out of busy GA corridors like the Colorado Front Range, this incident illustrates that procedural compliance and proper ADS-B equipage do not guarantee safety when other traffic operates outside the norms of coordinated airspace use. The TIS-B system re-broadcasts ADS-B targets to equipped aircraft, and the crew's ability to identify the traffic early was a direct product of that technology — but the 400–500 foot closest point of approach still represents a serious failure margin. Formation flight in the VFR environment is legal but governed by specific regulatory requirements, including the requirement that pilots in formation agree upon a flight plan in advance (14 CFR 91.111). Erratic maneuvering around IFR traffic in transitional airspace almost certainly violates the careless or reckless operation standard under 14 CFR 91.13 and potentially constitutes hazardous operation under 14 CFR 91.111(b).
The reporting question the pilot raises — ASRS versus FSDO — is not an either/or calculus. A NASA ASRS report is appropriate in essentially all cases involving unexpected safety events and provides immunity protection for the reporter, but it does not constitute a formal enforcement referral and may not prompt any corrective action against the offending party. Given the repeated, multi-aircraft nature of the hazardous behavior described, a direct report to the Denver FSDO is warranted and would be substantively different from an ASRS filing. ATC will likely have radar data, Mode C tracks, and possibly recorded communications that could establish the identity of the aircraft even without a callsign, particularly if the ADS-B ICAO hex code was logged from the traffic display. Reporting both channels simultaneously maximizes the likelihood of regulatory follow-up while preserving the reporter's protections.
The broader trend this incident reflects is the growing complexity of shared airspace in regions where GA training, recreational flying, and IFR operations are densely concentrated. Airports like KCOS and KCFO serve a cross-section of airline feeders, military operations, Part 135 and 91 business traffic, and high volumes of GA training and recreational flight. Anonymous or poorly-tagged ADS-B targets remain a systemic vulnerability: while ADS-B Out mandates in most controlled and high-altitude airspace have significantly improved traffic picture quality since the 2020 equipage deadline, the architecture still permits operations without callsign correlation in many environments, and enforcement of equipage requirements in Class E and G remains inconsistent. Operators relying on TCAS II and TIS-B as a safety backstop should treat anonymous or unresolved traffic targets with heightened caution, particularly in busy terminal corridors where the consequences of a late reaction are measured in hundreds of feet.