What I diagnosed inside one engine program, the White House just diagnosed for the whole country

When I wrote The Great Sucking Sound in Engineering, the core finding across all four parts came down to one sentence: the system drove those outcomes. Not one bad hire. Not one bad quarter. A system that selected for speed, rewarded extraction, and treated deep knowledge as overhead. I wrote that from inside a specific lineage of an OEM engine programs, watching specialists leave faster than their knowledge could transfer, watching validation quietly shift from correlation — prediction checked against test data — to seniority, where the most confident person in the room became the de facto ledger.

I didn't write it as policy. I wrote it as an autopsy.

In July 2026, the White House Office of Science and Technology Policy published Science: A New Golden Age — a 123-page report to the President from Michael Kratsios, the nation's Chief Technology Officer. Reading it, I kept finding my own sentences with the serial numbers filed off. Not because anyone read my Substack. Because the failure mode I was describing at one company scales to an entire national research system, and enough people inside that system have apparently been living it too.

Four diagnoses, side by side

The system drove those outcomes. That was never really about any single engineer's choices. It was about incentives that made speed and extraction rational and depth irrational. The OSTP report names the same structural problem under a different label: "The Incumbency Tax" and "Misaligned Incentives," diagnosed in Chapter II as funding and career structures that reward novel claims and short-term output over durable, patient work. Their fix is telling — long-horizon grants explicitly modeled on the NIH Director's Pioneer Award, designed to reward the kind of depth that short grant cycles currently punish.

Validation by seniority replaced validation by correlation. I watched the empirical ledger — the record linking a prediction to what the test actually showed — quietly disappear from engineering organizations, replaced by whoever had been in the room longest. The OSTP report calls this the reproducibility crisis, and it isn't vague about the cost: a majority of researchers now acknowledge the crisis is real, and one study found irreproducible biomedical findings alone misdirect an estimated $28 billion a year. Their fix is the Restoring Gold Standard Science Executive Order, signed May 2025, mandating reproducibility, transparency, falsifiability — and, direct hit on my own thesis — explicit "acceptance of negative results" across all federally funded research.

Short tenure is the mechanism, not a side effect. People have to stay long enough to become the institutional record. When they don't, the knowledge doesn't transfer, it just leaves. The report's Chapter IV, "The Marriage of Science and Craft," makes almost the identical case at the level of an entire economy: technology lives "not just in papers and patents, but in the tacit knowledge passed from mentor to mentee," and decades of offshored manufacturing severed exactly that transfer. Their fix: practitioner-in-residence programs embedding machinists and technicians alongside PhD researchers, national fellowships for skilled craftspeople, and a real push to modernize apprenticeships in science and technology fields — not just the trades.

A confident number with nothing standing behind it. That line was written about a specific failure mode I kept running into — a result stated with total confidence, no verification underneath it, and no one positioned to check. Chapter V of the report warns that AI is about to make this failure mode worse at industrial scale, warning it will soon be "easier to generate plausible-sounding scientific results than to verify them." Their fix: build verification infrastructure with the same seriousness as generation infrastructure — AI-enabled replication systems, machine-auditable replication packages, and real incentives for researchers who replicate or disprove influential results, instead of the current system where confirming someone else's work carries no reward at all.

The part that closes the loop

Here's what ties this back to the other half of what I've been writing. Two of these fixes — Gold Standard Science's "acceptance of negative results," and a separate FY2028 budget directive requiring agencies to fund the curation of data that's otherwise routinely abandoned — are, functionally, the shelf-and-bank mechanism I've been describing for shelved technology programs. Same idea, applied to a different failure mode: instead of a negative result or a failed trial getting buried because nobody had an incentive to keep it, it gets documented, banked, and made searchable for whoever needs it next.

I wasn't wrong about what the system was doing to engineers. I just didn't expect Washington to write the same diagnosis, eighteen months later, backed by an executive order and an actual budget.

The sucking sound reached the White House. Now the question is whether the fixes reach the engine programs where it started.

Herbert Roberts, P.E. — 30+ years in aviation R&D across two companies. 8+ years analyzing accidents for attorneys under my P.E. license.

Some people read books to be entertained. Some go to movies. I get entertained by thinking out solutions. That is the whole hobby. It has been for fifty years, and it is why I stopped scrolling last week.

A note before I start. I post on LinkedIn, but I am first and always a reader there. Most of what I know about what engineers are actually doing right now, I learned from people who posted it before I asked. This piece came from one of them.

The number

A student opened a post by telling everyone his thrust vector controller ran 43 percent slower when it moved under load.

That is not a triumphant sentence. It is not a sentence anybody writes to look good. It is a measurement, offered flat, and it was the first thing in the post.

Braxton Herold is trying to land a model rocket on its own thrust. A recent static fire gave him three numbers he needed: how far the gimbal can move, how fast it moves, and how long it takes to start moving. Authority, slew rate, latency. He wanted them to tune his software-in-the-loop simulation. What he got instead was an explanation for why the previous week’s flight had failed.

Braxton Herold’s Thrust Controller. Images captured from LinkedIn

The chain

Read the next part as an accident report, because that is what it is.

Through a series of conversion and scaling errors, his TVC system was producing roughly 60 percent of its intended control authority. Take that alone and it is survivable. Reduced margin, not lost margin. The vehicle would have flown.

Then he removed the landing legs for that test.

Mass came down. Velocity went up. Aerodynamic instability rose with the velocity. Near the end of the burn, the aerodynamic moment finally exceeded the restoring moment the degraded TVC system could still produce, and the rocket began to tumble.

Nothing broke. No component failed. A configuration change that nobody re-analyzed moved the vehicle into a regime where the remaining margin was no longer sufficient — and the margin had already been quietly spent by errors upstream that were individually tolerable.

I have spent eight years writing that same paragraph for attorneys, about aircraft, with different nouns. It is the most common accident architecture there is: several small deficiencies, each defensible on its own, and one change of configuration that pushes the stack into a corner where the reserve is gone. The student named it himself. He wrote that the failure was not one catastrophic problem but the interaction of several small errors that only surfaced when the vehicle entered a regime the available control authority could not cover.

He is right, and most working engineers I know would not have written it that cleanly.

What came back

Here is the part that made me sit up.

Within about a day, the comment section had assembled a design review panel.

An aerospace and quality engineer asked what the vector was responding to — accelerometer, altitude, waypoint navigation — and then told him to stay with the small motors and scale up later. A mechanical engineer flagged the center of mass as looking tail-heavy and told him to get it as far toward the nose as possible. An intern at Woodward asked whether his software loop accounts for thrust-to-weight ratio changing during the burn, from both propellant mass loss and grain geometry. Another mechanical engineer told him which Estes booster variant to use and to put an eighth of an inch of five-minute epoxy over the motor to keep the burn from ending energetically. Someone else told him brushless servos exist.

Add up the experience in that thread and you are well past a century. None of it was billed. None of it required an introduction, a referral, a conference badge, or a job offer. It arrived because a nineteen-year-old published a problem with numbers attached.

And it kept arriving because of what he did next. He answered every single one of them, specifically, with data. He explained he plans per-batch static thrust curve characterizations to fit the descent motor curve. He explained he measured servo latency frame by frame off video, using a buzzer as the command timestamp, and called the method a little sketchy but adequate for the purpose — which is exactly the right judgment about measurement, made without a lab. And when the brushless servo comment came in, his answer was ”I didn’t know those were a thing.”

That sentence is the price of admission, and it is the one most engineers will not pay.

The rule

Publishing a finished result is a closed post. Humbly seeking help is the ask that opens the door.

Nobody can help with an accomplishment. There is nothing to grab. The only move available to a reader is applause, and applause is the crowd talking to you. Everybody wants to help with a stated, quantified problem — because now there is a handle, and the reader can join instead of watch.

Run the counterfactual. Same rocket, same photo, same day, and the caption reads successful static fire. He collects the likes and he learns nothing. The epoxy trick stays in a stranger’s head in another state. The TWR question never gets asked. The tail-heavy call never gets made, and it costs him the next flight instead of this one.

A win gets applause. An unfinished effort gets company.

Leave room for the improvements

There is a timing rule underneath the openness rule, and it is the one that keeps you out of the corner.

Feedback has a shelf life, and the clock is set by how many degrees of freedom you have left. Braxton got the CG correction, the servo advice, and the motor sealing technique while all three were still actionable. Post the identical failure analysis after the vehicle is built, flown, filmed, and finished, and every one of those comments becomes trivia. The comments do not change. Their value does, because the room to use them is gone.

The corner you paint yourself into is rarely built out of bad decisions. It is built out of reasonable ones that quietly consumed all the remaining space.

Which is the same thing his rocket did. The scaling errors were tolerable. Pulling the legs was reasonable for a static test. Neither one was the failure. Spending the margin before knowing what it would be needed for was the failure.

So: design margin and editorial openness are the same discipline pointed in different directions. Reserve room deliberately, and know the date it closes. He does — there is a static-margin module coming in a few weeks that will roughly double the vehicle’s length and move the parachute mass away from the center of gravity. He is collecting input against a known freeze point, not drifting.

Thirty years of asking

Do not be embarrassed to ask in order to learn. I asked, every working day, for more than thirty years.

It did not get easier. It got harder. A student asking questions is expected, and nothing is at stake. Asking after the title, after the license, after sixty-two patents, in a room where everyone assumes you already know — that is when the ask costs something, because it is also an admission. That is the version worth defending, and it is the one that quietly stops happening to most engineers right around the time they become senior enough to be embarrassed.

Braxton found in his teens the thing it took me a career to keep doing. I am not holding him up as an example for young engineers. I am holding him up as a correction for the rest of us.

The part I do not know

This piece would fail its own rule if I ended it closed, so here is my open problem, and I would like the help.

The mechanism works beautifully for a student. Nobody loses status by teaching a nineteen-year-old, and nobody suspects a motive. I do not know whether it survives seniority. When a principal engineer with grey hair publishes a real unsolved problem under his own name, does the same panel show up — or does the room read it as decline, and go quiet out of politeness?

I have a guess. I would rather have your evidence.

Tell me about a time you asked publicly, late in your career, and it worked. Or the time it did not. I am collecting the data before I decide whether to spend the margin.

Braxton Herold’s original post and the full comment thread are on LinkedIn. Go read the comments. That is where the engineering is.

Subscribe now

Leave a comment

Herbert Roberts, P.E. — 30+ years in aviation R&D across two companies. 8+ years analyzing accidents for attorneys under my P.E. license.

Why Congress Shouldn't Pick the Technology — and What the White House Just Funded Instead

I've watched Congress question people like Mark Zuckerberg and Elon Musk — grilling them on what they're building, how they're spending their money, where the technology is headed. And every time, the same thing is obvious within the first few questions: the people asking don't understand what they're asking. The questions are staffer-written, read off a page, and it shows the moment a follow-up strays off script.

That's not a knock on any one senator. It's structural evidence of something more useful: Congress is tuned to governance — international affairs, state relations, the rights and needs of constituents. It is not, and was never built to be, tuned to the daily pulse of technology. So when government tries to pick the technology of the year — decide by committee what deserves funding and what doesn't — it's asking the wrong experts to make a technical call.

For most of my career, that's exactly the trap researchers operated inside. Chase the government's priority list, reshape your own research to match whatever the administration decided was the trend of the year, and hope the money follows. Miss the window, and the work — and the money already spent on it — just disappears.

Here's the distinction that matters: the government can help lead into the future through funding and technology banking. It does not have to steer the path that brings out the innovations. Those are two different jobs, and confusing them is exactly how you end up with a senator reading a staffer's question about a technology he's never used.

The Shelf, Not the Scrap Heap

Here's the reframe I've been working through: not every idea that stalls has failed. Sometimes the technology isn't ready for the need. Sometimes the need isn't ready for the technology. Either way, shelving the work — instead of cancelling it outright — lets the two catch up to each other later.

The difference between a shelf and a scrap heap is documentation. If you record, at the moment something gets shelved, why it was shelved — which side of the gap failed, technology or market — the archive becomes searchable instead of buried. In a digital age, with AI able to continuously scan that archive against current conditions, what comes back off the shelf isn't the original idea. It's a 2.0 derivative — improved by whatever changed while it waited.

Think of it like a bank. The money doesn't vanish because you didn't spend it this quarter. It sits, and it earns interest. Withdraw it later, and you get back more than you put in.

Three Ways a Shelf Gets Built

I've watched this play out three different ways across a single materials lineage in aerospace, and each one teaches something different about why things sit.

Supply-chain desync — ceramic matrix composites. GE Research Center and GE Energy both knew the physics case for CMCs decades before the technology reached the aviation world: run turbines hotter, keep parts in service for twenty or thirty years instead of throwing away worn metal, push T4 higher and get more efficiency out of the whole engine. The idea wasn't missing. What was missing was fiber available at volume, and a manufacturing base sized to actually produce at the scale GE Energy needed. That's not a science problem. That's an industrial capacity problem, and no amount of research funding fixes it faster than the supply chain can physically build.

Domain-transfer desync — PMC fan blades. Polymer matrix composites had already been proven, for years, in marine and boating applications before they ever made it into a jet engine. The material science wasn't in question. What took so long was qualifying that same material for a completely different stress environment — bird strike testing, fatigue certification, everything that separates a boat hull from a rotating blade under load. The technology was ready. The pathway to this specific application wasn't.

Sequential capability unlock — 3D printing. This one's the most interesting because it isn't one idea waiting on one thing — it's a whole stack, each layer waiting on the one below it to mature. Stereolithography and early CAD-to-plastic printing proved you could go from a digital model to a physical part, but the parts were floppy, imprecise, structurally unconvincing. Fiber and powder-based plastic printing solved precision — now the process itself could be trusted. Powder metal printing — Pratt was a leader here with titanium — then asked whether that same trusted process could carry a real structural material, and the answer helped make SpaceX's Raptor engine possible. Now composite and microfiber printing is the current unlock: an entire pre-existing database of laminate designs, sitting ready, waiting only for the printer to catch up to the material. Nobody has to reinvent that science. It's already banked. It just needed the process to mature enough to carry it.

This Isn't a What-If — It's Already Funded

Here's the part I want to be precise about: none of this is hypothetical, and the infrastructure it depends on is already law and already funded. In November 2025, President Trump signed Executive Order 14363, launching the Genesis Mission — a whole-of-government effort directing the Department of Energy to build the American Science and Security Platform, connecting the nation's supercomputers, AI systems, and scientific datasets into a single discovery engine, with the explicit goal of doubling U.S. science productivity within a decade. By December 2025, DOE had already signed agreements with 24 organizations, including AI companies, chip makers, and cloud providers. A companion piece of that infrastructure, the American Science Cloud, exists specifically to curate and distribute data currently "hidden behind government bureaucracy."

And critically, the FY2028 R&D budget memo — an actual annex in the OSTP report, not aspiration — directs every federal agency to propose funding specifically to curate data that is otherwise routinely abandoned for lack of funding or recognition: experimental records, negative results, operational data from failed trials. That's the closest the government has come, in concrete funded form, to the bank-and-scan mechanism I'm describing.

