The disconnect between what various pilots understood to be minimum-allowed altitude during an attack on the radar site was illuminated as a result of the debrief of a Flat Face mission flown by Scratch and Maj Dirt Fluhr. Due to the weather along the coast and with CAOC direction, they were forced to fly between cloud decks to search for the radar. As they neared the suspected coordinates of the elusive target, they dropped through a thin “scud” layer at about 4,500 feet. Once below the clouds, they searched the area along the coastline for the radar, threats, and a way back up through the weather, which they knew they would eventually need. During this search the Serbs shot a heat-seeking missile at them. Scratch and Dirt promptly defeated the shot, popped up through the clouds, and returned home.
Following their close call, Scratch and Dirt conducted the standard debrief with our squadron’s intel personnel. They stated that they were probably at about 4,000 feet at the time of the missile shot. Our excellent intel troops faithfully recorded their details and dutifully forwarded the mission report to the CAOC. That statement of flying at 4,000 feet—below the normal ROEs’ 5,000-foot minimum altitude for identifying targets, and 8,000-foot minimum used during attacks—without an operational explanation was certain to draw attention from anyone without our earlier understanding of the ROE “exception.” I learned an important lesson and noted that a timely operations review of the unit’s mission reports by its supervisors will provide a clearer picture of what is actually taking place and help reduce friction and fog. I had suffered a miscommunication on what I thought was a “onetime exception.” to the minimum attack-altitude for that firstnight sortie to use while they attacked the radar. I had understood that we were back to adhering to the normal ROE altitudes. If I had reviewed the mission reports, I would have been alerted to the squadron pilots’ inconsistent understanding of the ROEs’ minimum altitudes. We fixed this immediately. Although it seemed contrary to letting the intel troops do their job, in a shooting war with highly politicized ROEs, it is essential to use every available means to stay informed and ensure a good information flow at all levels.
The lightning bolt from the CAOC was swift and unequivocal. The two pilots involved, plus a supervisor
We had to get the details together fast. We heard pilots express surprise that the CAOC was upset about Scratch and Dirt inadvertently flying at 4,000 feet in daytime since the CAOC had already approved flying below 2,000 feet at night on that target. That’s when I realized the disconnect between the ROEs the CAOC understood to be in place and the ones our pilots were using. I interviewed all the pilots involved and looked over the mission reports from the previous two Flat Face sorties. They all told the same story—they had assumed that low-altitude attacks on the radar were approved. They had not listed their attack altitudes in their mission reports since that data was normally sought only for weapons-release conditions and threat reactions. These were the same guys who had routinely put themselves at risk to comply with the ROEs—as they understood them. They had enforced the ROEs to ensure that they, and the NATO fighters they controlled, would never come close to hurting civilians in Kosovo. I had no reason to doubt their integrity, professionalism, or sense of duty. When it came to accepting a higher personal risk to take out an important target, they went all out. I concluded that a couple of pilots had let their fangs get a mite too long and had taken unnecessary risks. They were grounded a day or more as a result—not to punish them because they went below any particular altitude but to recalibrate their in-flight and on-scene assessment of risk and payoff. These same great pilots justifiably earned important medals for heroism during other sorties.