When a window blows out at 36,000 feet, the first call from the quality organisation isn't to engineering. It's to traceability. Can you tell the investigator – within the first hour – which technician torqued which fastener on that frame, with which calibrated tool, on which shift, using material from which lot, under which deviation approval? If the answer takes days of digging through fragmented systems, the part failure is your second problem. The first is that your quality system was already broken, and nobody noticed because the audits kept coming back clean.

The Ryanair window blowout is dragging Boeing's stock down. Everyone wants to talk about the window. I want to talk about the system that should have been able to reconstruct it – and in most aerospace plants, can't.

What traceability actually means in aerospace

Not lot numbers. That's the beginner's definition. In aerospace, traceability means reconstructing the entire decision chain – every torque value, every inspection sign-off, every material certificate, every tool calibration record, every deviation approval. A single window assembly has dozens of touch points. Each one is a traceability node. Each one is a place where a human being made a decision, documented it – or didn't – and passed the part forward.

When I walk a line – whether it was building a greenfield QA operation for 900 people at SNOP, or now leading manufacturing engineering technical authority across North America at Airbus – the first thing I look for isn't whether records exist. I can find records anywhere. Most of them are even accurate. The question is whether I can reconstruct the decision chain from those records in real time. Can I follow a single serial number from raw material entry through every workstation to final inspection and pull up every sign-off, every tool serial number, every deviation granted and who approved it? That's traceability. A filing cabinet full of controlled documents is not traceability. It's documentation theatre.

Documentation theatre passes audits but fails investigations

Most traceability systems fail the same way. They pass audits. They satisfy AS9100 clause 8.5.2. They produce a certificate of conformance. But when a part fails at altitude and an investigator asks who installed this seal, with what torque value, and was the tool in calibration on that date – the answer takes days. Fragmented ERP entries. Paper travellers coffee-stained and scanned into a SharePoint folder with a naming convention nobody remembers. A calibration database that doesn't link to the production record. A deviation log that references a part number but not a serial number.

I've lived this. Before we implemented QRQC and A3 discipline at Witte Automotive, we could tell you a defect existed but couldn't reconstruct how the part was built. The gap between having records and being able to reconstruct the decision chain is where investigations die and regulators lose patience.

An audit measures whether you kept records. An incident measures whether you can read them.

I've sat through EASA audits that ended with 50% fewer findings in one cycle. Not because we had more documents – because our traceability was real. An auditor asks for a serial number, and in minutes – not hours – you show them the full history: material cert, torque record, tool ID with calibration date, inspector sign-off, deviations and their approvers. When that takes five minutes, the audit is a conversation. When it takes five days, the audit is a finding.

Routing verification builds the history in real time

At Airbus, the Routing Verification KPIs we implemented cut internal lead time by 97%. People focus on the speed number. It's a good number. But the mechanism wasn't speed – it was building traceability into the routing itself, so every part's history is reconstructable in real time, not pieced together after the fact from whatever survived.

Every workstation in the routing is a gate. The part cannot advance without its traceability record being complete – torque value logged, tool ID captured, inspector e-signature attached, material lot confirmed against the certified supplier record. Not paper. Not a sticker. An electronic record linked to the serial number, timestamped, immutable. When the part leaves the station, its history is already built. When it ships, its history ships with it. When it fails ten years later at 36,000 feet, you don't reconstruct the history. You retrieve it.

Quality management and systems engineering are the same discipline. The routing is the traceability system. The process flow is the audit trail. Bolt traceability on after manufacturing as a documentation exercise, and you get theatre. Build it into the routing, and you get a system that survives a real investigation.

Key takeaways

  • Traceability in aerospace means reconstructing the full decision chain – torque values, tool calibration, inspection sign-offs, material certs, deviation approvals – not just lot numbers on a traveller.
  • Systems that pass AS9100 audits but can't answer "who, what, when, with what tool" in minutes are documentation theatre, not traceability.
  • Routing verification builds traceability into the manufacturing flow so every part's history is complete at each workstation gate, not reconstructed afterward.
  • If your traceability system takes longer than your root cause investigation to produce a part's history, your quality system is one incident away from the same headline.

The Ryanair window will be fixed. The investigation will conclude. A root cause will be identified – a seal, a fastener, a procedure, a human error. The industry will move on. But if your traceability system can't answer who, what, when, and with what tool for every part on your line – right now, today, without calling three departments and waiting for someone to find a binder – the window didn't fail first. The traceability did.