To be precise about where the report's own language stops and my framework starts: the government's current mandate is built around data — failed trials, negative results, records that would otherwise be lost. It is not yet built around shelving whole technology programs — the way GE Research Center sat on CMC knowledge for decades waiting on a fiber supply chain, or the way PMC blades waited years for an aviation qualification pathway. That synchronization mechanism, applied one level up from data to entire programs, is my own extension of what the government has already funded and launched.

Good — Now Take It Further

To that first step: genuinely, good. As Musk has put it, the worst thing you can do is optimize a bad idea. What this report gets right is recognizing the opposite mistake is just as costly — killing a good idea because it wasn't ready on this year's schedule. The Federal Government is finally proposing to operate the way GE Research Center already did with CMCs: it didn't throw away decades of ceramic matrix knowledge just because the fiber supply chain wasn't there yet. It kept working the problem at the margins, kept the knowledge alive, and waited for the rest of the world to catch up. Eventually it did.

Thank goodness somebody with some forethought is finally at the steering wheel of technology.

But there's a next step that would multiply the value of the exact same infrastructure investment, without appropriating a single additional dollar for R&D itself. The report's own numbers make the case: American industry deploys roughly $700 billion annually in R&D, more than triple the combined spending of government and higher education. The Genesis Mission and the American Science Cloud, as funded today, only reach federal data. That means the shelf they're building covers a fraction of the nation's actual R&D pie — the smaller fraction.

The fix is to extend the same tagging discipline outward:

A standardized Readiness-Gap Tag — the same documentation the report wants agencies to apply to abandoned datasets, offered as a voluntary standard private industry could apply to its own shelved programs: what failed to sync, tech or market, and on what specific dimension.

A real incentive to make tagging worth a company's time — an R&D tax credit multiplier for documented, taggable shelved work, or an IP safe harbor that lets a company disclose that something was shelved and why, without disclosing the trade secret itself.

A federated private-sector mirror of the American Science Cloud — companies keep the actual work behind their own walls, but the readiness-gap metadata becomes searchable, so a national AI scan could flag that a company's shelved program and another company's new capability are a sync match, without either party exposing anything they haven't chosen to.

Build the tagging standard once, extend it across both federal and private shelves, and the same dollar already being spent on Genesis Mission's infrastructure now indexes a $900 billion pool instead of a $200 billion one. That's more power per dollar spent — not by spending more, but by finally being able to find what's already been paid for.

Let the people who understand governance handle governance. Let the people who understand technology handle technology. Government's job is to fund the bank and keep the shelf standing — not to steer which withdrawals get made or which path innovation has to take to get there. And let the shelf — federal and private alike — do what a good bank does: hold the value, quietly earning interest, until someone's ready to withdraw it and build something better than what they put in.

Herbert Roberts, P.E. — 30+ years in aviation R&D across two companies. 8+ years analyzing accidents for attorneys under my P.E. license.

The B-52 debate is arguing about the wrong noun

Herbert Roberts, P.E. | Inventor's Mind

Every few years, the same argument resurfaces about the B-52: build a new airplane to replace it, refurbish the refurbished one currently flying, or retire the mission and hand the role to the B-2. Three options, three camps, and a debate that's been running in one form or another for longer than most of the people arguing it have been alive.

I don't think any of the three is wrong, exactly. I think all three are answering the same narrow-end question, and the question itself is the problem.

Confession. My instinct, every time this debate comes back around, is to pick a side. New airframe versus refurbishment versus role transfer feels like exactly the kind of engineering trade study I was trained to run: compare the options on cost, schedule, capability, and risk, and land on the best one. That instinct isn't wrong. It's just answering a question that assumes its own premise before the trade study ever starts.

The false issue is "which airframe should carry this mission." That question feels productive because it has three concrete, comparable answers sitting right there, each with real cost and schedule data behind it. The true issue is "does this mission need to live on a single airframe type at all" — and that question doesn't have three answers. It has an entirely different shape, because it questions the assumption every one of the three options shares without examining it.

The forensic correction.

A bottleneck, by definition, is the narrow end of a funnel — the point where flow gets squeezed down to its tightest constraint. Every version of the B-52 debate treats the airframe as that narrow point: whichever plane wins the argument becomes the single vessel the mission has to fit inside for the next several decades. That's not a flaw in any individual argument for new-build, refurbishment, or role transfer. It's a shared premise none of the three arguments questions, because all three were built on top of it before the debate even started.

You cannot model the unknown future — which is precisely the problem with betting a multi-decade capability on one airframe's fate. Whatever mission profile justifies the B-52 today will not be the mission profile that matters in thirty years, and locking a capability to a single platform means every future adaptation has to happen inside that platform's constraints, whatever they turn out to be.

The technical teardown.

This is the FEB move, applied to a debate that's been running for decades without anyone stepping back far enough to ask the wide-end question. The narrow-end version of "which airframe" assumes the capability has to have a single home. The wide-end version asks whether the capability — persistent, long-range strike, in this case — needs an airframe home at all, or whether it can be architected to move across platforms as the future actually unfolds, rather than betting everything on correctly guessing what one airframe will still be relevant enough to do decades from now.

Stated as the general move: when a debate has settled into a fixed menu of options, check whether every option on the menu shares an assumption nobody's examining — and if it does, the real answer may not be on the menu at all. Build-new, refurbish, and transfer-to-B-2 all share the assumption that the mission requires a dedicated, persistent airframe. None of the three asks whether that assumption still holds in a future increasingly defined by distributed, networked, and attritable platforms working together rather than one exquisite airframe working alone.

I want to be careful not to overclaim here — this isn't a case where the "obvious" answer is provably wrong and the reframe is provably right. Nobody can model the unknown future, which is exactly the point: the honest position is that a single-airframe bet is a bet on being able to predict something that, by the terms of the debate itself, can't be predicted. A capability architecture that doesn't require betting correctly on one platform's continued relevance is a hedge against that uncertainty, not a guaranteed better outcome.

Forensic signature.

The tell that a debate has narrowed to the wrong question is when smart people keep having the same argument for decades without it ever actually resolving. That's not usually because the arguments are bad. It's usually because everyone arguing has quietly agreed on a framing that forecloses the answer that would actually settle it.

Aftermath, and a forward prediction.

I don't know which of the three options wins the next round of this debate, and I'm not sure it matters as much as the debate assumes it does. What I'd want to see, before any of the three, is a serious answer to the question none of them ask: can this capability be built to survive being wrong about which airframe carries it? That's a harder question than picking a plane. It's also the only one of the four that doesn't require successfully modeling a future nobody can actually see.

I'd love to hear where you've seen a long-running debate that never resolves because everyone arguing shares the same unexamined assumption. That question drives everything I write here.

Herbert Roberts, P.E. : Explainer and forteller of the Big Picture. : I write Inventor’s Mind Blog.

FEB (Formen Engpass Barriere)™ is a pending trademark of Inventor’s Mind Press, naming the practice of reframing a problem from the wide end of the funnel — reshaping the framing that produces a constraint, rather than working the constraint itself.

Where to go to get your facts questioned — or, the comment section is a free design review

I started life going to the encyclopedia. For a couple of decades after that, I went to Wikipedia. Now I just leave a comment on somebody’s post, and every fact I need comes to me.

I want to walk that arc slowly, because it runs backward from the way we usually tell it — and the backward version is the true one.

A few days ago a man posted a short video of himself making a prosthetic socket. No lab, no autoclave, no drama. He wrapped carbon fiber over a mandrel, pulled a plastic sleeve down over the whole thing, and milked the resin through by hand until the weave went wet and dark. Closed molding at about its most basic. Basic and clever as it gets.

Then the comments arrived, and the comments were the real show.

You could read each commenter’s home discipline by what they were anxious about. The audit-and-certification man asked, essentially, is this even real — where’s your outer-mold-line control, where’s your resin transfer system, you’ll end up with dry spots. The aerospace stress engineer worried about epoxy sensitization and bare skin. A metallurgist admitted, with genuine puzzlement, that he’d worn prosthetic legs for twenty-five years and had never once seen the thing get made. A chorus of good people said PPE — gloves, respirator, read the safety data sheet — and said it about eight separate times. One old hand recognized the resin family and warned that if it was the nasty stuff he remembered, it was carcinogenic as hell. He wasn’t wrong.

And then, quietly, two working prosthetists read the whole thing correctly in about four seconds: carbon over a mandrel that was probably printed from a scan of the patient’s leg, milked down under a bag, nice work. The people closest to the actual application had the least to correct.

That’s the tell, every time. The volume of correction a piece of work draws is not a measure of how flawed the work is. It’s a measure of how many places the work gave people to stand. Simple, visible, clean work hands everyone a foothold. Everyone can see it well enough to plant a flag that says I’m in this trade too. Saying “huh, that’s elegant” needs no credential. Saying “you should’ve run a resin transfer system” plants a flag. The medium over-samples the flag-planting. That’s not a verdict on anybody. That’s physics.

But I didn’t sit down to write about them. I sat down to write about the arc — because that comment section, the one that looked like a pile-on, was actually the most useful thing in the room.

Start at the beginning.

The encyclopedia had all the authority in the world and could not test my claim at all. Authority flowed one direction. I went to it, it spoke, I received, and the conversation was over before I arrived. If I had a specific question — not what is a composite but will this specific layup hold under this specific load — the encyclopedia had nothing to say to me. It was finished. It was a monument. You don’t argue with a monument.

Then came Wikipedia, and the thing was alive. Still me going to it — but now the fight was visible. Click the talk page and you could watch the seams: two people arguing over a sentence, a third citing a source, a fourth reverting the lot. For the first time the authority was contested in the open, and contested authority is worth more than the sealed kind, because you can see what it survived. But it still couldn’t cross-examine me. I could read the argument. I couldn’t enter it with my own claim and watch strangers come at it.

And now the third beat, which turns the whole thing inside out. I don’t go and fetch the fact anymore. I emit a claim and the facts come to me. I stopped being a seeker and became a lightning rod. I post the thing and wait four days, and a panel I could never have afforded to convene shows up unbidden and cross-examines my claim from five directions at once — and bills me nothing.

Look at what actually happened across those three steps. Each one got less authoritative and more useful. The encyclopedia had every ounce of authority and zero ability to test my particular fact. The comment section has no authority whatsoever and tests my particular fact harder than anything in the history of the species. The “worst” source is the best cross-examiner. Authority and usefulness came apart, and for the one job of getting my own claim stress-tested, usefulness is what I needed.

Because that’s what a comment section is, if you have the stomach to read it that way. If I genuinely wanted my facts questioned — deliberately, on purpose — where would I even go? I’d have to build a panel. Find a metallurgist, a certification auditor, an aerospace stress man, a couple of working clinicians. Get them in a room. Buy the coffee. Slow, expensive, mostly impossible. Or I post the socket video and wait until Thursday. The panel assembles itself. It arrives disguised as annoyance, which is exactly why most people throw it away instead of reading it.

I spent enough years signing my name to analyses to know that a claim isn’t worth much until somebody has tried to break it and failed. That’s not cynicism. That’s the whole job. A fact that has never been attacked is just an opinion that got lucky. Publishing one is voluntary cross-examination — you are handing your claim to strangers and inviting them to swing.

Here’s the honest limit, though, and it’s the part that keeps this from turning glib.

The crowd is a magnificent cross-examiner and a terrible judge. It will hand you challenges from five directions and adjudicate exactly none of them. It tells you where the weak points might be. It does not tell you which ones are real. That’s still your desk. The authority didn’t vanish across those three beats — it migrated. It moved out of the monument and into you. You became your own editor, and the price of the free panel is that you have to run it yourself.

Which means what you’re actually looking at is a free design review. Every engineer who’s sat in one knows the drill. A real review costs you a conference room, a dozen calendars, a week of prep, and somebody’s travel budget — and the whole expensive ritual exists to buy you one thing: eyes that will find what you can’t. Leave a comment on a technical thread and you get the same eyes for the price of a paragraph. The auditor checks your process, the stress man checks your materials, the clinician checks your application. That’s a review board. It just convened itself in your mentions instead of a booked room.

And every engineer already knows the other half: a review produces findings, not gospel. You don’t obey a review board — you disposition it. Some findings are action items you have to close out. Some are the same concern raised by three people who never heard each other. Some are a reviewer riding his own hobby-horse into a room where it doesn’t apply. You already sort review comments by whether they’re load-bearing. So the sorting isn’t a new skill I’m handing you. It’s the review-board instinct you’ve had for years, pointed at a comment thread.

So when the panel convenes, you sort before you feel. Read the comment as evidence of where the commenter lives before you decide whether it’s a verdict on your work. Roughly, they fall into five piles:

The load-bearing correction — someone caught a real error. You answer, you thank, you fix. The bare-hands-in-wet-resin note is this one. You do not let it roll; letting it roll would be dishonest, and saying so out loud is what keeps you credible.

The redundant-but-right — the same true note struck eight times. One gracious acknowledgment covers all eight. You don’t owe each of them a separate reply.

The genuinely curious — what’s the mandrel material? why not just infuse it? Those aren’t corrections at all. That’s the good stuff. Answer freely; that’s the conversation you were hoping for.

The out-of-domain correction — someone applying his shop’s rules to your context. Right in his world, not applicable in yours. A one-liner, or nothing. And a note to yourself: his misfire tells you which context you didn’t wall off clearly enough.

The reflexive flag-plant — the person demonstrating he’d have done it better. That comment tells you where he lives, not where your work failed. Let it roll, and don’t take the bait, because there’s no fact in it to catch.

The maker who drowns is the one who lets every comment land with equal weight. The one who lasts learns to watch the swarm like weather instead of taking it personally — and then reads it, because underneath the weather is a free panel of experts you could never have booked.

I started life going to the encyclopedia, and it never once questioned a single thing I believed. Now I put a claim into somebody’s comment thread and get more cross-examination before lunch than the encyclopedia offered me in thirty years. That’s not decline. That’s the cheapest design review I’ll ever sit through.

And here’s where I land, after all of it — after the noise, the eight PPE reminders, the flag-plants, the shop rules that don’t apply in my shop. My real answer is thank you. Because buried in the noise, every single time, is somebody who brings an angle I never thought of. There is a lot of noise. There is also a lot of information. You have to be willing to run the review to find it — but it’s in there, and it’s free, and it came looking for me.

So to everyone who ever corrected me in a comment section: thank you. Truly.

And wear your PPE and gloves.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 32 years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license.

Why "minimize scrap" is a metal-shop instinct that quietly kills composite parts

I spent the first half of my career telling technicians to hate scrap.

That wasn't wrong — for metal based parts. In an aluminum shop, scrap is just waste. Nest the parts tighter, save the material, save the money. That instinct is correct because aluminum is the same material no matter which way you cut it.

Composite doesn't work that way. And the instinct that made me a good aluminum engineer is exactly the instinct that quietly wrecks a composite part, if nobody explains that the rules changed.

The failure that started this

A composite shop COO posted about wing skins rated for 45,000 psi that tested at 28,000 psi — 38% below spec. The parts looked perfect. They passed surface quality inspection. No blisters or voids. Nothing was visibly wrong.

