Inventor’s Mind Press

I. The Premise

Fraud is theft. What’s stolen changes — money, identity, citizenship, valor, welfare, admission — but the mechanism stays constant: misrepresentation for gain. By that definition, fraud in America is not rare, marginal, or hidden in any real sense. It is documented, quantified, and published by government auditors every year. What’s actually scarce is prosecution at the level where the money is largest.

This isn’t a story about a few bad actors skimming benefits at the bottom. It’s a story about the machinery that decides which fraud gets pursued, which gets a press release and a plea deal, and which gets protected by the very people whose job is oversight. Small fiefdoms — a corrupt caseworker, a crooked storefront — are the visible, prosecutable layer. They are not the only corruption centers, and treating them as the whole problem is itself part of how the larger problem stays underestimated.

II. The Six Currencies

Money. The Government Accountability Office’s cumulative estimate of federal improper payments since 2003 exceeds $2.7 trillion, with $236 billion flagged in fiscal year 2023 alone. Pandemic-era fraud — PPP loans, unemployment insurance, PPE procurement — is estimated above $200 billion by the Department of Justice and multiple agency inspectors general.

Welfare. Minnesota’s “Feeding Our Future” case is the largest pandemic-fraud prosecution in the country: more than $250 million siphoned from a federal child-nutrition program through a network of shell nonprofits, over 70 people charged. It is the same fraud network independent journalist Nick Shirley’s reporting first drew national attention to before he moved his investigation to California.

Food assistance. The USDA reported roughly $12 billion in SNAP losses in 2024, driven heavily by EBT card skimming — magnetic-stripe cards with no chip, cloned by organized rings including one operating out of Romania. Separately, longtime USDA employee Arlasa Davis was convicted of selling stolen EBT retailer license numbers to co-conspirators, enabling roughly $66 million in fraudulent SNAP terminal access. A Propel survey found more than a third of EBT theft victims never filed a claim because they didn’t know they could.

Identity and citizenship. The Social Security Administration’s Earnings Suspense File — wages reported on W-2s that can’t be matched to a valid Social Security number and name — holds more than $1 trillion in unmatched wages accumulated since the 1930s. Separately, synthetic identity fraud (a real SSN, often a child’s or a deceased person’s, fused with a fabricated name) cost U.S. lenders $3.2 billion by mid-2024, according to TransUnion, up 18% year over year and concentrated in auto lending.

Valor. The original 2005 Stolen Valor Act was struck down by the U.S. Supreme Court in United States v. Alvarez (2012) for criminalizing the lie itself, regardless of gain. The 2013 replacement law survived only by narrowing its scope to lies made for tangible benefit — Congress conceded it could not criminalize false claims of military honors on their own, only false claims used to steal something material.

Merit. Operation Varsity Blues: college counselor Rick Singer ran a $25 million admissions-fraud scheme across at least eight universities — including USC, Yale, Stanford, and Georgetown — using two vulnerabilities: bribed SAT/ACT administrators who corrected answers or substituted test-takers, and fabricated athletic-recruit profiles that exploited a discretionary admissions channel nobody was cross-checking against actual team rosters. Fifty-three people were charged, including actors Lori Loughlin and Felicity Huffman. Legacy admissions and large donor gifts timed to a child’s application cycle are not prosecutable fraud, but they exploit the same discretionary “side door” — institutionalized rather than smuggled in.

III. The Prosecution Gap

Across every category above, enforcement clusters at the bottom. Pandemic fraud task forces pursued individual PPP applicants first — one signature, one bank account, easy to prove in court. Institutional fraud — a network of nonprofits, a healthcare billing scheme, a synthetic-identity ring spanning state lines — requires subpoena power and years of litigation against parties with lawyers and lobbyists. Eleven arrests over $50 million, in the California fraud case that triggered the legislative response discussed below, is a rounding error against a $200 billion pandemic-fraud estimate. It is a countable result, not a structural fix.

The ratio between fraud identified and fraud recovered stays in the low single digits across most federal programs — and that ratio is public. GAO publishes it every year. The fraud isn’t the secret. What happens to it after an auditor documents it is the part that rarely gets fixed, and because prosecutions are so rare relative to the dollar figures involved, most people never develop an intuition for how large the problem actually is. A story about eleven arrests reads as an isolated crime. It is not built to communicate that it represents a fraction of a fraction of what auditors already know is missing.

IV. The Tool Already Exists

The Centers for Medicare & Medicaid Services’ Fraud Prevention System uses predictive analytics on billing data and is credited with hundreds of millions of dollars in prevented payments annually. The IRS’s data-matching models catch more return fraud than manual audits ever could. The Pandemic Response Accountability Committee cross-referenced PPP loan data against death records and duplicate business addresses at a scale no manual review team could match. What independent journalists like Nick Shirley do — cross-referencing public records, spotting duplicate patterns across hundreds of organizations — is a manual version of what automated data matching already does at scale.

The technology to compile, cross-reference, and flag institutional fraud exists and has already proven itself in narrow deployments. The limiting factor is not capability. It is authorization — who is allowed to point which tool at which data, and who is allowed to publish what it finds.

The clearest case of a working cross-check being deliberately narrowed involves Social Security “no-match letters” — notices sent to employers when a W-2’s reported SSN didn’t match SSA’s records. In 2007, the Department of Homeland Security proposed a rule requiring employers to terminate no-match employees within 90 days. Federal courts blocked the rule (AFL-CIO v. Chertoff), and SSA scaled the letters back sharply afterward — not because the underlying mismatch problem went away, but because of the legal and political fallout from trying to act on the data. E-Verify, the newer voluntary alternative, remains optional in most states outside federal contracting. The data that would resolve the mismatch has existed for decades. The enforcement layer built on top of it was constructed, then deliberately weakened.

V. When the Blocker Gets a Bill Number

Disclosure: The following account of California’s AB 2624 relies on public reporting and the plaintiff’s own filed complaint. Nick Shirley’s characterization of the bill’s timing as targeted at him personally is an allegation made in active litigation (Shirley v. Bonta, E.D. Cal., filed September 4, 2026) — it has not been adjudicated, and this section should be read as reporting his claim, not confirming it as legal fact. AB 2624’s supporters, including its author, dispute that characterization and frame the law as workplace-safety protection for immigration-aid workers facing real harassment risk. Both framings are represented below.

The documented sequence:

• January 31, 2026 — Nick Shirley announces on social media that he is in California investigating alleged fraud, following earlier reporting on daycare fraud in Minnesota.

• Early February 2026 — Gov. Gavin Newsom publicly describes scrutiny of the San Diego Somali community as coming from “right-wing provocateurs,” a remark Shirley says was directed at him.

• February 5, 2026 — California Attorney General Rob Bonta holds a press conference calling fraud allegations “reckless, false, outrageous, and ridiculous.”

• February 20, 2026 — Assemblymember Mia Bonta — the attorney general’s wife — introduces AB 2624.

• May 2026 — The bill passes the California Assembly. Republican Assemblymember Carl DeMaio brands it the “Stop Nick Shirley Act.” State Assemblyman David Tangipa tells reporters it would “limit the release of video recordings by independent journalists who investigate taxpayer-funded programs.”

• August 22, 2026 — Newsom signs the bill.

• September 4, 2026 — Shirley, represented by America First Legal Foundation, sues the state, alleging the law is unconstitutionally content-based and viewpoint-discriminatory.

Separately, and in the same general window, the FBI arrested eleven people in connection with roughly $50 million in fraud tied to organizations Shirley’s reporting had scrutinized. The law that followed restricts publication of identifying information about immigration-support-service workers — not the fraud itself, the person identifying who to investigate.

AB 2624’s actual text is narrower than some coverage suggests: it targets publishing personal information with intent to incite imminent harm or induce fear for safety, not investigative reporting generally, and it extends California’s existing Safe at Home address-confidentiality program to a new category of workers. That is a legitimate, separately defensible policy goal. What makes this case study useful is not that the law is obviously illegitimate — it’s that the fifteen-day gap between the attorney general’s press conference dismissing fraud allegations and his wife’s introduction of a bill restricting the person who made them is a documented fact, independent of how the underlying constitutional question resolves.

VI. Sixty Years Is Not Enough Time

If the mechanism for uncovering the truth were simply the passage of time, the JFK assassination files would be fully public. They are not. The 1992 JFK Records Act mandated release and still built in an exemption letting agencies withhold documents the President finds “clearly necessary” to protect intelligence sources and methods — an exemption invoked repeatedly across three decades and multiple presidential release orders, including under President Trump in both his terms.

Martin Luther King Jr.’s FBI surveillance files present a different mechanism with the same effect: many were sealed by court order tied to the original wiretap authorization, with release timelines running past 2027, separate from any congressional records act. That material documents the Bureau’s own conduct — a COINTELPRO-era surveillance campaign built on no legitimate predicate — which is a different kind of institutional exposure than sources-and-methods protection.

Sixty-plus years, an act of Congress, and direct presidential intervention have not been sufficient to force full disclosure in either case. What has moved them, incrementally, has been forcing events — a feature film that shifted political will in 1991, lawsuits, changes in administration — not the calendar. That has a direct bearing on how to think about COVID-19 origins, where the documentary record is only five years old and the UNC records fight (Ralph Baric’s lab, sought by U.S. Right to Know under public-records law and currently before the North Carolina Supreme Court) is still being actively litigated, not five decades along. If sixty years wasn’t enough for JFK, five years should not be mistaken for close to enough for COVID.

VII. Why the Scale Doesn’t Register

Two forces keep the public underestimating how large this problem is, and both are separate from whether the underlying numbers are public.

The first is prosecution rarity itself. When enforcement clusters at the bottom — a caseworker, a corner store, eleven low-level arrests — each case reads to the public as an isolated crime story rather than as a sample from a much larger, already-quantified population. GAO’s $2.7 trillion figure and a local news story about a $50,000 EBT skimming ring live in completely different registers of public attention, even though the second is a rounding error of the first. Small fiefdoms are real and worth prosecuting. They are also the fraud that’s easiest to see, which makes them a poor proxy for the fraud that’s hardest to reach — and treating the visible layer as the whole problem is itself a form of underestimation, whether or not anyone intends it that way.

The second is more uncomfortable to state plainly: institutional and merit-based fraud implicates people and systems the public — and often the people documenting the fraud — would rather not examine too closely. It’s easier to accept a story about a caseworker skimming benefits than a story about admissions offices, licensed lenders, and named administrators declining to act on data they already have. Neither of these dynamics requires bad faith from any individual reporter, prosecutor, or voter to produce the effect. The scale stays invisible not because it’s hidden, but because the visible cases are the ones that get told, and the larger cases are the ones people have the least appetite to sit with.

VIII. Opportunity and Fraud Are the Same Detection Problem

Forensically, cost-savings analysis and fraud detection are the same operation run on the same data. Both ask: does this pattern deviate from the expected baseline, and by how much? A system built to find billing inefficiencies in a hospital network is structurally the same system that finds billing fraud in that network. A system built to find undervalued auto-loan risk is structurally the same system that finds synthetic-identity auto-loan fraud. The industry wants one output and not the other, but the underlying detection function doesn’t distinguish — it just surfaces anomalies. What happens next is a human decision, not a technical one.

That framing produces three separate questions, and they don’t have the same answer.

1) Who can find both? The capability already sits inside a small number of institutions: CMS’s Fraud Prevention System, TransUnion and the major credit bureaus, IRS return-matching, and private forensic-accounting practices (the Big Four’s forensic divisions, boutique firms, licensed forensic engineers and CPAs doing after-the-fact reconstruction). Palantir and similar data-integration firms hold government contracts built explicitly to do this kind of cross-referencing at scale. Independent journalists doing manual cross-referencing — Shirley’s model — are the low-budget, human version of the same function. The capability is not scarce. It is concentrated in whoever already has lawful access to the underlying data, which is a much smaller list than the list of people who could technically run the analysis if given access.

2) Who wants to stop that skill set? Not the tool generally — nobody objects to AI finding cost savings. The resistance shows up specifically when the same tool is pointed at an organization’s own books, grant records, or admissions data. That resistance takes different forms depending on who’s exposed: a university restricting access to athletic-recruit and donor records, a state legislature narrowing who can publish identifying information about organizations under investigation (AB 2624’s practical effect, whatever its stated intent), a lab or agency invoking a records exemption years past the point the underlying secret still matters operationally. None of these actors necessarily object to fraud detection as a category. They object to it being pointed at them specifically, and the tools available to slow that down are legal and legislative, not technical — which is why this piece keeps landing on records law and bill numbers rather than on the AI itself.

3) Who will enforce the bad once it’s found? This is the weakest link in the chain, and the one least discussed. A flagged anomaly is not a conviction. CMS’s system prevents payments; it doesn’t prosecute. TransUnion’s synthetic-identity flag protects a lender’s balance sheet; it doesn’t refer anyone to a U.S. Attorney. Enforcement still runs through the same resource-constrained, politically exposed prosecutorial pipeline covered in Section III — DOJ, state attorneys general, agency inspectors general — and that pipeline is the part conflicts of interest can reach directly, as in a state attorney general publicly dismissing fraud allegations weeks before his spouse, a state legislator, introduces a bill restricting the person who raised them. Better detection without a corresponding, insulated enforcement mechanism just produces a longer list of documented, unprosecuted fraud — which is close to the situation GAO’s own improper-payment reporting already describes.

The honest forensic conclusion: AI does not change who wants fraud found. It changes how cheaply and how completely fraud can be found, which raises the stakes on the second and third questions without touching them at all. Detection was never the bottleneck once government-scale systems already existed. Authorization to point the detector, and will to prosecute what it finds, remain exactly as scarce as they were before the tool got faster.

IX. Conclusion

Institutional secrecy that outlives its stated justification does more lasting damage to public trust than a declared adversary ever could, because it corrupts the machinery citizens depend on to hold power accountable. A foreign adversary doesn’t hide that it’s an adversary — opposition is the point, and it can be named, sanctioned, or fought openly. A domestic blocker’s entire function is to make its own existence look procedural: a records exemption, a workplace-safety bill, a quietly scaled-back letter program, a discretionary admissions channel nobody audits.

The tools to close most of the gaps documented here — automated data matching at AI scale, cross-state title and identity databases, existing public-records law — are already built and, in narrow pilot programs, already working. What’s missing in every case in this piece isn’t capability. It’s permission, and the political will to keep the permission in place once it starts finding something.

Leave a comment

Subscribe now

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

Sources

• GAO, Federal Improper Payments, cumulative estimate since 2003 and FY2023 figures — gao.gov

• DOJ, Pandemic Response Accountability Committee and Inspector General reporting on PPP/UI fraud

• U.S. Attorney’s Office, District of Minnesota — “Feeding Our Future” prosecution filings

• USDA, SNAP fraud and EBT skimming loss estimates (2024); U.S. v. Arlasa Davis

• Propel, survey on EBT theft claim-filing rates

• SSA, Earnings Suspense File data

• TransUnion, H2 2024 State of Omnichannel Fraud Report

• United States v. Alvarez, 567 U.S. 709 (2012)

• DOJ, Operation Varsity Blues case filings, District of Massachusetts

• AFL-CIO v. Chertoff, N.D. Cal. (2007), on the SSA no-match rule injunction

• The Daily Signal, Legal Insurrection, Deseret News, Bloomberg Law — AB 2624 reporting, Feb.–Sept. 2026

• Shirley v. Bonta, E.D. Cal., No. 2:26-at-01477, complaint filed 9/4/26

• National Archives, JFK Records Act release history

• U.S. Right to Know, UNC public-records litigation filings

• NAIIC, Fukushima Nuclear Accident Independent Investigation Commission Report (2012)

• Rogers Commission, Report on the Space Shuttle Challenger Accident (1986), Appendix F

This draft is for editorial review. Verify all figures against primary sources before publication, and confirm the legal-disclosure language in Section V with counsel given the active litigation it references.

Competitor noise is your friend. A practical guide to finding an unguarded market, entering it on the right axis, and building an advantage the incumbents can’t catch up to feature-by-feature.

By Herbert “Bert” Roberts, P.E.

This is the companion piece to The 75% Signal, which laid out the forensic case for why mature-market leaders keep missing disruptions aimed straight at them. This piece flips that diagnosis into instructions. If you’re an engineer, founder, or R&D lead looking at a market you don’t yet own, here is the sequence that has worked — checked against real cases, including the ones where it didn’t quite work, because those failures teach the boundaries of the method.

Step One: Target an Oligarchy, Not a Monopoly

People point at monopolies and cry foul. Don’t aim there. A monopoly is a single, unified target with no internal fracture — hard and expensive to dislodge.

An oligarchy of three or more incumbents is a softer target, and it’s softer for a specific, exploitable reason: each incumbent is watching the other two, not you. Detroit’s Big Three benchmarked each other on horsepower and styling. The business-jet flagships — Gulfstream, Dassault, Bombardier — benchmark each other on cabin volume and range. That mutual watching is a standing distraction. They are already spending resources fighting each other for the top spot inside a closed reference frame, which means none of them are spending resources watching the ground underneath all three of them at once.

Don’t aim at the bullseye — the metric the three of them are already fighting over. Aim just off-center, at whatever axis none of them are competing on, and their internal competition becomes your cover. Competitor noise is your friend: the louder they fight each other, the less attention is left over to notice you.

Diagnostic: find a market with three or more incumbents locked in a visible pecking-order fight. That fight is the signal you’re looking at a viable target.

Step Two: Define the Solution Set for the Neglected-Not-Exhausted Technologies

This is the whole consult in one sentence. If you only ever say one thing to a CEO, say this: define the solution set for the neglected-not-exhausted technologies. Everything else in this playbook exists to get you to the point where you can act on that sentence correctly.

Once you’ve found your oligarchy, identify what they’re no longer competing on. It’s rarely hidden — it’s usually the thing their current, wealthiest, most vocal customers don’t need, and therefore never ask for.

Here’s the method, not just the instinct:

Map the technology stack. For any oligarchy, break the product down into its ten or so constituent technologies — for business jets: airframe materials, engine efficiency, avionics, cabin pressurization, noise reduction, crew-requirement architecture, fuel economics, manufacturing process, certification pathway.

Rank by competitive investment, not by importance. Order the ten by how much visible R&D attention, marketing emphasis, and patent activity the incumbents are currently pouring into each — not by what matters most to the end customer. The top two or three are where the oligarchy is fighting itself (cabin volume, digital cockpit). The bottom half is where nobody’s racing anymore.

Split the bottom half into exhausted versus neglected. This is the filter that separates real opportunity from a dead end. Some low-ranked technologies are low-ranked because they’re genuinely solved — correctly abandoned, nothing left to find. Others are low-ranked only because the current customer doesn’t value them, not because the technology itself is tapped out. Crew-requirement architecture was a bottom-ranked technology in the business-jet flagship segment — not because it was solved, but because the flagship buyer doesn’t care about crew cost. That’s neglect, not exhaustion, and there’s a buyer waiting on the other side of it.

Define the solution set for what’s neglected, not what’s exhausted. This is where outside-discipline thinking earns its keep — cross-domain analogy, TRIZ contradiction resolution, adjacent-industry patent scanning — applied specifically to the technologies your ranking just proved are viable but unattended.

Detroit’s buyer wasn’t asking for reliability in 1965; they got it from brand loyalty instead. Gulfstream’s buyer isn’t asking for lower crew cost; they’re not price-sensitive at $75 million. The unaddressed layer isn’t a secret — it’s simply invisible from inside a measurement system built around the current customer.

Diagnostic: build the ten-technology ranking for your target oligarchy. Anywhere the bottom half is neglected rather than exhausted is your entry point.

