A Failed Peel Test, a Missing Spec, and What I Learned About Henkel Aerospace Adhesives

Last March, I was standing in our lab holding a failed peel test. The adhesive had cured for 24 hours at room temperature, the surface had been cleaned, and the bond still came apart like a sticker. It made the kind of popping sound you expect from a plastic lid snapping, not a structural joint.

The first thing I did was pull the product spec. The line item said “Henkel aerospace adhesives” under product family, but there was no exact grade. No cure schedule. No surface preparation notes. Just a product family name and a revision date that was three years old.

I’m a quality and compliance manager at an industrial materials company. I review roughly 200 documentation sets per year before they go to customers. In Q1 2025, I rejected about 8% of first-round submissions for missing or ambiguous data. That may not sound huge, but when a missing number means a failed bond, 8% is too many. That failed peel test changed how I think about documentation.

The Problem Wasn’t the Glue

It’s tempting to think “adhesive is glue.” You put it on the part, hold it together, and it sticks. That simplification fails more often than any product defect. A structural adhesive used in aerospace is a formulated system. The cure temperature, the mixing ratio, surface preparation, and fixture time are all connected. Change one variable and the bond can look fine for a day, then let go under load.

To be fair, the old datasheet wasn’t exactly wrong. It was incomplete. And incomplete is worse than wrong in some ways, because incomplete doesn’t trigger the alarm. A wrong number gets questioned. A missing number gets ignored.

From the outside, a datasheet looks like a simple PDF. The reality is that every line is a decision: which test method, what surface prep, what environmental limit. When someone removes a line to make the document simpler, they’re making a decision without seeing the consequences.

One Bad Spec Led Me to the Henkel Portal

Once we realized the spec was missing the exact grade, we called our Henkel rep. He sent us a link to the Henkel portal—and I’ll be honest, my first thought was “oh no, another customer portal.” Then I looked at the actual product data. The portal had the full technical datasheet for the Loctite grade we needed, including the cure schedule that the old PDF had lost. It also had application notes, compliance documents, and a revision history. We could see when the datasheet was updated and what had changed.

When I compared the old PDF and the portal-generated sheet side by side, I finally understood why detailed specs matter. The old sheet said “cure at room temperature.” The portal sheet said: 22–25°C, seven days to full structural strength, or 60 minutes at 120°C for an accelerated schedule. One line doesn’t look like a big deal. But for a production manager, the difference between seven days and one hour is a week of downtime. It’s not fine print. It’s the actual product.

The Same Problem Shows Up Everywhere

I started checking other product families after that. The same pattern appeared again and again—or rather, it showed up in every category we reviewed. With 2 part marine epoxy, the mixing ratio is not a suggestion. It’s a stoichiometric ratio. If the spec says 2:1, you need 2:1, not “roughly.” Under-mix the curing agent and you get a surface that stays tacky forever and a bond that fails under stress. The chemistry doesn’t care about your preferences.

IR coatings are similar. The curing schedule affects more than durability; it affects optical performance. Get the film thickness wrong and the reflection profile changes. A coating that looks fine under a flashlight can still be useless because it’s reflecting the wrong wavelengths.

When people search for “how to make resins,” they’re usually looking for a recipe. I understand the instinct. But resin formulation is not baking, where a little extra vanilla is fine. The resin-to-hardener ratio, the cure temperature, the humidity, the substrate—they all matter. If you’re starting from scratch, the Henkel portal at least gives you a set of tested starting points. It won’t turn you into a chemist overnight, but it can keep you from inventing a failure mode.

What Actually Changed

After the March failure, my team moved the most common product documentation into the Henkel portal workflow. The result wasn’t a complete overhaul. Some custom formulations still need old-style spec sheets. But for standard products, the difference was obvious. Our document turnaround went from five working days to two.

The automated process eliminated most of the data entry errors we used to have, because product details come from one source instead of being retyped into each new sheet. More importantly, the revision history ended the “who changed this?” arguments. Every datasheet has a timestamp.

That said, I’m not saying every traditional process is bad. At least, that’s been my experience with standard products. For highly custom work, a blank spec sheet and a knowledgeable engineer are still the best tools. But the standard stuff? Let the portal handle it.

Performance claims need substantiation. Per FTC advertising guidelines, a claim like “cures at room temperature” has to be truthful and non-misleading. That’s why data sheets need test conditions, not just a marketing one-liner. The same discipline applies internally: if you can’t show the test method, don’t write the spec.

What I’d Do Differently

I don’t remember the exact cost of that failed batch—don’t hold me to the number—but the rework, replacement shipping, and downtime were in the five-figure range. That’s why I keep saying: the cheapest spec is the one that prevents the failure, not the one with the lowest initial price.

I also almost never trust a spec that doesn’t include a revision date. The old datasheet had a date, but it was buried in a footer and hadn’t changed in three years. Now I check the revision history before I read the first page.

The failed peel test wasn’t a catastrophic event. No one got hurt, and the part was caught before it shipped. But it was a reminder that quality work is mostly about making the invisible visible. The Henkel portal didn’t create perfect documentation on its own. It gave us a way to check our assumptions and see what we were actually specifying.

If you’re in the same spot I was—staring at a spec that seems fine until it isn’t—start with the details you can’t see. Whether you’re working with Henkel aerospace adhesives, a 2 part marine epoxy, or an IR coating, the answer is usually in the data. Go find it before you need it.