The design called for fiber running in four directions — 0, 45, 90, and -45 degrees — so the part could carry load from any direction. Which is why we use composite materials in the first place — we want to carry high loads with the fiber running in its strongest direction, the same way an oak tree does. What actually got built only had fiber running in two directions, 0 and 90 — which turned our oak tree into a piece of grass, strong only in one pull direction. An airplane wing doesn't just load up and down. With engines hung on it and landing gear mounted to it, a wing carries heavy twisting loads that go far beyond a bird flapping its wings. Holding the wing flat and steady into the airflow is what gives the aircraft the lift it needs to fly. Twisting is not acceptable if you want that lift. That twisting load is exactly what the 45-degree fiber is there to resist — and in this part, there was almost no fiber running that direction at all. Just resin.

Nobody caught it, because you can't catch it by looking. Carbon fiber at 0 degrees looks identical to carbon fiber at 45 degrees. The shop was laying it up by eye — skilled people, doing what had always worked, on a curved part where "always worked" quietly stopped being true.

Why the 45-degree ply is the hard one

Here's the part that story left out. The 45-degree ply isn't just hard to check. It's hard to build.

Cut fiber tape at 0 or 90 degrees and you're cutting straight with the material — easy, low waste. Cut it at 45 degrees and you're cutting across the roll on a diagonal. That makes more scrap, and on a curved part it turns into something closer to puzzle assembly. Because the material only comes in fixed widths, you often can't cut one continuous piece at 45 degrees across a large part. You end up joining shorter pieces edge-to-edge, right inside the ply that's carrying the most important load.

That joint isn't automatically a problem. It's a known, designed-for detail — the load hops across the gap through the layers above and below it. But it only works if three things are done right: the gap is kept tight, the joints in neighboring layers are staggered instead of stacked in one spot, and each joint is kept clear of other trouble spots on the part. Every one of those is a judgment call made by hand, on the shop floor, and every one is invisible once the part is built.

In our shop, pre-preg material comes with a protective film over the resin-infused fiber, and that film gave us a place to draw an arrow showing fiber direction — a built-in guide right on the material, in front of the technician's eyes the whole time they're laying it up. Wet layup doesn't have that. There's no film, no arrow, nothing printed on the material to reference. The technician is working with raw fiber and has to hold the direction in their head and keep an eye on it constantly, ply after ply, with nothing on the part itself to check against. Two layup methods, two very different margins for error, and the harder one is the one more likely to be handed to someone without a reason to slow down and think about why it matters.

Where this actually goes wrong

I've spent my career around advanced materials, and I've watched this same failure happen the same way more than once: a technician gets a layup schedule and a stack of pre-cut plies and is told to build the part. Nobody explains why. Nobody tells them that a slightly wasteful cut that keeps the fiber angle true is worth more than a tight, efficient cut that lets the angle drift. Nobody tells them a joint isn't a shortcut — it's a feature with its own tolerances.

The technician isn't the problem. A technician doing exactly what they were trained to value — minimize scrap — on a material where that value doesn't apply, is doing their job correctly. The failure sits above them, in a training system that carried a metal-shop rule into a composite shop and never flagged that it doesn't survive the crossing.

I used to walk the floor and just watch and listen to the people building my parts. If I picked up on a level of casualness that worried me, I wouldn't write it up — I'd tell a story instead. I'd ask them to picture two outcomes: a small trash can with a few trimmed scraps in it, next to a part that's going to fly for thirty years, versus a full dumpster holding an entire wing that has to be scrapped because the fiber angle drifted and nobody caught it in time. Small scraps in a small can is what careful, correct layup actually looks like. A dumpster full of scrapped wing is what "saving material" costs when it goes wrong. That story did more to change behavior on the floor than any memo ever did, because it gave people a picture to hold in their head at the moment they were making the next cut — not a rule to remember, but a scale they could feel.

The grain nobody names

There's an older version of this same mistake.

Sand an oak table against the grain and you feel it immediately — the finish tears. Every woodworker learns that early. Sand a curved metal car fender, and direction doesn't matter at all. Steel has no grain, so you're free to work it however the shape demands.

Composite sits in the middle of both lessons. It has a real grain, like wood — direction matters, and the material cares which way you go. And it usually has to wrap a curved shape, like the fender — a wing, a nacelle, a fuselage panel, where the surface demands the same freedom of movement steel allows. A technician needs the woodworker's respect for grain and the metalworker's comfort with curves, at the same time, on the same part. Most people only arrive with one of those instincts already built in.

What test panels actually teach — and don't

We build flat test panels constantly, to check that each batch of material meets spec. That's necessary, and it's genuinely a good place to learn how grain direction affects strength.

But flat panels teach people to think in stacked, square layers — check the angle against a straight edge, done. That's the right skill for a flat coupon. It runs out the moment the real part is a tapered wing skin or a curved nacelle instead.

Building a real 3D structure means picturing how a flat sheet of directional material stretches and shifts as it wraps a curved surface — and catching the spot where the angle on the drawing and the angle the material can actually hold have quietly come apart. That's a different skill than the one flat panels train, and almost nobody teaches it directly, because almost nobody treats it as a separate skill from "know the layup schedule."

Why the standard fix doesn't stick

When a part fails, the usual response is a written one: root cause, retrain to procedure, sign off. Words on a page, aimed at a skill that was never a words problem in the first place.

People don't learn to picture complex 3D shapes by being told to picture them better. They learn it by handling material on curved tooling, watching a flat sheet fight a curve, and being shown the exact spot where the drawing and the real part disagree. Flat panels can't teach that, because on a flat panel, the drawing and the part never disagree.

A better fix looks like what test panels already do well for material properties — a real, hands-on training ground — except built on curved tooling instead of flat plaques, so people can see the grain fight the shape before they do it for real on a part worth six figures.

The finding

The shop's fix was a fiber-angle check with a digital protractor every fourth ply — 12 extra minutes per part. Against parts testing at 62% of rated strength, that's cheap insurance.

But a checkpoint only catches the mistake. It doesn't give the technician the eye to catch it themselves. That takes training upstream of the checkpoint: teaching why "minimize scrap" flips from good advice to bad advice the moment you cross from metal to composite, teaching grain the way a woodworker learns it, and teaching 3D visualization on real curved shapes instead of flat panels.

The part looked fine. The part was not fine. The gap between those two sentences is exactly as wide as the training gap that let a metal-shop instinct walk into a composite shop unquestioned.

We don't get to carry instincts across material systems for free. Every one has to earn its way back in, checked against the material in front of us — or it becomes the next invisible 45-degree ply: stronger than spec where nobody's testing, and empty where it matters.

The program ended. The idea didn't.

Subscribe now

Leave a comment

Herbert Roberts, P.E. — 30+ years in aviation R&D across two companies. 8+ years analyzing accidents for attorneys under my P.E. license.

THE BIG WHY — Follow the S-Curve series

I once sat in a review where a twenty-nine-year-old with eighteen months on the program outscored me on every metric the room cared about. Faster turnaround. Cleaner slides. A confident answer for every question, including the ones he didn’t actually know the answer to yet. I had thirty-two years of aviation R&D across two companies sitting behind my eyes, and none of it showed up on the scorecard that day.

That’s the moment this article is really about. Not Formula One. Not Cadillac. Us — the engineers who are good at things that don’t compress into a quarterly metric.

The Confession

Here’s the correction I have to make on myself before I make it on anyone else: for most of my career, I believed the scoreboard was the truth. If the standings said I was losing, I assumed I was losing. It took watching a Formula One team do something deliberately strange to see the flaw in that belief.

Cadillac entered the 2026 F1 season and has spent it in last place. Slow lap times, an empty points column, the predictable pile-on across social media. The easy read is failure. The forensic read — the one that actually holds up when you pull the telemetry apart — is a team that appears to have budgeted for exactly this outcome, on purpose, as the first stage of a longer plan.

The GM engine that will actually make Cadillac competitive doesn’t arrive until 2029. That date is fixed. It is not negotiable, not with effort, not with money, not with a better driver lineup. Which means the real engineering decision Cadillac faced wasn’t “how do we go faster this year” — that question was unsolvable by design. The real question was: what do we do with three years we’re forced to wait?

That reframe is the whole article. Everything else is teardown.

The Technical Teardown

TRIZ — the systematic innovation discipline I’ve relied on for twenty years — has a concept called the S-curve: every technical system moves through infancy, rapid growth, maturity, and decline, and the shape of that curve is often set by a limiting sub-system long before the rest of the system catches up. You don’t get to skip infancy by wanting to. You get to choose what you do during infancy.

Cadillac’s infancy is 2026 through 2028. The limiting sub-system is the engine — literally not yet built. Everything else on the car, the team, and the organization is free to develop on its own curve, independent of that constraint. That’s the engineering insight worth stealing: when your primary system is locked by someone else’s timeline, you don’t wait — you develop every sub-system that isn’t locked.

Look at what that actually means in practice, because this is where it stops being a metaphor and starts being a checklist:

(a) Data accumulation as a deliberate asset, not a byproduct. Every session in 2026, 2027, and 2028 generates telemetry, tire behavior, strategy calls, pit stop timing — a dataset most new teams don’t get until they’re already competitive, because most new teams arrive competitive or don’t survive long enough to matter. Cadillac gets three full seasons of “how Formula One actually behaves” before they’re under pressure to convert it into points.

(b) Personnel choices that signal the real plan. Bottas and Perez are not development drivers chasing their first contract. They are experienced heads brought in specifically to give precise, structured feedback under duress — the kind of feedback a nineteen-year-old prospect can’t yet articulate, because he hasn’t crashed enough times to know what he’s feeling. That hiring pattern is a tell. You don’t recruit veteran feedback-givers if the plan is only “survive.”

(c) Institutional knowledge as the actual product. Debrief notes, procedures, the accumulated judgment of “we tried that, it didn’t work, here’s why” — none of it shows up in the standings. All of it compounds. By 2029, when the competitive engine finally lands, it drops into an organization that already knows how to be a Formula One team. That is a categorically different starting position than a brand-new outfit trying to learn the sport and race a new engine in the same season.

(d) The willingness to be misjudged. This is the part that costs the most and pays the least visibly. Every front-running team, every commentator, every social media pile-on is scoring Cadillac against the wrong clock. Cadillac appears to be letting them. That’s not humility — it’s discipline. Correcting the record costs attention and energy that’s better spent on the actual work.

Now hold that up against a mid-career or late-career engineer, because the pattern doesn’t change — only the units do.

Mid-career, the visible clock is promotion cycles, headcount, title. If you’re not winning on that clock — passed over, reorg’d, sitting on a team nobody’s watching — the Cadillac move is to ask what your engine-arrives-in-2029 equivalent is. Usually it’s judgment that doesn’t show up on a scorecard: which failure modes actually kill a program versus which ones just look scary, which people to trust when the room is under pressure, how the organization really makes decisions versus what the org chart claims. That’s the Bottas-and-Perez move — become the person who gives precise feedback under duress, not the person chasing the fastest visible win this quarter.

But here’s the honest test, and I mean this as a correction I make on myself as much as anyone: are you actually accumulating transferable judgment, or are you telling yourself a “long game” story to excuse being stuck? Write down, concretely, what you know now that you didn’t know two years ago that someone would pay for. If you can’t fill that in, you’re not building the engine. You’re just losing quietly, and calling it strategy doesn’t make it one.

Late-career, the clock inverts entirely. You’re not waiting for your engine to arrive — you already have three decades of telemetry sitting in your head. The Cadillac question becomes: what happens to that dataset when you leave the building? This is not a retirement question. It’s an engineering question, and it has the same answer it always has: capture the procedure, not the nostalgia. Recorded expert interviews tied to specific repair procedures. A published methodology. A curriculum that lets a two-year engineer perform what took you twenty years to earn. That’s structurally identical to what Cadillac is doing right now — banking three seasons of data before the engine shows up. You’re banking three decades of data before you walk out the door.

The Forensic Signature

The tell that separates a real S-curve strategy from a convenient excuse is always the same: falsifiability. A team — or an engineer — playing the long game leaves evidence now, not just a story later. Cadillac’s evidence is the driver lineup and, we’ll find out, the facility investment and hiring pattern over these three years. An engineer’s evidence is the notebook, the written failure analysis, the documented judgment that didn’t exist two years ago.

If that evidence isn’t there, the “we’re building for the long term” story is just the standard excuse every backmarker gives. The engineering bet and the narrative bet are the same bet. That’s the part people skip because it’s uncomfortable, and it’s exactly the part worth sitting with.

The Aftermath — and the Forward Prediction

The 2026 standings will show Cadillac at the bottom. Formula One has a long memory, though — it remembers the teams that absorbed early humiliation and used it as information, the ones playing a game the rest of the paddock wasn’t watching. Maybe Cadillac was never racing Ferrari in 2026. Maybe they were racing the calendar. If the foundation holds and the engine arrives on schedule, 2026 won’t be remembered as the year Cadillac finished last. It’ll be remembered as the year they started.

The TRIZ prediction, stated plainly: systems that are locked by a sub-system on someone else’s timeline don’t get faster by protesting the lock. They get faster by developing every other sub-system while they wait — and the organizations, and the engineers, that understand this arrive at the inflection point already built for it, while everyone who spent the waiting years defending their position on last year’s scoreboard arrives with nothing but the scoreboard.

We are, most of us, running some version of Cadillac’s 2026 season right now — in a role, in a career stage, in a body of knowledge nobody’s asked us to hand over yet. The standings will say what they say. The question worth asking, the one nobody thought to ask about Cadillac either, is what you’re quietly building while everyone’s watching the wrong number.

Thank you for reading this one. If it named something you’re already doing without a word for it, that’s the point of the series.

— Herbert Roberts, P.E.

A Systematic Innovation homework assignment, decades early

Herbert Roberts, P.E. | Inventor's Mind

When I was learning systematic innovation, one of my homework assignments was to design a car that would run on vegetable scraps.

I thought about composting — how a pile of decomposing waste gives off gas as it breaks down — and started sketching from there. My concept used a GM Fiero as the base, because it was light and the engine bay sat in the rear, out of the way of everything else. Instead of the Fiero's gas engine, I put in a small gas turbine, running on the gas captured from composting waste, spinning fast enough to turn a generator. The generator made electricity. The electricity drove a motor at each wheel, independently, with energy recovery built into the same motors on braking and deceleration.

No mechanical connection between the engine and the road at all. The turbine's only job was making electricity. The wheels' only job was using it.

Confession. I didn't design that car because I had some early insight into where the automotive industry was headed thirty-some years later. I designed it because the assignment forced a constraint — vegetable-scrap fuel — that made the obvious answer (a normal engine, a normal driveshaft) impossible, and the impossibility is what pushed the design somewhere useful. That's worth admitting plainly, because it means the wide-end move I stumbled into wasn't foresight. It was a homework assignment doing exactly what a good constraint is supposed to do: making the narrow-end answer unavailable so you're forced to look upstream of it.

