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 the public record could not support. 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.

Updated July 18th: The chronology of the debrief and safety review has been corrected, and unsupported measurements have been removed from the video and schematic.

Updated July 22nd: The ending now records that the Saturday show flew and that a state legislator has relayed the pilot's own reading of the pass.

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

Updated July 22nd

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 the pass had put a pilot over a crowd in an unsafe situation and called for a heavy review. The secretary said the flight debrief was complete and there was no problem. They did not disagree about punishment; Bryan proposed none. Nor does it matter which man spoke first. Bryan said there was something to learn; Cao said there was nothing wrong.

The squadron had said it was conducting 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 By dawn on July 18th, they had not. A debrief can spare a pilot while a review decides what must change. “No problem” tries to make that distinction disappear before the public knows what the review found.

“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.

A vivid record, not flight data

Visible
A low, banked pass above an occupied beach; furniture and sand displaced below it.
Officially established
Lower than the standard profile; over the crowd; unsafe.
Not measured here
Altitude, bank angle, lateral separation, airspeed or intent.
What the video shows — and what it cannot. A low, banked pass over an occupied beach; not its altitude, angle, speed or intent. Camera position, lens and editing make the clip a vivid record but a poor measuring instrument. The navy's account supplies the safety finding. Third-party compilation credited on-screen to @mercadomedia1; full provenance in the evidence brief.

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. The navy has published no measurement; Bryan supplied the finding that matters: the jet was lower than standard, over the crowd and unsafe. The rules do not reduce to one box. They vary with the manoeuvre, the flight phase and the clearance. But their organising idea is margin: approved overflight is at least five hundred feet above spectators; the team's fifty-foot sneak pass buys its height with lateral separation on the five-hundred-foot show line. The honest fixes are about margin, not virtue — fly the arrival with more room, keep the sand beneath it clear, or bring a low pass inside the clearance written for it. What a working system cannot do is what the podium did: call it no problem, and leave the deviation normal and unmanaged.

Two published reference conditions show how margin works. An approved Blue Angels overflight of spectators is at least five hundred feet above them. The team's sneak pass may be flown at fifty feet on the five-hundred-foot show line. For the July 15th pass, the navy has released neither coordinate: the event cannot honestly be plotted.

Known rules; unknown coordinates. These are two published reference conditions, not a complete flight clearance: manoeuvre, energy, bank, flight phase and ingress or egress can add further limits. Pensacola is deliberately not plotted. The navy has released no altitude, lateral separation, bank angle or airspeed for the pass. Sources: FAA Air Show Special Provisions, paras 20–21; 2026 Blue Angels Maneuvers Manual, Sneak Pass; see note 8.

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. By dawn on July 18th no public safety finding had appeared, the main show was still scheduled over the same beach and the town would again be there by seven. It was, and they were: the show flew that afternoon, without incident.13 And one account has since left the room, though not through the navy: a state legislator who spoke with the pilot wrote that he had miscalculated a turn, made no excuses and was shaken at falling short of his own standard.14 A relayed conversation is not a record, and the navy has still published nothing. But the only voice from inside the squadron describes neither “no problem” nor a crime: an error, honestly carried — the third option both camps’ verdicts excluded.

Both camps wanted certainty before the evidence could bear it. Each supplied its own verdict — 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 conclusion the public record supported, and the one nobody was arguing about.