Step Three: Check Where You Are on Your Own Curve

If you’re already inside an industry, this step applies to you directly: track the marginal-return curve on whatever technology or process your own organization currently leans on. Below roughly 75% of its practical ceiling, keep pushing it — real, comparatively cheap gains are still available there.

Past 75%, treat that as a standing trigger, not a warning to note and move past. Field a second effort, staffed and resourced independently from the first, whose only job is finding a different curve to climb — one starting near zero, where the first cheap gains are still on the table.

Diagnostic: if your organization’s core technology hasn’t meaningfully improved per R&D dollar in the last several cycles, you’re likely past the threshold and should already have a second team looking elsewhere.

Step Four: Recruit From Outside the Industry’s Gene Pool

Once you know which curve you’re climbing, staff it deliberately from outside the incumbents’ own talent pool. Don’t hire from the stagnant companies. Their veterans are the people most thoroughly trained not to see what you need them to see — every instinct they bring in is calibrated to the paradigm you’re trying to escape.

HondaJet’s lead designer, Michimasa Fujino, came from automotive aerodynamics and NASA computational fluid dynamics research, not a career inside the business-jet industry. Southwest’s founder, Herb Kelleher, was a lawyer, not an airline executive. Richard Branson entered aviation with no background in it at all — his own team called the barriers to entry immense, and he crossed them anyway, precisely because he wasn’t carrying the industry’s own assumptions about what an airline had to be.

Location matters the same way talent does. Honda built its aircraft headquarters in Greensboro, North Carolina — not Wichita, the established aviation cluster with all its shared talent, suppliers, and inherited assumptions. The same company built its first major U.S. auto plant in Marysville, Ohio, not Detroit. Proximity to an established industry cluster imports that industry’s thinking by osmosis, through hiring, informal socializing, and the quiet sense of “how it’s done.” Distance protects your team’s ability to think differently before day one.

Diagnostic: if your founding or leadership team has deep tenure inside the industry you’re trying to disrupt, you likely need outside voices before you start, not after.

Step Five: Solve the Must-Be Layer First — Completely, Not Minimally

This is the step most new entrants get wrong, and it’s the one that determines whether the whole effort survives contact with the market.

Win on basics first. It changes a buyer’s mind faster than any delighter can, because a must-be attribute removes a reason to say no, while a delighter only adds a reason to say yes — and removing doubt is always faster than building enthusiasm, especially for an expensive or unfamiliar purchase.

More than that: delighters lose their impact entirely if the basics are wonky. A gorgeous product built on a shaky foundation doesn’t read as luxury — it reads as compensation, and it actively erodes trust rather than building it. Japanese automakers understood this instinctively: engine and transmission reliability came first, styling and luxury trim came only once reliability was no longer in question. HondaJet followed the identical order — the over-the-wing engine mount, composite fuselage, and laminar-flow wing were all proven over a decade of real flight hours before the company asked regulators and buyers to trust a single-pilot, transcontinental-range aircraft.

Southwest Airlines is the clearest low-cost version of this principle, and it’s the case worth studying if you don’t have Honda’s decades or budget. A single aircraft type, ten-minute turnarounds, point-to-point routing — pure operational discipline, no novel engineering required, executed more completely than any incumbent running a mixed fleet and hub-and-spoke network was willing to match. Only once that cost and reliability foundation was bulletproof did Southwest add its modest delighters: free checked bags, flexible changes, no change fees.

Diagnostic: before you spend a dollar on anything a customer would call “delightful,” ask whether the fundamental a skeptical buyer would check first is not just adequate but demonstrably, provably better than the incumbent’s. If it isn’t, that’s where the next dollar goes.

Step Six: Know Which Kind of Disruptor You’re Being

Not every entry requires solving new physics. There are two distinct paths, and picking the wrong one for your situation wastes the advantage the first five steps built.

The engineering disruptor has to solve a hard, unsolved technical problem before anything else — HondaJet had no existing airframe paradigm to borrow, so proving the fundamentals wasn’t optional. This path takes longer and costs more, but the resulting advantage, once built, tends to compound across several interdependent technologies at once rather than a single metric — which is what makes it hard for an incumbent to catch up feature-by-feature. A five-point simultaneous lead isn’t chaseable the way a single-point lead is, because the improvements are load-bearing on each other; catching up requires re-deriving the whole architecture, not patching the old one.

The experience disruptor borrows technology that’s already solved elsewhere and wins purely on delivery. Virgin Atlantic didn’t need to invent jet engines — those were mature, off-the-shelf technology by 1984 — so Branson could win entirely on service and experience from day one, because the hard physics problem had already been solved by someone else decades earlier.

The failure mode to watch for is applying the experience-disruptor playbook to a problem that actually required the engineering-disruptor playbook. Virgin Galactic is the clean cautionary case: two decades of brand-building and ticket deposits sold around a vehicle whose core engineering — safe, repeatable, commercially-cadenced spaceflight — still wasn’t solved. The delight came first and came loud; the fundamentals are still catching up to the marketing years later. Virgin Cola and Virgin Cars are smaller versions of the same mistake — brand and delight applied where there was no real structural gap underneath to protect the bet once the excitement wore off. Branson himself later acknowledged misjudging where the actual disruption opportunity in the auto industry was — it was in propulsion, not in how cars were sold.

Diagnostic: ask honestly whether the technology underneath your idea is already mature and solved somewhere else, or whether you are the one who has to solve it. If you’re not sure, assume you have to solve it — the engineering-disruptor path is the safer default, because it’s recoverable from over-delivery on fundamentals in a way the reverse mistake isn’t.

Step Seven: Enter Small, Stay Below the Alarm Threshold

Don’t launch where the incumbents are already looking. HondaJet’s Very Light Jet segment shares almost no customer overlap with Gulfstream’s or Dassault’s ultra-long-range flagship buyers — so strong growth there simply doesn’t register on the incumbents’ instruments. Southwest launched with three Texas cities, not a national challenge. Both waited to prove the model somewhere too small to trigger a response before climbing toward the incumbents’ own territory.

Diagnostic: if your launch plan would immediately show up on an incumbent’s competitive radar, you’re entering too big, too early, or too close to their existing customer base.

Close

None of this requires being smarter than the incumbents. It requires picking a target with an internal fracture already built in, finding the layer their own success has trained them not to watch, staffing outside their gene pool, solving that layer completely before chasing delight, knowing honestly which kind of disruptor you are, and starting small enough that their competitor noise covers your entry instead of drowning you out.

The companies at the top of the S-curve aren’t beatable by matching them. They’re beatable by not fighting them at all.

Leave a comment

Subscribe now

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

References

• See The 75% Signal for the full source list underlying the HondaJet, Detroit, and business-jet-flagship cases. Additional sources for this piece:

  • ResearchGate, “Case Study: Southwest Airlines Strategies”

  • Simple Flying, “How Southwest Pioneered The Low Cost Carrier Model”; “Why One Of The World’s Biggest Airlines Bet Its Future On A Single Aircraft Family”

  • PortersFiveForce.com, “Brief History of Southwest Airlines Company”

  • CNBC, “Virgin Group: Richard Branson’s companies from records to space travel,” 2019

  • CNBC, “Richard Branson, who never liked cruising, looks to disrupt the industry with Virgin Voyages,” 2021

  • Strategy+Business, “How Richard Branson Works Magic,” 1998

  • Kritarth’s Substack, “The History of Virgin Atlantic”

  • AMW Business Group, “Richard Branson’s Business Empire: Virgin’s Global Success,” 2026

  • Virgin Galactic Holdings, Q1 and Q2 2026 financial results and business updates

  • StockTi, “Virgin Galactic Advances 2026 Flight Plans Amid Narrowed Loss and Cash Concerns”

Three items from this week’s aerospace-and-composites news form a single narrative, and it isn’t really about aerospace. The University of Maine launched 3Dirigo X, a 30-foot fiber-reinforced thermoplastic boat designed for offshore operation near 40 knots — the latest step in UMaine’s large-format composite-printing program. Continuous Composites, under a U.S. Air Force contract, is building anisotropic finite-element analysis that reads actual fiber-orientation toolpaths so designers can predict a printed part’s performance before it’s ever tested. And Virtek’s new Iris AI system inspects composite production in real time, flagging foreign-object debris and backing-paper defects with a traceable digital record, in under three seconds.

Put those three together and you get a coherent digital thread: design intent flows into a toolpath, the toolpath is simulated with real fiber-orientation data instead of an isotropic-metal approximation, and the resulting part is inspected and logged as it’s built. That thread is what makes large-format composite manufacturing viable at all — you cannot certify a printed structure on faith, and these three developments are, together, the emerging evidence base that lets you certify it on data instead.

What the digital thread actually buys you

The direct benefits are the ones everyone in the industry is already talking about: lower delivery cost, shorter production duration, and a much higher ceiling on customization. A large-format printer doesn’t care whether it’s printing the same hull a thousand times or a slightly different hull every time — the cost curve that used to punish one-off and small-batch composite work is flattening. That’s genuinely good news for anyone who wants a vessel, a component, or a structure built to a specific spec instead of settled for off a shelf.

But customization and speed are only half the economics. The other half is what happens after delivery, and that’s where this digital thread runs out of road.

The valuation problem nobody’s solved yet

Large composite structures already carry a working-value curve that declines faster than most owners expect, and — unlike a metal hull or airframe — they typically have little to no salvage value once that curve bottoms out. There’s no scrap-composite market doing for a printed thermoplastic hull what a scrap-metal market does for an aluminum one. When the useful economic life ends, it largely just ends.

Now add high-customization manufacturing on top of that declining-value curve. Insurance valuation depends on being able to place a given unit within a class — comparable builds, comparable materials, comparable failure history — so an underwriter can price risk against something with a track record. Large-format composite printing is explicitly working against that assumption. If every hull off the printer can legitimately differ from the last one — different fiber orientation, different infill strategy, different print run — then “class” stops being a clean category. You’re not insuring a model. You’re insuring an individual, and individuals don’t have actuarial tables.

This isn’t a hypothetical for the forensic side of the business, either. When a large composite structure fails and the dispute is about value — total-loss determinations, diminished-value claims, subrogation — the digital thread that Continuous Composites and Virtek are building is exactly the evidence an investigation would want: the actual toolpath, the actual fiber orientation, the actual inspection log for that specific unit, not a generic spec sheet for the model. The manufacturing side is racing ahead to generate that evidence. The insurance and valuation side hasn’t caught up to asking for it yet.

What the scrap and insurance numbers already show

None of this is theoretical for fiberglass boats — the mid-to-small sail and power boat market is already living the negative-value half of this problem. Fiberglass hulls have essentially no scrap market: the resin-and-fiber matrix that makes them strong is exactly what makes them nearly impossible to separate into reusable material, so recyclers and salvage yards routinely pay nothing for a hull and often won’t take one at all. Disposal runs roughly $200–$500 a foot depending on size and condition, which means an aging fiberglass boat doesn’t decline to zero value — it declines through zero into a liability the owner has to pay to be rid of. That’s the endpoint large-format composite printing is racing toward for a much wider range of hull types, faster.

The insurance side already has two different tools for this, and the gap between them is the whole story. Actual Cash Value policies price a total loss off comparables — NADA, the BUC Used Price Guide, the ABOS Marine Blue Book — which only work if enough directly comparable units exist to build a market price from. Agreed Value policies sidestep that by having the owner and insurer settle a figure up front, but insurers increasingly require a fresh marine survey to keep that agreement current as the boat ages, which is itself an admission that the agreed figure decays without new evidence behind it. High-customization printing doesn’t break either tool outright, but it starves the ACV comparables approach of the very thing it needs — a big enough pool of matching units — and pushes more of the market toward Agreed Value, survey-by-survey, unit-by-unit.

Why this stays a big-boat story for now

There’s a practical ceiling on where this economics currently makes sense, and it’s worth being blunt about it: it’s very hard to make this manufacturing advancement pencil out for anything smaller than a twin-diesel-turbo-class commercial boat. Large-format printers, anisotropic FEA tooling, and real-time inspection infrastructure are capital-intensive systems built around production volume and part value high enough to justify them. A recreational hull at the smaller end of the market doesn’t carry enough per-unit value to absorb that infrastructure cost, and it doesn’t run at a volume that spreads the capital cost thin enough either. UMaine’s own program has scaled from a 25-foot boat to a 30-foot one — not toward smaller craft, toward larger ones — which tracks with where the economics actually work.

That scale ceiling matters for the valuation problem, too. A twin-diesel-turbo commercial vessel already operates in a world of individualized survey, individualized insurance underwriting, and individualized maintenance records — the industry is somewhat used to treating each unit as its own case. Push this manufacturing approach down toward recreational-class boats, where insurance has always leaned on standardized classes and blue-book-style valuation, and the mismatch between “every unit is legitimately unique” and “here’s the standard value for this model” gets a lot more visible, a lot faster.

Small craft aren’t uniformly exposed to that mismatch, though, and it’s worth naming the exceptions. Boston Whaler, kayaks, and personal watercraft may be the small-craft categories least affected — but each is insulated for a different reason, not because they’re small. Whaler’s foam-core Unibond hull has been built to the same standardized process across decades of production runs; despite being fiberglass, that consistency gives it a deep, well-populated NADA and BUC comparable set, which is exactly what lets it retain value the way most fiberglass boats don’t. Kayaks sit at the opposite end: rotomolded polyethylene commodity items, cheap enough that most insurers just cover them under a flat homeowner’s-policy rider instead of a surveyed marine valuation — there’s no comparables problem because there’s no individualized valuation happening in the first place. Jet skis and other PWCs are standardized, mass-produced units with their own NADA and J.D. Power guides, the same model as cars. None of these three categories is where large-format, high-customization composite printing is headed, so none of them inherit the valuation problem — but that’s a statement about what stays standardized, not about what stays small.

There’s a mirror-image exception worth naming too: APBA-class powerboat racing may be the one small-craft segment actively looking forward to this shift rather than being insulated from it. Racing hulls already live in an F1-car world — class rules bound the envelope, but within that envelope every hull is expected to be a distinct, optimized, one-off build, and nobody in that world is pricing a race boat off NADA comparables in the first place. Valuation there already runs on team assets, sponsorship, and performance history rather than a resale blue book. Large-format printing and fiber-orientation-aware FEA are a natural fit for that market precisely because it never depended on the standardized-class insurance model the rest of recreational boating is built on — it’s the one place where “every unit is legitimately unique” isn’t a valuation problem to solve, it’s the whole point.

That same push is likely to force safety technology into much higher visibility inside APBA racing, the same way it did in Formula 1. Once hulls are being individually optimized rather than built to a common standard, the class rules that used to implicitly constrain crash behavior stop doing that job — each one-off optimization is a fresh, unverified structural case until it’s proven otherwise. F1’s answer to that same pressure was a decades-long, highly public arms race in crash structures and driver protection running alongside the performance gains. APBA racing is a plausible candidate to go the same way, and the specific hardware is already recognizable from offshore powerboat racing today: enclosed, capsule-style cockpits for driver protection, flaps engineered against submarining (the bow digging in and burying the hull rather than skipping over the water), and blow-off panels meant to vent or shed structure if a hull goes airborne rather than let it flip and tumble. Each of those is exactly the kind of feature that a one-off optimized hull can’t simply inherit from a class standard — it has to be individually validated. The more individualized the hulls get, the more the safety case has to be made per-hull rather than inherited from the class, and that’s exactly the kind of evidence — fiber-orientation-aware FEA, inspection-logged builds — the digital thread is already positioned to generate.

The open question

The composite manufacturing story this week is genuinely a good one: design, simulation, and inspection are converging into a real digital thread, and that thread is what makes certifiable large-format composite production possible at all. But a digital thread that ends at the inspection stamp isn’t finished — not for an asset whose value declines fast, salvages for nothing, and increasingly can’t be grouped into a class. The manufacturing side has built the evidence. Nobody’s yet built the valuation model that knows what to do with it.

Sources: CompositesWorld on UMaine’s 3Dirigo X, Continuous Composites’ anisotropic FEA (USAF TACFI contract), and Virtek’s Iris AI Composite Inspection; fiberglass boat disposal cost and salvage-market reporting from Practical Sailor, Professional BoatBuilder/IBEX, and Virginia DEQ; boat insurance Agreed Value/Actual Cash Value practice from marine insurance industry guides; Boston Whaler resale-value and Unibond hull-construction reporting; NADA/J.D. Power personal watercraft valuation guides.

Leave a comment

Subscribe now

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

TRIZ has a technical trend that doesn’t get talked about as much as the more famous ones — ideality, dynamization, the S-curve itself — but it’s arguably the one that governs all of them: systems evolve toward increasing complexity first, and only later toward simplification. You add subsystems, functions, and operating modes to squeeze more performance out of a design, the system gets objectively more complicated, and it stays that way for a long time — until enough of those additions turn out to be redundant, or get integrated, or get trimmed outright, and the system snaps back to something simpler that does the same job with fewer parts. The mistake people make is assuming simplification is right around the corner just because complexity has started to feel excessive. It isn’t. The complexity phase usually has to run its full course first.

This week’s aerospace news handed me four live examples of the growth half of that trend, all converging on the same TRIZ move at once: hybridizing the operating environment. DLR’s HAP-Alpha demonstrator is going after the lower stratosphere as a distinct regime — not quite aircraft altitude, not quite satellite altitude, an environment of its own. Singapore’s NTU flew scaled eVTOL demonstrators that hover, fly fixed-wing, transition between the two, and hand off between remote and piloted control — stacking flight regimes and control regimes on the same airframe. GE’s HyCAT pairs a solid-rocket boost phase with a liquid-fueled dual-mode ramjet cruise phase on one air-launched vehicle, combining two entirely different propulsion physics in a single flight profile. And Regent’s Viceroy is a boat, a hydrofoil, and a wing-in-ground-effect aircraft depending on what speed it’s doing — three operating environments, one hull.

Naming the moves

If you’re working the classic TRIZ inventive principles, all four of these read as combinations of the same handful of moves:

• Another dimension — DLR’s lower stratosphere and Regent’s ground-effect layer are both new operating dimensions carved out between existing, well-understood regimes.

• Merging — GE’s HyCAT merges rocket and ramjet propulsion into one vehicle; NTU’s eVTOL merges rotorcraft and fixed-wing aerodynamics into one airframe.

• Transition to a new environment — Regent’s Viceroy physically changes environments mid-mission: water, then foil-borne transition, then ground-effect flight.

• Dynamization — NTU’s BVLOS-to-piloted handover is dynamization applied to the control system, not just the airframe: the system reconfigures its own operating mode mid-mission.

That’s four different programs, four different companies, and one shared strategy: instead of optimizing a vehicle for a single environment, stack multiple environments and modes onto one system and manage the transitions between them.

Why this is the complexity phase, not the simplification phase

None of these four programs is anywhere close to a mature, converged architecture. Each one is still in the stage where the industry is throwing every plausible combination at the wall: different propulsion pairings, different transition mechanisms, different control-handoff schemes, different structural approaches to surviving multiple environments in one airframe. That’s what the growing-complexity trend looks like from the inside — not one company settling on the right hybrid architecture, but several companies exploring different hybrid architectures for what will eventually turn out to be the same underlying market need.

That’s also why I’d put this case roughly a decade out from reaching its simplification phase. The TRIZ pattern for this kind of S-curve isn’t “complexity rises, then falls” on some fixed clock — it rises until the combinatorial space has actually been explored, which means enough failed variants, enough regulatory friction discovered the hard way, and enough operational experience banked that the industry can see which of the many stacked options are actually pulling their weight and which ones were added because nobody could yet prove they were unnecessary. Regent’s own program history is a preview of that cost: a prototype hydrofoil failure, a ten-and-a-half-month investigation and repair, and a deliberately incremental return to flight — that’s exactly the kind of expensive lesson that eventually gets folded into a simpler, more confident architecture, but only after it’s been paid for once.