The false issue, if you'd handed me that assignment and asked me to solve it the fast way, would have been "how do I get a normal engine to run on compost gas." That's a real engineering problem, and a hard one — compost gas is low-energy-density, inconsistent, nothing like refined fuel. The true issue, once the fuel constraint forced the question, was "does the engine actually need to be connected to the wheels at all, or can it just make electricity and let something else move the car." Once I stopped trying to make an unreliable fuel work in a mechanical drivetrain and started treating the engine as nothing but a generator, the fuel-quality problem got a lot smaller. The turbine didn't need to run smoothly enough to feel good through a driveshaft. It just needed to spin a generator well enough to keep a battery topped up.

The forensic correction.

Electric vehicle sales have slowed hard enough to draw a straight line through automaker balance sheets: Ford took a $19.5 billion charge on its EV plans, Stellantis booked $27 billion, GM absorbed $7.6 billion, and Honda cut its EV investment by $20 billion — all inside about a year. The narrow-end response to that kind of pressure is obvious, and on the surface reasonable: the market rejected the new architecture, so retreat to the old one. Go back to gas or diesel driving the wheels directly, the way it worked for a century before anyone tried anything else.

That's the trap, and it's the same trap the "how do I make compost gas run a normal engine" framing would have been, if I'd taken the easy way out on that homework assignment. It treats "EV" and "engine-to-wheels" as the only two shapes the problem can take, when the part of the EV architecture that actually struggled wasn't the drivetrain. It was the energy source. Range anxiety, charging time, and cold-weather battery performance are all problems with storing electricity, not with using electric motors to drive wheels. Electric motors are simpler, more efficient at converting energy into motion, and better at instant torque than a mechanical driveshaft has ever been. None of that stopped being true when battery-only sales cooled.

The technical teardown.

The wide-end answer, and the one the industry is actually converging on now, is close enough to my Fiero sketch that it's a little unsettling: keep the electric drive to the wheels, and reframe the energy source instead. An engine — gas, diesel, or otherwise — runs as a generator, feeding electric or hydraulic motors that do the actual work of turning the wheels, with no mechanical driveshaft connecting the engine to the road at all. Horse Powertrain's X-Range platform is built explicitly to let automakers convert a battery-EV platform into exactly this kind of extended-range architecture with minimal retooling. Toyota's hybrid lineup, already profitable and already immune to range anxiety, is the market proving the same point from the other direction, having never fully left the electric-drive-plus-engine-as-support architecture in the first place.

Here's the analytical move stated plainly: when a system fails, don't assume the whole system was wrong — separate the part that actually failed from the part that was just riding along with it, and only rebuild the part that failed. The EV architecture has two separable pieces: an energy-storage system (the battery) and a drive system (electric motors at the wheels). The battery struggled. The motors didn't. A narrow-end response throws out both and returns to what worked before either existed. A wide-end response keeps the motors — the part that was never the problem — and reopens the framing on the energy source alone.

Neither the extended-range platform nor the traditional hybrid is "going back" to the pre-EV architecture, and I want to be precise about that rather than overclaim it as a straight win for electric drive. There are real costs to this approach that a pure battery-EV, if the battery problem gets solved, doesn't carry: two propulsion systems instead of one, an engine's worth of maintenance that a pure EV skips entirely, and a fuel-burning component that a fully-charged pure EV doesn't need at all. The wide-end reframe isn't free. It's a deliberate trade — accepting the complexity and maintenance burden of keeping an engine on board, in exchange for solving the range and charging problem immediately rather than waiting on battery technology to catch up. That's a real trade-off, not a hidden win, and it's worth stating that plainly rather than pretending the reframe has no cost.

The same logic shows up in heavy equipment, where hydraulic-electric hybrid drivetrains let an engine run at a constant, efficient load while hydraulic or electric motors handle the variable, start-stop demands of the actual work — same reframe, different industry, and one more data point that the pattern isn't specific to passenger cars.

Forensic signature.

The tell that an industry is solving at the narrow end is a wave of automakers announcing they're "pausing EV plans" and quietly restarting pure gas-engine development from where it left off — treating the battery's problems as proof the whole electric-drive concept failed. The signature of the wide-end move is what's actually happening instead: billions in EV investment being redirected, not abandoned, toward architectures that keep the electric motors and change what feeds them.

Aftermath, and a forward prediction.

I didn't build that Fiero. It was a homework assignment, graded, filed, and mostly forgotten until an industry I'd been watching for other reasons started arriving at a very similar answer for very similar reasons — a fuel source that couldn't do the job on its own, forcing the question of whether the engine needed to be connected to the wheels at all. The lesson I'd draw from that isn't "I predicted the future." It's that a well-built constraint, even an artificial one handed to a student for a grade, can force the same wide-end reframe that a multi-billion-dollar market correction eventually forces on an entire industry. The constraint doesn't need to be real to do useful work. It just needs to make the narrow-end answer unavailable.

This closes out the four cases I set out to walk through — a legacy engine frame, a Cold War spaceplane, a falling rocket booster, and a compost-gas homework assignment that turned out to be closer to the future than I knew at the time. What ties them together isn't the industry or the decade. It's the same question, asked in four different rooms: when you hit a wall, is the wall the problem, or is it where an earlier decision, made by someone who's since moved on, finally became visible?

I'd love to hear where you've seen this pattern in your own work — the moment a system failed and the fix wasn't rebuilding what broke, but noticing that only part of it ever needed to change. That question drives everything I write here.

Leave a comment

Subscribe now

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development.

FEB (Formen Engpass Barriere)™ is a pending trademark of Inventor’s Mind Press, naming the practice of reframing a problem from the wide end of the funnel — reshaping the framing that produces a constraint, rather than working the constraint itself.

The NTSB said it plainly: the ice-protection system functioned as designed.

That sentence is true. It is also the most misleading true sentence in the entire report.

What actually happened was simpler, and more damning:

• On February 6, 2025, Bering Air Flight 445, a Cessna 208B Caravan on a scheduled Part 135 commuter run to Nome, Alaska, encountered icing more severe than forecast.

• The aircraft’s TKS ice-protection system engaged and worked exactly as it was built to work — it prevented dangerous ice buildup on the protected surfaces.

• Managing that system, on top of an already-degraded weather picture, added workload.

• The added workload eroded situational awareness of airspeed.

• The aircraft was also operating more than 1,000 pounds over its maximum gross weight for known icing conditions — one of many flights in a documented pattern of routine overweight operations at the airline.

• The overweight condition left less margin to recover once the stall began.

• Airspeed decayed to 89 knots. The pilot’s nose-up input deepened the stall instead of breaking it.

• All ten people aboard were killed.

NTSB Chair Jennifer Homendy’s own words: the crash was not one failure. It was a series of preventable breakdowns that eroded critical safety margins, one on top of another, until there was no margin left.

The System Language vs. The Operational Reality

Every phrase in the left column is accurate. Every one of them is also doing the same job: describing a component in isolation, when the actual failure lived in the interaction between components that were each, individually, working roughly as intended.

The Architecture Problem

A functioning ice-protection system is not the same thing as a safe flight. It is one input into a workload budget the pilot is managing in real time, alongside airspeed, altitude, a closed and de-icing runway, a rebuilt approach, and — unknown to him in the moment — thin margin from an aircraft already over its safe operating weight.

None of those inputs was hidden from the system. All of them were hidden from each other. The ice-protection system didn’t know about the weight. The weight didn’t know about the workload. The dispatcher’s risk assessment didn’t catch the pattern of overweight flights because nothing in the operational control process was built to catch it. Each piece performed its function. Nothing was watching the sum.

This is the same architecture problem that shows up in any organization running near its design margins under schedule or operational pressure: individually defensible decisions, none of them cross-checked against the others, compounding into a single unrecoverable moment.

The Operating System Mismatch

A single-pilot Part 135 operation assumes the operator’s dispatch and risk-management procedures are doing real work — catching the overweight flight before it leaves the ground, flagging the operational complexity that comes with rapid growth before a regulator has to notice it independently. On Flight 445, that assumption held on paper and failed in practice, seven times out of thirty-five reviewed flight legs.

The Cascading Cost

Ten people did not survive a flight where every individual safety system did roughly what it was built to do.

The NTSB’s response wasn’t a fix to the ice-protection system — it worked. It was a set of recommendations aimed at the seams between systems: mandatory upset-prevention training for single-pilot Part 135 operators, explicit surveillance triggers tied to an operator’s growth rate, and broader load-manifest requirements across the industry. The cost of this failure didn’t stay with one airline or one aircraft. It rewrote the oversight framework for how fast-growing regional carriers get watched.

Clarity as the Missing Control Loop

Complex operations don’t fail because every component is broken. They fail when each component is individually sound and nothing in the system is responsible for watching how they compound.

A regulator measuring individual compliance checkpoints will miss an airline that is compliant at each checkpoint and dangerous in aggregate. A pilot managing individually correct instrument readings can still lose the picture that matters most when workload rises faster than attention can track it. The control loop that was missing here wasn’t a piece of hardware. It was the function that should have been asking: what happens when all of these individually acceptable conditions occur at once?

The Most Expensive Metaphor

Ten lives is the cost of an industry-wide pattern most organizations run every day at a smaller, quieter scale: individually defensible decisions, made by people who are each doing their job correctly, that were never checked against each other before they compounded.

If your organization can point to every component and say “that worked as designed” after something goes wrong, you already know which version of this story you’re building toward.

The margins don’t announce themselves as they erode. They just get thinner, quietly, until there aren’t any left.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license

This piece draws on the National Transportation Safety Board’s final report on the February 6, 2025 accident involving Bering Air Flight 445 (NTSB report AIR-26-05) and public statements from NTSB Chair Jennifer Homendy. The finding examined here is systemic — the interaction of maintenance, dispatch, training, and regulatory oversight — not the judgment of the pilot in the final moments of the flight, who like the nine passengers aboard, did not survive.

The honest economics of the YouTube salvage flip

I once drove a TR-6 into a pole in a parking lot. Someone had painted the pole flat black — not "hard to see," invisible — and I found out later I wasn't the first person it caught. A cracked headlight, a dented fender, and an insurance claim that was entirely mine to carry, even though I was arguably the least responsible person involved. I never found out who painted the pole. There's no witness, no confession, nothing. Just a black pole and a bad night.

Nobody's ever going to pay six figures for that fender. And that's the honest starting point for this article, because that's what almost all car damage actually is: a repair bill, not a story. If you want to see that principle running at industrial scale, watch a YouTube salvage flip channel for twenty minutes.

The business model

The premise is simple and, it turns out, extremely repeatable: buy a wrecked car at salvage auction — Copart, IAAI, insurance total-loss lots — document the entire repair process on camera, sell the finished car, and monetize through ad revenue, sponsorships, and the sale itself. Channels built around this format produce two videos a week showing the actual collision-repair work, and at the end of every project they run the numbers on camera: purchase price, parts, labor hours, sale price, profit.

Copart listing of 2024 Porsche 911 Carrera Screen shot of https://www.copart.com/lot/64137226/salvage-2024-porsche-911-carrera-s-fl-orlando-north

It's not romantic. It's a P&L statement with a welder in it. And it works precisely because it's operating in the normal case — a wrecked car with no attached story is worth exactly what it costs to fix it, plus whatever margin the market allows for a clean rebuild. Every project these channels complete is, without anyone framing it this way, a repeated proof that repair beats as-is for ordinary damage. That's not a controversial claim. It's just usually true.

Where it gets interesting

The risk in this business model is quiet and structural, and it's worth naming: these flippers are implicitly betting that every car they buy is an ordinary wreck. Nothing in a Copart listing tells you otherwise — you get damage type, mileage, a VIN, some photos. You don't get "this was owned by someone notable" or "this was involved in a documented event." That information, if it exists at all, lives outside the auction listing entirely, in registries, marque historian circles, or old paperwork nobody thought to check.

Most of the time that doesn't matter, because most wrecked cars really are just wrecked cars. But every so often a flipper could be sitting on something else without knowing it — a chassis with real competition history, a car tied to a name that would matter to the right buyer — and the entire content format pushes toward cutting, welding, and repainting it back to showroom condition as fast as possible. That's the one scenario where the business model would be actively destroying the very thing that made the car worth more than the sum of its repair costs. Nobody's going broke over this. It's just the one blind spot built into an otherwise sound, honestly-run business.

The Model T problem, and the Nash exception

Not every old car behaves the same way once it's fixed, and it's worth knowing which kind you're looking at before you start swinging a wrench.

A driver-quality car from the 1950s sits in the easy case: the roads, fuel, and driving norms it was built for still exist, more or less unchanged. Repair restores real usability, and usability is worth something concrete. The math works the way you'd expect.

A Model T is a different animal entirely, and it's not really about age — it's about whether the world the car was built for still exists. Top speed in the low 40s, mechanical brakes, a transmission nobody alive learned to drive on, built for a road network and traffic environment that no longer exists anywhere.

1926 Ford Model T Roadster Pickup Screen shot of https://www.hemmings.com/auction/1926-ford-model-t-tyrone-ga-213545

You can restore it to full mechanical function and it still won't be useful the way a car is useful today. Repair there is closer to museum conservation than to fixing a tool — you're maintaining an artifact, not restoring a use.

A running Nash Metropolitan is the quiet exception that makes the whole comparison useful. It was always small, slow, and a little absurd, even brand new in 1954 — which means the gap between "how it drove then" and "how it drives now" never opened up the way it did for faster, more road-dependent cars. It didn't lose ground to modern traffic because it was never trying to keep pace with modern traffic in the first place.

1961 Nash Metropolitan Screen shot of https://www.hemmings.com/classifieds/listing/1961-nash-metropolitan-denver-co-2961237

Repair on a Metropolitan buys back real, usable function, close to dollar for dollar, plus a rarity premium most buyers are happy to pay on top.

Three cars, three different answers to "is repair worth it," and none of it depends on how old the car is. It depends on whether the operating context survived alongside the metal.

The honest close

Somebody, somewhere, will eventually buy a wrecked exotic with a real story attached and repair it anyway, without knowing what they had. That's a genuine risk in an otherwise sound business, and it's worth a line of caution for anyone buying salvage sight-unseen.

But that's not going to be most cars, and it was never going to be my TR-6. No famous driver, no documented event, no witness to a pole nobody can identify.

1976 Triumph TR-6 Screen shot of https://classics.autotrader.com/classic-cars/1972/triumph/tr6/102654620 - (Not mine, but similar)

Just a fender, a claim number, and a repair estimate — the ordinary case, playing out the ordinary way, the way it does for almost every car that's ever been wrecked. Fix it. That's not a failure of the story. That was always the right answer.

Subscribe now

Leave a comment

Herbert Roberts, P.E. — 30+ years in aviation R&D across two companies. 8+ years analyzing accidents for attorneys under my P.E. license.

Follow the S-Curve

Two pieces ago, I argued that innovations arrive on emotion and only survive on fixed-cost reduction. Last piece, I broke down why fixed cost doesn't fix itself — a bottleneck is usually 90% process conflict and 10% human problem-solving, and the two delays compound instead of canceling out.

Here's where that leaves AI, specifically.

AI does not fix your problems. Without a focus on fixed-cost reduction, AI makes your fixed-cost problem happen quicker.

Speed Doesn't Discriminate

