Selecting In-Circuit Test Systems for Aerospace PCBAs

Last updated: August 15, 2026

Key Takeaways for Aerospace ICT Selection

• In-circuit testing (ICT) provides electrical verification of aerospace PCBAs by checking shorts, opens, component values, polarity and insulation resistance before functional testing.
• Production volume shapes ICT choice: fixture-based bed-of-nails systems support high-volume throughput, while flying probe testing offers flexible coverage for low-volume, high-mix aerospace programs.
• Fixture design and test-program development create significant hidden costs that must be evaluated early, and design-for-testability decisions during schematic capture drive long-term test economics.
• AS9100 traceability, ITAR compliance and domestic manufacturing controls are mandatory for aerospace ICT partners, supporting audit-ready documentation and controlled supply chain integrity.
• Pro-Active Engineering delivers ICT strategy, in-house fixture design and test-program development under a single AS9100-certified workflow, and engages its engineering team from day one.

Matching ICT Platforms to Aerospace Production Volume

Production volume drives every ICT platform decision. Fixture-based bed-of-nails ICT achieves short cycle times per board, which suits stable, high-volume programs. That speed advantage appears once fixture and test-program development costs spread across enough units.

Low-volume, high-mix aerospace programs benefit from flying probe testing that avoids fixture investment and remains economical even for a single board. Flying probe systems generate test programs from CAD and netlist data, which supports fast updates when designs change. Many low-volume, high-complexity aerospace PCBAs remain on flying probe until repeat forecasts and revision stability justify a shift to fixture-based ICT.

This natural transition point explains why many aerospace teams adopt a phased strategy. Programs often use flying probe for new product introduction and engineering validation, then shift mature boards to fixture-based ICT once volume supports the investment. This approach aligns each method with its ideal lifecycle stage and improves overall return on test.

Fixture Design and Test-Program Development Costs

Fixture economics often receive less attention than they deserve. For low-volume, high-mix boards, custom ICT fixtures become the main hidden cost because each variant needs a machined plate with spring-loaded probes wired to the tester. That fixture must then be debugged against a known-good board before production starts.

Engineering change orders increase this burden. Every ECO that moves a test pad can require re-drilling or rebuilding the plate, which adds recurring nonrecurring engineering expense before the first production lot. Test-program development, model generation, limit setting, debug, diagnostics and qualification add further effort that must be scoped clearly at program start.

These individual cost elements show why total cost of ownership extends beyond the fixture invoice. ICT platform evaluation should include fixture burden, debug time, false failures, program maintenance, service response and integration with downstream verification, not machine price alone. These ongoing costs trace back to design-for-testability decisions during schematic capture and layout, where test access pads, keep-out zones and boundary scan interfaces determine whether ICT remains viable without a board redesign.

Pro-Active Engineering embeds DFT review into the design phase so fixture strategy is resolved before layout freezes. Engage Pro-Active’s engineering team on ICT strategy, fixture design and test-program development from day one.

Choosing PCB Test Fixture Manufacturers for Aerospace

Fixture partner selection for aerospace programs extends beyond price. ITAR-registered programs require that fixture design data, including netlists, board geometry and test-point coordinates, remain inside a controlled domestic supply chain. A fixture manufacturer without ITAR registration introduces compliance exposure that can delay program approval.

Domestic fixture partners also support faster iteration. When a design change requires fixture rework, geographic proximity and shared documentation systems reduce turnaround time compared with offshore tooling sources. Qualification traceability, which documents which fixture revision supported each production lot, is an AS9100 requirement that a capable fixture partner must meet.

Pro-Active Engineering designs and builds test fixtures in-house under AS9100, ITAR and Nadcap controls, maintaining a single chain of custody from board layout through fixture qualification and test-program release.

Primary PCB Test Methods and Where ICT Fits

A complete aerospace PCBA test strategy layers multiple methods because no single technique catches every defect type. Optical inspection finds placement errors, electrical testing finds opens and shorts and functional testing finds system-level failures. EPnP GmbH combines SPI, 3D AOI, ICT, flying probe testing, boundary scan, burn-in, stress testing, functional testing, programming, calibration and documentation into a test concept matched to risk profile, production volume and budget. The seven core verification methods most relevant to ICT platform selection are:

• Solder Paste Inspection (SPI): Inline after paste printing, SPI intercepts a significant share of downstream solder defects but does not test electrical continuity.
• Automated Optical Inspection (AOI): Post-reflow visual verification of component placement, polarity and solder quality. AOI cannot detect hidden solder joints or electrical opens.
• X-ray inspection (AXI): 3D AXI uses layered imaging to examine solder joints on both sides of double-sided PCBs and to slice multilayer views of BGA and plated-through-hole joints.
• In-Circuit Test (ICT): Electrical verification of shorts, opens, component values and polarity at the net level. ICT forms the primary focus of this guide.
• Flying Probe Test: Fixtureless ICT-equivalent coverage suited to low-volume and high-mix programs.
• Boundary Scan (JTAG): Digital interconnect verification for BGAs and hidden nodes via IEEE 1149.1 interfaces, covered in the next section.
• Functional Test (FCT): FCT is mandatory in aerospace applications because it is the only method that detects failures where all components and solder joints pass inspection yet the board fails due to incorrect firmware, timing misconfiguration or signal integrity issues.

