Aerospace NDT software for Nadcap suppliers: record control that survives an audit

NAS 410 currency is a date problem, not a certificate problem

NAS 410 Rev 5, issued September 2020, sets the qualification and certification requirements for personnel performing NDT, NDI or NDE in aerospace manufacturing, service, maintenance and overhaul. It is the standard almost every US prime flows down, running alongside EN 4179 in European supply chains. Rev 5 tightened sequencing: the specific examination is administered after at least 75 percent of the experience hours are accumulated, and the practical examination after 100 percent. Confirm which revision your purchase order actually invokes.

The audit question is never whether a certificate exists. It is whether the person who processed this part was current in this method at this level on this date. That takes four dates per operator per method: certification date, expiry, last annual near-vision examination, and last colour vision test, which must fall within the previous five calendar years. Miss any one and the certification is not current, whatever the certificate on the wall says. See NAS 410 certification requirements.

Model it as a matrix, not a folder. Operator by method by level, each cell carrying its own dates and its own next-action date, with a flag as each date approaches. That structure also answers the scheduling question, which is who can be put on this job today, and a folder of scanned certificates cannot answer it. Personnel certification tracking built this way stops expiries being discovered by an assessor.

Technique sheets are controlled per part number, per revision

In pipeline or structural work a procedure covers a class of joints. In aerospace, a technique sheet is written against a part number, sometimes against a specific feature on that part, and it names the parameters that produce a qualified inspection: penetrant method and sensitivity level, dwell and emulsification times, magnetising method and amperage, transducer frequency and angle, scan plan, kilovoltage and exposure time, image quality indicator selection and placement.

Because the technique is part-specific, the document count grows with the part catalogue. A supplier with a large part catalogue holds a technique sheet per part number and revision, each with a revision history and each referenced by jobs that ran under one particular revision. That is a database problem wearing the costume of a document problem, and it is why shared drives fail here: two revisions circulate on the floor and nobody can state which one governed a shipped lot.

The requirement is that a job record points at a technique revision, not at a technique. When Rev C supersedes Rev B, jobs already run under Rev B keep pointing at Rev B forever. An assessor sampling a two-year-old job then sees the document that actually governed it. Systems resolving that link to the current revision quietly rewrite history and produce a nonconformance the supplier cannot explain, because the evidence contradicting it no longer exists.

The frozen process, and who may change a parameter

The frozen-process concept comes from the customer side of the relationship. Once a technique is approved for a part number, the parameters producing the inspection are fixed, and a change does not take effect until the customer approves it in writing. Nadcap does not write that rule; primes do, through their process specifications and purchase order terms. The supplier obligation is to be able to prove the process did not drift between the approval and the shipment.

Proving it requires change history at the field level rather than the file level. A replaced PDF shows only that something changed. A parameter-level history shows that a dwell time changed, by how much, on which date, at whose request, and under which customer approval reference. When an assessor or a customer quality engineer asks why a parameter differs from their approved copy, only the second version answers the question without a meeting.

Approval routing is the other half. The person who authors a technique and the person who releases it are usually not the same, and in most aerospace NDT suppliers release authority sits with the responsible Level 3. Software letting any user edit a released technique erases that control entirely. See responsible Level 3 support for how the role is structured when a supplier contracts it rather than employing it.

Penetrant process control records under ASTM E1417

ASTM E1417/E1417M drives the fluorescent penetrant line, and the 2021 revision moved several check frequencies. Ultraviolet lamp integrity became a daily check rather than weekly. Method A(W) penetrants need weekly refractometer measurement of water content. Penetrant brightness testing and dryer oven verification moved from quarterly to semi-annual. Daily system performance checks against a known-defect panel remain the anchor of the whole regime, and the assessor starts there.

Suppliers usually record all of this. What they usually cannot do is connect it to parts. The check log lives in a binder beside the line, the job records live in the quality system, and the two are joined by date and by memory. An assessor who samples a part and asks for the system performance check covering the shift that part ran is asking for a join nobody has built, and the search takes minutes that feel much longer.

Building the join is not difficult once the checks are records with timestamps and the processing steps carry timestamps too. Every part then inherits the process control state of its shift automatically, and an out-of-tolerance check immediately identifies the parts at risk rather than triggering a manual reconstruction. That containment speed is the practical argument for putting process control inside NDT inspection software instead of beside it in a binder.

Magnetic particle field verification under ASTM E1444

ASTM E1444/E1444M sets the aerospace magnetic particle regime. System performance verification and black light intensity are daily checks. Field adequacy at the part surface is established with quantitative quality indicators or shims, and field strength is measured with a Hall-effect gaussmeter whose own accuracy is verified every six months. Each of those is a record with a date, a result, an instrument identity, and a person, and each is sampled independently.

The gaussmeter six-month verification is the classic quiet failure. It lapses, nobody notices, and every field reading taken afterwards is unsupported. The parts have shipped. Containment then means identifying every lot inspected between the lapse date and the discovery date, which is fast when the instrument serial number is bound to each result and archaeological when it was written on a bench log that has since been replaced.

That is the general rule for aerospace record design: bind the instrument, not the instrument name. Equipment calibration tracking that carries serial numbers, due dates and current status into every result turns the containment query into a filter. Without it, containment becomes an archaeology project performed under a customer escape notification, which is the worst possible circumstance in which to discover that your records do not join.

Radiographic technique and IQI records

A radiographic record has to reproduce the shot. Source or tube and its parameters, source-to-film distance, film or detector type and its identification, screens, exposure time, geometry, the image quality indicator selected and where it was placed, the essential hole or wire visible, and the density readings taken. AC7114/4 governs film radiography specifically, and AC7114/9 covers remote interpretation of radiographic film and digital images.