Ten years is roughly the timeframe it takes an S-curve to go from “several competing hybrid architectures, each adding complexity to solve a different piece of the problem” to “one or two architectures that have shed the options nobody needed, converged on a small number of proven transition mechanisms, and standardized enough that safety cases and insurance/certification frameworks can be built around a class instead of a one-off.” Right now, DLR, NTU, GE, and Regent are all still in the phase of adding options to the curve. The simplification phase will look like the survivors trimming most of those options back out.

What to watch for as the signal

The tell that this case study has entered its simplification phase won’t be a single dramatic breakthrough — it’ll be quieter than that. Watch for: a shared transition mechanism appearing across competitors instead of each company running its own proprietary approach; a control-handoff standard that regulators start requiring instead of merely allowing; and, most tellingly, at least one of these four programs quietly dropping a hybridized mode it originally announced, because operational experience showed it wasn’t earning its complexity. That last one is the real signature of the TRIZ trend completing its cycle — not new capability being added, but a capability that was added during the growth phase getting removed once the system could prove it didn’t need it.

Why this is also why second-to-market usually wins

That inversion — a mature system is defined by what it removed, not what it added — explains a business pattern that looks like a coincidence until you see it through this lens: why the company that enters second, or third, often ends up owning the market the first mover created. The first mover doesn’t get the complexity phase wrong; it gets it first, which means it pays full price for every combinatorial option that turns out not to be load-bearing. It ships with every hedge still attached, because at launch nobody can yet prove which hedges are unnecessary. The second mover gets to watch that process happen in public, for free, and enter with a design that’s already been trimmed down to what the market actually needed — arriving closer to the simplification end of the curve instead of starting the complexity climb from zero.

That’s not a story about the second mover being smarter. It’s the same TRIZ trend running on a compressed clock: the first mover absorbs the ten-year complexity phase in real time and real dollars; the second mover imports the lesson and skips straight to something closer to the trimmed, converged architecture. Whichever of DLR, NTU, GE, or Regent turns out to be first-to-market with its particular hybridization approach should expect exactly this dynamic — not to lose to a better idea, but to eventually lose to whoever watches its own field data long enough to know what to leave out.

The PC industry ran this exact sequence twice in a row, back to back, and it’s worth having on hand as proof the pattern isn’t limited to aerospace. IBM pioneered the personal computer in 1981 and, within two years, commanded roughly 42% of the market — but it got there by building out a full indirect infrastructure: a national reseller and distributor network, complex channel agreements, all the overhead a first mover accumulates while nobody yet knows what’s load-bearing. Compaq entered that same indirect-channel world and, by the early 1990s, had trimmed enough of IBM’s overhead to take the lead itself. But Compaq’s own growth phase kept adding complexity right back — including a costly DEC acquisition — while it tried to match a newer, leaner competitor. Dell, entering later still, stripped the model down to build-to-order and direct sales, cutting channel costs to roughly 2% of revenue against an indirect-model cost of 13.5–15.5%. Dell passed Compaq as U.S. sales leader in the third quarter of 1999 and took the global top spot the following year. Three companies, one market, and the same lesson repeating twice: each successive entrant won not by adding more than the last leader, but by correctly identifying what the last leader was still carrying that it no longer needed.

The auto industry has been running the identical three-generation sequence, just on a longer clock. Detroit’s Big Three built market dominance on mass production, but their answer to rising demand for more models and more options was to add complexity everywhere — larger, faster tooling; longer part routings; increasingly sophisticated materials-requirements-planning systems to manage it all. Toyota’s answer, developed out of postwar necessity, was the opposite move: the Toyota Production System stripped that complexity back out through just-in-time flow and systematic waste elimination. Toyota passed Chrysler in global volume in 1994, passed Ford in 2003, and passed GM in 2008 to become the world’s largest automaker — the same trimming-the-hedges pattern as Dell overtaking Compaq, just running across manufacturing floors instead of sales channels.

Now watch the third generation start the same way. China overtook Japan as the world’s largest vehicle exporter in 2023, and BYD passed Tesla as the top global EV seller in 2024 — and the mechanism is, again, trimmed complexity rather than added capability. An EV drivetrain is mechanically simpler than an internal-combustion one by design, fewer moving parts, fewer subsystems to integrate. BYD compounds that simplification with vertical integration — it builds its own batteries, its own chips, even owns lithium mines and car-carrier ships — removing an entire layer of external supply-chain complexity that both Detroit and Toyota still carry. Whether that makes China the Dell of this cycle or just the next Compaq waiting for someone leaner is exactly the open question the TRIZ trend predicts you should be asking. The pattern doesn’t say the current leader is safe. It says the current leader is carrying something the next entrant hasn’t found yet — and that’s worth watching for, not betting against.

Sources: Aviation Week on DLR’s HAP-Alpha; AIN on NTU’s eVTOL demonstrators and Regent’s Viceroy; GE Aerospace and Breaking Defense on the HyCAT hypersonic testbed; PC-industry channel-cost and market-share history from IDC/Gartner-sourced reporting on the Dell/Compaq/IBM sequence; automotive market-share history on Toyota vs. the Big Three and China/BYD vs. Japan from industry and trade-press reporting (Nikkei Asia, Bloomberg, Lean Enterprise Institute).

Leave a comment

Subscribe now

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

There’s a moment in every forensic engineering case — and in every good accident investigation — where the temptation to know outweighs the discipline to wait. You have a failed part, a damaged aircraft, an injured party, and a client or a public that wants an answer now. The engineer’s job is to resist that pull long enough to build the case properly.

I call the discipline the evidence ladder. It has five rungs, and you don’t skip any of them:

1. Observation — what physically happened, documented without interpretation

2. Exclusion — what can be ruled out, and on what basis

3. Event sequence — the order in which things occurred, established from data, not narrative

4. Contributing factor — what made the event possible or worse

5. Final cause — the conclusion, reached only after the first four rungs are solid

This week’s aviation news handed me four live examples of engineers and investigators working this ladder in public, at different rungs, with different levels of caution. They’re worth walking through together, because the differences are instructive.

Rung 1–2: Preliminary data, held at arm’s length

The NTSB’s update on the September 6 Boeing 767 runway excursion at Miami — 21 Air Flight 7598 — is a textbook example of Rung 1 discipline. The Board released preliminary cockpit-voice-recorder and flight-data-recorder information, and it went out of its way to flag that the timing and descriptions remain preliminary and unsynchronized.

That caveat is not boilerplate. It’s an engineering statement. Raw CVR and FDR data before synchronization is a pile of timestamped observations, not yet an event sequence. You can see things happened. You cannot yet say in what order, and you certainly cannot say why. The NTSB is sitting on Rung 1, publishing what it has, and explicitly refusing to climb higher until the data lets it.

The NATS investigation into the UK air-traffic-control disruption is doing something similar at Rung 2. NATS said it did not believe a cyberattack was responsible — that’s an exclusion, not a conclusion. It narrows the causal tree (software failure, hardware failure, operational-resilience gap, external threat) without yet claiming to know which branch is correct. Good forensic practice: rule out the sensational hypothesis early if the evidence supports it, but don’t let ruling one thing out feel like ruling something else in.

Rung 3–4: Root-cause pathways, made operational

The FAA’s three new airworthiness directives this week are further up the ladder, because each one already encodes an established event sequence and contributing factor — and converts it into a control.

• AD 2026-18-03 addresses tool-mark damage in A320-family main-landing-gear support-rib lugs. Contributing factor: a manufacturing/handling process introduced damage that wasn’t part of the original design intent.

• AD 2026-17-09 addresses missing chamfers under critical A350-1041 pylon fasteners. Contributing factor: a tool-control or manufacturing-spec gap — a geometry detail that should have been present wasn’t.

• AD 2026-18-01 adds repetitive operational tests for ATR 42-500 cargo-compartment ventilation shut-off valves. Contributing factor: maintenance-program drift — a component whose failure mode wasn’t being caught by the existing inspection interval.

What I want you to notice is that these are three different rungs of causal pathway — supplier process, design/manufacturing specification, and maintenance-program adequacy — arriving at the same kind of output: an inspection, a life limit, or a repetitive test. That’s the whole point of the evidence ladder. You don’t need every root cause to look alike. You need every root cause to be traceable back to evidence, and you need the fix to match the actual failure mode, not a generic one.

The Trap Above the Ladder: Correlation Is Not a Rung

There’s an old standard worth repeating until it’s boring: correlation is not the leading note in forensic work, cause is. It’s tempting to treat a pattern of similar-looking incidents as if the pattern itself were the finding. It isn’t. The pattern is a question, not an answer.

The same discipline applies to how you handle a single anecdote inside a big-picture trend review. Citing one dramatic incident while you’re surveying broad trends is a guideline violation, not a rhetorical flourish — it lets one vivid case quietly stand in for a statistical claim it can’t support.

The harder question sits underneath both of those: how do you know today’s issue is actually related to something that happened five weeks ago, or five months ago? That’s the trifecta of grouping — you’re implicitly claiming a shared cause across time, and you have to earn that claim with a grouping variable, not a gut feeling.

Take AD 2026-18-03, the A320-family main-landing-gear support-rib tool-mark damage, as the working example. The AD itself already names the fix — inspect for the damage, repair or replace as needed. But “tool marks” as a bare fact is not enough to pass judgment on what produced them, and the AD doesn’t have to settle that to do its job. The scope question — is this one aircraft, one operator, one manufacturing run, or the whole fleet — is a separate finding, and it depends entirely on what you pair the tool marks with. “Tool marks” is a single visible defect signature — but it can arise from at least three different processes, and each one clusters differently in time and space:

• Manufacturing-induced marks cluster by production date and lot — same tooling, same shift, same supplier batch. If you group the affected aircraft by build date and the marks line up with a tooling change or a specific production run, that’s your causal grouping.

• Repair-induced marks cluster by service event — same MRO facility, same mechanic crew, same repair procedure — regardless of when the aircraft was originally built. Build-date grouping would show nothing here; service-date grouping would show everything.

• Fleet-wide procedural marks cluster by directive or procedure-issuance date across the entire fleet, independent of both build date and repair date, because the common cause is a maintenance instruction or ground-handling practice everyone started following at the same calendar moment.

Same defect, three different clocks. Pick the wrong clock to group by and you’ll either see no pattern where one exists, or manufacture a false pattern where none does.

That’s also where the “none found or 1000 found” problem comes from. Search a case history or a literature base too narrowly and you’ll get zero hits — not because nothing relevant exists, but because you grouped by the wrong variable and missed it. Search too broadly and you’ll get a thousand hits that share only surface keywords, none of which actually share a causal mechanism. Knowing the history — being able to state the relevant facts across a broad range of prior cases — is what lets you pick the grouping variable that produces a meaningful result count instead of an artifact of your search terms.

That search problem gets worse when the search itself is scoped too narrowly by source, not just by keyword. The official record — ADs, NTSB reports, shop work orders — is where most investigations start and, too often, where they stop. Two sources routinely left out are textbooks and community chat boards, and they fail in opposite directions. Textbooks encode the generalized, already-digested failure modes for a class of design — useful as a baseline of what’s known to happen, but slow to update and silent on anything too new or too narrow to have made it into a published edition. Community chat boards — mechanic forums, type-specific owner groups, shop-floor message boards — carry the opposite problem: they’re current and specific, often reporting a pairing fact (which shop, which environment, which batch) years before it reaches an official database, but they’re unfiltered, and treating a forum post as equivalent to a logged finding is its own kind of premature synthesis. Leave either source out and you bias your grouping toward whatever’s easiest to search — official databases — instead of toward what’s actually true.

The evidence ladder gets you to a defensible cause for a single event. Grouping discipline is what lets you defensibly say a cause is shared across events — and it’s every bit as easy to get wrong.

From Outlier to Emerging Trend: The Label Changes Before the Cause Does

Here’s the part that trips people up in practice: the first time a tool-mark case turns up as a root cause, it gets labeled an outlier against whatever large trend you’re already tracking. That’s the correct label at n=1 — but “outlier” is a label, not a fact. It’s a placeholder for “insufficiently paired,” not a verdict. Treating it as a settled fact is exactly the premature-synthesis error the evidence ladder is built to prevent; treating it as a fact-in-waiting, still needing to be paired, is what actually speeds the research up. An outlier paired with the right relevant fact from the start gets resolved fast, one way or the other. An outlier filed away as just “an outlier” sits there doing nothing until someone rediscovers it from scratch.

Finding the outlier is not the finish line — it’s the point where the research widens, not where it stops. Internally, that means checking your own case files, your own shop’s history, your own fleet records for anything that resembles it, paired or not. Externally, it means checking whether the same pattern shows up somewhere you don’t control: other operators, other shops, the manufacturer’s own service bulletins, the textbooks and chat boards mentioned above. Calling something an outlier and closing the file is how a real emerging trend stays invisible for years — the research obligation doesn’t end at the label, it starts there.

But the label has a shelf life, and the trigger that ends it isn’t the raw count — it’s the count paired with a relevant fact. Every finding gets stronger when it’s paired with something outside itself: the operator, the maintenance event, the manufacturer, the operating environment. A bare tool mark is a fact. A tool mark paired with who found it, when, and under what conditions is tribal knowledge. Three quick illustrations of what pairing looks like in practice:

• Pairing with an operator’s procedure. Say Birdway Airlines runs annual heavy checks, and the same tool-mark pattern shows up at every annual on that fleet. That’s not three coincidences — it’s one finding paired with a maintenance-schedule clock. The pattern is telling you to look at Birdway’s annual-check procedure, not at the airframe design.

• Pairing with logged history. Say an outlier repair-shop finding shows up once, gets dismissed, and then shows up again at the same shop eighteen months later. The mistake isn’t missing it the second time — it’s that the first occurrence got filed away instead of logged with the relevant facts: which shop, which mechanic crew, which procedure, which tooling. If that first outlier had been logged properly instead of closed out, the second occurrence would have been an immediate two-count trend instead of a fresh outlier that has to rediscover its own history. And don’t assume the second occurrence is the only other one, either — a repair-based root cause found at one shop is not guaranteed to be the first instance anywhere, or the only shop it’s happened at. It’s just the first one that got paired.

• Pairing with environment. Say Fastair-manufactured business jets keep showing a short service life specifically when the aircraft is based in desert environments — but not elsewhere. That’s a manufacturing finding that only becomes visible when it’s paired with basing location. Judge it on manufacturing data alone and you’d conclude the whole fleet has a service-life problem. Pair it with environment and the finding narrows correctly: it’s a desert-basing interaction, not a universal defect.

These three cases group at very different speeds, and that speed difference is itself worth knowing going in. A fleet-wide or manufacturer-level issue — like the Fastair case — is already centralized: one production lot, one design, one directive, visible across every operator at once. It groups fast, almost by construction. A repair-based root cause is the opposite: it’s scattered across independent shops, crews, and procedures with no central log connecting them, so the same underlying cause can sit invisible for years, one unpaired outlier at a time, before enough of them get logged with the same relevant fact to group at all. Don’t expect a repair-based trend to announce itself the way a fleet or manufacturer trend does — it has to be found, shop by shop, on purpose.

None of these become an emerging trend on tool marks alone. They become one once you’ve paired three or more occurrences against the same relevant fact — same operator procedure, same shop history, same environmental exposure — not just three occurrences that superficially resemble each other. At that point “outlier” stops being the honest word, and the investigation posture has to shift: from “explain away this one case” to “find out how far this pattern already extends.”

The threshold matters because it’s the trigger for going back and re-examining every prior case you’d previously closed out as an unrelated outlier. If you logged the pairing facts the first time — which operator, which shop, which environment — that re-examination is fast and specific. If you filed the first outlier away without them, you’re stuck re-opening everything, because you don’t know which prior “outliers” belong to the same cluster and which genuinely don’t. That’s the real cost of treating an outlier as closed instead of as pending.

Why this matters if you’re not an accident investigator

If you’re an expert witness, a design engineer, or just someone trying to write clearly about a failure, the evidence ladder is a discipline against two very human failure modes:

Premature synthesis — reaching for “here’s what happened” before the event sequence is actually established. The NTSB’s Miami caveat is a model for resisting this. So is NATS declining to speculate about a cyberattack it hadn’t confirmed or ruled out with full confidence.

Padding — manufacturing a conclusion because a report is expected on schedule. This week’s digest deliberately excluded new forensic-engineering court cases and root-cause reports because nothing met the inclusion bar. That’s Rung 1 discipline applied to reporting itself: no new high-confidence evidence, no new conclusion, full stop.

The takeaway for your own case files

Next time you’re building a forensic report — or explaining one to a jury, a client, or a Substack reader — try writing it in five explicit sections, one per rung. Force yourself to write the Observation section using only what a camera or a sensor recorded. Force the Exclusion section to name what you ruled out and why. Only let yourself write “Final Cause” once the first four sections hold up on their own.

It’s slower. It’s also the only way an opinion survives cross-examination — or, for that matter, survives being right.

Sources: NTSB preliminary update on 21 Air Flight 7598 (Miami, Sept 6, 2026); FAA airworthiness directives 2026-18-03, 2026-17-09, 2026-18-01; NATS UK ATC system investigation, FlightGlobal.

Leave a comment

Subscribe now

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

A forensic look at why mature-market leaders keep missing the disruptions aimed straight at them — and the diagnostic signal that would have caught each one in time.

By Herbert Roberts, P.E.

I. The Milestone That Started This

In September 2026, Honda Aircraft Company announced completion of the first wing structure for the HondaJet Echelon test unit — a routine-sounding program update, five wing structures now moving through final assembly, mainline assembly targeted for early 2027. On its face, a manufacturing milestone.

Look closer and it’s stranger than that. This is the same company that, sixty years earlier, entered the American automobile market from the bottom with small, reliable, inexpensive cars while Detroit’s Big Three dismissed the segment as beneath serious competition. Honda is now doing something that rhymes with that move — in a completely different industry, with none of the original people, market conditions, or technology in common.

That’s not a coincidence worth a footnote. It’s evidence of something structural, and this article is the case file for what it is.

II. The Mechanism: S-Curves and the 75% Signal

Every mature technology follows a predictable improvement curve: slow early gains, a steep middle climb, then a flattening top where each additional dollar of R&D buys less and less. This is standard S-curve behavior, well documented in TRIZ methodology and broader innovation theory.

The flattening is the tell. Below roughly 75% of a technology’s practical ceiling, pushing the current paradigm harder is still rational — real, comparatively cheap gains remain available. Past that point, the economics invert: marginal cost per unit of improvement rises sharply while the return keeps shrinking. Continuing to push the same metric past this point stops being optimization. It becomes a symptom.

The diagnostic rule this article uses throughout: once a core technology passes roughly 75% of its exhaustion point, an organization should be actively fielding a second effort whose only job is finding a different curve — one starting near zero, where early gains are still cheap — while the first team keeps harvesting what’s left of the original.

What makes this signal hard to catch in practice is that it’s rarely visible from inside the system generating it. An organization measuring its own progress in the units of its own paradigm has no natural way to register movement on an axis it isn’t instrumented to see. That blindness — not a lack of intelligence, not laziness — is the throughline connecting every case below.

III. Case One: Detroit, 1960s–70s

By the mid-1960s, the American automobile industry was a settled oligopoly of three: General Motors, Ford, and Chrysler, competing almost entirely against each other on horsepower and styling. Each confirmed the others’ priorities were the right priorities simply by being the only other players worth watching. That mutual confirmation functioned as market validation, when it was really shared blindness.