AI is, at its core, a speed and scale multiplier. It doesn't know the difference between a well-designed process and a broken one. Point it at a genuine fixed-cost reduction — a real bottleneck, correctly diagnosed, with the human side already resolved — and you get real gains, faster than you'd have gotten them any other way.

Point it at a process that's still fighting itself, or a decision that a person has been quietly avoiding for two years, and AI doesn't resolve either one. It just runs the broken process faster, at more volume, with more confidence, in front of more people. The bottleneck was always going to cost you. AI just moves up the invoice date.

This is the part most of the current AI discourse skips. The framing is almost always: deploy this, and the friction goes away. The more honest framing is: deploy this, and whatever friction you didn't already resolve gets exposed faster and harder than it would have on its own.

The Lesson Was Always Going to Arrive. Now It Arrives Sooner.

Here's the part that actually makes this useful instead of just cautionary.

In a slower system, an unresolved bottleneck can hide for a long time. The process conflict grinds along, the human issue stays unspoken, and the cost accumulates quietly enough that nobody's forced to act. Organizations can run on this kind of low-grade dysfunction for years.

AI collapses that timeline. Because it executes faster and touches more of the process at once, the failure that used to take a fiscal year to become undeniable now takes a quarter. Sometimes a sprint. The lesson that the organization was eventually going to have to learn — that this process conflicts with that one, that this person has been the actual constraint the whole time — gets forced into the open on a much shorter clock.

That's not a flaw in the technology. That's the technology doing exactly what speed does: it takes lessons that used to arrive the hard way, over years, and makes them arrive the hard way, over weeks.

And lessons learned the hard way flow up. They don't stay contained at the level where the failure happened. A process conflict that used to be absorbable at the team level, quietly, over enough time that nobody upstream noticed, now surfaces fast enough and visibly enough that it has to be escalated. Someone above the team has to see it, name it, and decide whether to fix the process or keep tolerating the delay. AI doesn't make that decision easier. It just makes it impossible to keep postponing quietly.

The Actual Choice in Front of You

This is why "adopt AI" was never the real strategic question. The real question is the one from the last piece: have you already done the fixed-cost work — resolved the process conflict, forced the human decision that's been sitting there — or are you about to find out, faster than you expected, that you hadn't?

Organizations that clear both hurdles before they scale AI into a process get the compounding gain the tools were promised to deliver. Organizations that don't get the same lesson everyone eventually gets — they just get it on a shorter clock, in front of more people, with less time to absorb it quietly.

The S-curve was never going to let anyone skip that step. AI just changed how fast you find out you didn't.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license.

What I saw the twentieth time I watched the video, that I missed the first nineteen

Herbert Roberts, P.E. | Inventor's Mind

I watched the video twenty times. A rocket booster, roughly two hundred feet tall, falling out of the sky under its own control, and a net on a ship reaching up to meet it. Simple. Adaptive to small errors in alignment in a way that felt almost unfair compared to what I knew the alternative required. Better than SpaceX, I thought, somewhere around the fifth or sixth replay.

By the twentieth, I'd talked myself out of "better" and into something more useful: different, on purpose, because the two teams that built these systems had made opposite bets about what a catcher was allowed to assume about itself.

Confession. My first reaction to the net was admiration for the mechanism — the simplicity of it, the way it seemed to forgive exactly the kind of small alignment error that would be unforgiving in a rigid tower. That's the right reaction to have, but it's also the narrow-end reaction: evaluating the catch as a piece of hardware, graded against the other piece of hardware that already existed. It took a few more replays to notice that the interesting question wasn't which mechanism performs better. It was why two teams, solving what looks like the same problem, arrived at mechanisms that don't resemble each other at all.

The false issue is "which is the better rocket-catching system, tower or net." That question assumes both teams were optimizing the same design once they'd both accepted the same premise. The true issue is "what premise did each team accept before they ever drew a mechanism" — and once you go looking for that premise, the two systems stop looking like competitors solving one problem and start looking like two different answers to two different framings of it.

The forensic correction.

Catching a returning rocket booster is, functionally, catching a falling building. SpaceX's Super Heavy booster stands roughly two hundred and thirty feet tall, and the company's solution — the tower-mounted "chopstick" arms at Starbase that grab the descending booster by its grid fins — is a genuine engineering achievement, refined over years of iteration to the point of routine, repeatable catches. It's also, once it existed and worked, an easy trap to fall into for anyone building the next version of the same idea: assume that catching a rocket means building a taller, stronger tower with better arms, and spend your engineering effort optimizing inside that architecture.

China's state-owned CASC didn't do that. When its Long March 10B booster returned from its maiden flight, the recovery system waiting for it wasn't a fixed tower with mechanical arms at all — it was a moving net, mounted on a ship, that met the falling booster mid-air using hooks built into the rocket itself. The alignment tolerance that made me sit up on the fifth replay isn't an accident of the net's design. It's the direct consequence of a different wide-end assumption: instead of "how do we build a bigger, better catching tower," CASC's engineers asked "does the catcher need to be fixed in place at all, or can it come to the rocket." A fixed tower has to be perfectly positioned relative to where the booster will actually be, because the tower can't move to correct for error. A net on a ship can adjust its position right up until the moment of catch — which is exactly the small-alignment-error forgiveness that struck me as almost unfair the first time I watched it. It isn't unfair. It's the payoff of refusing to inherit the fixed-tower assumption in the first place.

The technical teardown.

This is FEB applied to a problem that looks, on the surface, like pure hardware — and it's worth being precise about where the reframing actually happened, because it wasn't in the net itself. The net is a relatively simple mechanism. The reframing happened one step upstream, in the decision about what kind of system was allowed to do the catching at all.

Here's the analytical move stated plainly, because it's the one I want you to be able to use, not just admire: when an existing solution has already defined the shape of the problem for you, the wide-end move is asking which of that solution's assumptions were actually load-bearing, and which ones just came along for free because nobody questioned them. SpaceX's fixed-tower architecture carries an assumption that isn't obviously necessary once you name it: that the catching mechanism should stay in place and the booster should be guided to meet it precisely. That assumption produced brilliant engineering — the chopstick arms, the guidance precision required to hit a fixed target from two hundred feet up. But it's an assumption, not a law of physics, and CASC's net is what happens when you go back to the wide end and decline to inherit it.

I want to be fair to both approaches rather than declare a winner, because the honest engineering story is more interesting than that. CASC's net caught its booster successfully on the very first attempt, where SpaceX's tower-and-arms approach took years of iteration — multiple failed catches, aborted attempts, and hard-won guidance refinement — before it became routine. That's a real point in the net's favor for how quickly a wide-end reframe can pay off. But SpaceX's architecture was built for a different requirement from the start: rapid, repeated reuse at high cadence, with the booster returning to the exact launch site rather than a ship that then has to transit back to port. The tower's rigidity is a liability for alignment tolerance and an asset for turnaround speed. The net's mobility is an asset for alignment tolerance and, potentially, a liability for how fast you can fly the booster again. Different wide-end framings, optimized for different missions — reuse cadence versus first-flight success — not a strictly better and worse version of the same idea.

Forensic signature.

The tell that a team is working at the narrow end here would have been a Chinese engineering group spending years trying to build a better version of SpaceX's tower — more precise arms, tighter tolerances, a taller structure — and still fighting the same fundamental alignment problem the tower architecture makes hard by design. The signature of the wide-end move is the opposite: a completely different-looking mechanism that makes an old problem simply stop being as hard, because the framing that made it hard was never inherited in the first place.

Aftermath, and a forward prediction.

I don't think "better than SpaceX" was ever the right way to describe what I was watching, and I'm glad it took twenty replays instead of one to notice that. The more useful question — the one I keep applying now — isn't which team built the better catcher. It's which team was more willing to ask whether the thing everyone had already agreed the catcher should look like was actually the only shape it could take.

That same question is about to show up in a place with an entirely different kind of falling: not a rocket booster, but an entire industry's sales numbers, as automakers decide whether "the EV didn't work" means going back to what worked before, or means asking exactly what part of the electric architecture actually needs to change.

I'd love to hear about a moment you watched two teams solve what looked like the same problem and realized they'd never actually agreed on what the problem was. That question drives everything I write here.

Leave a comment

Subscribe now

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development.

FEB (Formen Engpass Barriere)™ is a pending trademark of Inventor’s Mind Press, naming the practice of reframing a problem from the wide end of the funnel — reshaping the framing that produces a constraint, rather than working the constraint itself.

They called it risk transfer. A fixed price, locked in before a single rivet was cut, so the taxpayer would never eat a cost overrun again.

That’s not risk transfer. That’s a translation failure with a $1.35 billion price tag.

What actually happened was simpler, and more damning:

• The Navy needed a stealth attack aircraft to replace the A-6 Intruder on carrier decks.

• In 1988 it signed McDonnell Douglas and General Dynamics to a fixed-price contract for the A-12 Avenger II — a flying-wing design built around a heavily composite structure.

• The composite wing, carrying much of the aircraft’s stealth shaping, came in significantly overweight.

• The overweight wing meant the aircraft could not meet its carrier landing weight limits — not a marginal miss, a structural one.

• The problem required a redesign, not a manufacturing fix.

• The contractors kept building anyway, and the full scope of the weight problem was not disclosed to Navy oversight as it was discovered.

• By January 1991, the losses were unrecoverable and the technical picture was unrecognizable from what the contract assumed. Secretary of Defense Dick Cheney cancelled the program outright.

Total contractor losses: roughly $1.35 billion. Litigation over the termination ran for over two decades — well into the 2010s — before it was finally resolved.

The theory of fixed-price development is clean: put the financial exposure on the party building the thing, and you’ll get honest, disciplined engineering, because they can’t afford not to. It’s a good theory for a known product built with known processes. It is a bad theory for developmental engineering with real unknowns still on the table — because in that situation, the contractor isn’t just incentivized to solve the problem cheaply. They’re incentivized to not tell you the problem exists, for as long as the math lets them believe they can still solve it before anyone has to write the check.

That is not a hypothetical failure mode. That is exactly what the A-12 record shows.

The Architecture Problem

Composite structures were still a maturing discipline in naval aviation in the late 1980s. A flying-wing design pushed a huge fraction of structural and stealth-shaping load into that composite wing — high-payoff engineering, and high-uncertainty engineering, in the same part.

High uncertainty and a fixed price are not compatible inputs. One of them has to give. On the A-12, the uncertainty didn’t shrink. The disclosure did.

This is the same pattern that shows up anywhere a contract, an incentive plan, or a performance metric is built on the assumption that the problem is already well understood at signing. When the assumption is wrong, the instrument doesn’t produce honesty under pressure. It produces concealment under pressure — right up until concealment is no longer possible, at which point the failure arrives all at once, at maximum cost, instead of early and cheap.

The Navy didn’t lose oversight because anyone was incompetent. It lost oversight because the instrument it built — the fixed-price contract — was structurally blind to its own failure mode. You cannot ask an organization to bet its survival on hitting a number and also expect it to volunteer, early and often, that it’s about to miss.

The Cascading Cost

The explosion did not stay in the wing.

McDonnell Douglas and General Dynamics absorbed the direct losses. The Navy lost its next-generation carrier-based stealth strike capability with nothing queued to replace it — a capability gap that shaped carrier air wing planning for years afterward. And the termination itself became a two-decade legal fight over who owed whom, consuming legal and program-office attention long after the aircraft itself was forgotten.

A composite wing that came in overweight didn’t just kill one program. It rewrote how the Pentagon thought about fixed-price development contracts for advanced aircraft for a generation.

Clarity as the Missing Control Loop

Complex programs don’t fail because contractors are dishonest by nature. They fail when the incentive structure and the technical reality are pointed in different directions, and nobody has built a control loop fast enough to catch the divergence before it becomes unrecoverable.

A fixed-price contract is not a control loop. It’s a bet. It only works when the thing being bet on is already well characterized. The moment real engineering uncertainty is still on the table, the fixed price stops enforcing discipline and starts enforcing silence.

The Most Expensive Metaphor

A $1.35 billion contract termination is simply the most visible version of a pattern running in most organizations right now: an incentive structure built on the assumption that the hard part is already solved, applied to a problem where it isn’t.

The engineer who knows the wing is overweight and says nothing because the program can’t survive saying so out loud is not a rare person. They are the predictable output of an instrument that rewards confident numbers over honest ones.

If your organization’s contracts, comp plans, or KPIs assume the risk is already known, you already know which version of this story you’re building toward.

The physics — and the balance sheet — will eventually enforce the truth either way.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license

You can throw away or recycle most items. But, You can never easily dispose of a large PMC composite resin structure.

That's not a joke. It's an engineering claim, and I'm going to spend the next several minutes proving it, because once you see it you can't unsee it, and it turns out to be a much bigger problem than anyone selling you a boat, a car, or an airplane is willing to say out loud.

Beached sailboat with PMC hull Royalty free stock photo pexels.com

The scene

A man in Green Cove Springs, Florida, wrote a check for $11,000 last spring to make a sailboat go away. He owned her outright. No loan, no lien, no storm damage. Thirty-six feet of solid hull, a straight mast, a dry bilge. He paid to have her cut up.

Walk that yard on the St. John's River and you'll see forty more waiting their turn. Jack stands settled into the gravel. Sail covers gone chalky and split along the seams. Furling drums seized solid. Boats that crossed the Gulf Stream in their day, standing in a dirt lot with their halyards slapping at nothing. Every one of them was somebody's plan.

Typical sailboat storage yard Royalty free stock photo pexels.com

The dream doesn't usually die in a gale. It dies in a storage yard with an invoice.

The real gatekeepers

Here's what nobody tells you at the boat show, the car lot, or the delivery ceremony: the salesman will give you forty minutes on headroom and horsepower and legroom. He will never once tell you what she'll be worth to the next owner, because by the time that question matters, he's busy selling someone else a different sunset.

Understand who actually decides whether an object gets to keep living in commerce. It isn't the buyer, and it isn't the market in any romantic sense. It's underwriters and loan officers. Insurers have spent the last few years going back through their books on older hulls — rig age, wiring, moisture in the core, grounding history. Boats past twenty or twenty-five years old are seeing premiums jump, upgrades demanded before renewal, and in plenty of cases, coverage declined outright. Marinas won't hand you a slip without liability coverage — $300,000 minimum in most places, $500,000 in some. Most lenders stop writing notes on a hull somewhere past fifteen or twenty years old, at any price.

Follow that chain all the way down. No insurance, no slip, no financing, no financed buyer. What's left is the cash market, and the cash market is small, and it is very particular about what it takes home.

So here's the actual test an object has to fail before it becomes a disposal problem, and it has two gates, not one:

Gate one — repair economics. Does she cost more to fix than she'd be worth fixed? That's a straightforward, honest question, and it applies to any object made of any material.

Gate two — insurability and financeability. Can she get coverage, a slip, a loan to a buyer? This gate has nothing to do with her condition. It's a line drawn by people who have never seen her, based on nothing but a date.

An object only needs to fail one of these gates to become undisposable. And the more interesting failure — the more unfair one — is the boat that passes gate one easily and fails gate two purely on age. A dry bilge and a straight mast don't matter to an underwriter working off a birth year. That's exactly the boat in the yard on the St. John's River, and it's where the real story starts, because up to this point it's just an unfair market. What happens next is chemistry.

