Airmanship & Argument

Glad to be here

A jet flew too low over a beach in Florida on July 15th 2026, and two camps spent the week demanding a verdict before the review that might produce one had begun. In the middle of it the squadron's commanding officer did what neither camp would: he called the pass unsafe, and sought no one's dismissal. That distinction — no punishment is not the same as no problem — is the one the argument never made.

Editorial illustration: an empty squadron debrief room at dusk, with one red chair pulled out beneath a blank whiteboard and an unmarked flight helmet resting on it
Illustration generated with OpenAI; art direction by Threadonomist

The car parks at Pensacola Beach filled by seven in the morning. They always do, on the Wednesday of air-show week, for an event the town calls Breakfast with the Blues, at which the United States Navy's flight demonstration squadron comes home and says hello. On July 15th 2026 a Super Hornet came down the shoreline lower than it should have and the beach lost its furniture. Tents went over. Chairs went cartwheeling into the surf. A woman who had been coming for ten years said she thought she was going to be taken out, and that it was amazing.1

Nobody was hurt. By the next morning the pass had been watched more than a million times, the secretary of war had announced that the flyovers would continue until morale improves, the Pentagon's spokesman had captioned a photograph of a jet over people's heads with “Carry on Patriots”, and a former naval flight-test engineer had written a thirteen-post thread arguing that the pilot was either incompetent or had done it on purpose.2 The thread was seen six hundred and ninety-five thousand times. Adam Kinzinger, a Republican and a former air-force pilot, replied: good thread.3

Somewhere in the middle of this, Captain Adam Bryan, the squadron's commanding officer, stood in front of a camera at Naval Air Station Pensacola and was asked the question directly: you have had a lot of attention, including from Pete Hegseth, who says keep flying flyovers; talk about the incident, and what you do afterwards, if anything.4

Here is what he said. “Every flight we do, whether it goes incredibly well or we don't have the best flight, we look at it and we debrief it every day. During yesterday's Circling Arrival Maneuvers, one of our pilots found himself over the beach line, over a crowd in an unsafe situation. The safety of our flight demonstration, the safety of the crowd that goes out there and watches it every day, is the utmost of what we do. So we'll have a heavy review of what happened yesterday to ensure that, one, we don't put ourselves in unsafe situations again, and two, that we learn from it.”

That is the whole of it.

What he did not do

He did not minimise. Handed a national row and an invitation to say the flying had been fine, the boss said his pilot had been over the beach line, over a crowd, in an unsafe situation. Flatly. He conceded the one fact that the administration's version never concedes.

And he did not reach for a scalp. There is no punishment in those thirty-eight seconds: no suspension, no board, no reprimand. There is a review, there is learning, and there is tomorrow.

Both of those things at once. That combination is not squeamishness and it is not a fudge. It is a technology, it is about fifty years old, and a large part of why you can get on an aeroplane. You cannot fix what you cannot see; you only see it if the man who did it tells you; and he will only tell you if telling you is survivable. So you build a system in which honest error buys a debrief rather than a court, you protect what is said inside it, and in exchange you get the truth. American naval safety investigations are privileged for exactly this reason: their findings may not be used against anyone, so aircrew will say what actually happened.5 The price is that the system cannot defend itself in public. The benefit is that it works.

That is what Captain Bryan was doing. In the middle of a political brawl, under a camera, with a secretary already posting, he ran the ordinary procedure: name the error, keep the man, review it hard, learn. It was not what the argument was about.

The two ways to break it

A no-fault system can be broken from either side, and this week both were tried.

The first way is to demand a hanging: punish the pilot, make an example, show that standards mean something. This is the intuitive move and it is precisely wrong, because the moment error costs a career, error stops being reported. You do not get fewer mistakes. You get fewer accounts of mistakes, which is the same number of mistakes and no way to find them. The debrief works because a man can walk into the room, say he nearly killed everybody, and fly again on Thursday.

The second way is subtler, and it is what actually happened. At 2.32 in the afternoon the acting secretary of the navy posted: “Flight debrief complete. No reprimands. No firings. No problem. That's the sound of Freedom! Semper fi and Hooyah.”6

