An AOG part can clear customs in hours and still wait at the receiving desk because of its paperwork: the wrong certificate type for the operator's authority, a used US part without the dual release statement, a Form 1 whose part number misses the dash number on the PO. Most of these problems are visible on the certificate before the part ships. AI makes it practical to look.
TL;DR. Ask for the certificate PDF with the quote, not with the part. Check four things before shipping: certificate type against the installing organisation's rules, part number and serial against the PO, Block 11 status against what was bought, and Block 12 for the dual release statement when one is needed. Doana reads certificate type and part numbers from Form 1, 8130-3 and TCCA Form One in its web app, extracts EASA Form 1 box by box, and extracts 8130-3 and other release certificates field by field in custom pipelines. Acceptance stays with the inspector.
Which paperwork problems stop an AOG part?
| Problem | Where it shows | Check before shipping |
|---|---|---|
| Certificate type not acceptable to the installer | Block 1 and 2, authority | Release paperwork map |
| Used US part to Europe without dual release | 8130-3 Block 12 | Dual release on FAA 8130-3 |
| Part number or dash number differs from the PO | Block 8 | Form 1 vs invoice mismatch |
| Status differs from what was bought | Block 11 | Overhauled vs Inspected/Tested changes value and acceptance |
| Serial missing or unreadable | Block 10 | Scanned or unreadable Form 1 |
| Certificate missing, only a CoC sent | Whole document | EASA Form 1 vs CoC |
Where does AI help?
On reading and comparing, at night, across a batch:
- Sort a mixed batch. Several quotes, each with a certificate: read the certificate type and part numbers from each and match them to PO lines. Doana's web app does this for Form 1, 8130-3 and TCCA Form One.
- Read every block of a Form 1. Status, remarks and the signed release block, with the page each value came from and a list of uncertain values. Doana does this self-serve for EASA Form 1: Authorised Release Certificate OCR.
- Read 8130-3 and other certificates field by field. For a team whose certificates are mostly US tags or Canadian Form One, Doana builds a custom extraction pipeline on its own documents, with output to the format its systems use.
- Flag mismatches for a person. A part number that differs by one dash number, a missing serial, a Block 11 that doesn't match the PO.
Where does a person still decide?
Whether the certificate is acceptable, whether the part is eligible for installation, whether a supplier's correction is good enough, and whether to quarantine. AI reads the document; it does not certify airworthiness or authenticity. The installer's record still needs its own installation certification.
What should an AOG desk change?
- Put "legible PDF of the release certificate" in every AOG RFQ.
- Run the four checks on the PDF before accepting the quote.
- Keep the extracted fields with the PO, so receiving compares the physical part against data already checked.
Next
For the receiving side, use the EASA Form 1 incoming inspection checklist. For a custom pipeline on your certificates, use the contact form.
Sources
- https://www.easa.europa.eu/en/faq/66700
- https://www.easa.europa.eu/en/faq/43770
- https://www.faa.gov/documentLibrary/media/Order/Order_8130.21J.pdf
- https://doana.ca/en/easa-form-1-automation
- https://doana.ca/en/contact
