The 13B rotary doesn't forgive inattention. It rewards warmup routines, disciplined cooldowns, and oil changes that actually happen on schedule. Not the ones you intend to do. Not the ones you mean to get to. The ones you physically execute before the engine starts accumulating debt.
Running a :contentReference[oaicite:1]{index=1} in a hillclimb program turned that into something more than theory. It became routine. Then it became habit. Then it became a kind of mechanical discipline that stopped feeling optional.
The uncomfortable part is that the discipline held. The engine never failed because of neglect. It failed because the car did not survive an entirely different kind of event — a guardrail, unrelated to anything mechanical at all.
Knowing versus doing
Rotary engines are straightforward in their demands. Warm them properly. Cool them properly. Keep oil consumption intentional. Monitor compression over time. None of this is obscure. The entire maintenance philosophy is widely known and consistently ignored in equal measure.
The gap is not knowledge. It is execution under routine conditions. I could list what the 13B needed in precise detail long before I ever maintained one properly. The difference was whether that list actually translated into behavior every single time the car ran.
What the program actually asked of the car
A hillclimb program is a specific stress profile. Short, hard runs with extended idle gaps between them, repeated over a full day. That combination is thermally inefficient in the worst possible way for a rotary: repeated heat cycles without sustained equilibrium.
The maintenance strategy was built around that reality. It worked. The engine stayed consistent, run after run, season after season. Nothing about the mechanical discipline was theoretical — it was validated continuously by the fact that the engine kept doing exactly what it was supposed to do.
The problem is that validation only tells you what did not fail. It does not tell you what might have, under a different failure mode entirely.
The accident, and what it doesn't teach you
The ending is not mechanical. The :contentReference[oaicite:2]{index=2} was put under a guardrail by another driver. The engine, the maintenance program, the discipline — none of it is responsible for the outcome. The car is now being parted out.
That creates a mismatch between expectation and conclusion. Mechanical empathy narratives tend to expect mechanical endings. This one does not have that shape.
The rotary did not fail the program. The program was simply never tested against the actual failure mode that ended the car.
What the discipline actually bought
The maintenance regime still mattered. Every run the engine made was a run made without deferred failure accumulating in the background. That is not dramatic, but it is real.
It means performance data from the car was not distorted by neglect. It means failures that did not occur can be ruled out with confidence. It means the engine’s behavior was representative of its design, not its maintenance debt.
That is a quieter kind of correctness. It does not survive accidents well as a narrative, but it is still the baseline condition under which everything else happened.
What's left
The car is transitioning into parts, which is the standard lifecycle for most project builds at some stage. The maintenance philosophy remains unchanged: warm it properly, cool it properly, and do not treat oil as optional.
The difference now is only evidentiary. There is no longer a single complete machine that demonstrates the outcome of that discipline over time. There is only the record of what it did before something unrelated ended the experiment early.