Read that against Bryan. The boss said we'll have a heavy review — future tense, not yet begun. The secretary announced the flight debrief finished. Bryan said his pilot had been over a crowd in an unsafe situation. The secretary said there was no problem. They were not disagreeing about punishment; Bryan never asked for any. They were disagreeing about whether anything had happened — and the man with the aircraft, the pilot, the video and the debrief said that it had.

The squadron had promised a thorough safety review. What the secretary declared complete was the flight debrief. Asked whether those were the same thing, navy officials would not say.7 One is what happens after every sortie the team has ever flown; the other is what you announce when something has gone wrong. Nobody has answered the question. “No problem” is how a political answer tries to close it before the safety answer arrives.

“No punishment” and “no problem” are not the same sentence. The first is a finding about a man. The second is a claim about the world, and it is the enemy of the review, because a review is a thing you hold when there is a problem.

The same incident, two different findings

Agreement on punishment concealed a disagreement about reality.

Question
Safety findingCaptain Bryan
Political verdictActing Secretary Cao
What happened?
An “unsafe situation”
“No problem”
What follows?
A “heavy review”
“Flight debrief complete”
Who is punished?
Nobody asked to be
“No reprimands. No firings.”

Compatible: no punishment and a serious review. Incompatible: no problem and a reason to learn.

The difference is not whether to fire the pilot. It is whether the system is still allowed to describe an unsafe event as a problem. Sources: Captain Bryan's recorded remarks and the acting secretary's post; see notes 4, 6 and 7.

Why the prosecution fails

The engineer's thread was not stupid. It was the best-argued thing written about the pass all week: the manual's altitudes are minimums; the very low passes are flown parallel to the crowd and behind a five-hundred-foot line, so that a jet at fifty feet would take a major failure to reach the beach, not a small mistake. What he read off the video was a jet at about a hundred feet in a ninety-degree banked turn with its energy aimed at the sand. Since Blue Angels pilots are the best of the best, he argued, it cannot have been a mere mistake: either the man was incompetent, or he meant it.

What the video shows. The July 15th pass, from a compilation of bystander and drone clips. In the closest ground frames the jet is in a hard, high-g bank — the vapour off the wing roots marks the loading — its full underside turned to the beach, above a packed crowd. Read off the film it is about a four-g turn, which is roughly seventy-five degrees of bank: steep, but well short of the knife-edge some claimed, since a level turn cannot hold ninety degrees, and a true ninety would show the wings edge-on rather than the whole underside the camera reads here. A side view over the water puts it around seventy-five feet up. These are estimates from a phone, not a data card — enough to place the pass well outside the envelope, and nowhere near the telemetry a career should turn on, which the navy has released to no one. Footage compiled via @mercadomedia1 from bystander and drone sources (unverified), reproduced for commentary on a public matter; this publication does not hold its copyright. Scale: bank estimated from the aircraft; altitude not established.

The trouble is the manoeuvre. Bryan named it: Circling Arrival Maneuvers. The sneak pass belongs to Blue Angel number five and it belongs to the show; an arrival is how you get there.8 His sharpest inference — that a pilot this good could not have strayed so far by accident — is drawn from the geometry of a manoeuvre that was not being flown. The worry about energy over a crowd survives that; the proof of intent does not.

Then the tell, in the engineer's own follow-up: in a sane administration, he wrote, the pilot would be fired, and so would the secretary of defence. There it is, in one man — eight posts of real airmanship, and then the pilot stops being a man and becomes an argument. Neither half is insincere. Both are the same man's honest reading. There is no operation that separates them.

Which is why the hanging cannot be granted, whatever the flying was. To punish a man you need a finding of culpability, and nobody has released one. Error gets a debrief; recklessness or wilful breach may get a board. The navy has released no altitude, no bank angle, no telemetry. Intent was inferred from a phone video, which is an inference wearing a finding's uniform. The safety inquiry cannot make the punitive case: its findings are privileged by design, and a separate command investigation would have to build one independently. That separation is not a flaw in the system; it is the system.

Step back, and the quarrel rests on a mistake both sides share. All summer the administration had been clearing low passes by units with no business making them — Apaches over a musician's house, Guard helicopters down a Carolina beach — and over Pensacola it reached for the same refrain: carry on, patriots. The critics made the mirror error, filing a Blue Angels arrival alongside those stunts as one more piece of indiscipline to punish. But a gunship crew freelancing over a public beach and the flight demonstration squadron over its own home water, on the morning it opens its own show, are not the same event. One exceeded its remit; the other has that remit exactly, and flew it badly for a few seconds. That is a matter for the debrief. The demand to settle it within the day was a political reflex, not a safety one.