Reliability and fuel economy — genuine must-be attributes for a car buyer — were left largely unaddressed, because the captive, brand-loyal American buyer of that era wasn’t demanding them loudly enough to move the metric incumbents were already winning on.

Japanese manufacturers, Honda and Toyota chief among them, entered from a different axis entirely: durability and operating cost, starting near zero on a curve Detroit wasn’t watching. They didn’t out-style Detroit. They made styling temporarily irrelevant to a growing population of buyers who wanted a car that didn’t need constant repair. By the time the 1970s oil shocks made the gap undeniable, the disruption had already been underway for years.

IV. Case Two: The Business-Jet Flagships, Today

A parallel oligopoly of three exists in ultra-long-range business aviation: Gulfstream, Dassault (Falcon), and Bombardier, each racing the others on cabin volume, quiet, and digital cockpits — Kano’s “attractive quality” dimension — because range and speed have converged into a solved, must-be layer that no longer meaningfully differentiates a purchase decision. The Bombardier Global 8000 and Gulfstream G800 now both offer comparable maximum range in the 8,000-nautical-mile class; further gains there don’t move the needle the way a better cabin does.

The tell that this segment has crossed its own 75% mark is visible in the market’s own language: the Dassault Falcon 10X is explicitly marketed as trading a slice of maximum range for what many consider the finest cabin in the sky — a manufacturer consciously spending its remaining development budget on delight rather than the core performance metric, because the core metric has stopped being cheap to move.

Leadership at both companies reinforces the blindness rather than correcting it. Gulfstream’s president, Mark Burns, joined the company in 1983 as a CAD operator and rose entirely from within over more than four decades. Dassault’s CEO, Éric Trappier, joined Dassault in 1984 straight out of engineering school and has spent his entire career inside the company. Neither profile is a failure of individual talent — both are accomplished, respected leaders. But four decades of promotion within a single institution’s internal logic is a structural way to lose the outside eye needed to notice a different curve rising elsewhere. Nationality is a red herring here — Trappier is French-trained, Burns American, and neither pedigree explains the pattern. Tenure inside one incumbent institution is the more likely variable.

The must-be layer this segment has left unaddressed isn’t a mystery: crew cost and operating economics. None of the flagship makers’ current customers are price-sensitive enough to ask for a fix, so it doesn’t register as a gap from inside their measurement system.

V. Case Three: HondaJet, Now

HondaJet’s own sequence, from certification in 2015 to the Echelon program today, follows the identical two-phase pattern Honda’s automotive division used sixty years earlier: solve the must-be layer completely and visibly first, then climb into delighter-tier attributes only once trust in the fundamentals is earned.

Phase one was pure structural engineering: an over-the-wing engine mount configuration — a genuinely novel structural answer that solved cabin noise and drag simultaneously — a composite fuselage that solved weight, and a natural laminar flow wing that solved aerodynamic efficiency. None of these were about comfort or market expansion. They were physics problems, solved to a standard the existing paradigm hadn’t matched, and proven over a decade of real flight hours.

Phase two, the Echelon, is the climb the fundamentals earned: single-pilot certification for a transcontinental-range aircraft, expanding who can buy and operate the jet without a second pilot’s salary and training overhead. Regulators do not extend single-pilot trust to an airframe without a decade of proven structural data behind it — the sequencing wasn’t a choice, it was the only available path.

The team that built this entered from outside the industry’s own gene pool at every level. Lead designer Michimasa Fujino held an aeronautical engineering doctorate from the University of Tokyo but built his early career in Honda’s automotive aerodynamics and NASA computational fluid dynamics research — not as a career business-jet-industry veteran. The company itself was built outside the established aviation cluster: rather than Wichita — home to Cessna and Learjet, with the shared talent pool and supplier networks that come with it — or an established California aerospace hub, Honda located its aircraft headquarters in Greensboro, North Carolina, chosen for available land, workforce, and airport growth potential rather than proximity to incumbent thinking. The parallel to Honda’s automotive history is exact: the company’s first major U.S. plant was built in Marysville, Ohio, not Detroit.

This is not incidental. Co-locating with an established industry cluster imports that industry’s assumptions by osmosis — through hiring, informal socializing, supplier relationships, and the quiet sense of “how it’s done” that any team absorbs from its surroundings. Physical and disciplinary distance is a way of protecting a team’s ability to think differently before day one, rather than trying to unlearn incumbent orthodoxy later.

The compounding effect of this sequencing is what makes the resulting gap hard to close. HondaJet’s advantages — engine mount, composite structure, laminar wing, weight distribution, resulting fuel economics enabling single-pilot certification — are interdependent, not additive. An incumbent cannot bolt any single piece onto an existing two-pilot, non-composite airframe; the architecture was built around a different set of trade-offs from the ground up. Catching up on one dimension means re-deriving the whole structure, not patching the old one.

VI. Case Four: GE and the Ceramic Matrix Composite Lineage — The Control Case

Every forensic case needs a control, and this one matters because it proves detection alone isn’t sufficient.

GE Research Center’s work on ceramic matrix composites identified a correct answer years before it could be acted on: a clear physics case and cost rationale — higher operating temperature tolerance, longer part life, higher turbine efficiency — long before the fiber supply chain existed at the volume needed, or a manufacturing base existed to produce at scale. This is a technology that read its own 0%-curve signal early and correctly.

What separates this case from Detroit and the business-jet flagships isn’t detection failure — it’s institutional override. A funded, technically sound program still faced cancellation pressure for institutional and political reasons unrelated to the underlying physics. The lesson this case adds to the forensic file: correctly reading the signal is necessary but not sufficient. An organization also has to grant the team that found the new curve permission to act on it, and protect that permission from the institutional forces that default to defending the current one.

VII. The Big Why: Why Detection Fails

Pulling the four cases together, detection failure is not one cause. It’s several compounding failure modes, each structural rather than a matter of individual competence:

Incumbents measure the wrong buyer. Feedback loops run against current, already-captured customers, who by definition never ask for the thing that will eventually displace the incumbent — because they are not the buyer the disruption is aimed at.

Internal incentives reward the wrong axis. Promotion and budget flow toward whoever improves the metric the organization already competes on. Nobody advances a career by flagging a small, currently-irrelevant competitor climbing a different curve.

Entry barriers create false security. Certification costs, capital intensity, and brand trust are real defenses against a frontal assault on the current paradigm. They do nothing against an entrant who makes the current paradigm’s battleground irrelevant instead of attacking it directly.

Insider-only leadership loses the outside eye. Long tenure inside a single institution builds deep expertise and simultaneously erodes the capacity to see that institution’s own blind spot — because the blind spot is built into the institution’s own operating logic.

The disruptor’s early product looks weak on the axis being measured. Early HondaJets, early Toyotas, and early Southwest Airlines flights all underperformed the incumbent on the incumbent’s own chosen metric. That’s not an oversight on the incumbent’s part — it’s the correct reading of incomplete evidence, using a measurement framework built to track only one curve.

Segment distance compounds all of the above. A disruptor rarely enters where an incumbent’s customers already shop. HondaJet’s Very Light Jet segment shares almost no customer overlap with the ultra-long-range flagship buyers at Gulfstream, Dassault, or Bombardier — so strong, visible growth in one segment simply doesn’t register as competitive pressure in the other, until the disruptor matures enough to climb toward the incumbent’s territory.

The synthesis: history repeats because market maturity manufactures the same four ingredients — a fully served buyer, an incumbent optimized to serve that buyer at rising margins, an underserved buyer at the edge willing to accept “good enough” at lower cost, and an outside capability unlock — every time a market matures, regardless of era or industry. Detection fails because the very apparatus built to keep an organization winning today — customer feedback, internal incentives, competitive benchmarking, leadership pedigree — is structurally calibrated to defend yesterday’s definition of winning, which is precisely the axis a real disruption doesn’t compete on.

VIII. The Antidote: Different Thinkers Never Stop Thinking Differently

Honda’s cross-industry repeat is the case that suggests a genuine antidote exists, and it isn’t mysterious. It looks like an organization that never stopped running a second team — hunting for a curve at zero — regardless of which industry it happened to be operating in at the time.

The practical version of this, assembled from the evidence above, is a short checklist any organization could actually apply, not merely aspire to:

• Track the marginal-return curve on your core technology. Past roughly 75% of its ceiling, treat that as a standing trigger, not a warning to note and move past.

• Field a second team explicitly tasked with finding a different curve, staffed independently from the first.

• Recruit that second team from adjacent disciplines and distant geography — not from the industry you’re trying to out-think. The industry’s own veterans are the people most thoroughly trained not to see what you need them to see.

• When a new curve is found, solve its must-be layer completely and visibly before spending anything on delight. A shaky foundation doesn’t just fail to support a delighter — it actively converts the delighter into evidence of misplaced priorities, once the foundation’s weakness becomes visible.

• Expect the resulting advantage to compound across several interdependent technologies rather than a single metric. A single-point lead is catchable by a well-resourced incumbent. A five-point architectural lead usually isn’t — catching up requires starting over, not patching the old design.

IX. Close

The companies that get disrupted are rarely the ones who weren’t smart enough to see it coming. They’re the ones whose own success built the instruments that guaranteed they couldn’t.

Leave a comment

Subscribe now

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

References

• CompositesWorld, “HondaJet milestone reinforces commitment to business jet market advancement,” 2026

• Wikipedia, “Honda Aircraft Company”; “Michimasa Fujino”

• Pursuitist, “HondaJet: Innovation in the Skies, American Jobs on the Ground”

• Forbes, “How The HondaJet Took Flight: An Engineer’s 29-Year Obsession,” 2015

• BNN Bloomberg, “Dassault pitches new jet against Bombardier and Gulfstream,” March 2026

• Jet Members, “Battle of the Flagships: Falcon 10X vs. Global 8000 vs. Gulfstream G800,” June 2026

• The Flying Engineer, “Private Jet Types: Complete Guide,” 2026

• Skies Mag; Crunchbase; Georgia Historical Society — Mark Burns biographical profiles

• Wikipedia, “Éric Trappier”; Dassault Falcon official biography

• Fractional Jet Ownership Insights, “The Best Luxurious Private Jets of 2026”

• ResearchGate, “Case Study: Southwest Airlines Strategies”

• Simple Flying, “How Southwest Pioneered The Low Cost Carrier Model”; “Why One Of The World’s Biggest Airlines Bet Its Future On A Single Aircraft Family”

• CNBC, “Virgin Group: Richard Branson’s companies from records to space travel,” 2019; “Richard Branson...looks to disrupt the industry with Virgin Voyages,” 2021

• Virgin Galactic Holdings, Q1 and Q2 2026 financial results and business updates

• StockTi, “Virgin Galactic Advances 2026 Flight Plans Amid Narrowed Loss and Cash Concerns”

Every research proposal I wrote contained a small act of honesty hidden inside a sentence nobody noticed.

The sentence usually read something like this: “The team will evaluate five candidate approaches and down-select to two leading contenders.”

To a program manager, that line reads as a plan. To the engineer writing it, the line is a confession. It says, in the politest language available, that three of the five ideas are expected to fail, and that those failures are part of the work rather than a detour from it.

The Tightrope

Much of my 32 years in aviation R&D involved high-temperature composites, materials that live inside jet engines at temperatures that would soften most metals. One recurring question was repair. When a part made from these materials gets damaged, can it be fixed, or does it go in the scrap bin at enormous cost?

A repair program would start with five or so ideas in mind. A bonded patch. A filler worked into the damage. Re-infiltrating the damaged zone. A mechanical insert. And the baseline an honest program carries: replace the part and compare the cost. Somewhere inside, there was usually a favorite. Engineers are human, and humans develop hunches and root for them.

The proposal could not say “idea number three is going to work.” Funding organizations want confidence, and research cannot promise it. Proposals walk a tightrope: confident enough to earn the money, honest enough to admit that most roads lead to dead ends.

“Down-select to two” was the balancing pole.

Run the arithmetic on that sentence. Three out of five is 60 percent. A typical proposal quietly budgeted for a 60 percent failure rate.

What makes that job work is a distinction most people never stop to draw. Failing is an event: the test ran, and the answer was no. A failure is what happens when nobody learns anything from the no.

What a Dead End Is Worth

A good researcher is rewarded not because the first guess is always right, but because experience says which “no” to collect first.

A negative result, the experiment that did not produce the hoped-for outcome, is still a measurement. It records something true about how the material and the physics behave. A patch that lets go at temperature marks a boundary. A filler that cracks defines what the part will and will not tolerate. Each one narrows the search.

Even the most humbling result, “this part cannot be economically repaired,” is worth a great deal. That single sentence can stop a company from spending the next five years on the same question.

Add a Method to the Shelf

Some failures are not dead ends at all. They are side doors.

One repair effort targeted damaged coating on a small, local area of a part. The usual way to prepare a spot like that for a masked recoat is abrasive: blast the zone clean and rough it up so the new coating will grab. Abrasive methods are hard to confine to a small area, so the idea was to replace the grit with chemistry. Leach the bond coat out of only the zone that needed repair, and leave behind a clean, prepared pocket ready for the mask and the new coating.

The leach worked. That was the problem.

It knew no bounds. I can’t go into the chemistry, but the behavior is the point. Once started, it kept going, advancing past the edge of the repair zone into coating it was never invited to touch. No chemical antidote could stop it at the line. As a method for local repair, it failed, and no amount of wishing would move it into the “win” column.

Then the result turned over in my hands. A process that refuses to stop is a liability when the goal is a small, surgical repair. That same process is exactly what you want when the goal is to remove everything. The failed spot-preparation method was, in fact, a total-removal method, ready for the day someone needs a part stripped bare.

Lose, then win. The local repair lost. The shop gained a new way to strip a part completely.

The difference between those two outcomes came down to how the failure was labeled. Filed as “local leach: failed,” the result disappears into a drawer. Filed as “bond coat leach: will not stop at a boundary; candidate for full strip,” it becomes a method on the shelf, waiting for the right problem to walk by. Same data, different label. Write down what a method does, not only what it failed to do for you.

Every Day Is an Education

A phrase carried through my whole career: in R&D, every day is an education, but not every day earns an A+.

School trains us to treat grades as the point, and a report card full of A’s signals a student doing well. In a laboratory, a notebook full of nothing but A’s should make you nervous. It means one of two things: the problems were too easy, or someone is fooling themselves. Real exploration produces C’s and D’s, and the C’s and D’s are where the density of learning is highest.

The B-minus quiz tells you what to study. The failed test specimen tells you where the physics pushed back.

Where Failures Go to Disappear

Successes get written up, which means reports, patents, conference papers, and promotions. Failures get a shrug and a shelf, and too often it is the wrong kind of shelf. Scientists have a name for this: the “file drawer problem,” a term psychologist Robert Rosenthal coined in 1979 for studies with unremarkable results that never leave the researcher’s desk.

In industry, the file drawer runs even deeper. The engineer who knows why approach number four failed carries that knowledge in memory, not in a database. When that engineer retires, the knowledge retires too. Five years later a bright new team proposes approach number four, spends the budget, and rediscovers the same dead end.

That is the most expensive kind of failure: the one already paid for once.

Negative results are the most perishable form of tribal knowledge, because nobody schedules a meeting titled “Things That Didn’t Work.”

Why This Matters Outside the Lab

No lab coat is required to run experiments. The natural instinct is to hide the misses and advertise the hits. The engineer’s instinct runs the other direction. Write down what you tried, what happened, and what you learned, because a failure you understand is worth more than a success you can’t explain. The approach that didn’t work may have taught you exactly what the right one looks like.

Down-Select With Honor

The three ideas that didn’t survive the down-select were never losers. Some were the scaffolding that held the winners up. Without them, the two survivors were just guesses. With them, the survivors were chosen. Others went on the shelf, labeled for what they could do, waiting for a different problem to need them.

Sixty percent of the work failed. None of it was a failure.

So here is my ask. What is the most valuable “failure” in your work or your life, the dead end that turned out to be a side door? Tell me in the comments. I suspect some of the best methods we have are still sitting in file drawers, mislabeled.

Subscribe now

Leave a comment

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

Case file: Boeing 737 MAX, MCAS, 2018–2019

Forensic Failure Files #5 made the case with a drag strip and a Las Vegas landing ramp: some people find the truth in the data on purpose, and some people get lucky. Drag strips and stunt jumps are where that gap shows up cheap. Aviation is where it shows up expensive — and where nobody gets a second flight to eyeball it and go with their gut.

The Case File

To fit a larger, more fuel-efficient engine on the 737 MAX, Boeing mounted it farther forward and higher on the wing than on earlier 737s.[^1] That relocation changed the airplane's aerodynamics: under certain flaps-retracted, low-speed, nose-up conditions, the new engine position gave the aircraft an unwanted tendency to pitch up.[^2] Boeing's fix was software — the Maneuvering Characteristics Augmentation System, MCAS — designed to trim the nose back down automatically so the MAX would handle like the 737s pilots were already certified on.[^3]

MCAS took its input from a single angle-of-attack sensor, with no cross-check against the second sensor mounted on the other side of the fuselage, even though the aircraft carried two.[^4] An AoA disagree alert was designed to be a standard feature warning pilots when the two sensors disagreed — but a software error linked it instead to an optional angle-of-attack indicator, so the alert only activated on the roughly 20% of MAX aircraft whose airlines had paid for that extra display. Neither crashed aircraft had it.[^5] The AoA sensor at the center of both accidents had itself been flagged in more than 200 incident reports to the FAA before the crashes, and Boeing did not flight-test the failure scenario that ultimately occurred.[^6]

On October 29, 2018, Lion Air Flight 610 crashed into the Java Sea shortly after takeoff, killing all 189 aboard.[^7] On March 10, 2019, Ethiopian Airlines Flight 302 crashed shortly after takeoff from Addis Ababa, killing all 157 aboard.[^8] In both cases, a single faulty AoA reading triggered MCAS, which repeatedly drove the nose down. The Lion Air crew had no prior knowledge that MCAS existed. The Ethiopian crew, flying five months after an emergency directive following Lion Air had briefed pilots on the runaway-stabilizer procedure, correctly diagnosed the problem and cut out electric trim as instructed — but under the aerodynamic loads at their speed, manual trim wouldn't move the stabilizer, and when they re-engaged electric power to try to correct it, MCAS reactivated and drove the nose down again before they could recover.[^9] The two crashes killed 346 people combined.[^10]

The evidence that matters most: Late in MCAS's development, its authority to move the horizontal stabilizer per activation was quietly increased from an original limit of 0.6 degrees to 2.5 degrees — nearly half the stabilizer's total range of motion, and repeatable every time the system reset. Boeing's safety assessment, however, was never updated to reflect it; the certification submitted to the FAA still classified an MCAS malfunction as a "Major" hazard rather than "Hazardous" or "Catastrophic," a classification that permitted a single-sensor design with no redundancy requirement.[^11] That classification is why a single point of sensor failure passed review at all. The engineers didn't skip a check. The process itself, as submitted, no longer matched what the system could actually do.

The forensic point: Boeing had data. They automated a response to it. Nobody re-ran the hazard classification once the system's authority changed underneath it. That is Armstrong's clutch problem exactly — an assumption tuned around instead of tested — except here the assumption was baked into flight-critical software, verified against an outdated version of itself, and the consequence was not a slower run. It was 346 deaths.

The Clock Gets Faster From Here