Aerospace and defense PCBAs often combine SPI, 3D AOI, 3D X-ray, ICT and FCT to reach high fault coverage. ICT occupies the electrical verification layer between optical inspection and system-level functional test.

Boundary-Scan ICT Needs for BGAs and Hidden Nodes

Physical probe access declines as board density increases. BGAs, fine-pitch devices and HDI stackups leave few exposed pads for a bed-of-nails fixture. Boundary scan reaches interconnects under BGAs and fine-pitch devices through a four-wire JTAG connection that a bed-of-nails fixture cannot contact, which maintains coverage as physical test points disappear.

JTAG boundary scan testing per IEEE 1149.1 verifies IC-to-IC interconnects, memory interfaces, FPGA connections and board-level continuity on high-density PCBs with limited probe access. Modern platforms extend this further, using boundary scan as a workhorse for interconnect testing at board and package levels, detecting opens, shorts and stuck-at faults, with specialized support for high-speed differential interfaces through IEEE 1149.6.

A hybrid strategy that combines boundary scan for digital interconnects and BGA joints with limited physical probing for analog and passive measurements often delivers cost-effective coverage without a fixture that reaches every node. Modern ATE systems that combine ICT, JTAG boundary scan and functional testing typically achieve high fault coverage on complex PCBs.

Boundary scan integration starts at the design stage. Design for testability adds test points, keep-out zones and boundary scan interfaces during circuit design, which supports high ICT coverage for complex aerospace assemblies instead of addressing access issues after layout completion.

AS9100 Traceability in Modern ICT Systems

AS9100 Rev D sets specific traceability obligations for every released unit. AS9100 requires aerospace manufacturers to maintain traceable, tamper-evident test records for every unit produced, covering monitoring and measuring resources, control of documented information, identification and traceability, release of products, nonconforming outputs and corrective action.

Modern ICT systems support these requirements through automated record generation. Universal ATE platforms generate automated digital test records that include timestamps, serial numbers and operator IDs, which provide the traceability documentation required for AS9100 compliance in aerospace supply chains.

Station-level traceability plays a similar role. Station identifiers recorded for every test run link results to specific calibrated test fixtures and equipment, satisfying AS9100 traceability requirements for monitoring and measuring resources. Nonconformance records must capture failed measurements with exact values, limits and root-cause data to support rework and retest documentation.

AS9100 also requires control of documented information, including quality test records retained for customer- or regulator-specified periods that often span many years. ICT platform selection must account for long-term data accessibility, not only test execution capability. Pro-Active Engineering maintains AS9100-compliant documentation and traceability across its integrated test workflow. Discuss how Pro-Active’s traceability infrastructure supports audit-ready aerospace programs.

Legacy GenRad Support and Long Lifecycle Planning

Aerospace programs often outlast the commercial lifecycle of their supporting test equipment. Military platforms can last decades, while commercial off-the-shelf components follow obsolescence cycles measured in a few years, which creates sustainment challenges for legacy systems.

GenRad ICT platforms, used in aerospace and defense programs since the 1980s, present a common legacy support issue. Test programs written for GenRad hardware contain institutional knowledge that is difficult to migrate. When fixture documentation is incomplete or personnel with platform expertise have retired, loss of undocumented tribal knowledge and incomplete design data for legacy platforms increases program risk.

Modernization strategies that preserve test coverage while updating hardware are well established. Successful legacy modernization programs emulate original hardware behavior, manage startup initialization, interpret incoming commands exactly as legacy hardware expected and return measurement data in the same format, which preserves validated test workflows without recertification.

Platform selection for new aerospace programs should consider vendor support commitments, fixture migration paths and test-program portability. Seica’s VALID LR system supports up to thousands of channels and enables migration of legacy test programs and fixtures for high-reliability electronics testing, which illustrates the type of migration capability buyers should evaluate. Zero-fault-escape expectations in aerospace programs make long-term platform support a program risk factor rather than a simple procurement detail.

Buyer Checklist for Selecting an ICT Partner

Aerospace program managers evaluating ICT partners can use the following checklist before committing to a platform or supplier:

• Fault coverage strategy: Confirm that the proposed test approach, whether fixture-based ICT, flying probe, boundary scan or hybrid, achieves adequate coverage for BGA count, node density and functional complexity.
• DFT integration: Verify that the partner embeds testability review into PCB layout, not after design release, to avoid costly fixture workarounds.
• Fixture economics and ownership: Clarify fixture cost, build lead time, revision policy and storage responsibility across the program lifecycle.
• Test-program development scope: Confirm that program development, debug and qualification effort are included in the engagement, not treated as separate unknowns.
• AS9100 traceability: Confirm that the partner generates serial-number-linked, station-traceable, audit-ready test records with defined retention periods.
• Certifications and compliance: Require AS9100 registration, ITAR compliance and Nadcap accreditation for aerospace programs. JCP certification applies to programs with military documentation requirements.
• Domestic manufacturing and ITAR controls: Confirm that fixture design data, test programs and board data remain within a controlled domestic environment.
• Legacy support and migration: Assess the partner’s capability to maintain, migrate or modernize test programs across the expected program lifecycle.
• Integrated workflow: Evaluate whether the partner can own the full design-to-test chain, including DFM, layout, fixture, test program and production, under a single accountable relationship.