The reader sheet and the technique are usually separated in practice, because the interpretation gets stored with the job while the technique lives with the part. An assessor sampling a shot wants both together, plus the interpreter certification currency on the date of reading. Three records in three systems, joined by hand. That is a slow answer during an audit, and a slow answer is a finding waiting to be written up.

Remote interpretation has made this sharper. When film or digital images are read at a different site from the one where they were shot, the chain of custody, the reader qualification under the accreditation, and the transmission record all become auditable objects in their own right. A supplier offering remote reading needs those three recorded automatically, because a manual chain-of-custody log spanning two sites will not survive contact with volume.

The audit trail a Nadcap assessor samples

The assessor works backwards from a job. Pick a part, find the paperwork, then follow every thread it exposes: which technique revision, which operator, was that operator current, which process controls covered the shift, which instruments, were they in calibration, who reviewed the interpretation, what happened to the rejects. Each thread must terminate in a record with a date on it rather than in an explanation from a supervisor.

That makes the audit a data-model test rather than a documentation test. A supplier with excellent documents and no relationships between them fails threads two, four and six. A supplier with adequate documents and complete relationships passes all of them in a fraction of the time, which also shortens the audit and reduces the surface area the assessor has time and appetite to explore further.

Run it on yourself first. The self-audit is a Nadcap requirement and the most frequently cited nonconformance area, and it works only when re-run against the current criteria revision with objective evidence attached to each line. Nadcap AC7114 audit readiness covers how that pre-audit pass is structured and what gets sampled. The gap you find yourself is always cheaper than the gap the assessor finds.

What aerospace changes about software selection

Aerospace inverts the usual priority. In most NDT segments the report is the deliverable and the records support it. Here the records are the deliverable, because accreditation is what lets you quote at all. So evaluate on record structure: can a job bind to a technique revision, can a certification carry four independent dates, can a process control check join to the parts it covers, can an instrument bind to a result.

Then evaluate change control. Who can release a technique, is the approval captured with an authority reference, is field-level history retained, and can a released document be edited without leaving a trace. Ask the vendor to demonstrate an edit to a released technique and to show you the resulting audit entry on screen. If the demonstration is a slide rather than a click, the capability is aspirational rather than real.

Atlantis ERP holds certificates with vision tests, instrument calibration records, procedures with controlled revisions and method-specific reports; binding a technique revision to a part number on each job is scoped during implementation. Configurability matters here because every prime flows down a slightly different set of required fields, and a fixed schema forces the difference into free text. Affordable, accessible, fully customizable. Request a demo and bring your hardest audit thread, the one that currently takes three people and a shared drive to answer.

What Atlantis ERP does for aerospace NDT records

Each technician certificate records its scheme, with NAS 410 held as another scheme alongside SNT-TC-1A, CP-189 and ISO 9712, and its level, method, certifying body, issue and expiry dates, training and experience hours and exam results. Near-vision, far-vision and colour perception tests are recorded with their own expiry, status is worked out automatically, and warning tasks are raised before a certificate or a vision test lapses. Procedures sit in a register with document number, revision, method and acceptance criteria, move through draft, review, approval and publication, and keep a full revision history with approved revisions locked.

Penetrant, magnetic particle, radiographic, ultrasonic and eddy current work is reported on its own report type, with review and approval signatures. Instruments are tracked by serial number with calibration certificates, due dates and expiry alerts, and a warning is raised when out-of-calibration equipment is assigned to a job. See the NDT Reports app and the ISO 17020 software requirements.

The same system is set up for other industries too: tank inspection software for API 653 contractors, pipeline inspection software for US NDT contractors and refinery and petrochemical inspection software.

What Atlantis ERP does not do for a Nadcap supplier

It is not Nadcap, PRI or eAuditNet, and using it does not make a supplier compliant with AC7114 or with any customer specification; accreditation comes from the audit. It does not approve technique sheets on your customer's behalf or replace the responsible Level 3's sign-off. Dedicated penetrant system-check and magnetic particle field-verification logs are not standard apps; where you need them in the same system, they are set up during implementation.

What it does is keep the threads an assessor follows in one place, so the answer to a sampled job is a record rather than a search. Start a free trial, or book a guided walkthrough with your hardest audit thread.

Questions aerospace NDT suppliers ask

Does Nadcap accreditation require particular software? No. Nadcap accredits a process against AC7114 and its method slash sheets by examining evidence you produce. No software product is accredited and no vendor can supply accreditation. What software changes is how completely and how fast you can produce evidence when an assessor pulls a thread, which is what most of the audit day actually consists of.

Which NAS 410 revision should we track against? The one your customer purchase order or process specification invokes. NAS 410 Rev 5 was issued September 2020 and is the revision most US aerospace contracts cite. Build the tracking matrix against the invoked revision and record that revision on each certification record, because a supplier serving several primes can be held to more than one revision simultaneously.

How should a responsible Level 3 be represented in software? As an authority attached to methods and to release actions, not as a job title in a field. The record needs to show which Level 3 approved which technique revision, in which method, on which date, and that their own certification was current then. That is a link from person to method to document to date, which a folder structure cannot express.

Can process control checks and job records live in the same system? They should. The join between a check and the parts processed in its window is what an assessor asks for and what containment depends on when a check fails. When checks are timestamped records and processing steps are timestamped records, the join is automatic. When one lives in a binder and the other in a database, someone rebuilds it by hand under pressure.

What is the highest-value record fix before an audit? Bind instruments and technique revisions to results. Those two links account for most of the threads an assessor follows and most of the time lost answering them. Personnel currency comes next, because lapsed vision examinations and colour vision tests stay invisible until someone queries the dates. Start a free trial or request a demo to test your own audit threads.

Request a consultation