Six ways out, all closed

Once a hull fails the insurability gate, here's every path back to value, and here's why each one is closed.

Resale. Already covered — this is the gate that got her here in the first place. Clean Ranger 33s, a 1970s racer-cruiser built by Gary Mole, ask $7,500 to $15,000 today. Not because she's a poor boat. Because the fleet she was built for — Wednesday night racing, handicap classes — thinned out and mostly disappeared, and the cruising buyer who steps below finds a Spartan interior and steps right back off.

Parts-out. This is where the material itself starts working against her. A fiberglass hull is a monolithic bonded structure — hull, deck, stringers, often the interior pan, chemically fused into essentially one part. There's no unbonding a keel stub or reselling a section of hull skin. Cut fiberglass and you have scrap, not a component.

Compare that to a wood hull, which is mechanically fastened, not chemically monolithic. Frames, planks, deck beams, cabin joinery, bronze ports and chainplates — all discrete, all removable with a screwdriver or a saw, all individually salable. A dead wood hull liquidates piece by piece. A dead composite hull does not, with exactly one exception: lead ballast. Many composite sailboats carry an internal or external lead keel — four, five thousand pounds on a boat this size — and lead doesn't degrade with age. It's the one component on a fiberglass hull that behaves like the wood-boat model: separable, valuable regardless of condition, priced by current scrap rates. It's also the heaviest thing on the boat, which tells you something about how little of her total mass actually has a second life.

Grinding to feedstock. Fiberglass dust is a serious industrial hazard — silica and glass fiber particulate requiring respiratory protection and specialized handling, which drives cost well above ordinary demolition. Glass fiber is abrasive; it chews through blades and equipment fast. And the output has no market. Ground fiberglass isn't a feedstock anyone wants — thermoset resin can't be re-melted like a thermoplastic, so it isn't recyclable into new composite at scale, isn't usable fill, isn't compostable. It goes to landfill either way; grinding just makes disposal marginally cheaper per truckload, if that.

The coarsest, cheapest version of this — crushing to roughly one-inch chunks with standard construction-demolition equipment rather than fine-grinding to powder — lands close to ordinary aggregate size and skips the worst of the hazard and equipment-wear cost. But it still has to compete with quarry aggregate, which is dug, crushed, and sorted at massive scale with fully depreciated equipment and sold for a few dollars a ton. Fiberglass chunks carry acquisition cost, breaking cost, crushing cost, abnormal blade wear, contamination sorting, and hauling — a fundamentally different cost structure than geology. And even if the economics worked, the supply doesn't: the backlog of derelict hulls is a fixed stock, not a renewable flow. A single serious processing operation would exhaust the visible national backlog within a year, then sit on idle equipment waiting for boats to individually age into the disposal window, one at a time, decades apart. Quarries work because geology is functionally infinite. Derelict hulls are the opposite — bounded, one-time inventory.

Reforming under heat. This is where the chemistry finally says no outright. Epoxy and polyester resins are thermosets — the cross-linking that cures them is a one-way chemical reaction, not a phase change. Heat cured resin enough to try to soften it and you don't get pliable material, you get thermal degradation: charring, off-gassing, chemical breakdown, well before anything resembling a moldable state. There is no temperature at which cured resin becomes soft and compressible the way a thermoplastic does. It's the same mechanism that makes vulcanized rubber a decades-long disposal headache — sulfur cross-links rubber polymer chains into a permanent structure the same way curing cross-links resin. Once vulcanized, once cured, neither material reverts. The permanence that lets a hull survive a Gulf Stream crossing is the same permanence that makes her impossible to unmake.

Sandwich-panel construction material. On paper, this is the most credible idea on the list — a wood-skin, composite-core sandwich panel, the same skin-and-core logic that already exists in structural insulated panels and engineered lumber. Outer plywood veneer carries the structural load; a chopped-fiberglass core adds dimensional stability, resisting the moisture-driven expansion and contraction that warps wood panels over seasons. Placed at the panel's neutral axis, a resin-encapsulated core that doesn't absorb water would genuinely constrain shrink-and-swell cycling.

It runs into two separate physical walls anyway. A fiberglass hull is a compound-curved shell, curved in more than one axis at once. Cut a section from it and it won't lie flat — thermoset composite doesn't reflow or relax, so forcing it flat cracks the laminate or leaves it stressed. That forces you back to full grinding to get a flat-compatible feedstock, which reintroduces the cost wall from the previous paragraph. And even ground material isn't uniform: builders vary hull thickness deliberately, heavier at the keel and high-stress areas, thinner in the topsides, with local reinforcement around fittings. Every donor hull yields a different, uncontrolled mix of glass-to-resin ratio depending on where on the hull the material came from. A construction material needs a consistent input. This can't reliably provide one.

Reefing. Steel works as an artificial reef because the material behavior is known and stable — steel sinks reliably, corrodes slowly into iron oxide, which is broadly inert, and there's an established federal approval pathway built specifically around steel hulls. Fiberglass fails on two separate points. Foam-cored hulls often won't sink cleanly or stay down — trapped air and closed-cell foam fight submersion, so a hull that won't stay put isn't a reef, it's a hazard. And most reefing programs don't approve fiberglass vessels at all, excluded by category rather than evaluated case by case, because resin and gelcoat leaching don't meet the same stability standard steel does.

And the two fallbacks everyone reaches for when nothing else works, also closed. She won't rot — nothing biological recognizes cross-linked resin or glass fiber as food, so left alone she'll still be substantially a fiberglass hull in two hundred years, just uglier. And she won't burn, not usefully. Glass fiber survives combustion entirely — its melting point is well over 1400°C, far beyond any open burn or ordinary incinerator — and the resin releases dense, toxic smoke rather than combusting clean, which is exactly why burning fiberglass boats is illegal in most jurisdictions.

There is no economics where reimagining an old fiberglass hull works. She won't rot, won't melt, won't grind into anything worth buying, and won't even burn. She's forever waste.

What this doesn't mean

One honest correction, because the claim above is easy to overstate. A repairable thing isn't undisposable — it just hasn't needed disposing of yet.

Fiberglass car bodies are the clean counter-case. Lotus built a reputation on fiberglass monocoque construction for the same reasons boatbuilders liked it — light weight, complex curves out of a mold, no stamped-steel tooling cost. Same resin, same glass, same one-way cure chemistry as any hull. But automotive fiberglass repair is a mature, decades-old industry: panels are more separable than a continuous hull shell, gelcoat repair and panel patching are routine body-shop work, and there's an active resale market that keeps a damaged Lotus in circulation for decades before anyone asks the disposal question at all.

So the claim isn't that composite is worthless. It's narrower and more defensible than that: composite has no exit once repair economics fail or insurability closes — and that's a different day for every object, depending entirely on whether a market still wants her whole.

The category, widened