Next Step: Partnering With Pro-Active Engineering

Pro-Active Engineering is a Wisconsin-based PCBA manufacturer with AS9100, ITAR, Nadcap and JCP certifications. The engineering team supports ICT platform selection, in-house fixture design using SolidWorks, test-program development, flying probe and functional test and full AS9100 traceability documentation, all within one facility.

Aerospace and defense programs benefit from the early ICT integration described above, combined with domestic control over all test data and the certifications required for regulated supply chains. Pro-Active’s integrated workflow reduces handoff risk between separate design, fixture and test vendors, which often creates schedule exposure on complex programs.

Start a conversation with Pro-Active Engineering’s test engineering team about ICT platform selection, fixture design and test-program development for aerospace PCBAs.

Frequently Asked Questions

What is the difference between flying probe testing and fixture-based ICT for aerospace PCBAs?

Flying probe testing uses a small number of motorized probes that move across the board surface, contacting pads and component leads without a custom fixture. It generates test programs from CAD and netlist data, which suits low-volume, high-mix or frequently revised aerospace PCBAs where fixture costs would multiply with each design change. Fixture-based ICT uses a bed-of-nails plate that contacts all test points at once, which delivers much faster cycle times per board. That speed advantage becomes economical when production volume supports amortization of fixture and test-program development investment. Many aerospace programs adopt a phased strategy that uses flying probe during new product introduction and early ramp, then transitions to fixture-based ICT once the design stabilizes and volumes grow.

How does boundary scan integrate with in-circuit testing on high-density aerospace boards?

Boundary scan, standardized under IEEE 1149.1, allows digital ICs to shift test data through a serial chain of boundary-scan cells, which enables verification of IC-to-IC interconnects, memory interfaces, FPGA connections and board-level continuity without physical probe access to individual pins. High-density aerospace boards with BGAs and fine-pitch devices often lack accessible test points for a bed-of-nails fixture. Boundary scan fills that coverage gap by testing interconnects through the JTAG port. Modern ICT platforms integrate boundary scan alongside parametric ICT measurements, so a single test insertion can cover analog passives through physical probing and digital interconnects through JTAG. Effective boundary scan integration requires JTAG interfaces at the schematic stage because adding them after layout often requires a board revision.

What AS9100 traceability records does an ICT system need to generate for aerospace programs?

AS9100 Rev D requires that every released unit carry traceable, tamper-evident test records linking the serial number to specific test results. Required fields include pass or fail determinations, measurement values with limits, test station identifier, calibrated fixture revision, operator ID and timestamp. Records must be retained for the period specified by the customer or regulator, which in aerospace programs often spans many years. ICT systems that generate automated digital records with these fields support AS9100 clause compliance for monitoring and measuring resources, identification and traceability, release of products and nonconforming outputs. Nonconformance records must capture failed measurement values, applicable limits and root-cause data to support rework and retest documentation under corrective action requirements. Buyers evaluating ICT platforms or contract test partners should confirm that data output supports long-term retrieval by serial number, station, date range and result, not only immediate pass or fail reporting.

How should aerospace program managers approach legacy GenRad ICT support and platform migration?

GenRad ICT platforms remain in service across many aerospace and defense programs because their test programs and fixtures represent validated, program-specific intellectual property that is difficult and costly to recreate. When GenRad hardware reaches end of support, the primary risk becomes loss of test coverage continuity, especially if fixture documentation is incomplete or the engineers who developed the original programs are no longer available. Successful migration strategies focus on emulating legacy hardware behavior at the software and interface level, which preserves existing test workflows without full recertification of the test process. Buyers selecting new ICT platforms for long-lifecycle programs should evaluate vendor support commitments, fixture migration paths and test-program portability as primary criteria alongside technical capability. Contract test partners with in-house fixture design and test-program development capability reduce migration risk by providing a single accountable team that can reverse-engineer legacy programs, rebuild fixtures to current standards and qualify the replacement setup against original acceptance criteria.

Can Pro-Active Engineering support both ICT strategy and fixture design under a single engagement?

Pro-Active Engineering provides ICT platform consultation, in-house fixture design, test-program development, flying probe testing, functional test and full AS9100 traceability documentation within a single workflow. The engineering team embeds testability review into the PCB design phase, which resolves fixture access, test-point placement and boundary scan integration before layout release. This approach removes the handoff risk between separate design, fixture and test vendors that often creates schedule exposure on complex aerospace programs. All work takes place domestically under AS9100, ITAR, Nadcap and JCP controls, which maintains a single chain of custody over board data, fixture design files and test records. Programs that begin with flying probe testing during early builds can transition to fixture-based ICT within the same facility and quality system as volumes increase, without changing partners or requalifying the manufacturing process.