What separates MCAS from the clutch and the ramp isn't the underlying failure — trusting an unverified input — it's the amount of time available to catch it. MCAS could reactivate roughly five seconds after a pilot released the manual trim switch if the faulty AoA reading was still present; crews had a narrow, repeatedly-closing window to diagnose and override it, and in both accidents ran out of altitude first.[^12]

Self-driving cars compress that window into single-digit milliseconds, with no crew and no post-flight investigator to read the logs — the judgment has to be built in before the fact, because there's no time to build it in after. Rockets push the same problem further, generating more telemetry per launch than a person could review in a lifetime, sometimes on hardware that doesn't survive to be inspected. Same problem, faster clock, less room for a wrong guess.

Is AI Different, Or Just Higher-Stakes Software?

MCAS raises a fair question: is AI actually a new problem, or just software with worse consequences? Software has always had this failure mode, and MCAS is the proof case — a system trusted one input, acted automatically, and nobody built in the check.

That part isn't new, and AI inherits it. But there's a place the comparison breaks down. MCAS's logic was fully specified — an engineer wrote the rule: if AoA exceeds a given value, trim nose-down by a given amount. Once investigators pulled the software, they could point to the line. The failure was bad, but it was auditable.

A lot of what AI produces doesn't come from a rule anyone wrote. It comes from a model that learned a pattern from training data, and when it's wrong there frequently isn't a single line to point to — the "why" is distributed across weights nobody can read like a rulebook. AI doesn't just carry MCAS's failure mode forward. It can stack a second one on top: not just trusting bad data automatically, but being unable to fully explain, even after the fact, why the system did what it did.

There's a second distinction worth naming, and it's the one that actually changes the shape of the problem: every instrument in the drag-racing and aviation cases — Armstrong's data recorder, the flight data recorder, rocket telemetry — was built to answer one defined question first. The data had a job. A lot of what AI generates doesn't start from a question at all; it's output produced because the system can produce it. That's a failure mode upstream of "misread the data" — nobody ever decided what would count as signal in the first place.

Afterthought: The Standard for Critical Software Corrections

This is the practical rule the MCAS case file argues for, stated plainly: any software correction touching a safety-critical function has to be justified against a stated, sufficient body of data — not a plausible-sounding assumption, and not a single input trusted because nobody thought to ask what would happen if it lied.

That standard has three parts.

How much data is enough has to be answered, not assumed. "We had a sensor" is not a data standard. "We had one sensor, no cross-check, and no flight test of what happens if it fails" is what MCAS actually had, and it was not enough — not because more data is always better in the abstract, but because nobody stated in advance what quantity and diversity of input the correction needed to be trusted, so nobody could tell they'd fallen short until 346 people were dead.

If the data doesn't exist, building the means to collect it is part of the engineering job — not a step that gets skipped because the deadline is close. Armstrong didn't have clutch-lockup data until he built a way to get it. Boeing had the AoA sensor hardware already on the airframe and chose not to cross-check it, and chose not to flight-test the failure scenario that killed two planes. The difference between those two stories is the difference between a craftsman and a shortcut.

A single reading, or a handful of them, is not a statistical standard. One data point can tell you what happened once. It cannot tell you what the system does across its full operating envelope, under the range of conditions a critical correction will actually see in service. That requires continuous, constant data collection — not a snapshot from a test flight or a bench run — sustained long enough and broadly enough to establish a real statistical picture of normal versus failing behavior. MCAS treated a single sensor's momentary reading as ground truth. A statistically sound system treats any single reading as one data point in a distribution, and knows what "outside the distribution" looks like before it trusts the reading enough to move a control surface.

Put together: a critical software correction is only as sound as the data behind it, the data has to be built if it doesn't already exist, and one reading — or even a few — is never a substitute for a standard established across enough continuous data to know what normal actually looks like.

The Call to Action: Sloppy Software Has to Be Cleaned Up

MCAS wasn't inevitable. A single point of sensor trust with no cross-check is not an unavoidable cost of complexity — it's sloppy engineering, the kind that gets caught in review on any system where someone is personally accountable for the design. It got built and certified anyway.

A Professional Engineer's stamp on a bridge or a pressure vessel means a specific, licensed individual reviewed the design and is personally answerable if it fails. Safety-critical software already has its own version of rigor — standards like DO-178C and ARP4761 exist precisely to classify failure conditions and set the assurance level a system has to meet before it flies. MCAS went through that process. The standards didn't fail; the classification feeding them did, and it went unrevised after the system's authority was quietly expanded. That's the real gap: not the absence of a standard, but the absence of one accountable, licensed individual whose name and liability were on the line when that classification stopped matching the design. Nobody's license was on the line when MCAS's authority tripled without its hazard rating being revisited.

References

[^1]: Joint Authorities Technical Review (JATR), Boeing 737 MAX Flight Control System: Observations, Findings, and Recommendations, October 2019.

[^2]: Ibid.

[^3]: Ibid.

[^4]: U.S. House Committee on Transportation and Infrastructure, The Design, Development & Certification of the Boeing 737 MAX, Final Committee Report, September 2020.

[^5]: Boeing press statement, "Boeing Statement on AOA Disagree Alert," May 5, 2019 (software linked the standard AOA Disagree alert to the optional AOA indicator, so only aircraft with the paid indicator had the alert active); CNBC, "Boeing says disabled alert on 737 Max wasn't necessary for safe operation," May 5, 2019.

[^6]: CNN, "Boeing relied on single sensor for 737 Max that had been flagged 216 times to FAA," April 30, 2019.

[^7]: Komite Nasional Keselamatan Transportasi (KNKT), Final Aircraft Accident Investigation Report, Lion Air PK-LQP, KNKT.18.10.35.04, October 2019.

[^8]: Ethiopian Civil Aviation Authority, Aircraft Accident Investigation Bureau, Interim Investigation Report, Ethiopian Airlines ET-302, 2019/2020.

[^9]: Ethiopian AAIB Interim Report, op. cit.; U.S. House Committee Final Report, op. cit., on the Lion Air crew's lack of prior MCAS awareness versus the Ethiopian crew's briefing under the post–Lion Air emergency airworthiness directive.

[^10]: KNKT Final Report and Ethiopian AAIB Interim Report, op. cit. (189 + 157 = 346).

[^11]: U.S. House Committee Final Report, op. cit., and U.S. DOT Office of Inspector General report on FAA's 737 MAX certification, on the increase in MCAS stabilizer authority from 0.6 to 2.5 degrees and the "Major" hazard classification (Development Assurance Level C) that authority increase was never re-assessed against.

[^12]: Ethiopian AAIB Interim Report, op. cit., on MCAS reactivation timing relative to electric trim input.

Leave a comment

Subscribe now

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

What a 40-year-old TRIZ argument about grass teaches you about every engineering debate you’ll ever have

There’s an old argument inside TRIZ that sounds like a joke the first time you hear it, and then quietly stops being one.

The question: what’s the ideal solution to cutting grass?

Not the best mower. Not the quietest, fastest, most autonomous mower. The ideal solution has no mower at all. The grass simply stops growing at two inches, the way a human stops growing at some final height, and the function — a manicured lawn — exists without anyone or anything performing an action to produce it.

The opposition’s response is immediate and reasonable: that’s an enormous biomimetic investment in genetic engineering just to avoid buying a mower.

Both sides are right. That’s what makes the argument worth having.

What the process believed

Every mower ever built — push, self-propelled, riding, robotic — has been an answer to the same unexamined question: how do we cut grass better? Faster, quieter, less fuel, less labor, more autonomy. Each generation’s “delighter” becomes the next generation’s assumed minimum — self-propulsion was a marvel once, then a baseline. The robotic mower quietly running laps while you’re at work is this decade’s version of the same story, and in ten years it’ll just be what a lawn mower does.

Every one of those improvements optimizes the mechanism. None of them asks whether the mechanism should exist.

That’s the question TRIZ’s Ideal Final Result forces onto the table: not “how do we build a better mower,” but “what if the function existed and the mechanism didn’t?” IFR doesn’t want a better tool. It wants the problem to solve itself, or better yet, to stop needing solving.

The contradiction

Here’s the pair actually in tension: elegance of the ideal vs. cost of getting there.

Self-limiting grass is IFR taken to its logical end — zero mower, zero fuel, zero noise, zero labor, function still delivered. On paper, that’s the most elegant answer in the room. The objection — too much biomimetic investment for the payoff — isn’t wrong, but it’s usually stated as a feasibility complaint when it’s actually an objective-function disagreement in disguise. It’s really saying: the one-time R&D cost of engineering a stop-condition into grass exceeds the value of the outcome.

That framing hides its own contradiction. It measures the numerator — the R&D cost — against a single mower, when the honest comparison is against every mower, every gallon of gas or battery charge, every hour of human or robotic labor, on every lawn, forever. TRIZ has a name for that kind of unexamined assumption: mistaking a recurring cost for a one-time one, simply because the recurring cost is familiar and the one-time cost is unfamiliar and therefore feels bigger.

But the opposition has a stronger argument available, if it reaches for it — one that isn’t about money at all. Human height plateaus because of a hormonal feedback system that evolved for reasons that have nothing to do with landscaping convenience. Grass has no equivalent internal reason to stop growing at a height humans find tidy. Cutting height is a human preference, not something any selection pressure in the plant’s evolutionary history was ever pushing toward. So the real floor isn’t “is this too expensive” — it’s “does a trait like this exist anywhere in nature to borrow from at all.” For self-limiting height in turfgrass, specifically, the honest answer is close to no.

The lessons

1. Every “ideal final result” argument eventually reduces to a resource question — but not always the resource you think. The first objection reaches for cost. The stronger objection reaches for biological precedent: is there a selection pressure anywhere in nature this trait could attach to, or are you asking evolution to install a stop-condition it never had a reason to build.

2. Comparing a one-time investment to a recurring cost without amortizing is a quiet accounting error, and it shows up everywhere, not just in lawn care. Any time “too expensive” is the whole objection, ask: expensive compared to what, over what time horizon, against how many repetitions of the current cost.

3. Delighters expire on a schedule, and the schedule is the whole story. Self-propulsion, then autonomy, then — maybe — the mechanism disappearing altogether. Each stage makes the previous one look primitive in hindsight. The lawn mower’s history isn’t a sequence of better tools. It’s a sequence of the tool mattering less.

4. The “ideal” isn’t a destination, it’s a direction-finder. Nobody is engineering self-limiting grass this year. But asking the question anyway reorganizes every intermediate step — a mower that needs less human attention is a step toward the ideal, not just a better mower, once you’ve stated where “better” is ultimately headed.

The principle

The Best Answer to “How Do We Do This Better” Is Sometimes “What If We Didn’t Have To.”

Every engineered product carries an assumption about what its mechanism is for — and the assumption is rarely questioned, because the mechanism has always been there. TRIZ’s discipline is asking the question anyway, all the way out to the edge of absurd, because the answer at the edge tells you which direction “better” has been pointing the whole time.

Before you go

Pick something in your life you improve constantly without ever asking whether it needs to exist at all — a routine, a tool, a recurring task you’ve gotten steadily better at doing.

What would the ideal version look like if the task simply stopped needing to happen?

And be honest: is the obstacle in the way of that ideal a cost problem — or is it something more fundamental, like nothing in the system was ever built to want that outcome in the first place?

A special note:

A thank-you: Ellen Domb was one of my first TRIZ teachers, and she was the one who first posed the self-limiting grass question to me, years ago. She passed away last December. Every time this argument comes up, it's hers before it's mine — I'm just still turning it over the way she taught me to.

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.

Case file: NHRA Top Fuel, 1985–1992 — the search for 300 mph

In 1992, Dale Armstrong helped Kenny Bernstein become the first driver in drag racing history to break 300 miles an hour, running 301.70 mph at the NHRA Gatornationals in Gainesville, Florida, on March 20, 1992.[^1] Everybody remembers Bernstein’s name — the run earned him the nickname “King of Speed” and a $50,000 bonus.[^2] Far fewer people remember Armstrong, the crew chief who actually found the speed.

Heading into the 1992 season, the top names in the sport doubted 300 was even achievable that year. Don Prudhomme, who had run 293.15 mph the season before, stated flatly: “No one’s going to run 300 miles an hour.”[^3] Armstrong disagreed, on engineering grounds — he had long believed a Top Fuel dragster should be capable of roughly 10 mph more than a Funny Car, and Funny Cars had recently crossed 290.[^4] The math said 300 was sitting there to be found. Armstrong just had to find it.

For years, teams across the sport believed the clutch on a Top Fuel car locked up fully by the end of a run. That belief wasn’t stupid — it was built on what drivers felt and what crews had always assumed. Armstrong was one of the first crew chiefs in the sport to bring onboard data recorders and dynamometer testing into nitro racing, moving tuning decisions away from feel and folklore and toward measured behavior of the car.[^5] He is credited as the developer of the multi-stage lockup clutch — technology built specifically to address how a Top Fuel clutch actually behaves through a run, rather than how it was assumed to behave.[^5b]

Once Armstrong knew that, he helped develop a multi-stage lockup clutch that engaged progressively through the run — technology credited across multiple sources as central to the barrier-breaking pass.[^6] Working alongside assistant crew chief Wes Cerny, who built an advanced cylinder-head and magneto combination specifically for the effort, Armstrong’s team went through every part of the car looking for anything that could add speed.[^7] Bernstein backed up the record within the one-percent tolerance NHRA requires, running 298.30 and 299.30 mph in eliminations that same weekend — proof the 301.70 wasn’t a fluke.[^8]

Armstrong himself put it plainly, years later: “Being the crew chief on the first car to run 300 means more to me than any national event win or any Winston championship... People will forget which years they won championships, but they will never forget the first 300 mile an hour run.”[^9] He was right. When NHRA fans later voted on the greatest moment in the sport’s history, Bernstein’s 301.70 mph pass finished first.

The forensic point: Armstrong didn’t get lucky once. He built a career on measuring the thing nobody else was measuring — first the clutch, later cylinder-head airflow and ignition timing — and correcting the model when the data disagreed with the folklore. That’s not luck. That’s method.

The Same Failure Mode, Off the Racetrack

A parallel case, cheaper and far less controlled: on December 31, 1967, Evel Knievel attempted to jump his motorcycle over the fountains at Caesars Palace in Las Vegas — a planned distance of about 150 feet. He cleared the fountains themselves, but came up short on the landing ramp; his rear wheel caught its edge, throwing him over the handlebars.[^10] He suffered a crushed pelvis and femur and fractures to his hip, wrist, and both ankles; multiple accounts report he was in a coma for close to a month afterward.[^11]

The failure wasn’t mysterious in hindsight — it’s visible on film. What matters forensically is what it took to fix it. Twenty-two years later, on April 14, 1989, Knievel’s son Robbie attempted the same jump at Caesars Palace and became the first person to clear it successfully, covering roughly 150 to 160 feet — his rear wheel also touched down first on the landing ramp, but with enough speed and control that he rode it out into the underground garage below instead of losing the bike.[^12] “That was for you, Dad,” he said afterward.[^13]

Neither jump was a hardware story in any documented sense — there’s no sourced difference in suspension setup between the two attempts. What separated them was margin: Evel’s jump came up short of the distance the stunt required, and a small shortfall proved catastrophic; Robbie’s jump had the speed and control to absorb the same rough landing and still make it. Same obstacle, same family, 22 years apart. One attempt without the margin the jump demanded. One with it.

Why This Is a Forensic Problem

In both cases, the event that decided the outcome — clutch lockup, a rear wheel catching a ramp edge at speed — happened in a fraction of a second, under load, mid-motion. No one standing trackside or ramp-side can observe that in real time, no matter how experienced. Eyewitness testimony and slow-motion film after the fact describe the aftermath, not the mechanism. The car looked hooked up. The bike looked like it came up short. Both are honest observations and neither is data about what happened in the moment that mattered.

That gap is where forensic work is either done right or gotten lucky.

Failure mode one: not collecting the right data at all. No instrumentation, no film, no recorder — just recollection and damage patterns, reconstructed backward from a transient nobody actually captured. Sometimes the reconstruction lands on the truth anyway. That’s luck, not method.

References

[^1]: “On this day in history, 1992: Kenny Bernstein breaks the 300-mph barrier,” NHRA.com, March 20, 2020.

[^2]: Jacob Sundstrom, “Kenny Bernstein’s shattering of the 300-mph barrier at the 1992 Gatornationals is the event’s signature moment,” NHRA National Dragster, March 24, 2019.

[^3]: Ibid.

[^4]: Ibid., quoting Armstrong: “I’ve always been one of those people who felt that a dragster can run 10 mph faster than a Funny Car.”

[^5]: “Gearhead Guys You Should Know: Dale Armstrong,” BangShift.com; “NHRA Champion Driver and Crew Chief Dale Armstrong: 1941–2014,” Dragzine.com/NHRA National Dragster, Dec. 2014 — Armstrong “widely credited as the first Funny Car crew chief to use wind-tunnel testing and data recorders,” and pioneer of dynamometer testing for nitromethane engines.

[^5b]: Ibid. — Armstrong credited with pioneering the multi-stage lockup clutch, now industry standard.

[^6]: Terry Callahan, “NHRA’s 50 Greatest Drivers: Number 10, Dale Armstrong,” The Auto Channel, September 23, 2001.

[^7]: “Digging Through the Archives,” National Speed Sport News archive reprint, SpeedSport.com, reprinted March 2022; “First 300,” NHRA.com, 2012 retrospective.

[^8]: “First 300,” NHRA.com, 2012.

[^9]: Callahan, “NHRA’s 50 Greatest Drivers,” op. cit.; also quoted in BangShift.com and Dragzine.com obituary coverage.

[^10]: “Evel Knievel,” Biography.com; Las Vegas Advisor, “Question of the Day,” Dec. 15, 2017; Las Vegas Review-Journal, “’This is a crazy life. This is nuts’: Robbie Knievel’s high-flying life in Vegas.”

[^11]: Biography.com, op. cit. Coma duration (”nearly a month”) is reported consistently across secondary sources; treat as commonly reported rather than independently verified here.

[^12]: Deseret News (AP), “Knievel Son Completes Jump That Injured Dad,” April 15, 1989; Las Vegas Review-Journal, op. cit.; Biography.com, op. cit. Sources vary on exact distance (roughly 150–160 feet).

[^13]: Las Vegas Review-Journal, op. cit.

[^14]: NHRA National Dragster obituary, Nov. 2014, op. cit.

[^15]: kennybernstein.com, official team site, career timeline.

Subscribe now

Leave a comment

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

Who profits when the server farm never gets built

Drive past a proposed data center site in almost any state right now and you'll find the same scene. A county commission meeting running four hours past its scheduled end. A line of residents at the microphone raising a real concern — the water table, the noise, the tax abatement, the power bill. A team of consultants and attorneys in the back row, billing by the hour regardless of which way the vote goes.

The concerns are almost always legitimate. The water really can drop. The transformer hum really does carry at night. The tax abatement really does shift the burden onto the school district. None of that is manufactured.

What's worth asking is a different question: who benefits from the fight lasting as long as possible, regardless of who wins it?

The Objections, Inventoried

Strip the data center fight down to its component objections and you get a short, consistent list, repeated from Loudoun County to rural Georgia to the Ohio corridor:

Grid strain — new industrial load competing with residential ratepayers for capacity

Water usage — cooling systems drawing down aquifers, especially in already water-stressed regions

Noise — round-the-clock cooling fans and backup generators near residential zones

Land use — farmland or green space converted to industrial footprint

Tax abatements — locals subsidizing a facility that pays little in ongoing property tax

Low job yield — a construction boom followed by a handful of permanent, often non-union technical jobs

Diesel backup generators — air quality concerns from emergency power systems

Loss of local control — decisions made by state economic development offices over local objection

