In aviation, an untraceable part is a defective part, regardless of how beautifully it was machined. The airworthiness release certificate — EASA Form 1, FAA 8130-3, or their bilateral equivalents — is not a label attached to the product. It is the product in legal and airworthiness terms, because it is the only artefact that carries the conformity statement forward through the aircraft's life.

A perfect component with an invalid certificate cannot be fitted. A marginal component with a valid, accurate certificate at least enters the system with its history intact, where inspection and surveillance can act on it. Across two decades in automotive and aerospace quality, I have found that most production managers accept this intellectually but still let the certificate be treated as the last bureaucratic hurdle before shipping — which is precisely where errors breed.

The stamp on Block 19 or 20 is a personal legal attestation. When you sign it, you state that the work described is complete, that the part conforms to the approved data cited, and that you personally verified it or directly supervised those who did. Nobody downstream can repair that attestation. Treat the certificate as a live airworthiness record rather than shipping paper, and the error rate drops on its own.

Anatomy of the EASA Form 1

Block-by-block accuracy matters because each block answers a distinct question that somebody downstream — a repair station, an operator's continuing airworthiness organisation, an accident investigator — will rely upon. Block 4, the work order reference, ties the certificate to the controlled record set. Block 11 describes the work accomplished, and vague entries here are among the most common findings in any audit: "overhauled per CMM" tells nobody which CMM revision, which section, or whether repairs beyond standard practice were performed.

Block 12 states the part number released; Block 13 the quantity; Block 14 the serial or batch number. Any mismatch between the physical part and Blocks 12 through 14 voids the release in practice, even if the work itself was flawless. Block 12b deserves particular attention: "new/unused" and "used" carry strict meanings under Part-145 and Part-21 rules, and misdescribing a tested or bench-run unit as new creates a false history that propagates permanently into the operator's records.

Block 15, the airworthiness approval tag number, must be unique and logged so the certificate can be traced back years later. Blocks 16 and 17 cite the approved data — design data, maintenance manual, repair specification — with enough precision that an engineer can retrieve exactly the revision used. When auditors write findings against Form 1 accuracy, it is most often these citation blocks that fail, not the physical work.

The certificate is a live airworthiness record: its accuracy governs every maintenance decision made on the part for the rest of the aircraft's life.
The certificate is a live airworthiness record: its accuracy governs every maintenance decision made on the part for the rest of the aircraft's life.

Dual Release and What It Actually Requires

Dual release means one certificate carries both the EASA Form 1 statement and the FAA 8130-3 statement, releasing the article under both regulatory systems simultaneously. It sounds like a formality. It is not. The two systems define the scope of release differently, particularly for components: a part new-released under Part 21G without an FAA production approval generally cannot be dual-released as a new article, because the FAA side requires manufacture under an FAA-approved production system or an approval under a bilateral agreement.

Workshops that stamp dual release reflexively on everything they ship are creating invalid FAA releases, and those certificates surface years later during operator audits or, far worse, during an investigation. The correct approach is a documented decision process per work scope. For maintenance and overhaul under an appropriately rated Part-145 organisation with the corresponding FAA part certificate or bilateral authorisation, dual release is legitimate. For articles outside the bilateral's scope, issue single releases and tell the customer plainly.

Dual release eligibility check before signature

  1. 01Define work scopeNew manufacture, maintenance, overhaul or repair — each has different bilateral coverage.
  2. 02Check approvals heldPart-145 rating, FAA part certificate, or bilateral agreement authorisation.
  3. 03Confirm article eligibilityVerify the article falls inside the bilateral's scope for that work type.
  4. 04Select release typeDual or single release; single release is communicated to the customer explicitly.
  5. 05Cite the correct clauseReference the applicable bilateral agreement clause in the remark, not a paraphrase.
The check runs per work scope, not per customer habit, and the outcome is recorded in the work order.

Authorised release certificate staff must check eligibility before signing, not afterwards, and record that check in the work order. The remark wording matters too: the standard block must reference the applicable bilateral agreement clause, not a homemade paraphrase. Inspectors copying a colleague's remark text from an old job is exactly how incorrect bilateral citations get institutionalised across years of paperwork.

Tracing a Documentation Error to Its Full Extent

When a documentation error is discovered — a wrong serial number, an incorrect part number, a cited manual revision that never existed — the first question is not "who signed it". The first question is: how far has this error propagated? The part may already be fitted to an aircraft. The operator's records now contain a false entry. Downstream scheduled maintenance may have been calculated from a false in-service date or a false condition.