The evidence that it works

None of this is theoretical. In January 2021 a Blue Angel came 82 feet inside the mandatory 500-foot show line at El Centro, 15 knots over the limit, damaged three buildings and a fire truck and left twelve people reporting ringing ears, headaches or worse. The navy's own investigators called it a possible error to be debriefed and corrected, found no misconduct, and concluded that no punitive action was warranted — under the previous administration.9

But read the rest of that file. They removed a camera. They cut the speed limit. They mandated a no-manoeuvre call if the jet projects inside the line or within 200 feet of a person. They forgave the man and they rewrote the rule — and the same file records the ground safety observer, who thought a 50-foot excursion, at a training base with no crowd beneath it, not uncommon or concerning.

That is what a working system looks like: nobody was punished and something changed. By the air-show industry's count, no spectator has been killed by a performing aircraft at an American air show since 1951, when an aircraft went into a crowd at Flagler, Colorado, and killed nineteen people, thirteen of them children.10

Pensacola is owed the same. Whatever the exact height — the navy has released none — a fast jet banked low over a packed beach is outside the envelope; where flight over spectators is permitted at all it is kept five hundred feet up, and the boss called this one unsafe. A circling arrival is a dynamic thing, and a pilot will now and then misjudge one; the rules exist so that when he does, the aircraft is not over the crowd. The honest fixes are about margin, not virtue — fly the arrival with more room, keep the sand beneath it clear, or bring the low pass inside the rules with the separation the sneak pass already keeps. What a working system cannot do is what the podium did: call it no problem, and leave the deviation normal and unmanaged.

Where the line is. Height against distance from the crowd. The shaded corner — low and close at once — is the only place the rules forbid; everywhere else is inside the envelope. Drag the jet, or use the sliders. The sneak pass sits on the boundary it is flown to; the July 15th pass sits deep in the corner, over the crowd. El Centro 2021 is the one earlier breach the record gives geometry for — eighty-two feet inside the line, but over empty ground. The Lynchburg roll of 2011 and the Georgia Tech stadium flyover of 2009 are on the record too, yet no height or distance was ever released, so they cannot be drawn. That is the shape of the file: it names the breaches that were caught and measures almost none of them — as the navy's own safety manual says of the record it keeps, unreported hazards do not get into the safety database. Envelope from the FAA air-show provisions and the team's manual; El Centro from the 2021 preliminary inquiry; the quoted line from OPNAV M-3750.6, Naval Aviation Safety Program (2024).

The trade also removes people, when removing them is the answer. Donnie Cochran cancelled shows and resigned in 1996 over deficiencies in his own flying that nobody outside had noticed — once you start nibbling on the edges, he said, you have to start questioning. Dave Koss flew a roll too low at Lynchburg in 2011, stood the team down and stepped down five days later.11 That is not softness. It is a trade that knows the difference between a man who erred and a man who should not be there, and makes the call itself, without a podium.

Glad to be here

Every Blue Angels flight ends in a room where rank comes off and each pilot narrates his own errors aloud to the men who watched him make them. At the end of his account, whether the hop was good or bad, he says that he is glad to be here. A former team member wrote it down in 1998.12 It is not a slogan. It is what you say when you have just finished telling the room you nearly killed everybody, and the room lets you fly tomorrow.

Set the secretary’s sentence beside it. “No problem” sounds like the same easy confidence, and means the opposite: not I have told you what I did, but that nothing further need be said.

The pass was unsafe, and over a crowd. Bryan said so, and the man who flew it will have sat in that room and said what he got wrong, and the team will fly the show this weekend over the same beach, and the town will be there by seven in the morning, and none of us will ever know what was said.

Both camps wanted the verdict without the review that produces it. Each supplied its own instead — one punitive, one absolving, both certain, both about something else. In between, for thirty-eight seconds, a man in uniform said his pilot had been somewhere unsafe, that the team would look at it hard, and that they would learn from it. It was the only verdict on offer that the system could actually produce, and it was the one nobody was arguing about.