NDT Reporting Software for Aerospace: NADCAP-Ready Documentation

NADCAP audits the paper trail with the same rigor as the process

Aerospace NDT is unusual among industrial inspection sectors in that the audit itself is as procedurally exacting as the inspection technique being audited. A National Aerospace and Defense Contractors Accreditation Program (NADCAP) audit against the AC7114 family of NDT audit criteria doesn't just confirm a technician can run a phased array scan or read a radiograph correctly — it pulls a sample of actual reports and traces every field back to a source: the procedure it was performed to, the calibration record for the equipment used, the qualification record of the person who signed it, and the specific engineering specification that defined the acceptance criteria. A report that's technically correct in substance but missing a citation, using an outdated specification revision number, or referencing a calibration record that doesn't clearly tie back to a specific instrument and date is a documentation nonconformance — and in a NADCAP audit, documentation nonconformances are not a footnote, they're a primary finding category.

This is a genuinely different bar than most industrial NDT reporting operates against, and inspection companies moving from oil and gas or general fabrication work into aerospace supply chain inspection consistently underestimate how much the documentation standard changes, even when the underlying technique — UT, PT, MT, RT, eddy current — is one they've performed thousands of times elsewhere.

Part and serial number traceability, not just a work order number

Industrial NDT reporting typically identifies what was inspected by equipment tag, weld joint number, or job number — sufficient traceability for that industry's needs. Aerospace reporting needs to go further: a report has to trace to the specific part number, serial or lot number, and, where applicable, the specific operation or manufacturing step in the part's routing where the examination occurred. This matters because aerospace parts carry traceability obligations for the life of the airframe or engine — if a fleet-wide issue is identified years later, tracing it back to which specific parts were inspected, by whom, under which procedure revision, has to be possible from the report alone, without relying on institutional memory or a separate cross-reference that may not survive a change of ownership, a plant closure, or simply enough time passing that nobody who worked the job is still there to ask.

A reporting system built for aerospace work needs part/serial-level fields as a structural requirement, not an optional field a technician might skip when under schedule pressure — because the report is functionally incomplete without it in a way that a missing optional field on an industrial report typically isn't.

Calibration traceability chains back to NIST

Calibration documentation requirements in aerospace NDT go a layer deeper than "the gauge was calibrated on this date." NADCAP-level expectations generally require the calibration record to show an unbroken traceability chain back to a national metrology standard — in the U.S., the National Institute of Standards and Technology (NIST) — meaning the reference standards used to calibrate the equipment are themselves traceable to a recognized standard, not just internally verified against another shop-floor gauge with no further pedigree. A report that cites an instrument's calibration due date without the underlying calibration record demonstrating that full chain is documentation that looks complete on the surface and falls apart the moment an auditor asks to see the calibration certificate behind it.

Reference standards and reflectors need equally tight documentation

The same traceability expectation extends to reference blocks, reflectors, and comparison standards used to set sensitivity or verify a procedure — an IIW block, a distance-amplitude correction (DAC) reference reflector, a penetrant sensitivity comparator panel. Each needs its own identification, verification history, and — where the governing specification requires it — traceability documentation, referenced explicitly in the report rather than assumed. Aerospace primes auditing their supply chain, and NADCAP auditors reviewing accredited suppliers, routinely ask to see this chain specifically, because a marginal or improperly verified reference standard undermines the validity of every examination performed against it, not just the one report being reviewed.

Procedure specificity: citing the exact engineering spec revision

Aerospace acceptance criteria are almost never generic — they're defined by a specific customer engineering specification, an AMS (Aerospace Material Specification) standard, or an OEM-specific process specification, often at a revision level that changes more frequently than most industrial codes. A report that cites "per customer specification" without the exact document number and revision in effect at the time of the examination is not sufficiently specific for aerospace documentation standards, because acceptance criteria can and do change between revisions in ways that materially affect disposition. Reporting software that hard-codes a specification reference into a template, rather than requiring it to be pulled current and explicit at the point of report generation, creates exactly the kind of silent drift that shows up as a finding when an auditor cross-references the cited revision against what was actually current on the examination date.

Personnel qualification records the auditor will pull

NADCAP audits routinely sample personnel files alongside reports, checking that the individual who performed and signed a given examination held current, appropriate certification at the time — under the company's written practice, which for most suppliers Atlantis works alongside is built on ASNT SNT-TC-1A, and, where a specific customer or contract requires it, alongside qualification to SAE AS9100 quality management system expectations and, in some cases, to NAS410, the aerospace-specific personnel qualification standard many primes require in addition to or instead of general industrial certification schemes. It's worth being precise here: NAS410 and NADCAP accreditation are separate, aerospace-specific frameworks, and an inspection company should be clear with clients about exactly which qualification pathway its technicians hold and which one a given contract requires, rather than assuming general NDT certification automatically satisfies an aerospace-specific requirement. Reporting documentation needs to reflect whichever qualification framework is actually contractually required for that job, cited specifically rather than generically.

Nonconformance and corrective action linkage

