EASA Form 1 extraction
Doana turns Authorised Release Certificates into structured data: every item line, every serial number, both release blocks. Each value carries a confidence score and the page it came from, so reviewers only check what is uncertain.
Boxes 1 to 14
Every value returned with a confidence score and source page
Works inside ChatGPT, Claude and your agents
Every value returned with a confidence score and source page
Receive the certificate
By web upload, through the API, or from ChatGPT and Claude over MCP. PDF up to 50 MB and 20 pages, or a JPEG or PNG scan.
Extract box by box
Header boxes 1 to 5, one record per item line for boxes 6 to 12 with serial numbers as a list, and blocks 13 and 14 kept separate.
Flag what is uncertain
Values under 0.7 confidence are listed for review. A box Doana cannot read comes back empty, not filled in by a fallback.
Output
Broker-ready data, draft replies, and review notes
Operational gap
Workflow
The output follows the form itself, so every value maps back to the box a reviewer sees on paper. Multi-item certificates return one record per line, and the result lists the paths that need review in uncertainFields (threshold 0.7).
Connect Doana over MCP and send the certificate in the conversation: the same box-by-box result comes back, ready to check or pass on.
Three kinds of software read Form 1 today. They answer different questions, so pick by where the certificate goes next.
| Criterion | Doana | Standalone certificate parser | MRO / CAMO suite |
|---|---|---|---|
| Fields captured | Boxes 1 to 14, per item line, both release blocks | Mainly part number, serial, supplier, date and certificate type | The fields the suite needs for its receiving and work-order records |
| Low-confidence values | Listed for review; unreadable boxes come back empty, with no fallback fill | Confidence score; some fill gaps with a pattern-matching fallback | Usually typed or checked by hand at receiving |
| Evidence per value | Source page on every extracted value | Link to the stored PDF | Document attached to the part record |
| Release blocks 13 and 14 | Returned separately, sub-boxes A to E | Not listed in its documented fields | Handled in the suite’s own release workflow |
| Where it runs | Web upload, API, and MCP for ChatGPT and Claude | Its own web app | Inside the MRO system |
| Your MRO or ERP | Kept; Doana feeds it structured JSON | Kept; CSV export | The suite becomes the system of record |
Categories summarise public vendor documentation reviewed in September 2026: AMO CertVault (docs.briankimemia.is-a.dev/amocerts) as a standalone parser, Aviatize (aviatize.com/easa-maintenance-crs-software) as an MRO/CAMO suite. Check each vendor for its current capabilities.
Internal links
The one that returns the boxes your receiving decision depends on. Compare four things: whether blocks 11 to 14 come back or only part number, serial and date; whether each value carries its source page; whether an unreadable box is left empty or filled by a fallback; and where the tool runs. Doana returns boxes 1 to 14 with a confidence and page on every value, from ChatGPT, Claude or your own agent over MCP. For FAA 8130-3, see the question below.
Doana benchmarks its Form 1 extraction offline against a human-reviewed gold set, with exact-match checks on the critical boxes: 3 (tracking number), 8 (part number) and 10 (serial numbers). In the API result, every value also carries its own confidence and page, and anything under 0.7 is flagged for review. Ask for a test on your own certificates.
According to its public documentation, AMO CertVault is a certificate repository: upload a PDF and it extracts part number, serial, supplier and date, with a regex fallback when the AI fails. Aviatize is an MRO/CAMO suite that attaches Form 1 and 8130-3 to work orders. Doana extracts every Form 1 box with its evidence and sends the result to the system you already use, including ChatGPT, Claude or your own agents over MCP.
Yes. Each line of boxes 6 to 12 becomes its own record with its own part number, quantity, status and list of serial numbers.
Yes. Doana exposes the extract_easa_form1 tool over MCP, so ChatGPT, Claude or your own agent can send a certificate and receive the same structured result. The EASA Form 1 API page documents the fields, authentication and upload limits.
No. Doana extracts document data to support human review. Airworthiness, authenticity and regulatory determinations remain with qualified reviewers.
Not box by box yet. Extraction with confidence and page is EASA Form 1 only: an FAA 8130-3 sent to extract_easa_form1 comes back as documentType unknown instead of being forced into Form 1 boxes. The Doana web app reads the certificate type and part numbers from 8130-3 tags, and every 8130-3 block can be extracted in a custom pipeline set up on your own documents.
The API returns JSON that maps directly to spreadsheet columns: one row per item line, with serial numbers kept as a list.