Once you see the mechanism, it stops being a boat story. Power boats, jet skis, canoes — same laminate, same resin, same six closed gates, at every price point and size class in recreational watercraft. (Aluminum and polyethylene canoes are the honest exception — those materials have real scrap and recycling paths that composite simply doesn't.) Wind turbine blades are already a documented, headline-level version of this same crisis — thousands sitting in landfills today with no melt-down path, arguably the strongest existing real-world proof that this isn't a theoretical problem. FRP pipe and tank liners, skis, snowboards, surfboards — same chemistry, smaller volumes, same dead end.

There's a useful contrast case worth sitting with: scrap tires. Vulcanized rubber shares the identical one-way-cure chemistry — sulfur cross-linking instead of resin cross-linking, same permanence, same refusal to melt back down. Tire stockpiles were once exactly this kind of problem — fire hazard, mosquito breeding ground, visible blight — and they got a real disposal pathway only after forty years of regulatory mandate and subsidized market-building: crumb rubber, rubberized asphalt, playground surfacing, markets that had to be invented and funded into existence because none arose naturally. Composite hasn't even started down that road. No mandate, no funded market, just quiet accumulation in yards like the one on the St. John's River.

The centerpiece: the 787 has nowhere to go

Here's where the stakes stop being local.

Boeing 787 - Composite primary structure Royalty free stock photo pexels.com

Composite primary structure — the 787, the A350 — is carbon-fiber thermoset. Same chemistry as a sailboat hull, same six dead ends, at a scale that makes a stranded Ranger 33 look almost quaint. Roughly half of the 787's airframe by weight is composite, far more than any prior commercial airliner. That's not a hull's worth of cured resin per aircraft. It's tens of thousands of pounds, multiplied across a fleet that will eventually number well over a thousand aircraft.

Aluminum airframes retiring today feed a mature, genuinely profitable melt-down and scrap industry — the boneyards at Pinal Airpark and Mojave have run on exactly that economics for decades, the same mechanism as a steel ship headed for the reef. There is no equivalent pathway waiting for carbon-epoxy primary structure. The first generation of 787s is only now approaching retirement age, and the industry that will need an answer hasn't priced one in yet.

A resin-hulled sailboat and a 787 fuselage are the same chemistry problem at different scales — cure once, stay cured, forever. The boat in the yard on the St. John's River just got there first.

I have a strange vantage point on this one. I built composite aircraft components at y in the mid-1980s, alongside Honda R&D engineers working on what would eventually become the HondaJet program — years before this material was ever primary structure on anything commercial. I watched composites move from racing hulls and boat building into aerospace with almost no knowledge transfer between industries. Nobody carried the material's long-term behavior with them into the new application. We knew how to make it fast and light. Nobody was asking yet what happens to it in sixty years, because in 1985 there was no sixty-year-old carbon-fiber airframe to look at.

There's one now.

The close

She doesn't have to be broken to become undisposable. She just has to fail one of two tests — worth less than she costs to fix, or unwelcome at any price by the people who gate access to buyers. Composite fails the first test rarely. She fails the second test constantly, and once she does, chemistry makes sure there's no way back.

You can re-gift a fruitcake. You can never dispose of a resin structure.

A stranded Ranger 33 eventually gets cut up, hauled, buried — ugly and expensive, but finite. One hull, one yard, one invoice. A 787 doesn't have that ending available to it at scale. None of the six gates open any wider for a fleet. They close the same way. Just multiplied.

A sailboat that won't go away is a curiosity in one marina. A jet fleet that won't go away is a new kind of landscape.

Retirement isn't a sale for a composite airframe. No scrap value, no melt-down recovery — the same six dead ends as the hull, wearing a bigger price tag. It's an expense. Someone — an airline, a lessor, eventually maybe a regulator-mandated fund — has to pay to close her out, exactly the way the man in Green Cove Springs did.

He paid $11,000 to close out a thirty-six-foot hull. Somebody, someday, pays to close out a 787 — because retiring her was never going to be a sale. It was always going to be an invoice.

There is one exit that actually works, and it isn't a disposal pathway at all — it's a different question entirely. A sound hull that fails the insurability gate while passing the repair-economics gate easily isn't structurally worthless. She's just unwelcome in one particular market. Buy her for cash, outside the financing chain that excluded her. Use her fully — she'll do everything she ever did. Then, when it's time to let her go, don't sell her and don't destroy her. Give her to a Sea Scout unit or a sail-training program, an institution that was never screening on resale value in the first place, that wants a boat with deferred maintenance and an outdated interior precisely because rigging repair and engine maintenance are the curriculum, not a defect. She doesn't need to be perfect to be donated. She needs to be exactly what she is — which is, for the first time in this whole story, an asset instead of a liability.

There's no version of that exit built yet for a 787.

Subscribe now

Leave a comment

Herbert Roberts, P.E. — 30+ years in aviation R&D across two companies. 8+ years analyzing accidents for attorneys under my P.E. license.

Follow the S-Curve

Last week's piece made a claim: innovations arrive on emotion, but only fixed-cost reduction lets them survive. A fad is just an innovation that never clears that second hurdle.

That raises an obvious question. If fixed cost is the thing that decides whether something lives or dies, why doesn't every organization just go find it and fix it? Everyone agrees bottlenecks are expensive. Nobody's in favor of waste. So why does fixed cost sit there, visible, un-shrunk, year after year?

Because a bottleneck is almost never one problem. It's two, stacked on top of each other, and each one has a different reason for not getting fixed.

The 90/10 Split

In my experience, most organizational bottlenecks break down roughly like this:

90% is process conflict. Two systems, two teams, two procedures that were each built correctly for their own purpose, now butting heads at the seam where they meet. Nobody designed this on purpose — it accumulated. The fix is usually knowable. An engineer, a process owner, or a competent outside eye can look at it and see where the friction is. This is a structural problem, and structural problems are solvable in the ordinary sense: you can write the fix down.

10% is human problem-solving. Somewhere in the chain, a person has to make a call, own a decision, or admit that the way something has always been done needs to change. That's not a structural gap. That's a will gap.

Two different problems. Two different reasons the delay happens. And critically — two different kinds of cost.

Opportunity Cost vs. Emotional Cost

The process-conflict delay is an opportunity cost. The fix is known or knowable, the org just hasn't spent the resources — time, budget, attention — to implement it. Every day it sits unfixed, you're not paying a penalty so much as forfeiting a gain you could have already banked. It's the cost of the thing you didn't do yet.

The human-issue delay is an emotional cost. This is the part that doesn't respond to a whiteboard. Avoidance, ego, fear of being visibly wrong, sunk-cost loyalty to "how we've always done it" — these delay a fix that everyone privately knows is coming anyway. This isn't a resourcing problem. Throwing more budget or more headcount at it doesn't touch it, because the constraint isn't capacity. It's a person, or several people, who have to move first.

Here's the part that matters for the S-curve: these two delays don't just sit side by side. They compound.

The process conflict makes the org visibly slower, which raises the emotional stakes of admitting whose process has to change — which makes the human delay longer — which lets the process conflict compound further, because nobody's touched it. The 10% makes the 90% harder to fix, and the 90% makes the 10% harder to face.

Why "Naming the Bottleneck" Isn't the Fix

There's a popular idea in AI-and-org-design conversations right now: identify where the organization loses the most momentum — usually coordination, decision-making, fragmented information — and that's where technology becomes transformative.

That's directionally right, and it's also incomplete. Naming the bottleneck is diagnosis. It's not treatment. You can have a perfectly accurate map of the 90% process conflict and still not move, because the 10% human issue is what's actually holding the org in place. A tool that automates the process conflict away does nothing for the person who doesn't want to be the one who admits their team's procedure was the wrong one.

This is why so many technology rollouts — AI included — look like they should collapse fixed cost on paper and don't, in practice, for months or years longer than the business case predicted. The math was right. The 10% wasn't accounted for.

What This Means for the AI S-Curve

If AI is going to climb its own S-curve the way the last piece argued — surviving on fixed-cost reduction rather than emotional appeal — it has to clear both parts of this split, not just one.

The 90% is the easy sell: AI genuinely can resolve a lot of process conflict, faster and more visibly than most prior technologies. That's real, and it's why the emotional excitement isn't baseless.

The 10% is where most of these efforts will actually stall. Someone has to admit a role changed. Someone has to stop being the bottleneck they've quietly been for years. Someone has to make the call that the old process — the one they built, defended, or inherited — isn't the one going forward. No model ships that decision. It still has to be made by a person, on a Tuesday, in a room, at some emotional cost to them personally.

Fixed cost only goes down when both halves move. Track the 90%, and you'll see where the opportunity is. Track the 10%, and you'll see why it's still sitting there.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license

Why the right answer to "which engine" is sometimes "how many kinds"

Herbert Roberts, P.E. | Inventor's Mind

There are so many ways to fly into space, and early in my career I watched one that used three different engines on the same vehicle.

My first reaction wasn't admiration. It was arithmetic. Three propulsion systems means three sets of hardware, three sets of fuel or oxidizer, three integration problems, three ways for something to fail — and all of it riding along as dead weight during whatever portion of the flight each engine wasn't the one doing the work. That's a lot of payload added to the airframe, I thought, before I'd worked out why anyone would accept that penalty on purpose.

It took me longer than I'd like to admit to see that the three-engine answer wasn't a failure to optimize. It was the correct response to a framing problem the vehicle couldn't escape any other way.

Confession. My training pushed me toward a single instinct almost every time I looked at a propulsion problem: pick the best engine for the mission and then work hard to make the mission fit it. That's narrow-end thinking, and it's usually right — most vehicles fly through one kind of physics for their whole mission, and forcing a single, well-optimized engine to do the job is exactly correct. It just isn't correct every time, and the National Aero-Space Plane concept, developed through the 1980s and into the '90s, was the vehicle that finally made me see where that instinct runs out of road.

The false issue was "which engine is best for a vehicle that needs to reach space." That question assumes there's a single best answer waiting to be found, and it sends you looking for it — better materials, better cooling, a cleverer cycle. The true issue was "does this mission actually fit inside one engine's operating envelope at all" — and for NASP, the honest answer was no, not because engineers hadn't tried hard enough, but because the mission itself spanned physics that no single propulsion architecture handles well from end to end.

The forensic correction.

A vehicle accelerating from a runway to the edge of space passes through flight regimes that don't share the same rules. A turbojet breathes air and runs out of it at altitude. A rocket carries its own oxidizer for the whole trip and pays a brutal weight penalty for that independence the entire time it isn't needed. A ramjet doesn't produce useful thrust until the vehicle is already supersonic, and a scramjet doesn't work until well past that. Each of these is an excellent, well-understood engine — for the specific slice of the flight envelope it was built for. None of them, alone, covers the whole mission.

The narrow-end answer to that would have been to pick the single least-bad compromise engine and force the mission to live inside its limits — accept a lower orbit, a smaller payload, a narrower performance window, whatever it took to keep the propulsion architecture simple. NASP-era combined-cycle work — turbine-based combined cycle and rocket-based combined cycle architectures, documented extensively in NASA technical literature — refused that trade. Instead of narrowing the mission to fit one engine, the program built a shared flowpath that could hand off between turbojet, ramjet or scramjet, and rocket modes as the flight regime changed underneath it. That's not "a better engine." That's declining to accept that the mission had to collapse down to a single propulsion means at all.

The technical teardown.

This is the FEB move applied to hardware instead of an organizational decision, and it's worth being precise about why it counts as the same move. FEB — Formen Engpass Barriere — names the practice of reshaping the framing that produces a constraint, rather than working the constraint once it's already been accepted. The narrow-end constraint here would have been "our engine can't cover the whole mission, so let's make it better." The wide-end move was refusing to accept that a single engine had to cover the whole mission in the first place, and building the vehicle around a propulsion architecture that could change shape as the physics changed underneath it.

There's a version of this that's worth naming precisely, because it's the one analytical move in this piece I want to say outright: when a single component is being asked to perform well across conditions that don't share the same physics, the wide-end question isn't "how do we improve the component" — it's "does one component need to cover this whole range at all, or does the range itself need to be split." NASP split it. Three propulsion modes, one shared flowpath, each mode carrying the mission only through the regime it was actually built for.

Now the contrast, and it's an honest one rather than a criticism of anybody. Boom Supersonic's Overture, powered by the Symphony engine, doesn't face NASP's problem. Overture is designed to cruise supersonically within the atmosphere and never leave it — one flight regime, one set of physics, start to finish. A single-cycle turbofan is the correct, uncompromised answer for that framing, and building in NASP's multi-mode complexity would be solving a problem Overture doesn't have. This is the part that's easy to get backward: the FEB question was never "should every vehicle use multiple propulsion means." It's "what does this specific mission actually require me not to assume away." NASP's mission spanned two physics regimes and would have hit a real bottleneck forcing one engine to cover both. Overture's mission doesn't span those regimes, so the multi-cycle answer would be complexity in search of a problem. Same wide-end question, two correctly different answers, because the missions were shaped differently before either engine was ever selected.

Forensic signature.

The tell, here as everywhere else this pattern shows up, is a team that's very good at optimizing the component in front of them and no better off for it. If NASP's engineers had spent their effort exclusively trying to build one engine that did everything — a turbojet with rocket-like performance, or a rocket that somehow sipped propellant like an air-breather — they'd have gotten very good at an engineering problem that physics doesn't actually permit a clean answer to. The three-engine architecture wasn't a concession. It was the moment someone stopped trying to solve the unsolvable narrow-end version and asked what the mission actually needed instead.

Aftermath, and a forward prediction.

I still think about the payload penalty I calculated in my head the first time I saw that three-engine architecture, because the instinct behind that calculation wasn't wrong — it was just answering the wrong question. Three engines is more mass, more integration risk, more ways to fail. All of that is true and none of it is the point. The point is that the alternative — one engine, one set of physics, a mission quietly narrowed to fit — would have cost more than the weight ever did.

I'll carry this same question into the next piece, because it shows up again almost immediately once you start looking for it, in a place with even less obvious kinship to a Cold War spaceplane: two very different answers to the problem of catching a two-hundred-foot object as it falls out of the sky, arrived at by two engineering teams who made opposite bets about what the "catcher" was allowed to assume about itself.

I'd love to hear about a time you watched someone split a problem instead of trying to force one solution to cover all of it. That question drives everything I write here.

Leave a comment

Subscribe now

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development.

FEB (Formen Engpass Barriere)™ is a pending trademark of Inventor’s Mind Press, naming the practice of reframing a problem from the wide end of the funnel — reshaping the framing that produces a constraint, rather than working the constraint itself.

I read The Radium Girls by Kate Moore recently, and it did something I didn't expect: it made me grateful for every annual safety training I've ever sat through. It also made me go back and ask a harder question — did any of that training actually change how I moved through my own workplace?

Mostly, no.

About the book: The Radium Girls (Kate Moore, 2017) tells the true story of young women who hand-painted glow-in-the-dark watch dials with radium paint in the 1910s–20s, pointing their brushes with their lips on company instruction. Years later they developed crumbling jawbones, anemia, and tumors, while the companies denied any link. Their fight for legal recognition became a foundation for modern occupational safety law.

No Red X's

Every job I've had ran the training. Annual refreshers, procedure binders, a video in a conference room. I sat through all of it. But it arrived as procedure — steps, thresholds, PPE requirements — delivered the same way you'd teach someone to file a report. It never once said: that dust by the security room vents, the one you walk past without noticing. That smell on the open shop floor you stopped registering years ago. The hazards that were actually present didn't get a red X painted on them. They just sat there, camouflaged by routine, while the training talked about hazards in the abstract, somewhere else, to someone else.

We were too cavalier for our own good — but cavalier is the wrong word for what it actually felt like from the inside. It felt like nothing was happening. That's the trick familiarity plays. A knife with a red X on the handle gets respected. The same knife, handled every day without incident, disappears into the furniture. Nobody hands you the paint.

Eyes, Fingers, Toes

Unlike the Radium Girls, we weren't a uniform group of workers sharing one exposure, one employer, one clear villain. We were scattered individuals, each mildly under-cautious in our own way, across different jobs and different decades. That's harder to write about, and maybe harder to fix — there's no single company to name, no one settlement to point to.

But here's what I can say for myself: I wore my PPE. Every time. I valued my eyes, my fingers, my toes — the parts of me I could see, the injuries I could picture. Glasses on. Gloves on. Steel toes laced. That's the equipment the training made vivid, because the harm was vivid. A red X practically painted itself.

What I didn't think about nearly enough was my thyroid. My liver. My lungs. The parts of me that don't show up in a mirror, that don't hurt until they've already been hurting for years. The dust and the vapor didn't come with a red X, because they don't threaten anything I could watch get injured in real time. I was careful about the body I could see and cavalier about the body I couldn't — and nothing in thirty-some years of annual training ever quite closed that gap.

The Crosswalks Exist Now

What's striking, reading about the Radium Girls' plant, is how thoroughly that specific world is gone. Contaminated rags piled in workrooms, waste dumped in a washroom toilet, ventilation venting over a children's playground — none of that happens now, not because the industry got lucky, but because the company was forced to hear it, see it, and change. Regulation, monitoring, industrial hygiene as a discipline — all of it exists downstream of exactly this kind of failure. The crosswalk got painted.

But a crosswalk only works if you use it. The world didn't stop being dangerous when modern safety standards showed up; it just stopped being invisibly dangerous by default. The hazard data exists now. The exposure limits exist. The training exists — abstract as it sometimes is. What's still optional, the way jaywalking is still optional, is whether you actually treat the walk from your car to your desk, your bench, your dip tank, as a hazard zone instead of a formality.

That's the real difference between the Radium Girls' era and ours. They had no crosswalk to use. We do — and the failure now isn't a company hiding the paint. It's an employee, PPE on for the eyes and fingers, walking past the vent without a second thought because the light's green and it always has been.

The Scissor Lifts

And to be fair, some of it clearly did work. Walking the shop floors and assembly bays of one major jet engine company for over twelve years, I never once saw a stepladder. Not one. Scissor lifts were everywhere instead — and once you noticed it, it made obvious sense: thirty and forty foot ceilings, engine stands, overhead crane paths. Somebody had already run the numbers on falls from height and simply engineered the stepladder out of the environment. You didn't have to remember to be careful about height, because the option to be careless about it had been designed away.

That's what a real crosswalk looks like. Not a poster telling you to look both ways — a curb cut, a signal, a system that makes the safe choice the only convenient one. The fall hazard got that treatment. The dust, the vapor, the thing you breathe walking past the security room vent — that mostly didn't. Some risks got engineered out of the environment entirely. Others just got a line item in the annual training and were left for the individual to notice, or not, on their own.

A little knowledge is dangerous. So is knowledge that's real, current, and fully available — if it never gets localized to the room you actually stand in.

P.S. Take a CPR class. Learn what to do for a diabetic or hypoglycemic emergency, and for a choking victim, too. I took that training and the refreshers throughout my career and never once had to use it myself — but others who sat in the same classes did, and it mattered. That's a red X you can paint on yourself, in advance, for someone else's worst five minutes.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 32 years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license.

A FEB™ Big Why on Why the Best Companies Won't Hire New Grads for the Hardest Jobs

Read a materials or manufacturing engineering job posting at SpaceX or an Anduril-adjacent hardware company and a pattern jumps out fast: they are not asking what you know. They are asking what you have already touched, broken, and fixed.

SpaceX's composites materials role wants someone with hands-on experience who can walk in and immediately develop new processes and required training for prepreg systems, resin transfer molding, and automated fiber placement — not learn them. Their metallurgy role wants direct experience with in-house forming and casting methods, including additive, on the exact alloys the job touches. Look at who staffs the companies orbiting them, and the recruiting pitch says the same thing out loud: our people come from SpaceX, Anduril, Scaled Composites, Lockheed Martin Skunkworks. The company name on the resume isn't a line item. It's the credential.

That's the whole thesis in one sentence: the leading edge of American hardware isn't hiring engineers. It's hiring used engineers — people who already have the mileage on them, because nobody trusts a brand-new one to survive first contact with a real part.

That should stop you. Not because it's cynical. Because it's rational, and the reason it's rational is a story about why.

The Big Why

We've built the case for this in two earlier pieces, and it's worth stating the mechanism plainly instead of case-by-case.

Why can't a new engineer walk in ready? Because the barrier that would have prepared them acts upstream of the classroom, in domains the core curriculum simply doesn't require. Pull the actual degree charts. MIT's required mechanical engineering core is Mechanics and Materials, Dynamics and Control, Thermal-Fluids, Design and Manufacturing, Numerical Methods, and a thesis. Ohio State's core runs through Statics, Dynamics, Mechanics of Materials, Thermodynamics, Machine Elements, Fluid Mechanics. Neither required list contains composites or additive manufacturing. Where that material exists at all, it's an elective, or it's walled off in a standalone master's program built specifically because the undergraduate core doesn't reach it. The gap isn't a rumor. It's printed on the curriculum sheet.

Why does that gap matter now, more than it did ten years ago? Because the parts being built at the leading edge — printed titanium brackets, optimized composite structures, AI-generated geometry — fail in ways that a classical metals education has no category for. None of it shows up in a converged FEA plot. None of it shows up on a transcript.

Why does that push hiring toward "used" engineers instead of "new" ones? Because a resume can't show you what a person was never taught to look for, and neither can a portfolio of clean stress plots. The only thing that reliably signals someone has actually hit this wall and learned from it is having stood at the machine when a part came out wrong, or having sat in the room when a printed bracket failed a fatigue test the FEA said it would pass. That experience isn't teachable in a lecture. It's only earned by being present for the failure — which means the fastest, most legible proxy for "has the missing training" becomes "worked somewhere that already had to learn this the hard way." Pedigree-by-employer replaces credential-by-institution, quietly, without anyone declaring it as policy.

What the Curriculum Sheet Leaves Out

A few examples make the gap concrete rather than abstract:

Composite cure state. A datasheet material property describes an idealized coupon cured under lab-optimal conditions. The as-cured laminate in a production part — its void content, fiber alignment, degree of cure — can differ from that datasheet property in ways a standard FEA model never sees, and standard metals NDE (X-ray, dye penetrant) won't catch it. That requires C-scan or thermography, tools most metals-trained engineers have never been taught to ask for.

Printed-metal grain structure. A thin wall in an additive process isn't just a stiffness question — it's a different melt-pool history, which changes grain morphology and porosity in that specific feature. And fatigue behaves differently depending on which regime you're in: high-cycle fatigue is often driven by as-built surface condition and near-surface porosity, while low-cycle fatigue is governed by columnar grain structure and defect population. Two separate problems, not one problem with a different number plugged in.

Optimized robustness. A part topology-optimized against its design loads has incidental margin deliberately removed — that's the entire point of the optimization. The better it worked, the less is left over for the load case nobody wrote into the objective function: the hammer strike, the dropped part, the mis-rigged handling load.

None of this shows up in a converged stress plot. None of it shows up on a transcript.

What "Used" Actually Buys You

A used car, at minimum, comes with a maintenance record you can inspect. A used engineer comes with something better and worse at the same time: scar tissue you can't audit directly, but that you can trust probabilistically because you know which fires they were standing near. Someone who cut their teeth on SpaceX's composite shop floor has, almost by definition, been present for a resin-flow defect, a void-content rejection, a cure-cycle deviation that quietly changed the material state of a part that looked fine on paper. That's not something you can put in a course. It's something you can only get by being in the building when it happened.

This is the honest answer to "where will Anduril and SpaceX hire these skills" — not a pipeline, not a new degree track, but a small number of organizations functioning as the informal graduate school for the entire industry, training people the hard way and then watching everyone else recruit from their alumni.

You don't have to look far for a current example of exactly this kind of failure. Blue Origin's investigation into the May 2026 New Glenn pad explosion — traced to the main oxygen valve on one of the booster's BE-4 engines — is a reminder that this isn't a hiring thought experiment. Some of the most capable hardware engineers in the country, working at one of the best-funded and most scrutinized rocket programs on the planet, still had a component behave outside what the design and test program anticipated. That's not an indictment of Blue Origin's team. It's the pattern itself, in public, in real time: even at the leading edge, the barrier finds the gap before anyone else does.

San Bruno: The Steel Was Never the Problem

The pipe segment that ruptured under a San Bruno street in September 2010 had been in the ground since 1956. Fifty-four years of pressure cycling, soil movement, and ordinary wear, and the steel itself never gave out.

What failed was something that never carried a physical load at all: the paperwork. The NTSB's investigation found that the pipe's construction records didn't match what was actually buried in the ground — a welded seam type on file that didn't correspond to the pipe segment installed at that location. Nobody caught the mismatch for over half a century, because nobody had a reason to go back and check a record against the physical part it was supposed to describe. The record wasn't being tested. It was being trusted.

That's the second barrier, and it's the one this piece is actually about. A metallurgical failure gets inspected, tested, and replaced on a schedule. A records failure just sits there, silently correct-looking, until the day something else — a pressure transient, a control-room decision, an ordinary Tuesday — forces someone to finally rely on it. San Bruno's steel held for 54 years. Its records were wrong from day one, and nothing in the system was designed to notice.

The Question Worth Asking

Not "does this candidate have a degree in the right field." Not "does this vendor's design tool produce clean output." The question is narrower and it's the one nobody puts in a job posting:

Who taught this person, or this process, what a barrier looks like — and was it a classroom, or was it a failed part?

If the honest answer is "neither yet," you're not necessarily looking at a bad hire or a bad vendor. You're looking at someone who hasn't been used yet. That's fine — as long as you know it going in, and build the guardrails accordingly, instead of finding out the same way the last company found out.

Subscribe now

Leave a comment

Herbert Roberts, P.E. spent 30+ years in aviation R&D across two companies and analyzing accidents for attorneys under his PE license, translating engineering findings into legal language.

This piece extends a FEB™ application series — San Bruno (barrier acting through time), the metals-to-composites training gap (barrier acting through domain), and this one: the barrier acting through the labor market itself, and the quiet industry-wide answer to it — hire used.

Follow the S-Curve

A few years ago, buying an electric vehicle felt like a statement. You weren't just buying a car — you were buying a position. Lower impact. Lower guilt. A small, visible bet that you were on the right side of the future.

That's a real reason to buy something. It's just not a real reason for an innovation to survive.

Here's the pattern I keep finding, industry after industry, case after case: an innovation arrives on an emotional need, but it only stays if it reduces fixed cost. Those are two different tests, and most people only ever check the first one.

The Two Questions Every S-Curve Has to Answer

When something new shows up — a technology, a product category, a way of working — it has to clear two separate hurdles, usually years apart.

Hurdle one: why did anyone try it?

This is almost always emotional. Status, identity, hope, fear, belonging, guilt relief. Early adopters aren't doing a cost-benefit analysis; they're making a statement about who they are or want to be. That's not a criticism — it's just how liftoff works. Nothing climbs the early part of an S-curve on spreadsheets.

Hurdle two: why does anyone keep it?

This is where fixed cost takes over, whether the buyer realizes it or not. Does the thing actually lower the recurring cost of doing what it does — time, money, labor, energy, risk? If yes, the curve keeps climbing after the early adopters move on to the next identity purchase. If no, the curve stalls, flattens, or reverses the moment the emotional premium stops being enough to carry it.

The tell is simple: if the reason you bought it and the reason you'd need to keep it are different things, the innovation is still riding on the purchase, not standing on the economics.

The EV Case

EVs are a clean example because the two hurdles are so easy to separate.

Arrival reason: lower the environmental impact of driving. That's an emotional, values-based purchase — a hold reason, not a structural one. It answers "why did I buy this," not "why is this cheaper to operate than the alternative, forever."

Survival test: does an EV actually lower fixed cost?

Time. Gasoline refueling is a five-minute transaction. Charging is a scheduling problem — home charger installation, planning around trip length, waiting at a station on longer drives. Time is a fixed cost like any other, and this version of the technology adds to it rather than removing it.

Energy source. In a grid still substantially powered by coal, the emissions haven't been eliminated — they've been relocated upstream to the power plant, with conversion and transmission losses added on top. The externality didn't go away. It moved and got a markup.

Net result. The two things an EV was supposed to fix — cost of driving and cost to the environment — haven't structurally improved for a meaningful share of buyers. What's improved is the story about the purchase.

That's why you're now seeing EV adoption curves flatten or dip in several markets. Not because people stopped caring about the environment — because the emotional premium that got the curve moving was never converted into a fixed-cost advantage that could carry it the rest of the way.

Why This Matters Beyond Cars

The pattern isn't specific to EVs. Solar succeeded past its own emotional-purchase phase because it eventually did lower a fixed cost — the electric bill — independent of how anyone felt about it. Remote work is persisting in the roles where it demonstrably lowers fixed cost (office square footage, relocation, hiring radius) and reversing in the roles where it doesn't. Same curve, same test, different technology.

Which brings me to the one everyone's actually asking about right now.

AI Is Going to Run the Same Curve

Right now, AI is deep in hurdle-one territory. The framing is almost entirely emotional — utopian in the optimistic corners, existential in the anxious ones. People are excited about what it could mean for how we work, what we're capable of, what gets easier. That excitement is real, and it's exactly what gets any S-curve off the ground. It is not, on its own, what keeps it climbing.

The S-curve doesn't know it's AI. It doesn't care about the discourse. It only asks the same question it's asked of every innovation before it: did the fixed cost actually go down?

Not "does this feel transformative" — ask five people in five different rooms and you'll get five different answers, none of them falsifiable. Ask instead: does this measurably collapse headcount, coordination overhead, decision latency, or error rate? That question has one answer, and it's the one that predicts what survives past this hype cycle and what gets remembered as this decade's version of the EV chart that flattened.

The tools that make it through won't be the ones that made the best case for a better future. They'll be the ones some finance department can point to and say: this line item is smaller than it used to be, and it stayed that way.

The Question to Ask Next Time

Before you bet on an innovation — as a buyer, an engineer, or an investor — separate the two questions:

Why is this arriving? (Usually emotional. Fine. That's how liftoff works.)

What fixed cost does this actually reduce, and can you measure it? (If you can't answer this one, you don't know if you're looking at a technology or a mood.)

Ask it about EVs. Ask it about remote work. Ask it about whatever AI tool is showing up in your feed this week claiming to change everything. The curve only cares about one of those two questions in the long run — and it's never the one that got the innovation in the door.

Subscribe now

Leave a comment

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development across two companies, and has spent eight years analyzing accidents for attorneys under his P.E. license.

Why the fastest way through a bottleneck is to never reach it

Herbert Roberts, P.E. | Inventor's Mind

I was first introduced to systematic innovation as a Black Belt, and the assignment that taught it to me was a trap disguised as a straightforward engineering problem.

The company had built a long, profitable history on derivative products — new offerings engineered off a single engine frame that was, by the time I got the assignment, roughly twenty years old. It had earned its keep. It was proven, well-understood, cheap to manufacture, and every engineer in the building had a decade or more of hard-won intuition about exactly how it behaved. The customer base, meanwhile, was asking for real innovation — capability the old frame architecture had never been designed to deliver and, after two decades of derivative refinement, wasn't going to deliver no matter how cleverly you pushed on it.

My Black Belt assignment was to help the engineering team find a way to integrate new innovation into a new engine frame — without losing the magic of the past.

That last phrase did more work than it looked like it was doing. "Without losing the magic" wasn't a nostalgia clause. It was the actual constraint, and it's the one that made the assignment hard: not "design something new," which is easy, and not "keep the old frame," which is also easy — but find whatever it was about the old frame that customers, and the engineers themselves, were actually attached to, and carry that forward into something the old architecture could never have supported.

The bottleneck wasn't the engine frame. The frame was just where the constraint became visible.

Confession. My first instinct, and the instinct of most of the engineers in that room, was to treat this as a narrow-end problem: characterize what the old frame did well, then find a way to bolt new capability onto it, or alongside it, without disturbing what worked. That instinct isn't wrong, exactly. It's the entire discipline of engineering, in fact: characterize the system, isolate the variable, converge on a fix within the architecture you've got. It's just aimed at the wrong end of the funnel more often than any of us like to admit, and it took me embarrassingly long to name why.

The false issue was "how do we add new capability to this engine frame." It felt like the real problem because it was the one sitting directly in front of us, backed by twenty years of institutional knowledge, with a clean and defensible path to a fix. The true issue was "what is 'the magic' actually made of, and does it require this specific frame to exist at all" — a question that required walking back past the frame itself to the design decisions and customer experiences that had made the old product beloved in the first place, most of which had nothing to do with the frame's specific geometry and everything to do with what that geometry had allowed the product to do.

The forensic correction.

A bottleneck, by definition, is the narrow end of a funnel. It's the point where flow — material, information, design freedom, whatever you're moving — gets squeezed down to its tightest constraint. Every established discipline built around bottlenecks treats them the same way: work at the narrow end. Manufacturing engineering relieves the constraint, adds capacity, buys down the choke point. Traffic engineering widens the road, retimes the signal. Eliyahu Goldratt's Theory of Constraints — still the standard reference three decades after The Goal — is explicitly a narrow-end discipline. Its entire method is finding the constraint and working directly on it until it stops being the constraint.

All of that is legitimate, proven engineering. None of it is what I'm about to describe, and the distinction matters enough that I want to be precise about it before going further: this isn't a claim that "bottleneck" is a word FEB owns. It isn't. Collins English Dictionary categorizes "bottleneck" under Automotive Engineering for exactly the reason above — it has real, established technical meaning in manufacturing and production-throughput contexts, and Goldratt's framework is rigorous and correctly narrow-end-focused for the problems it was built to solve. What follows is a different question, asked at a different point in the funnel, before the narrow-end tools ever get their turn.

The technical teardown.

There's a second place to work, and it's almost never where anyone looks first: the wide end of the funnel — upstream of the constraint, at the framing and assumptions that determined the funnel would narrow down to that point at all.

The trap is subtle, and it's not the bottleneck itself — it's arriving at one and assuming that's where the work starts. By the time a constraint is visible enough to name — an engine frame that's aged out of what the market needs — the framing that produced it is usually long settled, unquestioned, and invisible to the team now staring at the narrow end. FEB thinking is the discipline of catching that trap before you fall into it: refusing to accept the funnel's shape as given, and checking upstream before you spend a career optimizing a frame you never needed to keep.

This is the move I call FEB — Formen Engpass Barriere, a German-language coinage that translates roughly to "shape the bottleneck-barrier." That literal translation undersells what's actually happening grammatically, and the grammar is the whole point. Formen is a verb — "to form, shape, mold." It governs the two nouns that follow it: Engpass, the bottleneck or constraint, and Barriere, the barrier. Read correctly, the phrase doesn't label a subject matter the way "a book about bottlenecks" would. It names an action performed on a constraint — and the action isn't "relieve" or "widen," the narrow-end verbs. It's "reshape the framing that produced it."

Concretely, the FEB move looks like this, and it's the one analytical move in this piece I'll name outright rather than let you infer it: when a solution space collapses down to a single hard constraint, stop optimizing at the constraint and instead walk the causal chain backward until you find the decision that created the funnel shape. Not "why is this hard" — "what upstream framing made this the only shape the problem could take."

In the engine-frame case, the upstream framing wasn't a single decision — it was twenty years of derivative products, each one a small, individually reasonable choice to build on what already existed rather than question whether it still should. Nobody on that Black Belt assignment had signed off on any single decision that trapped the product in that frame. It had accumulated, one derivative at a time, the way most real bottlenecks do. The narrow end was the frame. The wide end was two decades of "just build on the last one" that nobody had been asked to revisit until the customers stopped letting us get away with it.

This is where TRIZ and FEB shake hands but aren't the same tool, and the distinction is worth being exact about since I use both. TRIZ gives you a structured way to resolve a contradiction once you've correctly identified it — the classic forty principles, the contradiction matrix, the discipline of refusing to trade off two requirements that both matter. FEB sits upstream of that. It's the check you run before you accept that the contradiction you're staring at is the real one, or just the shape the funnel happened to take because of a decision three steps back that nobody revisited. TRIZ solves the problem you've named. FEB checks whether you named the right one.

Forensic signature.

The tell that you're solving at the narrow end when you should be at the wide end is almost always the same: the team is very good at the problem in front of them and no better off after solving it. An engineering group that's spent twenty years getting excellent at extending one frame will keep getting better at extending it — right up until the extending stops being enough, and the skill that made them good at the old problem doesn't transfer to the new one.

If you want to catch this pattern earlier than I did, the fastest question you can ask isn't "how do we fix this." It's "who decided this had to be this shape, and were they solving for something we've since stopped needing?" That question does something the narrow-end tools can't: it reopens a decision instead of optimizing inside one.

Aftermath, and a forward prediction.

We found the magic, eventually — and it wasn't the frame. It was a small set of things the frame had happened to enable: a specific handling characteristic, a serviceability trait technicians had come to rely on, a silhouette customers recognized without needing the badge. None of those required the twenty-year-old architecture specifically. They required knowing, precisely, which parts of "the magic" were load-bearing and which parts were just the frame that had been carrying them for two decades because nobody had asked. Once we knew that, the new frame wasn't a betrayal of the old product. It was the old product's actual values, carried by hardware finally capable of doing what the customers had been asking for the whole time.

Here's the forward-looking piece, and it's the reason I'm writing this now rather than filing it away as an old assignment: I don't think this pattern is limited to engine frames, or to engineering teams, or even to hardware. Anywhere a group of smart, disciplined people are working very hard at a well-characterized constraint and not gaining ground, there's a real chance the constraint isn't the problem — it's the residue of a framing decision made one or two steps upstream, by people who've since moved on and have no reason to know it's still costing you. Over the next several pieces, I'm going to walk through that same wide-end move showing up in places you wouldn't expect it — a Cold War propulsion program, a rocket landing on a boat, and the middle of the current EV market correction — because once you've seen the pattern once, it gets hard to stop noticing it everywhere else.

I'd love to hear about the bottleneck you eventually stopped solving by refusing to solve it — the moment you went looking upstream instead of leaning harder on the narrow end. That question drives everything I write here.

Leave a comment

Subscribe now

Herbert Roberts, P.E. is a licensed professional engineer with 30+ years in aviation research and development.

FEB (Formen Engpass Barriere)™ is a pending trademark of Inventor's Mind Press, naming the practice of reframing a problem from the wide end of the funnel — reshaping the framing that produces a constraint, rather than working the constraint itself.