Every one of these is defensible on its own terms. But run each through the question the original excavation industry argument insists on: not "is the concern real," but "who has a financial position staked on how this plays out, and did they place that position before the fight started."

Money, Traced

The answer is different for almost every line item — which is itself the finding.

Grid strain cuts both ways. Utilities often want the load, since new interconnection triggers rate-base expansion they earn a guaranteed regulatory return on. Opposition tends to come from incumbent generation owners who don't want new capacity competing with theirs, or utilities angling to negotiate premium contract rates before agreeing to connect.

Water usage traces to agricultural and municipal water-rights holders with existing allocation contracts, for whom a new industrial draw threatens a negotiated share they already depend on.

Land use and zoning trace to competing jurisdictions — counties and states actively bidding for the same project with rival incentive packages, sometimes amplifying local opposition in a jurisdiction they're trying to out-recruit.

Tax abatements trace most cleanly of anything on the list — school districts and municipal governments losing real property tax base, a direct and quantifiable loss, arguably the most legitimate financial objection here.

Diesel generators and environmental review trace to the same actor the original piece named in the California high-speed rail case: environmental attorneys, expert witnesses, and permitting consultants who are paid by the hour, for whom the length of the fight — not its outcome — is the revenue.

That last category is the closest thing to a single node connecting the whole list. Not one industry with one motive, but a permitting-and-review complex with a shared interest in prolongation, regardless of which side eventually wins.

The Precedent Already Exists

This isn't a new pattern invented for data centers. It's the same mechanism that already reshaped American energy policy once, and the paper trail is public.

In 1970, Robert O. Anderson — head of Atlantic Richfield, a major oil company — personally funded the founding of Friends of the Earth with a $200,000 donation. The organization became one of the most influential anti-nuclear voices in the country for the next fifty years. Coal industry leadership was on record even earlier, in 1963, warning that continued federal investment in nuclear power risked destroying the coal industry outright — not a hidden motive, just a competitor saying the quiet part in an internal memo. In the decades since, investigative reporting has surfaced branded fossil-fuel campaign material designed to manufacture the appearance of grassroots anti-nuclear sentiment where the underlying sentiment wasn't organic.

None of this means the public's fear of nuclear power was fake. Three Mile Island and Chernobyl were real events with real consequences, and the fear that followed was genuine. But genuine fear and funded amplification aren't mutually exclusive — the fossil fuel industry didn't invent the fear, it invested in keeping it alive long after the safety data stopped supporting the scale of it. The capacity gap nuclear left behind got filled almost entirely by natural gas, not renewables, for the next three decades.

Coal miners' unions were part of that same 1960s coalition opposing nuclear, and their motive requires no conspiracy theory at all: a new technology threatened their members' jobs, so their union did exactly what unions exist to do. The same logic ran in reverse when nuclear plants themselves faced closure — nuclear plant workers in Zion, Illinois made the identical argument coal workers had made a generation earlier: high-wage union jobs, an economic engine for the town, a tax base the community depended on. Different fuel, same defense, same institutional reflex. Whoever's labor is already attached to the incumbent system defends it — not out of ideology, but because that's the job description.

The One Actor With Both Keys

Here's where the data center fight differs from every other example in this piece.

Land use, water permits, and tax abatements get decided locally — county commissions, planning boards, city councils. That's where the permitting-and-review complex operates, and it's where most of the "excavation industry" friction against data centers currently lives.

But unions are the one actor in this entire chain with genuine standing at both levels simultaneously. A local IBEW hall can turn out members and testify at a county zoning hearing the same way coal miners' locals did in the 1960s. The national union can apply pressure through state legislation, NLRB posture, and federal permitting policy at the same time. No permitting consultant has that reach. No competing jurisdiction has that reach. Utilities are regional at best. Unions are the only actor positioned to move both the county commission and the statehouse from the same institutional base.

Which raises the actual lever available here.

Transmission line construction and power plant construction are already heavily unionized — IBEW on the lines, building trades on the plants. If that's true, and if grid interconnection and generation buildout are the real binding constraints on data center growth (which most reporting on the industry suggests they are), then the labor building the actual bottleneck infrastructure already has a direct financial stake in projects moving forward, not stalling.

What's missing is the operational workforce — the permanent staff running the finished facility, currently thin and largely non-union. Right now that's also the industry's weakest political argument: few permanent jobs, easy target for the "low job yield" objection. Organize that workforce, and the calculus changes on both ends. The unions with clout over the harder bottleneck — transmission and generation — already have skin in the game. Add an organized operational workforce with its own stake in the facility's survival, and organized labor stops being a neutral bystander to data center fights and becomes an active political counterweight to the permitting complex profiting from delay.

The TRIZ Forward Read

The underlying contradiction here is the same one that runs through every example in this piece: the people with the technical and legal standing to resolve a dispute quickly are rarely the people whose revenue depends on it staying unresolved. Engineers sign PE stamps and carry personal liability. Consultants bill hourly with no such exposure. That asymmetry doesn't fix itself.

But unions occupy a different position in that asymmetry than any other actor in the data center fight. Their institutional survival depends on organizing new industrial workforces, not on prolonging permitting fights — the opposite incentive from the consulting-and-review complex. If that incentive gets pointed at data centers specifically, the likely trajectory over the next several years is a gradual shift from adversarial-or-neutral labor relations toward the same alliance nuclear plants and large industrial builds already have with their unionized workforces: an organized, well-funded political constituency arguing for speed, not against it.

The lawn is still there. The excavators are still bidding. But this time, one of the trades on site has a reason to want the job finished — not just started.

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

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 sensor in my tibial stem uploads while I sleep. It is the newest part of my knee and, structurally, the least load-bearing thing in it. Everything that actually has to survive decades of walking — the bearing surface, the cement interface, the bone-implant bond — was solved by materials engineers years before anyone thought to put a radio in there. That ordering is the whole story, and it happens to be forty years personal.

My grandparents had bad knees. Their son — my father — had bad knees. I inherited the osteoarthritis: cartilage as a wear surface, running out on a family schedule. Vitamins didn’t touch it. Steroid shots bought time, not repair. By fifty the outcome wasn’t in question. What I was actually watching, without framing it this way at the time, was a race between my own mobility and composite biomedical device technology. A few years later the curves crossed, on a table, mid-September.

One pivot, not a museum tour

Early total knees, hitting clinical use in the late 1960s, were simple hinges — a metal pin fixing femur to tibia. They solved pain by removing motion the knee actually needs: no rotation, no rollback, every load meant for ligaments routed through one axis instead. Loosening and hardware failure followed. The real pivot came in the mid-1970s with the total condylar knee: femoral and tibial components resting on each other instead of pinned, letting soft tissue do the constraint work again — the design lineage every modern knee, mine included, still belongs to. It only worked because of one material arriving alongside it: ultra-high-molecular-weight polyethylene as the bearing surface. Metal-on-metal sheds debris and wears fast; metal-on-polyethylene gave a couple that could survive years of cyclic load. That’s the pivot. One material, one design change, one decade.

The sealed proof: cross-linking against osteolysis

Polyethylene bought the field a decade, and then it created its own failure mode. Wear generates submicron polyethylene particles, and the body treats them as an invader — an immune response called osteolysis that dissolves the bone holding the implant in place. Not a fracture. A slow biological demolition of the anchor, driven by the very material chosen to prevent wear.

The fix took most of two decades to get right. Radiation cross-linking the polyethylene cuts the wear rate by disrupting how the polymer chains slide past each other under cyclic load — fewer particles shed per million cycles of walking. But cross-linking also generates free radicals in the material, and unquenched free radicals oxidize the polymer over time, making it brittle exactly where you need toughness. The industry’s early cross-linked liners solved wear and quietly created a new fatigue problem. Vitamin E — an antioxidant blended into the polyethylene before final cross-linking — was the correction: it scavenges the free radicals without needing post-processing heat treatments that themselves degrade mechanical properties. Vivacit-E, the bearing material in my own tibial insert and patella, is that formulation. It is a true composite, not a marketing word — polymer matrix, dispersed-phase stabilizer, engineered against a failure mode nobody could see happening until retrieval studies of explanted, years-old components showed the oxidation front eating into liners from the outside in. The proof isn’t a lab spec. It’s a decade of other people’s failed hardware, sectioned and read like a fatigue autopsy, before the material got trusted at scale.

The architecture problem the sensor doesn’t solve

The Persona IQ tibial extension in my knee is a sealed accelerometer-and-gyro package uploading gait metrics overnight — cadence, step count, walking speed, range of motion. FDA-cleared as an adjunctive kinematic measurement device, explicitly not a diagnostic. That caveat isn’t fine print. It’s the architecture.

A sensor reports motion. It cannot tell the difference between a well-balanced knee and a poorly balanced one that happens to move smoothly in whatever position the patient favors that week. If the bone cuts were off, if the rotation ignored the epicondylar axis, if the soft tissue was left tight on one side, the telemetry will faithfully upload the kinematics of that error for years, graphed and trending and looking exactly as authoritative as a correct knee’s data. Instrumentation does not redeem an unverified structure. It reports on one. The same hierarchy that took fifty years to build — bearing material, then interface material, then load-transfer material, each one earning its place by surviving someone else’s retrieval study — still has to be right before the newest, least structural layer has anything true to say.

What travels to the next program

The reusable finding isn’t that my curves crossed. It’s the ordering underneath it: every layer of a load-bearing system has to survive the failure mode the previous layer couldn’t see coming, and no amount of downstream instrumentation moves that requirement earlier in the stack. An implant engineer can take that straight into the next material choice. So can anyone building a smart anything on top of a structure whose failure modes aren’t fully retired yet — the sensor is only as honest as what it’s sensing.

• Herbert Roberts, composite person.

References

Insall JN, et al. Total condylar knee replacement: preliminary report. Clin Orthop Relat Res, 1976.

Kurtz SM, ed. UHMWPE Biomaterials Handbook — cross-linking, free-radical oxidation, and vitamin E stabilization in joint arthroplasty.

FDA De Novo DEN200064, Canary Tibial Extension with CHIRP System — adjunctive kinematic measurement device clearance and scope.

Zimmer Biomet Persona / Persona IQ and Vivacit-E clinician materials.

The government just agreed with the thing I've been doing on a shop floor

For years, "tribal knowledge" has been treated inside most engineering organizations as a polite word for a problem — the stuff that lives in one person's head, doesn't show up in a drawing or a spec, and disappears the day that person retires or walks out the door. The instinct, almost everywhere I've worked, has been to try to eliminate the need for it: standardize the procedure, write the perfect work instruction, make the human judgment unnecessary. Get rid of the tribe, keep the knowledge.

That instinct is backwards, and I've spent the last stretch of my career at Quest Defense trying to prove it.

What we're actually doing

The work is simple to describe and hard to do well: sit down with the people who hold the knowledge that never made it into a document, and capture it before it walks out the door. Our pilot session covered a combustion chamber weld repair procedure — the kind of thing where the spec tells you the parameters, but the actual judgment about when a weld pass looks right, when to stop, when something's about to go wrong, lives in the hands and eyes of someone who's done it a thousand times, not in the paperwork. We sat with the person who holds that judgment and worked to get it captured in a form the next generation can actually learn from.

I've also been mentoring some materials engineers — which is its own version of the same principle. Not everything that matters transfers through a training module. Some of it only transfers person to person, in the room, over time.

None of this is glamorous. It's slow, it's specific, and it doesn't scale the way a policy memo scales. But it's the actual mechanism by which knowledge survives an organization's turnover instead of leaving with it.

Then the White House said the same thing

Science: A New Golden Age, the July 2026 OSTP report to the President, has a chapter — "The Marriage of Science and Craft" — that reads like it was written by someone who'd sat in on that weld repair session. The report states plainly that technology is encoded "not just in papers and patents, but in the tacit knowledge passed from mentor to mentee," and that decades of offshored manufacturing broke exactly that transmission line.

Its proposed fixes aren't abstract, either. The report calls for practitioner-in-residence programs that embed machinists and technicians directly alongside PhD researchers. It calls for portable, industry-recognized credentials in advanced manufacturing and lab techniques — so that a skill proven on one shop floor travels with the person who holds it, instead of staying trapped inside one company's walls. It calls for modernized apprenticeships in science and technology fields, not just the traditional trades.

That's not a new bureaucratic layer being proposed. That's the Federal Government looking at what companies like the one I work with are already doing on a shop floor and saying: keep doing that, and let's build the infrastructure to do more of it, everywhere.

Don't throw out the tribe

Here's the diagnosis versus the remedy, side by side. The bureaucratic diagnosis is macro — it looks at a national economy and sees that manufacturing capacity walked overseas, and with it, the mentor-to-mentee chain that used to carry knowledge forward. My remedy is micro — one weld procedure, one mentee, one session at a time, on the assumption that the chain doesn't get rebuilt at the policy level. It gets rebuilt one deliberate capture session at a time, by people willing to sit down and do the unglamorous work of getting judgment out of someone's head and into a form the next person can actually use.

The government's report validates that instinct instead of contradicting it. It's not telling companies to standardize their way out of needing experienced people. It's telling them the opposite: the tacit knowledge is the asset, not the liability, and the fix is building better ways to pass it on, not better ways to make it unnecessary.

Don't throw out tribal knowledge. The government finally sees its value. Now it's a matter of who actually does the work of capturing it before the people who hold it are gone.

Subscribe now

Leave a comment

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

Did you crash into a light pole, or the Eiffel Tower? Doesn’t matter. Nobody’s paying a premium for James Dean’s Porsche because the Ford he hit was interesting. They’re paying for Dean. I know the other side of that coin personally — I put a TR-6 into a pole someone had painted flat black, and no amount of story turned that fender into anything but a repair bill. Most damage is that. Ordinary math, running the ordinary direction.

This article is about the narrow set of cases where the math runs backward — and about a mechanism that’s quietly changed what “backward” even means. It used to be a market question: does enough of the world agree an object’s history is worth more than its function. Now, increasingly, it’s an engineering-and-legal question: does the party who built the object even permit you to find out. When the manufacturer holds veto power over whether repair happens at all, “worth more broken” stops being a collector’s eccentricity and becomes a control loop — one with an off switch somebody else is holding.

The mechanism, once

Repair destroys evidence. Replace a panel, polish a case, reglaze a canvas, and you can never again prove what was underneath. Most damage documents nothing, so this doesn’t matter. Occasionally it documents something real — a specific event, verifiably tied to a specific object — and once that evidence is gone, no amount of paperwork brings it back.

The best case: a gearbox nobody can use

James Dean died in a Porsche 550 Spyder in 1955. The insurance company sold the wreck for $1,092 to a doctor who stripped it for spares and gave the body to George Barris, who lost it in transit to a car show in 1960. It has never been found. In 2021, the only documented surviving piece — the transaxle, permanently unusable — sold at auction for $382,000. Nobody bought a gearbox. They bought proof of one hour on one day.

The control case: nothing happened here

A run-down Victorian missing its porch trim and shingle work doesn’t get a curse premium. It just loses money, discounted roughly by what it costs to recreate what’s gone. The difference from Dean’s car isn’t condition — the house is arguably in better shape than a stripped transaxle. The difference is that nothing verifiable happened to it. Absence isn’t evidence. No event, no premium, ordinary repair math, full stop.

Two data points is enough to establish the rule. One more is worth keeping, because it isolates the mechanism from damage entirely: a witnessed meteorite fall — seen coming down, recovered promptly, date and location documented — commands a real premium over an undocumented find, even when the rock is chemically identical. No damage involved anywhere in that transaction. Proof that provenance and damage are two separate variables that just happen to travel together in car stories, and not the same thing.

The engineering behind the veto

Here’s where the market-authority model breaks down, and where I have more standing than most people writing about this to say exactly why.

A carbon-fiber monocoque doesn’t fail the way a steel unibody does. Steel dents visibly and tells you, roughly, what it absorbed. A composite structure can take an impact that leaves the surface looking intact while the resin matrix has already delaminated internally — fiber layers separated from each other, load paths compromised, none of it visible without ultrasonic or X-ray nondestructive testing performed by someone who actually knows what a good scan looks like versus a bad one. I spent thirty-two years in aviation R&D working ceramic and polymer matrix composites specifically because this problem is real: composite damage assessment is not optional expertise. Get it wrong on a component that sees real structural load, and the failure mode isn’t cosmetic.

That’s the legitimate half of a manufacturer’s repair-control argument, and it deserves to be taken seriously as engineering, not dismissed as pretext.

The illegitimate half is parts pairing, and the two get bundled together in a way that should worry anyone who understands what each one actually is. Parts pairing means a replacement component — genuine, OEM-manufactured, metallurgically and dimensionally correct in every respect — is cryptographically linked to a specific vehicle’s electronic control system before it will function. You can have the exact right part in your hand, installed correctly, and it will not work, because it has not been paired. That’s not a materials-science problem. There’s no delamination risk, no NDT question, no safety case to make. It’s a software lockout, full stop, and it happens to also guarantee that every dollar of replacement-parts revenue on that vehicle flows back through the manufacturer’s own service network.

Both arguments get delivered in the same sentence, in the same tone of voice, and from the outside they’re indistinguishable. That’s the trick. One is genuine engineering caution. The other is a revenue model wearing a lab coat. You cannot always tell which one you’re looking at, and that ambiguity is doing real work for the party who benefits from the confusion.

The fourth authority

In 2024, a content creator crashed a Bugatti Chiron Pur Sport — north of $6 million — and bought the wreck back from insurance for roughly $1.9 million. He brought in Mat Armstrong, who’d built a career reviving wrecked supercars, to do the repair privately rather than pay Bugatti’s own quote of around $1.7 million.

Bugatti blacklisted the VIN. Not “we declined the job” — they’d already declined and been turned down in return. No dealership anywhere on earth would sell parts against that number, paired or unpaired, at any price, to anyone Bugatti hadn’t personally authorized. The car could not be fixed. Full stop. Not by Armstrong, not by any independent shop on the planet, regardless of skill, regardless of whether the composite work was flawless — because the veto sat one layer above the metal entirely. It took Bugatti’s own CEO personally intervening before the lockout lifted.

Every mechanism earlier in this piece — Dean’s transaxle, the Victorian’s discount, the meteorite’s clean-fall premium — assumes the owner still gets to choose what happens to the object. Somebody argues, the market decides, the object either keeps its damage or doesn’t. Bugatti’s VIN lockdown isn’t an argument. It’s a veto over whether the argument gets to happen at all.

Run the thought experiment the rest of this piece has been building toward. Porsche recovers Dean’s wreck in 1955, decides the VIN is permanently blacklisted — no shop, no salvage buyer, no touching it without Porsche’s authorization and Porsche’s price, forever. The transaxle never reaches a 2021 auction. It never becomes evidence of anything, because it never leaves the custody of the one party who gets to decide it doesn’t exist as a tradeable object at all. That’s not a hypothetical anymore. It’s the live mechanism sitting inside a $6 million car, deployed in front of a public audience, in 2024.

This is the reusable finding, and it’s worth stating in engineering terms rather than collector terms: when repair authority is centralized in the manufacturer, the manufacturer holds the off switch on provenance itself. It’s a single point of failure sitting on top of every other authority layer — paper trail, expert authentication, market consensus — none of which get to run if the party at the top declines to permit the repair, or the non-repair, in the first place.

Where the law stands

This is live, not theoretical. An amended REPAIR Act, folded into the Motor Vehicle Modernization Act of 2026, cleared House committee and would codify a decade-old voluntary data-access agreement between automakers and independent shops into federal law. More than thirty right-to-repair bills were introduced across a dozen-plus states in the first weeks of 2026, several explicitly banning parts pairing — the exact mechanism that let Bugatti make Armstrong’s sourcing irrelevant even if he’d found compliant parts elsewhere. Massachusetts voters approved a telematics-access expansion by a 75-percent margin back in 2020; the industry’s own lobbying group sued before it could take effect, and the litigation is still unresolved five years later.

