It was Fairford, the year they had the full Carrier Air Wing package on the static line, and I remember standing close enough to an EA-18G Growler to read the maintenance stencilling on the access panels while the heat from the previous day’s flying still seemed to be radiating off the fuselage. The aircraft had a quality that was different from almost anything else on that flight line. Not elegant, not brutal in the way a Tornado was brutal, but purposeful in a way that felt almost architectural, as though every surface had been argued over by engineers who cared about outcomes rather than appearances. The crew chief saw me studying the wingtip jamming pod and said something I couldn’t quite catch over the background crowd noise. I nodded anyway.
That was before Idaho.
I have been following the Growler story through the aviation press since the first grounding, the way you follow anything that sits at the intersection of military transparency and the kind of operational safety questions that never quite get answered in the official statements. The Idaho incident, the details of which remain genuinely unclear in the public domain in ways that are themselves worth paying attention to, triggered a fleet-wide stand-down that the Navy handled in the manner these things are generally handled: a brief acknowledgement, a reference to the ongoing investigation, and an implied assurance that the process was proceeding as it should. The fleet was cleared. Flying resumed. Then the fleet was grounded again. Then it was cleared again.
Twice. Both times quietly.
That word, quietly, is doing considerable work in the coverage of this story, and I think it is worth sitting with for a moment. A fleet grounding is not a quiet event inside the institution that imposes it. It involves engineering assessments, maintenance reviews, command decisions, and a considerable number of people who all have opinions about what happened and what should change. What is quiet is the version of that process that reaches the public. The Navy cleared the Growler twice without, as far as the available reporting shows, providing a substantive account of what the investigation found, what the identified fault was, or what specifically changed between the grounding and the clearance. We are asked to conclude, on the basis of the clearance itself, that whatever was wrong has been addressed.
I understand why military aviation works this way. Some of it is genuinely classified. Some of it is liability-adjacent in ways that legal departments understandably manage carefully. And some of it is simply institutional culture, the preference for resolution over explanation, the sense that confidence in the fleet is better served by returning it to operations than by walking the public through the engineering analysis that got it there. I understand all of that. I don’t think it is adequate.
When I was at Biggin Hill two summers ago, there was an unannounced substitution in the display programme. Nothing was said from the commentary box about why the scheduled aircraft hadn’t appeared. An hour later someone near me in the crowd had heard from a marshal that there had been a technical issue on the ground. The official line, when I checked afterwards, referenced airspace coordination. These are not the same thing, and the people in that crowd who had driven a long way and paid entry for a specific display deserved better than a euphemism. I raise this not to equate a civil display cancellation with a naval fleet grounding. The stakes are entirely different. But the habit of mind is the same: the preference for a form of words that closes the subject rather than one that opens an honest account of what happened.
What unsettles me about the Growler situation, specifically, is the twice. A single grounding, investigation, and clearance can be read as the system working as intended. Something was noticed, the aircraft was stood down, the issue was resolved, operations resumed. That is the process functioning. But a second grounding, a second investigation, and a second quiet clearance raises a different question. It suggests either that the first investigation did not fully identify the root cause, or that the root cause was identified but the contributing conditions were not fully addressed, or that something was missed. None of those possibilities is necessarily a condemnation of the process. All of them would benefit from being said plainly rather than absorbed into an institutional silence that the public is expected to accept as resolution.
The Growler is an extraordinary piece of machinery. The electronic warfare capability it carries is genuinely significant in ways that military aviation coverage often underplays. If it appears at RIAT in the coming season, which given the timing and the current programme patterns is not unlikely, the crowds will respond to it with exactly the attention it warrants. People will stand at the static cordon and look at the jamming pods and think about what those aircraft actually do. Some of them will have followed this story. Most won’t.
What I want, and what I think the people who care about military aviation are owed, is not access to classified fault analysis. It is a clearer account of what category of problem caused the grounding, and what category of solution resolved it. That is not an unreasonable ask. The aircraft flies over populations. It appears at public events. The people who share that airspace, even as spectators on the ground, are not required to take institutional confidence on faith simply because no one has chosen to offer them anything more specific.
Trust in these systems is not built by silence. It is built by being honest about what happened, even when honesty is inconvenient.
