About
What this is
A single-purpose tool that converts an AS9102 Form 3 document into an Excel spreadsheet. It is built for small and mid-sized aerospace suppliers whose customer requires a first article inspection report but who do not run a dedicated FAI platform.
Why it exists
Aerospace manufacturing digitised how inspections are performed. It largely did not digitise what happens to the data afterwards. A shop can own a CMM, export a clean Form 3, and still have someone retype every measurement into a spreadsheet because the downstream column set lives in Excel.
A part with 150 ballooned characteristics measured across six sample pieces produces 900 data cells. None of that transcription adds quality insight. It is pure friction, and it is the sort of friction that a small tool can remove entirely — provided it stays small.
Who it is for
- Small and mid-sized machine shops in an aerospace supply chain, typically 20 to 200 people.
- Quality engineers who own the FAIR package and the customer submission.
- Suppliers who do not run a dedicated FAI platform, and who cannot absorb a six-week pilot or an annual contract to solve one transcription task.
Who it is not for
- Large primes and tier-1s with an existing FAI platform. Your platform should already be handling this, and if it is not, that is a conversation to have with your vendor.
- Anyone who needs a compliant FAIR package produced. This tool outputs data. It does not produce a submission package and it does not certify anything.
- Chinese domestic military programmes operating under GJB 908. That standard uses different form templates. See AS9102 vs GJB 908.
How it is built
- No backend
- A static site. There is no server that receives your files, and no database holding them.
- No third-party libraries at runtime
- The spreadsheet writer and the PDF text extractor are implemented directly, so there is no supply-chain surface and no dependency that can silently change behaviour.
- Client-side by construction
- The no-upload guarantee is architectural rather than a policy. There is nowhere for a file to go.
- Mobile-first
- The interface is designed for a phone first, because that is where a quality engineer will open it when a supplier sends a Form 3 at short notice.
Published limitations
Stated plainly, because a tool that overstates itself is worse than no tool:
- Typed PDFs only. Scanned and handwritten documents are not supported.
- The PDF text extractor is deterministic rather than model-based, so unusual table layouts may need the paste box instead.
- No pass/fail calculation, no FAIR formatting, no drawing ballooning, no platform integration.
- Layouts vary between QMS vendors, so some documents will require manual correction after extraction. The tool flags what it is unsure about rather than guessing silently.
Contact
Questions, bug reports, purchase enquiries and invoice requests: [email protected]. See also the contact page.