The public has voted on this, repeatedly, lopsidedly, on the owner’s side. Whether a manufacturer can override that vote is still an open legal question — which means the control loop this article is actually about isn’t settled. It’s being argued right now, in real courtrooms, over real VINs.

The close

Provenance used to be assigned by whoever had the authority to tell a convincing story and whoever was willing to pay for a piece of it. That’s still true — until the manufacturer decides the story doesn’t get told. My TR-6’s dent has no authenticator because there’s nothing to authenticate — no name, no witness, no chain. That’s the honest, ordinary case, and it’s still almost all of them. But the extraordinary case has a new gatekeeper now, and it isn’t a historian or an auction house. It’s whoever wrote the firmware.

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 same instrument that killed the four-hundred-megawatt ghost, run across the whole energy transition

Herbert Roberts, P.E.

Part two of two. Part one told the story of a gas turbine that never found a customer — a machine with no rung on either scaling ladder — and the small, distributed, pooled-service fleet the company refused to build instead. This part takes the lesson outward.

The ghost was one company’s mistake with one product. But the instrument that convicts it — did you optimize for one number and quietly pay the bill on every other axis? — doesn’t stop at the gas-turbine yard. Once you’re holding it, you start seeing the same mispriced trade everywhere the energy system was built big and central. The gas-turbine fleet was the proof of concept, argued with hardware real customers actually bought. Here is the pattern it was a special case of.

The instrument, widened

Centralized big-iron thinking optimized hard for one metric — lowest cost per megawatt at scale — and mispriced everything that metric couldn’t see. Four more facets, each the same finding:

Correlated versus uncorrelated risk. One big plant is a single point of failure — trip it, or pull it for a six-week outage, and you lose the whole block at the worst possible moment. A teamed fleet degrades gracefully; you never lose more than one unit’s share, and geographic spread turns one watershed’s drought into a rounding error. Mispriced: redundancy and thermal resilience. The gas-turbine buyers in part one proved this with their own purchase orders — pairing units for exactly this reason. It was never a theory.

Baseload versus peak. Pair a firm nuclear floor with solar and the failure modes run anti-correlated — the sun is strongest on exactly the hot bright afternoon when a thermal plant wants to derate. Mispriced: a free hedge sitting in plain sight.

Combust versus build. This one reaches past electricity into the barrel itself. We burn petroleum for energy when the molecule is worth far more as a thing you build with — plastics, lubricants, specialty chemicals, feedstocks with no substitute. Electrify transport and the crude gets liberated from the flame; because a refinery cracks crude into a fixed slate all at once, the surplus light fractions don’t get “produced less,” they get exported. Oil doesn’t die. It retires from the combustion business and keeps the chemistry business — smaller, higher-margin, permanent, because you cannot make a polymer out of sunshine. Mispriced: the highest-value use of the resource. Petroleum stops being something you combust and becomes something you build things out of. The molecule is worth more as a polymer than as a flame.

Once-through versus closed loop. And the atom does the identical move. A once-through fuel cycle burns a few percent of the energy in the fuel and buries the rest as “waste” — combust once, entomb the remainder, the same mispricing as the barrel. Spent fuel isn’t garbage; it’s overwhelmingly unburned fuel plus a stream of medical isotopes we are genuinely starved for. Mispriced: the atom’s upmarket value.

Hold that last one — once-through versus closed loop — because it is the facet everyone thinks is nuclear’s fatal weakness, and it is actually the largest unopened opportunity in the whole system. It gets its own reckoning below, once the safety case is on the table.

The division left in amber

Part one left a division dormant — the nuclear business in the coastal Carolina town, managed for cash and never woken up. Here is the debt I owed on that, because it is the cleanest proof the whole two-part argument has.

Reviving that business was never a matter of flipping a switch. It would have taken two long, expensive campaigns, and both are pure cost for a decade before either earns a dollar. The first is regulatory: a sustained effort to reshape a licensing framework built to police a handful of enormous one-off plants, not to serial-produce small identical ones — years of work, paid out entirely over the horizon. The second is a clean-sheet reactor program that actually folds in thirty years of operating lessons: everything the existing fleet taught us about what fails, what costs too much, and what the last generation of designs got wrong, rolled into a new machine built to be made in a factory instead of poured on a riverbank. Both of those are, precisely, the slow-maturing invention the wrong metric cannot tell apart from waste. So neither happened. The division didn’t die of a market — it died of a measurement, left in amber exactly when the lessons were richest and the case for a comeback was strongest.

And that is why the revival now underway is happening almost everywhere except the old giants. The small modular reactor is the clean-sheet machine that division never got to build, and the regulatory campaign it never got to run is being fought by newer companies with nothing to manage for cash and everything to gain from a horizon further out than a quarter. The lessons didn’t vanish. They just had to wait for owners whose instrument could see them.

The reconciliation

Here is why this is worth writing now instead of as a memoir.

Everything the mid unit was quietly right about, and everything that horse community already knew in its bones, the nuclear industry is rediscovering under a new name: the small modular reactor. Regional-scale. Serial-produced. Deployed in fleets with redundancy in the count. The mid-size machine that earns for decades on service instead of once on the sale. The SMR is, almost exactly, the sub-two-hundred-megawatt product that services arm refused to build — and the buyers are the communities I was pointing at, finally visible because the hyperscalers made mid-size power fashionable.

Notice, too, that the horse community wasn’t only a market. It was a proof about how people organize when nobody stops them. Pool resources, share the pasture, share the manure grounds, split the cost of the thing that’s better held in common. That commons instinct is the fleet argument in human form — and it runs all the way down to the fuel. A closed fuel cycle is the same move at the scale of the atom: shared infrastructure that turns a waste stream into a managed, higher-value resource instead of a private burden each operator buries alone.

And it reconciles the split that killed us. Modular-and-identical is exactly what lets the power side finally run the aviation-aftermarket model — because the service annuity only works when the units are a fleet, not a collection of monuments. The same serial line that makes the tenth reactor cheap is the line that makes the closed fuel cycle pencil out, because the machine that actually burns the recycled actinides is a fast reactor — and several of the leading mid-size developers already are fast reactors.

Which means the fleet future and the recycle future were never two ideas.

And the pairing with solar, which read as a one-line hedge back in the list of facets, becomes something larger at this scale. A firm nuclear floor and a solar peak are complementary by physics — the reactor wants to run flat-out as steady baseload and dislikes chasing the daily load swing, while solar is all swing and no floor; put them on the same node and each covers the other’s weakness. In the hot-weather communities that are natural buyers for these small units, the fit gets sharper still, because peak sun and peak air-conditioning load arrive at the same hour — the solar shows up exactly when the demand spike does, and exactly when a thermal plant would otherwise be derating in the heat. But the real payoff is what the pairing does for the fleet. A small reactor holding the baseline lets the community lean on solar for the peak without needing a mountain of storage to make the sun dependable; the reactor is the storage substitute, the always-on floor under the intermittent ceiling. Distributed across a region, you get nodes that each balance their own firm-plus-variable mix and then back each other up — which is simply the teaming problem again, one more time, now spanning two different kinds of generation instead of two identical machines. Firm under variable, small under distributed, each node covering the next. The peak management that a single monument handles by burning gas, the fleet handles by arrangement.

The wall, and the prize

That bet hits a wall, and I won’t pretend otherwise, because the honest version survives contact with an expert and the optimistic one doesn’t. The fleet doesn’t exist yet. Every Western unit is still the first of its kind. The learning curve is promised, not proven. The closed fuel cycle waits on a fast-reactor fleet that isn’t built, shaped the whole way by a proliferation tax — separating pure plutonium is why the United States shut commercial reprocessing in the 1970s, and why the modern schemes deliberately keep the transuranics together so pure plutonium never exists at any step.

The physics is solved. The pipeline is a decade out. And the thing standing between here and there isn’t the reactor and it isn’t the panel — it’s the coordination layer. The control system that teams dissimilar units so they cover each other’s failures without a human babysitting every handoff. Team five percent of the fleet offline and the rest absorbs it. Team solar under nuclear so each covers the other’s weak hour. Team the nodes across a region so no single grid operator holds you hostage.

That layer is not the hard part standing in the way of the prize. That layer is the prize. And anyone who has built teamed autonomous systems will recognize it instantly, because it’s the same problem wearing a different costume — dissimilar units, one controller, graceful degradation, no human in the loop. Power fleet, drone swarm, same spindle.

The lessons-learned file nobody opened

Here is the part that should have been a program and instead became a eulogy. The three accidents everyone names as the case against nuclear are, read correctly, the most expensive lessons-learned file ever compiled — and the striking thing is that they don’t repeat one lesson three times. They teach three different ones.

Three Mile Island was a partial meltdown in which the containment did its job and almost no radioactivity escaped — but it happened because operators, misreading their instruments, fought an accident the plant would have survived on its own. Its lesson was about the human interface: the machine asked people to make split-second sense of an ambiguous board at the worst possible moment, and they couldn’t. Chernobyl was the opposite — a reactor with a fatal design instability, run without a real containment structure, pushed into catastrophe during a botched test by operators who had switched safety systems off. Its lesson was about intrinsic design: never build a machine whose physics can run away, and never operate one you can defeat by hand. Fukushima was neither a design runaway nor mainly an operator error; it was a foreseeable external hazard the siting ignored, in which the backup power to cool the cores sat where a tsunami could and did take it out. Its lesson was about the failure chain and the emergency response around it: the accident grew because the cooling depended on active power and a command structure that fell apart when it was needed.

Put those three findings on one page and a design brief writes itself. Take the human out of the split-second loop — safety that works by physics, not by a correct decision under panic. Make the core incapable of the Chernobyl runaway and impossible to strip of its own protections. And break the Fukushima chain by removing the dependence on active power entirely — cooling that happens by gravity and natural circulation whether or not anyone acts and whether or not the grid survives. That is precisely the direction the advanced designs took: passive safety systems that rely on basic physical forces and need no operator and no outside power to keep the core stable. The lessons-learned file didn’t just exist. It was answerable. Somebody simply had to be paid to open it — and the quarterly number never was.

So the forward path is not complicated, it is only patient, which is the one thing the old metric couldn’t tolerate. You mine the three accidents for every lesson they hold — a list a mile long, and every item on it hard-won. You take that list to the regulators and you walk a paired path: the design and the license moving together, each shaping the other, so what gets built is both licensable and sellable rather than one at the expense of the other. You don’t design in isolation and then beg for approval, and you don’t chase approval for a machine nobody wants. You co-develop the safety case and the product until the unit that emerges is the same unit the regulator can sign and the community can buy. That is a decade of work with no quarterly payoff and a generational payoff at the end of it — which is exactly why it had to wait for owners whose instrument could see past the quarter to run it.

The waste is the next barrel

And once you are thinking past the quarter, the thing everyone calls the dealbreaker turns into the opportunity — the same inversion we ran on the oil barrel, run again on spent fuel. The whole argument against nuclear rests on the waste, and the whole argument treats the waste as an end-state: something you seal in a mountain and walk away from. But that is the combust-once-and-bury instinct wearing a different coat. A once-through cycle burns a few percent of the energy in the fuel and entombs the rest. What you are burying is overwhelmingly unused fuel plus a handful of genuinely valuable separated streams. It is a barrel we set on fire once and threw in a hole.

Say the honest version, because it is the strong one and the overclaim is where this argument usually dies. Recycling does not make the waste vanish. It shrinks and shortens it — cuts the mass, the volume, and the span of time the leftover stays dangerous — while generating its own smaller, messier secondary streams and carrying real cost. Claim smaller and shorter and no specialist can lay a glove on you; imply gone and one will bury you. And name the wall plainly: the machine that actually closes the loop by fissioning the long-lived leftovers is a fast reactor, and a fast-reactor fleet at scale does not exist yet. The whole technology is also shaped by a proliferation tax — the old separation chemistry produced a stream of nearly pure plutonium, which is why one U.S. administration shut commercial reprocessing in the 1970s, and why the modern schemes deliberately keep the dangerous actinides together so pure plutonium never exists at any step. None of that is a reason to look away. It is the design constraint the out-of-the-box work has to respect.

Inside those honest limits, the opportunities are real, and they are opportunities the bury-it-and-forget frame can’t even see. Separation is a resource-recovery business, not a disposal cost — you are pulling apart a mixed stream into fractions, and several of those fractions are worth more than the mining that would otherwise supply them. The sharpest example is the one that turns the fear on its head: the same spent fuel and stored material everyone wants gone contains the feedstock for medical isotopes the world is starved for — the isotopes behind cancer diagnostics and targeted therapies, in such short supply that patients wait, while the raw material sits in a pool being described as garbage. Recovering it is the atom’s version of specialty chemicals, not flame: the highest-value use of a resource we were paying to throw away. Other fractions are heat sources, industrial and space-power isotopes, materials with no cheap substitute. The waste stream is a mine we refuse to read as one.

And the fuel cycle is where your community model comes all the way back around. No single small unit should run its own reprocessing — that is exactly the proliferation and cost nightmare the critics rightly fear. But a shared fuel-cycle facility serving a whole distributed fleet is the pooled-spares idea at the scale of the atom: one guarded, regulated, well-run separation and recovery operation that the entire network draws on, so no community carries the burden alone and no community touches the dangerous chemistry itself. The commons that handled the horses’ manure, one energy source over, handling the fleet’s fuel — waste in one end, recovered fuel and medical isotopes and shortened, shrunken leftovers out the other. That is not disposal. That is a business, a medical supply chain, and a proliferation-controlled service all in one — and every piece of it is invisible to an instrument that can only see the cost of the hole in the ground.

Strip all of it down and the honest promise is five words: lower the long-term volume, and manage the rest. Not eliminate — no serious person says eliminate. You fission down the long-lived fraction so the part that has to be watched for millennia becomes a part that has to be watched for centuries, you pull the valuable streams out for medicine and industry, and what remains — smaller, shorter-lived, fully characterized — you manage, deliberately and in the open, the way every mature industry manages a known byproduct. That is the entire claim. It is unglamorous, it is completely defensible, and it is the exact opposite of both the fantasy that the waste disappears and the fear that it is an unsolvable curse. Lower the volume that lasts. Recover what’s worth recovering. Manage what’s left. And the scale is worth seeing, because it is the fact that dissolves the fear. The waste everyone pictures as a mountain is often illustrated as a single stack: all the spent fuel U.S. reactors have produced since the 1950s, gathered onto one football field, comes to roughly ten yards deep — the whole of it, six decades of it, on one field. But that pile is mostly fuel, not waste — better than ninety percent of it is unburned material a breeder fleet could run on for a century or more. Separate out what has actually fissioned — the true waste — and the stack on that same field drops to something you could stand beside, a fraction of a person’s height rather than a wall towering overhead. Ten yards of stuff; inches of genuine long-lived waste; and in between, the modest, human-scale pile you actually store and watch. The mountain was never there. It was an artifact of refusing to separate the fuel from the ash.

The fear is the last thing to address, and the most stubborn, because it does not answer to a football field or a burnup figure — it answers to a feeling, and the feeling was welded on early. We met the atom first as a weapon, and the dread of the bomb never fully separated from the power plant that shares its physics. But there is a place that quietly argues the other side, and it is the one everyone reaches for as the worst case. In the exclusion zone around the site of the worst civilian nuclear accident, the wildlife came back — not sparingly, but in abundance, until the zone became one of the more biodiverse stretches of its region. Not because the radiation is harmless; the animals there live under a real burden. But because the thing that had been suppressing that whole landscape turned out to be us — our farms, our roads, our presence — and when the people left, the living world moved back in. A handful of old residents refused to leave, or quietly returned, and lived out their lives there anyway. Read honestly, the most feared nuclear ground on earth is not a dead zone. It is a rewilded one, with the human pressure removed — which is not the story the fear tells, and is closer to the truth than the fear has ever been.

And the next thirty years stack up smaller still, because the machines themselves are changing. New-generation units run their fuel harder — higher burnup, more energy pulled from every kilogram before it is spent — so they make less spent fuel for the same electricity. Designs meant to consume or recycle their own actinides shrink the long-lived fraction again. Put those together and the waste from the next stretch of nuclear does not pile up the way the last six decades did: the same energy, a materially smaller and shorter-lived residue, trending toward that inches-high stack of pure fission products rather than the mountain nobody ever actually had. The direction is the whole point — every generation of design leaves less behind and leaves it dangerous for less time.

And this holds even as the fleet grows. The pipeline is real but early — the marquee U.S. first-movers are aiming at the early 2030s, and credible forecasts put meaningful deployment on a horizon of the mid-2030s into the 2040s, plausibly a couple dozen new units over that stretch rather than a couple. Notice what that does to the waste argument: it strengthens it. More reactors making less waste per unit of energy is not a contradiction — it is the entire thesis. You can add units and shrink the long-term residue at the same time, because the new units burn their fuel harder and bury less of it. Growth and shrinkage point the same way, which is the tell that the old framing had the sign backwards: it counted reactors as waste-makers when the newer ones are, per megawatt-hour, waste-reducers.

An instrument that could only see the cost of the hole never let anyone say it out loud — which is the same failure, one last time, that let the ghost haunt a company for thirty years.

The honest ledger

None of this works as an argument if it only lists the credits, so here is the debit column, stated plainly. The dangers are real. Freshly removed spent fuel is lethal up close — stand next to an unshielded assembly and the dose can kill you. A reactor is a genuine industrial hazard that demands disciplined operation, and the history in this piece is proof: three serious accidents, real land rendered off-limits, real thyroid cancers downstream of one of them, real cleanup costs measured in decades and billions. The long-lived waste, even after you shrink and shorten it, has to be isolated and watched for a span longer than any institution has ever reliably lasted. The proliferation risk is not folklore — the wrong separation chemistry in the wrong hands produces weapons material, which is exactly why the whole fuel cycle is built around preventing it. And the failure modes are unforgiving: a nuclear accident is low-probability but, when it happens, it is severe, expensive, and slow to undo. Anyone who tells you otherwise is selling something. These are the real costs, and they are the reason the discipline, the regulation, and the design conservatism in this whole essay are non-negotiable.

Now counter the stigma — not by denying any of that, but by putting it on the same scale as everything else we live with. The stigma’s trick is that it grades nuclear on a curve no other energy source has to face: it counts nuclear’s worst days and compares them to the ordinary operation of everything else. Set them side by side honestly and the picture inverts. The routine business of burning fossil fuel — not its accidents, its Tuesdays — fills the air with fine particulate that kills millions of people a year worldwide, quietly, with no exclusion zone and no headline, and warms the planet on top of it. Measured per unit of energy delivered, across the whole history including its accidents, nuclear sits among the safest sources we have, in the same low band as wind and solar and far below coal, oil, and gas. That is not a claim that nuclear is harmless. It is the observation that we have filed nuclear’s rare, visible, contained harms under terror and fossil fuel’s constant, invisible, dispersed harms under normal — and the filing is exactly backwards.

The stigma, in other words, is one more instrument reading the wrong number. It prices the dread of the photograph and ignores the body count of the ordinary. It is the same error that killed the ghost and mothballed the division, wearing its most human face: optimize your judgment for the fear you can picture — the mushroom cloud, the ghost town, the mountain of waste that was never there — and you will pay the bill on every hazard that doesn’t photograph, including the one currently changing the climate. Fear the right things, in the right proportion. That is the entire ask. It is not stop being afraid; it is be afraid to scale.