When an aerospace NDT examination identifies a rejectable indication, the report doesn't stand alone — it typically triggers a nonconformance record, a material review board (MRB) disposition process, and, depending on the customer's quality system, a formal corrective action if the finding indicates a process escape rather than an isolated discrepancy. A reporting system that treats the inspection report as the end of the workflow, rather than the entry point into a connected nonconformance and disposition trail, forces someone to manually re-key the same part and finding information into a separate quality system — reintroducing the exact transcription risk the report was supposed to eliminate in the first place, and creating two records of the same event that can drift out of sync.

Retention for the life of the airframe

Aerospace record retention requirements are typically driven by the design life of the aircraft or engine program, not a fixed number of years — which in practice can mean decades, well beyond the tenure of most of the staff who originally generated the records, and often beyond the operating life of whatever software system produced them. This has real implications for how an inspection company chooses reporting infrastructure: a platform needs a credible answer to "how do we retrieve and prove the authenticity of a report generated fifteen years ago on a system that may have been replaced twice since," not just a promise that current records are well organized. Structured digital records with preserved metadata — who signed it, when, against which procedure and specification revision — age far better under this kind of long-horizon retrieval demand than a PDF whose supporting context lives in someone's memory of how things worked at the time.

First article inspection and the broader quality system linkage

Aerospace suppliers running first article inspection (FAI) — typically structured under AS9102 for suppliers operating within an AS9100 quality management system — need NDT results to feed directly into that broader FAI record, not exist as an isolated document a quality engineer has to manually cross-reference against the part's dimensional and material certification data when assembling the full FAI package. An NDT finding on a first article part is one input among several — dimensional inspection, material certification, process verification — that together support the disposition of that specific part number as representative of the production process going forward. Reporting workflows that can export or directly feed structured data into a customer's FAI documentation format, rather than requiring a quality engineer to retype NDT results into a separate FAI form, remove a manual step that's a common source of transcription error precisely because it happens under the schedule pressure of closing out a first article package.

Special processes and sub-tier supplier documentation

Aerospace NDT is classified as a "special process" under most quality system frameworks — meaning its results can't be fully verified by inspecting the finished part alone, so the process itself, and the qualification of everyone who performed it, has to be documented as rigorously as the outcome. This has particular weight for inspection companies operating as a sub-tier supplier to a larger fabricator or a prime contractor, where the prime's own quality system will periodically audit not just the fabricator but the fabricator's NDT sub-tier directly. A sub-tier inspection company needs reporting documentation robust enough to survive that flow-down audit independently — the fabricator's own accreditation doesn't automatically extend credibility to a sub-tier supplier's paperwork if that paperwork can't stand on its own when reviewed directly.

Flow-down requirements change the acceptance criteria, not just the paperwork

It's worth flagging specifically because it trips up companies moving into aerospace sub-tier work for the first time: a prime contractor's engineering specification often flows down acceptance criteria that are stricter than the generic AMS or industry standard a fabricator might otherwise default to, and the report needs to cite the specific flowed-down requirement, not just the underlying general standard. A report that says "per AMS-2175" without also capturing which customer-specific addendum or deviation applies is incomplete in a way an auditor familiar with that customer's flow-down requirements will catch immediately, even if the underlying inspection technique was performed flawlessly.

Sub-contracted and temporary technicians on aerospace contracts

Aerospace suppliers frequently supplement permanent staff with contract or agency NDT technicians during production peaks, and this arrangement creates a specific documentation obligation that's easy to underestimate: the contract technician's qualification records — certification, training history, and often a formal statement of equivalency confirming their qualification basis matches what the supplier's own quality system requires — need to be on file and referenced correctly on every report they sign, for as long as records retention requires, which as discussed can mean decades. A supplier that loses track of a contract technician's qualification documentation after the contract ends has a real problem if any of that technician's reports are later reviewed, because there's no straightforward way to reconstruct qualification history for someone no longer affiliated with the company. Reporting systems that capture and permanently retain qualification documentation for every signing technician — contract or permanent — at the time the report is generated, rather than relying on a separate HR record that may not survive the end of a contractor relationship, close this gap before it becomes unrecoverable.

Customer source inspection and the report's third audience

Beyond the supplier's own quality system and NADCAP, a significant share of aerospace NDT reports have a third audience: the customer's own source inspector, who may visit the supplier's facility specifically to witness inspection activity or review documentation before accepting delivery of parts. A source inspector reviewing a report cold, without the context a long-standing internal relationship provides, applies essentially the same scrutiny an external NADCAP auditor would — checking specification citation, calibration traceability, and personnel qualification independently. Reports built to satisfy that level of independent scrutiny by default, rather than relying on familiarity to smooth over gaps, hold up consistently regardless of which of the three audiences — internal quality, NADCAP, or customer source inspection — happens to be reviewing them on a given day.

Getting the documentation discipline right before the audit, not during it

Inspection companies preparing for a first NADCAP accreditation, or expanding an existing accreditation to a new NDT method, are best served treating the reporting system's structure — part/serial traceability fields, calibration chain documentation, specification revision citation, and nonconformance linkage — as part of the accreditation preparation itself, not a documentation cleanup exercise done after a finding. A Level III review of the reporting structure against the specific AC7114 criteria the company will be audited under, before the audit rather than in response to one, catches structural gaps in how reports are built — gaps that no amount of technical competence in the field corrects, because the auditor isn't questioning whether the scan was performed correctly. They're questioning whether the paperwork proves it.

Atlantis NDT Products & Services

Atlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.