Traceability of the error means reconstructing the entire chain: work order, traveller, inspection records, certificate copy, shipping documents, customer receipt records, and installation records in the aircraft technical log and status sheets. This requires that you retain controlled copies of every release certificate issued, indexed by certificate number, work order, part number and serial number. Without that register you cannot even identify which customers received certificates affected by a systemic error — an inspector who misdated every certificate in a week, or a template carrying an obsolete manual reference.

Error traceability also demands you distinguish isolated transcription errors from systemic ones. A single mistyped serial is a human factors event; the same wrong data-field entry across thirty certificates points to a training gap or a form layout that invites the mistake. Each type gets a different corrective path, and only the systemic one justifies contacting every recipient.

A wrong serial number in Block 14 can leave a timed-out part in service — the paperwork error becomes the proximate cause of an airworthiness defect.

Common Failure Modes in Release Paperwork

Certain errors recur so reliably that they should be treated as expected findings in any internal audit. Wrong serial numbers dominate: they arise when the inspector copies from the routing paperwork rather than the physical part, or when the tag and the certificate get separated and re-paired on the bench. Quantity errors in Block 13 follow, usually when a kit is split or a partial shipment occurs and the original certificate is reused without amendment.

Obsolete data citations rank third — the workshop updated to a new manual revision mid-job, and the certificate cites the old one, inconsistently with the actual work records. Each of these is detectable at source with a two-minute check that too few organisations mandate. Then there are the self-inflicted failures: certificates signed by staff whose authorisation had lapsed, and certificates issued against work orders still open because someone closed the paperwork before the final test results were filed.

Copies altered with correction fluid are an immediate regulatory violation, since release certificates are permanent records and corrections must follow the defined amendment process: single line-through, initials, date, and where permitted a new certificate with cross-reference to the voided one. I have grounded shipments over a corrected copy. Investigators and auditors read a mutilated certificate as concealment, fair or not, and the reputational damage exceeds the cost of reissuing properly.

Recurring Form 1 errors and their causes

What teams do wrong

  • Copy serial numbers from routing paperwork, not the physical part
  • Reuse the original certificate after a kit split or partial shipment
  • Cite the manual revision current at shipping, not at the work
  • Sign outside the authorised scope during holiday cover
  • Amend a copy by hand or with correction fluid

What works

  • Verify serial and part number against the part itself before Block 14
  • Issue an amended or new certificate for every quantity change
  • Freeze the data citation at work order closure
  • Live register of signature scopes, checked against issued certificates
  • Defined amendment route: line-through, initials, date, cross-reference
Each failure mode pairs with the control that catches it at source rather than after shipping.

Controlling the Process at the Point of Signature

The certificate should be produced by the quality system, not composed by hand per shipment. Template-controlled generation from the work order data eliminates most transcription errors at a stroke: part number, serial, quantity and work description flow from the recorded data rather than an inspector's memory of it. Where templates exist, they must be configuration-controlled, because an uncontrolled edit to a template — a well-meaning tweak to the remark text — can silently invalidate hundreds of subsequent releases. The template revision log belongs on the standing audit checklist.

The system should also hard-block certificate generation while the work order carries open operations or unfiled test results. Signature authority needs the same discipline: maintain a live register of authorised release certificate staff with the scopes each person may sign for, and review it against the certificates actually issued. An inspector authorised for mechanical components who signs an avionics release is a recurring finding, often committed innocently during holiday cover.

Independent verification before signature — a second person checking the physical part against Blocks 12 to 14, and the manual citation against the record — is the single most effective barrier I have implemented. It costs minutes. Compare that with the cost of a fleet-wide records investigation after a mis-identified unit reaches an operator and gets installed.

Treating Paperwork Errors as Safety Events

The cultural shift worth insisting on is this: a Form 1 error is reported, investigated and closed exactly as a nonconforming product would be — not as a typo, not as something quietly fixed with a reissued certificate. The reason is mechanical, not sentimental. The airworthiness system depends entirely on record accuracy for the aircraft's remaining life; an operator planning a structural inspection threshold or a life-limited part replacement is acting on data that originated in your paperwork.

Investigation therefore follows product-nonconformity logic. Contain the affected certificates, assess propagation into operator records, notify recipients formally where required, correct through the proper amendment route, and feed the root cause back into template design, training or the verification step. Measure documentation findings separately from hardware findings in internal audit metrics, because a workshop can pass every dimensional check and still be one paperwork incident away from losing customer approvals.

The organisations that last in this industry are the ones whose inspectors hesitate before signing — not because they fear blame, but because they understand exactly what the signature asserts and what its accuracy is worth to the aircraft flying overhead.