The verdict

Six facets, one spindle. Sale versus service. Monument versus fleet. Correlated versus uncorrelated risk. Baseload versus peak. Combust versus build. Once-through versus closed loop. Every one is the same forensic finding — a contradiction resolved in the wrong direction, one axis optimized by silently expensing all the others.

The company that built the ghost is about to have company. The whole energy system is standing at the same fork the gas-turbine yard stood at: keep building monuments optimized for a single number, or build fleets — small, identical, teamed, distributed, serviced — that price every axis the monument threw away. The reactors are ready. The panels are ready. The barrel is ready to move upmarket. What isn’t built yet is the coordination layer that teams them, and that layer isn’t the obstacle standing in front of the prize. It is the prize.

Before the slogan, the cost — because it should be counted honestly. What the metric destroyed wasn’t a line of reactors that would surely have worked. It was the option on all of them: thirty years of iteration that never compounded, a safer machine that never got drawn, a licensing framework that never got modernized, a generation of engineers who took their operating lessons into retirement instead of into the next design. And the sharpest edge is the one the quarterly view was least equipped to see — that a reactor built to fold in three decades of hard-won lessons is, by definition, a safer reactor, and a campaign to rebuild the policy around it is a safety project as much as a commercial one. The number couldn’t price safety any better than it could price durability or invention, so it expensed that too. We didn’t just lose a business or a division. We lost the thirty years in which the better, safer product should have been getting built — and the clock those years were on, the climate clock and the safety clock both, never once stopped to wait for the quarter. That is the real bill. Not the sale we missed. The decades we burned proving that a machine with no rung was a design problem, while the machine that would have mattered went undrawn.

Fleet or monument. Polymer or flame. Same instrument, two verdicts.

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.

They called it quality assurance.

A bundle of documents, certifying that an imported steel truss had been welded to the design drawings and fabrication requirements.

That’s not quality assurance. That’s a signature on a promise nobody checked.

What actually happened was simpler, and more damning:

• A 440-tonne structural steel package for the Kew Recreational Centre redevelopment in Melbourne was fabricated by a subcontractor in China and shipped to Australia.

• The façade contractor and principal contractor visually inspected the first few shipping containers of steel.

• The imported truss — designated GT1, a large structural component spanning the pool hall — arrived with a bundle of quality assurance documents attesting it had been welded in accordance with the design drawings and fabrication requirements.

• Nobody with the competence to verify those documents actually checked them against the physical steel.

• The truss was erected in February 2022. It was not fabricated to the design drawings and fabrication requirements it was certified against.

• The structure sat erected — and structurally unsound — for eight months, with workers present on and around the site the entire time.

• In October 2022, during a paint work inspection, defective welding was discovered. Remedial work began.

• The truss collapsed that same night, when no one was on site.

Nobody died. The regulator’s own language makes clear how close that came to being luck rather than outcome: “It was pure luck that the risk didn’t eventuate when people were on site.”

The Certification Language vs. The Physical Reality

The paperwork wasn’t forged. It was simply never verified against the thing it described. That gap — between a document that says the work was done correctly and steel that says otherwise — sat unexamined for eight months, through every day workers moved through and around that pool hall.

The Architecture Problem

Importing structural steel at scale is a supply-chain problem wearing an engineering costume. The physical fabrication happens somewhere the buyer cannot watch it happen. What arrives instead is a package: the steel, and a set of documents asserting the steel meets specification.

Those two things — the object and the paperwork about the object — are not the same thing, and a system that treats them as interchangeable has already built its own failure mode into the process. A visual inspection of a shipping container tells you the crate arrived. It tells you nothing about whether the weld inside the truss meets the design’s structural requirements. That verification requires someone competent to actually check the QA documentation against the fabrication — not glance at it, not file it, check it.

That check never happened here. Not because anyone decided to skip it. Because nothing in the process assigned the check to anyone in particular.

The Operating System Mismatch

The regulator’s own summary of the fix required is the clearest possible statement of the mismatch: “Having a robust system in place to ensure steelwork meets specific design requirements and Australian standards is simply a non-negotiable when importing products from overseas.” Non-negotiable, and also — on this project — absent.

The Cascading Cost

The truss’s collapse didn’t stay contained to one component.

The façade contractor that fabricated and erected the steel was fined $400,000 and has since gone into liquidation. The principal contractor entered an $850,000 enforceable undertaking — not just a fine, but a mandate to research and draft a new industry standard for structural steel procurement, fabrication, and erection, with a specific focus on welding quality assurance. The project itself stalled for two years before resuming. A regulatory body filed eighteen separate charges against the fabricator and its director, prosecution ongoing years later. And the reputational cost followed the parent company to its next project — a separate council was forced to publicly promise, before construction even began, that steel on its new build would be sourced domestically.

One unverified weld, certified on paper as compliant, produced a cost that outlived the truss itself by years.

Clarity as the Missing Control Loop

Complex supply chains don’t fail because nobody cares about quality. They fail when the artifact that’s supposed to prove quality — the certificate, the inspection report, the QA bundle — gets treated as equivalent to the verification it’s supposed to represent, instead of as a claim that still needs checking.

A shipping container passing customs is not the same event as a weld meeting a design drawing. An organization that can’t tell those two events apart in its own process will eventually erect something on the strength of a document nobody actually verified — and then discover, on a lucky night with no one on site, exactly how much weight that document was never carrying.

The Most Expensive Metaphor

A collapsed truss is simply the most visible version of a pattern running in any organization that outsources a critical function and accepts the paperwork as proof the function was performed.

The engineer who signs off on a vendor’s certification without independently verifying it isn’t lazy. They’re the predictable output of a process that never assigned anyone the job of checking the check.

If your organization treats a certificate as equivalent to the verification it claims to represent, you already know which version of this story you’re building toward.

The steel doesn’t care what the paperwork says. It only cares what it was actually welded to hold.

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

A story about a company that had the answer in its own catalog and kept reaching past it

Herbert Roberts, P.E.

Part one of two.

Ten years ago I worked at an energy production manufacturer, and we kept trying to build a machine nobody wanted.

We had two good gas turbines. The mid unit was the 200-to-300-megawatt class — a regional machine. You didn’t sell one; you sold three or four into a region, and the fleet gave you something no single unit could: when one came down for service, the others carried the load. The customer never went dark. Redundancy wasn’t a feature we bolted on. It came free with the arithmetic of buying more than one.

The large unit was the 500-plus-megawatt class, aimed at the handful of places on earth big enough to swallow it whole. Mexico City. New York. Tokyo. A magnificent machine with a small address book, because there are only so many cities that fit that number.

And then there was the ghost. Somewhere between those two classes sat a 400-megawatt hole, and we could not stop trying to fill it with a single machine. The plan that kept coming back was to take the mid unit and push three-dimensional aerodynamics into the compressor — squeeze more efficiency out of it and lift one unit to 400 megawatts. We ran the iterations. Three different design efforts, as I remember it. We got right up to the edge of a prototype. And every time, marketing came back with the same sentence: nobody wants to buy it.

Here is why they didn’t, and it is the whole lesson in one configuration. The regional sites that wanted roughly 400 megawatts already knew how they wanted to buy it: two of the mid units feeding one steam turbine — a 2-on-1 combined-cycle block. That arrangement won on both axes at once. It kept the redundancy, because a site running two machines never loses everything when one comes down for service. And it captured the co-generation, because the exhaust heat off two gas turbines drove the steam unit for output and efficiency the single machine couldn’t touch. The customer had already engineered the better answer out of the fleet parts. Our monolithic 400 offered the same nameplate and forfeited both advantages — no redundancy, no co-gen fit, one throat for the whole site to choke on. The ghost wasn’t losing to nothing. It was losing to a smarter version of itself that the customer had already drawn up.

And it had nowhere else to go, because the large buyers scaled the same way. Nobody who bought the large unit bought just one either — they paired two on a shared steam plant, and when a site needed more, it added a third large unit and a second co-gen train. And the reason they stayed on the same machine wasn’t sentiment — it was interchangeable parts. A site standardized on one unit runs a single spare-parts inventory that fits every machine on the property: one set of blades, one set of hot-section components, one stock of consumables, any part swappable into any unit on any shift. That interchangeability is the whole economic point of a fleet — it collapses the inventory, shortens the outage, and lets the crews master one machine cold instead of splitting their attention across two. Drop a 400 onto that site and you break exactly that. Now you’re carrying a second, dissimilar parts inventory for a single orphan unit, a second set of procedures, a second thing that can strand you waiting on a part that fits nothing else on site — all to get less than you’d get by simply adding another large unit the crews already knew cold. So the ghost died from both directions at once. Paired and co-genned, a 400-class block overshot what a regional site could ever absorb. And on a large site it was the dissimilar orphan nobody wanted, losing to the obvious move of just buying more of what already worked. The mid unit scaled by adding mid units. The large unit scaled by adding large units. And the same parts logic that kept the large buyers from stepping down to the 400 kept the mid buyers from stepping up to it — or to a large unit at all. A mid-unit site was already sitting on years of spare-parts inventory, trained crews, and procedures built entirely around the mid machine. Stepping up meant walking away from all of it and standing up a second, dissimilar inventory from zero. So the mid buyer’s next purchase was almost always another mid unit, because the sunk investment in interchangeable parts made staying on the rung cheaper than climbing to a new one. The parts base wasn’t just an operating convenience — it was a switching cost, and it locked every buyer onto their own ladder in both directions. The 400 fit neither ladder — which is the entire reason it never found a customer, and the exact reason we kept mistaking that for a design problem we could iterate our way out of. It was never a design problem. It was a machine with no rung.

So we shut it down. There’d be a lull — maybe a year — and then, like clockwork, a new plan for the same ghost. The four-hundred-megawatt system that never had a customer, resurrected on a schedule.

I’ve thought about that cycle for a decade. It isn’t a story about a bad turbine. It’s a story about a company that had the answer in its own catalog and kept reaching past it.

The mistake had a shape

The mistake was that we were mesmerized by the big sale.

A large bespoke installation is a lump of revenue every ten years, hostage to the customer’s capital cycle, custom enough that the service business behind it never standardizes. The large unit was the purest expression of that instinct — build the biggest possible thing, sell it to the biggest possible customer, book the biggest possible number. And the addressable market was a dozen skylines.

The mid unit was quietly telling us the opposite. Its economics didn’t live in the sale; they lived in the fleet — identical units, identical parts, identical service intervals, spread across a region with redundancy built into the count. That’s not a razor. That’s a razor-and-blades business, and the blades are an annuity.

Here is the part that should have been unforgivable: the best razor-and-blades operation on the planet was sitting one division over. The company’s aviation division had turned the aftermarket into an art form — the engine nearly given away, the money made over decades of service agreements on a standardized installed fleet of thousands of near-identical units. Same parent company. Same finance culture. Same playbook available for the cost of a phone call down the hall. And the power side kept swinging for the monument.

The four-hundred-megawatt ghost was that instinct made visible. It wasn’t a market need. It was an institution that could only imagine selling a bigger thing, when the thing it already had was telling it to sell a system.

But the customers were already there

The ghost was the supply-side half of the failure — we couldn’t stop building a thing nobody wanted. The demand-side half was worse, because it wasn’t a misjudgment. It was a refusal.

I had family in a horse community, and they showed me the answer years before I had a name for it. A group of horse people networked with each other, pooled their money, and bought a large patch of land together. Then they built the commons. A shared area for working manure. Common pasture for the horses. And because some of the animals were trained as jumpers, shared grounds laid out for jump training. They didn’t build a subdivision. They built a community organized entirely around a shared resource, because the shared version was better and cheaper than every family going it alone.

I looked at that and saw a power customer.

Put a small generating unit — call it 75 to 150 megawatts — at the center of eight or nine of those large farms and you’ve got a buyer a gigawatt salesman can’t see, because the buyer isn’t a city. It’s a community. And once I started looking, the pattern was everywhere the map got thin. Fly-in aviation communities, where people already share a runway and a hangar culture. Housing developments going up across the West, where power was never as dense as it is on the East Coast and the grid was never a given. Every one of them a natural buyer for a mid-size, networked, easy-to-maintain machine — and every one of them beneath the notice of a team that measured opportunity in gigawatts.

That was the real prize, and it was the exact inverse of the ghost. Build a network of 75- and 150-megawatt units — simple, small, easy to service — and you don’t book one heroic sale. You put forty or fifty units into the field and you sell the service contract behind every one of them. Recurring money, for decades, on a fleet you can actually maintain — instead of one giant machine, a single onetime contract, and the headache of networking all that power to wherever it had to go.

I brought it up. More than once. The sales-and-service office sat in a different city from the design-and-manufacturing center — and it answered the same three words every time: big money, big money, big money. The sub-two-hundred-megawatt market wasn’t big money, so it wasn’t a market. We ceded it — handed whole segments to competitors we simply chose not to compete with, because serving those customers didn’t feel large enough to be worth serving.

And here is the part that should have made the sale to any executive who could see past the current quarter, because the small end doesn’t just scale — it scales in a way the big machines never could. A small-unit buyer grows with the community it serves: add a unit when the farms multiply, add another when the airpark fills in, add a third when the development builds out the next phase. The fleet spreads across wider and wider regions, and at some point the spread itself becomes the product. Because once you have small units scattered across a set of unassociated communities, you can stand up a shared spare-parts pool — one contrived inventory serving all of them, so no single community has to carry a full parts base of its own. Each community draws on the pool; the pool is cheaper for everyone than a shelf of spares nobody uses most of the year. That is a new service size and a new kind of contract: service and spares as the recurring product, sold across a distributed fleet of small buyers who individually could never justify it and collectively can’t live without it. New contracts, renewing forever, on a base that only grows.

It was the best business in the building, and it was invisible to the people who ran the building — because they were quarter-focused executives hunting immediate, huge wins. A pool of small recurring service contracts doesn’t book like a nine-figure turbine sale. It doesn’t land in one quarter, doesn’t photograph well in a board deck, doesn’t move the number this period. It just compounds, quietly, for twenty years. And a leadership measured on the immediate huge win is structurally blind to the compounding small one — not because the executives were foolish, but because the instrument they were paid against couldn’t see recurring, distributed revenue at all. Same mispricing as the ghost, one level up: the organization optimized for the size of the sale and expensed the durability of the business.

And the pooled-spares model hides one more advantage the quarterly view could never price: whoever controls the spares controls the upgrade path. When you own the parts pool, you don’t just service the fleet — you improve it, one component at a time, through the channel you already run. A better blade, a more efficient hot-section, a new control module enters the pool, and it propagates across the whole installed base at the normal cadence of scheduled maintenance. No forklift retrofit, no heroic capital campaign, no ripping out a plant. The upgrade rides the service contract you were fulfilling anyway. The aftermarket stops being a cost center and becomes the distribution network for every technology gain you make.

Which makes the small distributed fleet the best new-technology launch site in the entire business — for exactly the reason it was easy to dismiss. On a single large machine, trying something new is terrifying: one unit is the site, so a first-of-its-kind failure takes the whole plant down and every megawatt with it. On a fleet of small units backing each other up, the outage risk of any one machine is a rounding error. You can field a new blade in one unit, watch it for a season while the rest of the fleet carries the load undisturbed, and only feed it into the shared pool once it’s proven. The redundancy that made the fleet reliable also makes it fearless — it turns every site into a low-stakes test bed, and the pool into the mechanism that scales the winners. Small, distributed, and pooled isn’t just the resilient architecture or the durable business. It’s the fastest, safest way to advance the technology itself — which is the one thing an engineering company is supposedly for, and the one thing the immediate-huge-win instrument was structurally built to miss.

That is the finding the four-hundred-megawatt ghost was hiding. We built a phantom product that had no customer, and in the same years we ignored the real customers who had no product. One instrument, pointed both directions.

The instrument

Run every one of these decisions through a single forensic control. Call it the cutoff line: did you optimize for one number, and quietly pay the bill on every other axis? Hold the record against it and the same two readings come back.

Sale versus service. The monolith is a lumpy sale every decade. The fleet is an annuity by design. Mispriced: recurring revenue — the exact business the aviation division was printing next door.

Monument versus fleet. A bespoke gigawatt machine is a one-off; a serial-produced fleet gets cheaper with every copy. Mispriced: the manufacturing learning curve — the tenth unit costing half the first.

The verdict

Two divisions of one company. One instrument. One division built a fleet and got an annuity. The other chased the four-hundred-megawatt ghost, ignored the communities already showing us how to build a commons, and got a lull and a funeral, on repeat.

The ghost is still with us. It’s every argument that the answer must be bigger when the answer was always more — more identical units, teamed, serviced, and spread among the people who were always ready to buy them. We built a phantom with no customer and turned our backs on the customers with no product.

And the deepest cut isn’t that we misjudged a market. It’s that the small, distributed, pooled fleet was the better business on every axis the quarter couldn’t see — durable revenue, a captive upgrade channel, the safest test bed an engineering company could ask for. The instrument the division leaders were paid against couldn’t read any of it. They optimized for the size of the sale and expensed the durability of the business.

But blaming the division CEOs stops one level short of the finding. They weren’t blind — they were aimed. A division CEO chases the carrot the parent CEO hangs, and when the only carrot is quarterly dollars, every rational division leader does exactly what ours did: reach for the lumpy immediate sale that lands this period and ignore the compounding, distributed business that pays out over twenty years someone else will be sitting in the chair to collect. They weren’t failing at their jobs. They were succeeding at the job they were actually given, which was to move a single number by the end of the quarter. The ghost, the ceded market, the pooled-service business we never built — none of it was a failure of engineering or even of judgment. It was a failure of the metric at the top. Make quarterly dollars the only thing you measure, and you will reliably, quarter after quarter, kill the best long-term business in the building and never see the body. That is the instrument turned on the people holding it: optimize your leaders for one number, and they will pay the bill on every axis that number can’t see — including the survival of the company they run.

And notice what the wrong metric kills, because it is never just one thing. A patient business plan and a patient technology fail the identical test: both pay out past the horizon the number can see, so both look like pure cost today. Quarterly dollars can’t tell the difference between a slow-growth vision and a slow-maturing innovation — it wipes out both, indiscriminately, for the same reason. The pooled-service community fleet that would have compounded for twenty years, and the new blade or new cycle or new material that needs a decade of development before it earns a dollar, are the same kind of casualty. Anything whose return lands beyond this period reads as a line item to be cut. So the company keeps only what pays immediately — which is precisely the work that required no vision to begin with. Run an engineering company on the wrong metric long enough and it stops being an engineering company. It becomes a sales desk with a famous name, quietly euthanizing its own future on both fronts at once: the slow business and the slow invention, buried in the same unmarked grave, by the same number.

You can watch it happen to a whole division. The same company had a nuclear business — reactors and fuel, headquartered in a coastal Carolina town — and over these years it simply went quiet. It is worth being precise about why, because the easy version is wrong and the true version is worse. The metric didn’t kill it; the domestic market had already gone silent on its own, the new-reactor order book emptied out years earlier by cost and public fear. What the metric did was guarantee nothing would ever wake it back up. A dormant division under a quarterly-dollar regime gets managed for cash, not invested for a comeback — and a comeback was the one thing on offer, because reviving that business would have taken exactly the work the number can’t see. I’ll come back to what that revival would have required. For now, hold the shape: the division wasn’t killed. It was left in amber. Same grave as the ghost, quieter burial.

Part two takes this same instrument out of the gas-turbine yard and runs it across the whole energy transition — redundancy, peaking, the petroleum barrel, and the nuclear fuel cycle — to a place where the mistake we made with the ghost is about to be made again, or finally corrected.

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.

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.