Electronics Guide

DO-160: Environmental Conditions and Test Procedures

RTCA DO-160, titled "Environmental Conditions and Test Procedures for Airborne Equipment," is the primary environmental testing standard for commercial aviation electronics. Published by RTCA, Inc. (originally the Radio Technical Commission for Aeronautics), this standard defines the environmental conditions that airborne equipment may encounter and specifies test procedures to verify equipment performance under these conditions. Revision G, issued in 2010, remains the current version; the FAA recognizes DO-160 revisions through advisory circular AC 21-16G. EUROCAE publishes a technically equivalent document, ED-14, so a single test program generally satisfies both authorities.

DO-160 covers a comprehensive range of environmental factors including temperature and altitude, temperature variation, humidity, operational shock and crash safety, vibration, explosive atmosphere, waterproofness, fluids susceptibility, sand and dust, fungus resistance, salt spray, magnetic effect, power input, voltage spike, audio frequency conducted susceptibility, induced signal susceptibility, radio frequency susceptibility, emission of radio frequency energy, lightning induced transient susceptibility, lightning direct effects, icing, and electrostatic discharge.

Each test category in DO-160 includes multiple test levels corresponding to different installation locations and aircraft types. Equipment designers must identify the appropriate test categories and levels based on where the equipment will be installed and the environmental conditions it will experience. A pressurized, temperature-controlled avionics bay draws far milder categories than a wing-mounted or engine-mounted unit, and the resulting category string, recorded in the equipment's environmental qualification form, becomes part of the installation approval data. Compliance with DO-160 is typically required for FAA certification of airborne electronic equipment and is referenced by equivalent standards worldwide.

A few DO-160 sections drive design decisions more than the rest. The power input section constrains how equipment behaves during voltage transients, power interrupts, and abnormal bus conditions on a 28 V DC or 115 V 400 Hz aircraft supply. The lightning induced transient susceptibility section sets pin-injection waveform levels that determine transient suppression on every external interface. The radio frequency emission and susceptibility sections govern shielding, filtering, and cable design. Engineers who defer these sections until the end of a program frequently find that passing them requires a board respin.

MIL-STD-810: Environmental Engineering Considerations

MIL-STD-810, "Environmental Engineering Considerations and Laboratory Tests," is the United States Department of Defense standard for environmental testing of military equipment. Revision H, issued in 2019, is the current version. While DO-160 focuses specifically on airborne applications, MIL-STD-810 provides a broader framework applicable to all military equipment including ground vehicles, naval systems, portable equipment, and aircraft.

The document is organized in three parts. Part One describes the environmental engineering program and the tailoring philosophy, Part Two contains the laboratory test methods, and Part Three addresses world climatic regions and related environmental data. This structure matters because MIL-STD-810 is not a pass or fail checklist in the manner of a product safety standard. It emphasizes tailoring test procedures to reflect actual service environments rather than applying generic test levels, so engineers must analyze the specific conditions their equipment will encounter throughout its lifecycle, including storage, transportation, and operational phases. A well-written tailoring rationale, captured in a life cycle environmental profile, is as much a deliverable as the test reports themselves.

Key test methods in MIL-STD-810 include low pressure (altitude), high temperature, low temperature, temperature shock, contamination by fluids, solar radiation, rain, humidity, fungus, salt fog, sand and dust, explosive atmosphere, immersion, acceleration, vibration, acoustic noise, shock, pyroshock, acidic atmosphere, gunfire vibration, temperature-humidity-vibration-altitude, icing and freezing rain, ballistic shock, and vibro-acoustic temperature. Several of these have no counterpart in DO-160, notably pyroshock, ballistic shock, and gunfire vibration, which reproduce mechanical environments peculiar to munitions and armored platforms.

A common misuse of the standard is the marketing claim that a product is "MIL-STD-810 certified." No such certification exists. There is no central certifying body, and the standard explicitly rejects the idea of a fixed qualification level. A defensible claim identifies the specific test methods, procedures, and levels applied, and the laboratory that performed them.

DO-178C: Software Considerations in Airborne Systems

DO-178C, "Software Considerations in Airborne Systems and Equipment Certification," is the primary standard for developing software used in airborne systems. Published in 2011 and issued jointly with EUROCAE as ED-12C, it succeeded DO-178B without changing that document's underlying philosophy. The FAA recognizes DO-178C and its supplements as an acceptable means of compliance through advisory circular AC 20-115D. Together with its predecessor, the standard has shaped avionics software development for decades and represents the most rigorous software development framework in widespread use.

The fundamental concept in DO-178C is the software level, commonly called the Design Assurance Level (DAL), which is derived from the severity of the failure condition to which the software can contribute. Level A corresponds to catastrophic failure conditions, Level B to hazardous conditions involving a large reduction in safety margins, Level C to major conditions involving a significant reduction in safety margins or a significant increase in crew workload, Level D to minor conditions, and Level E to software with no effect on safety. Higher levels require more rigorous development processes, more extensive verification activities, and more comprehensive documentation. Note that the level is assigned by the system safety assessment, not chosen by the software team; DO-178C consumes the output of the aircraft- and system-level process described in ARP4754B and ARP4761A.

DO-178C defines objectives across several process areas including software planning, software development (requirements, design, coding, integration), verification (reviews, analyses, testing), configuration management, quality assurance, and certification liaison. The standard specifies which objectives apply at each level and whether each objective must be satisfied with independence, meaning that the verification is performed by someone other than the person who produced the item. The number of applicable objectives and the number requiring independence both fall sharply as the level decreases, which is why the assigned level dominates program cost.

Structural coverage analysis illustrates how sharply the levels differ. Level C requires statement coverage, Level B adds decision coverage, and Level A additionally requires modified condition/decision coverage (MC/DC), in which each condition within a decision must be shown to affect the outcome independently. Level A also requires verification that the executable object code traces to source code, which becomes a substantial effort when compiler optimization is enabled. These requirements are why Level A software commonly costs several times as much per line as Level C software of comparable function.

Supplements to DO-178C address specific technologies and methods. DO-330 provides guidance for tool qualification, DO-331 addresses model-based development and verification, DO-332 covers object-oriented technology, and DO-333 addresses formal methods. These supplements allow modern development techniques while maintaining the safety rigor of the base standard.

MIL-STD-498: Software Development and Documentation

MIL-STD-498, "Software Development and Documentation," was the Department of Defense standard for software development before being superseded by commercial standards. While no longer actively maintained, MIL-STD-498 continues to influence military software development and is still referenced in some contracts. The standard defined a comprehensive set of software development activities and documentation requirements.

Many current military programs instead reference the 12207 software life cycle process standard, now maintained as ISO/IEC/IEEE 12207 and last revised in 2017, which incorporates concepts from MIL-STD-498 while aligning with commercial software engineering practice. Its companion, ISO/IEC/IEEE 15288, covers system life cycle processes. Programs requiring high assurance software frequently invoke DO-178C directly, even for military platforms, because the certification evidence and the trained supplier base already exist.

Safety-critical military systems also reference MIL-STD-882, "Department of Defense Standard Practice, System Safety," currently Revision E. MIL-STD-882 defines the system safety process, the severity and probability categories used to build a risk assessment matrix, and the software criticality levels that flow down to software development. Its risk acceptance framework, which routes higher residual risks to progressively more senior decision authorities, is the mechanism by which a program formally accepts a hazard rather than eliminating it.

DO-254: Design Assurance Guidance for Airborne Electronic Hardware

DO-254, "Design Assurance Guidance for Airborne Electronic Hardware," provides a framework for developing complex electronic hardware for airborne systems. Published in 2000 and issued by EUROCAE as ED-80, it answers the growth of complex programmable devices such as FPGAs, ASICs, and PLDs by establishing processes analogous to those in DO-178C but tailored for hardware development. The FAA recognizes the document through advisory circular AC 20-152A, "Development Assurance for Airborne Electronic Hardware," with the companion AC 00-72 offering best-practice guidance; EASA applies the equivalent AMC 20-152A.

Like DO-178C, DO-254 uses design assurance levels to scale requirements based on failure severity. The standard addresses hardware planning, hardware design (requirements capture, conceptual design, detailed design, implementation, and production transition), validation and verification, configuration management, process assurance, and certification liaison. Hardware verification may include requirements-based testing, review, analysis, simulation, and testing of the physical article.

DO-254 draws a working distinction between simple and complex hardware. A simple item is one whose correct behavior can be established by exhaustive testing alone, and it needs no further design assurance argument. Anything else is complex, and complex items at the two highest assurance levels require additional measures drawn from the standard's advanced verification strategies, such as elemental analysis, safety-specific analysis, or formal methods. Deciding early which devices are simple and which are complex is one of the highest-leverage planning decisions on a DO-254 program.

The remaining challenges are practical. The standard requires bidirectional traceability from requirements through design and implementation, verification of the design at multiple levels, and assessment of the tools used in development. Tool assessment is a frequent source of trouble because synthesis and place-and-route tools can transform a design in ways the source HDL does not obviously express, so teams must either qualify the tool or add verification that is independent of it. Commercial off-the-shelf devices and licensed intellectual property blocks pose a related problem, since the design data needed to make a development assurance argument is often unavailable and must be replaced by service experience or additional testing.

MIL-PRF-38535: Integrated Circuits Manufacturing

MIL-PRF-38535, "Integrated Circuits (Microcircuits) Manufacturing, General Specification for," establishes requirements for integrated circuits used in military and space applications. It is administered by the Defense Logistics Agency and is the foundation of the Qualified Manufacturers List (QML) approach, in which the agency certifies and audits a manufacturer's processes and quality system rather than qualifying each part number individually. Once a line is certified, the manufacturer may add conforming devices to it under agency oversight, which is far more workable for modern semiconductor technology than part-by-part qualification.

Rather than a single quality tier, the specification defines device classes. Class M covers devices built to MIL-STD-883 requirements without full QML listing, Class Q is the military class used for airborne, ground, and missile applications, and Class V is the space class. Revision M, released in 2022, added the organic Class Y for space-qualified devices in advanced non-hermetic and flip-chip package technologies that the traditional hermetic Class V flows could not accommodate. Space-class devices carry the heaviest burden: extended burn-in, wafer lot acceptance testing, destructive physical analysis, tighter electrical test limits over the full temperature range, and radiation lot acceptance testing where specified.

Two related documents complete the picture. MIL-STD-883, "Test Method Standard, Microcircuits," defines the individual environmental, mechanical, and electrical test methods that MIL-PRF-38535 invokes, including hermeticity, temperature cycling, mechanical shock, burn-in, and total ionizing dose testing. Standard Microcircuit Drawings (SMDs), maintained by the Defense Logistics Agency, describe specific device types procurable from one or more qualified sources, allowing a designer to specify a function rather than a single vendor's part number. Comparable test method standards exist for other component families, notably MIL-STD-750 for discrete semiconductors and MIL-STD-202 for passive and electromechanical parts.

MIL-PRF-38534: Hybrid Microcircuits

MIL-PRF-38534, "Hybrid Microcircuits, General Specification for," provides similar requirements for hybrid and multichip modules that combine multiple die, passive components, and interconnections in a single package. Hybrids remain common in aerospace and defense applications where custom functionality, high reliability, radiation tolerance, or volume constraints preclude the use of standard integrated circuits. Power converters, radio frequency modules, and motor controllers for spacecraft and missiles are typical examples.

The specification covers design requirements, materials and construction, quality assurance provisions, and testing requirements, and it is the basis for a Qualified Manufacturers List of certified hybrid suppliers. Its principal product assurance classes are Class H for military and ruggedized applications and Class K for space applications, with Class K adding more demanding screening, element evaluation, and lot conformance requirements. The current revision, MIL-PRF-38534M, was issued in 2024.

AS9100: Aerospace Quality Management Systems

AS9100, "Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations," is the quality management system standard for the aerospace industry. Built on the foundation of ISO 9001, AS9100 adds requirements specific to aerospace including configuration management, design verification, first article inspection, and control of work transfers.

The current revision, AS9100D, was released in 2016 and aligns with ISO 9001:2015. AS9100 certification is typically required for suppliers to major aerospace and defense prime contractors. The standard requires organizations to establish and maintain a quality management system that addresses customer focus, leadership, engagement of people, process approach, improvement, evidence-based decision making, and relationship management. Revision D added explicit requirements for product safety, prevention of counterfeit parts, awareness of ethical behavior and its effect on product conformity, and consideration of human factors when investigating nonconformities.

The standard is published as a family of equivalent documents by regional bodies, appearing as AS9100 in the Americas, EN 9100 in Europe, and JISQ 9100 in Japan, all derived from a single International Aerospace Quality Group (IAQG) baseline. The IAQG has announced that the next revision will be rebranded as IA9100 to reflect that common baseline, with publication timed to follow the pending revision of ISO 9001; organizations should expect a multi-year transition window once it appears.

Related standards in the family include AS9110 for aviation maintenance organizations, AS9120 for distributors, AS9145 for advanced product quality planning and the production part approval process, and AS9102 for first article inspection. The Online Aerospace Supplier Information System (OASIS) database maintains records of certified organizations worldwide and is the authoritative place to confirm that a supplier's certificate is genuine and current.

NATO AQAP: Allied Quality Assurance Publications

NATO Allied Quality Assurance Publications (AQAPs) define quality requirements for defense contracts among NATO member nations. These standards ensure consistent quality management across the alliance and facilitate international defense cooperation. The central document is AQAP-2110, "NATO Quality Assurance Requirements for Design, Development and Production." Its Edition D, published in 2016, consolidated the previously separate AQAP-2120 for production and AQAP-2130 for inspection and test, so contracts that still cite those older numbers are working from a superseded structure. AQAP-2131 remains available for contracts whose scope is limited to final inspection.

Supporting publications extend the framework. AQAP-2210 adds software quality assurance requirements on top of AQAP-2110, AQAP-2105 governs deliverable quality plans, and AQAP-2070 defines the mutual government quality assurance process by which one nation's authority performs delegated oversight on behalf of another.

AQAP requirements align with ISO 9001 but add defense-specific requirements including configuration management, government quality assurance, risk management, and contract-specific quality plans. NATO member nations recognize AQAP certifications, reducing the need for multiple country-specific certifications when supplying defense equipment internationally.

MIL-Q-9858: Quality Program Requirements

While largely superseded by AS9100, MIL-Q-9858A historically defined quality program requirements for defense contractors. Many legacy programs and specifications still reference this standard, and understanding its requirements helps interpret older technical data packages and contract requirements. The standard established requirements for quality planning, work instructions, records, corrective action, and supplier control that influenced subsequent commercial and military quality standards.

Workmanship and Special Process Accreditation

Quality management standards describe the system; workmanship standards describe the acceptable physical result. For aerospace and defense electronics, the governing documents are largely those of IPC. J-STD-001 sets requirements for soldered electrical and electronic assemblies, and its Space and Military Applications addendum adds requirements for hardware that cannot be repaired after deployment. IPC-A-610 defines visual acceptance criteria, IPC-6012 covers qualification and performance of rigid printed boards, and IPC/WHMA-A-620 covers cable and wire harness assemblies. Each of these uses a class system, and aerospace hardware is generally procured to Class 3, the highest performance class, with space and military hardware invoking the additional space addendum requirements.

Because these processes depend heavily on operator skill and process control rather than on inspection alone, the industry supplements them with independent accreditation. Nadcap, administered by the Performance Review Institute on behalf of a group of subscribing primes, audits special processes including electronics assembly, printed board fabrication, coatings, welding, and heat treating. A supplier's AS9100 certificate attests to its quality system; a Nadcap accreditation attests that a specific process, performed on specific equipment by qualified operators, meets industry-agreed technical requirements. Prime contractors commonly require both.

RTCA Standards for Aviation Electronics

The Radio Technical Commission for Aeronautics (RTCA) is a private, not-for-profit organization that develops consensus-based recommendations for communications, navigation, surveillance, and air traffic management systems. RTCA documents, while not regulations themselves, are frequently referenced by the FAA and international aviation authorities as acceptable means of compliance with regulations.

Key RTCA documents beyond DO-160, DO-178C, and DO-254 include DO-297 for integrated modular avionics development, DO-278A for ground-based communication, navigation, surveillance, and air traffic management software, and numerous equipment-specific Minimum Operational Performance Standards (MOPS) that define performance requirements for particular types of avionics equipment. DO-278A parallels DO-178C but uses assurance levels AL1 through AL6 rather than software levels A through E, reflecting the different risk profile of ground infrastructure.

Aircraft cybersecurity is addressed by a coordinated set of documents published jointly with EUROCAE as the ED-200 series. DO-326A, "Airworthiness Security Process Specification," defines the process for handling the threat of intentional unauthorized electronic interaction with aircraft systems; DO-356A provides the security methods and considerations that support it; and DO-355 covers information security guidance for continuing airworthiness once the aircraft is in service. Regulators increasingly expect this process to run alongside, and feed into, the traditional safety assessment rather than being treated as a separate compliance exercise.

EUROCAE Standards

The European Organisation for Civil Aviation Equipment (EUROCAE) is the European counterpart to RTCA. EUROCAE develops standards for aviation equipment that are recognized by the European Union Aviation Safety Agency (EASA) and other international authorities. Many EUROCAE documents are produced by joint committees with RTCA and are technically identical apart from their designation, including ED-12C for DO-178C, ED-80 for DO-254, ED-14 for DO-160, and ED-135 for ARP4761A.

This joint development is a deliberate convergence, and it matters commercially: a manufacturer can produce one set of certification evidence and present it to both the FAA and EASA, rather than running parallel programs. Where the documents differ is in how each authority accepts them. The FAA issues advisory circulars while EASA issues acceptable means of compliance, and each may add its own interpretive guidance, issue papers, or certification review items on top of the shared technical document. EUROCAE also publishes documents with no RTCA equivalent, particularly in areas where European regulation has moved first.

SAE Aerospace Standards

SAE International (formerly the Society of Automotive Engineers) develops aerospace standards through its Aerospace Council. SAE aerospace standards cover a wide range of topics including materials, processes, electrical systems, quality, and counterfeit parts avoidance. The two most consequential for electronics development sit above DO-178C and DO-254 in the assurance hierarchy: ARP4754, "Guidelines for Development of Civil Aircraft and Systems," and ARP4761, which covers the safety assessment process. Both were revised in December 2023, ARP4754 to Revision B and ARP4761 to Revision A, the latter published jointly with EUROCAE as ED-135. The revision moved the detailed safety assessment methods out of ARP4754 and into ARP4761A, so ARP4754B now describes what the development assurance process must accomplish while ARP4761A describes how the supporting analyses are performed. Engineers referring to older material should note that the widely cited ARP4754A and the original ARP4761 have been superseded.

These documents matter to electronics engineers because they are where design assurance levels originate. The functional hazard assessment, preliminary system safety assessment, fault tree analysis, failure modes and effects analysis, and common cause analysis described in ARP4761A produce the function development assurance levels and item development assurance levels that DO-178C and DO-254 then consume. Architectural choices made at this stage, such as introducing dissimilar redundancy or partitioning a function so that only part of it is critical, can lower the assurance level a given circuit board or software item must meet and are usually far cheaper than meeting a higher level.

SAE also administers the ARINC standards through SAE ITC. These define the physical and logical interfaces that avionics equipment must implement, including ARINC 429 for the long-established point-to-point avionics data bus, ARINC 664 Part 7 for deterministic switched Ethernet (commonly called AFDX), ARINC 653 for the partitioned real-time operating system interface that makes integrated modular avionics practical, and ARINC 600 for the connectors and enclosures that house line-replaceable units.

ECSS: European Cooperation for Space Standardization

The European Cooperation for Space Standardization (ECSS) develops standards for European space programs. ECSS standards cover space project management, space engineering, space product assurance, and space sustainability. These standards are required for European Space Agency (ESA) programs and are widely adopted for commercial space applications.

Key ECSS standards for electronics include ECSS-E-ST-10 for system engineering general requirements, ECSS-E-ST-20 for electrical and electronic engineering, ECSS-E-ST-50 for communications, and ECSS-Q-ST-60 for electrical, electronic, and electromechanical (EEE) components. The ECSS-Q series addresses product assurance more broadly, with specific standards for component selection, screening, and qualification, for materials and processes, and for the use of commercial components in space applications. Component procurement in Europe is further supported by the European Space Components Coordination (ESCC) specification system, which plays a role broadly comparable to the American QML system.

Space applications present unique challenges including radiation effects, vacuum operation, extreme temperature cycling, contamination and outgassing, and the impossibility of repair after launch. Radiation deserves particular attention because it is the failure mechanism with no terrestrial analogue. Radiation hardness assurance addresses three broadly distinct effects: total ionizing dose, which shifts device parameters gradually over the mission; displacement damage, which degrades optoelectronic devices and bipolar transistors through lattice disruption; and single event effects, in which one energetic particle causes an upset, a transient, a latch-up, or permanent destruction of a power device. Each demands a different response, ranging from parts selection and shielding through circuit-level mitigation such as current-limiting against latch-up, to architectural mitigation such as error-correcting memory, triple modular redundancy, and watchdog-driven recovery.

Because fully radiation-hardened parts are expensive, slow to procure, and often generations behind commercial technology, many programs now use commercial or automotive-grade components with mission-specific radiation lot acceptance testing and system-level mitigation. This trade is central to the economics of small satellites, but it shifts risk from the component vendor onto the program's own test and analysis effort, and it is a poor fit for missions with long durations, high orbits, or crew aboard.

NASA Standards

The National Aeronautics and Space Administration (NASA) maintains its own set of standards for space hardware and software development, published through the NASA Technical Standards System. The NASA-STD-8739 series covers workmanship, including soldered electrical connections, crimping, cabling and harnessing, and the implementation requirements that govern how these are applied; NASA increasingly invokes the IPC documents with their space addendum in place of maintaining wholly separate workmanship requirements. Software assurance and software safety are covered by NASA-STD-8739.8, whose Revision B, issued in 2022, absorbed and cancelled the former software safety standard NASA-STD-8719.13. Software engineering requirements themselves come from NPR 7150.2, which assigns software classifications analogous in spirit to design assurance levels.

Environment-specific guidance is spread across the handbook series. NASA-HDBK-4002 addresses spacecraft charging, specifically the mitigation of internal charging caused by energetic particles penetrating into the interior of a spacecraft, a distinct problem from total dose or single event effects. Parts selection, screening, qualification, and derating guidance is provided in EEE-INST-002, which many programs use as their baseline parts control document.

NASA programs often invoke a combination of NASA standards, ECSS standards, and commercial standards depending on program requirements and international partnerships. The agency's standards reflect decades of experience with space system development and lessons learned from both successes and failures.

MIL-STD Overview

United States Military Standards (MIL-STD) define technical requirements for defense equipment. A 1994 policy shift directed the Department of Defense to prefer commercial standards and performance specifications wherever they would serve, which cancelled many detailed military specifications, but MIL-STDs remain essential where no commercial equivalent exists. Key standards for electronics include MIL-STD-461 for electromagnetic interference requirements, MIL-STD-464 for system-level electromagnetic environmental effects, MIL-STD-1553 for digital data bus communications, MIL-STD-704 for aircraft electric power characteristics, and MIL-STD-1275 for 28 V DC vehicle electrical power.

MIL-STD-461, currently Revision H, published 17 April 2026 and superseding Revision G of 11 December 2015, is particularly important for defense electronics. It establishes limits for conducted and radiated emissions and susceptibility through a set of lettered test requirements, such as CE102 for conducted emissions on power leads, RE102 for radiated electric field emissions, CS114 for conducted susceptibility to bulk cable injection, and RS103 for radiated field susceptibility. The applicable requirements and limits vary by platform, so equipment for a surface ship, an army ground vehicle, a fixed-wing aircraft, and a spacecraft face materially different sets. Compliance demonstrates that equipment will neither interfere with other systems nor malfunction in the electromagnetic environment of the platform, an environment that on a naval vessel or a combat aircraft can include high-power radar and communications transmitters at close range.

MIL-STD-1553 deserves particular note for its longevity. Defined in the 1970s and stable since Revision B, it specifies a dual-redundant, transformer-coupled, shielded twisted-pair bus operating at 1 Mbit/s with Manchester biphase encoding, in which a single bus controller schedules all traffic among as many as 31 remote terminals. Its data rate is trivial by modern standards, but the determinism, fault tolerance, and enormous installed base of the design keep it in service across military aircraft, armored vehicles, and spacecraft, often alongside higher-bandwidth Ethernet-based buses that carry the traffic 1553 cannot.

MIL-HDBK: Military Handbooks

Military Handbooks (MIL-HDBK) provide guidance for implementing military standards and specifications. Unlike standards, handbooks are not contractually binding but offer valuable technical information. Key handbooks for electronics include MIL-HDBK-217 for reliability prediction, MIL-HDBK-338 for electronic reliability design, MIL-HDBK-454 for general guidelines for electronic equipment, and MIL-HDBK-1823 for nondestructive testing.

MIL-HDBK-217, "Reliability Prediction of Electronic Equipment," has historically been the primary reference for predicting electronic equipment reliability. Its last widely distributed update, Revision F Notice 2, dates from 1995, so its component failure rate models predate essentially every semiconductor technology in current production. The models are also built on a constant-failure-rate assumption that does not describe wear-out mechanisms well. The handbook nonetheless remains widely referenced because contracts demand a number and it supplies a common, auditable framework for producing one. Practitioners should treat its output as a comparative figure of merit for trading one design against another, not as a prediction of field reliability. Alternatives and supplements include physics-of-failure modeling, analysis of the organization's own field return data, Telcordia SR-332 for commercial-grade parts, and the FIDES methodology, which was developed by a European aerospace and defense consortium and accounts explicitly for mission profile and process quality.

Defense Specifications

Defense Specifications (MIL-SPEC) define material, product, and service requirements for defense procurement. For electronics, specifications cover components, materials, processes, and finished equipment. Examples include MIL-PRF-19500 for semiconductor devices, MIL-PRF-55342 for resistors, and MIL-PRF-123 for capacitors.

The Defense Logistics Agency maintains the Qualified Products List (QPL) and Qualified Manufacturers List (QML) databases that identify products and manufacturers meeting specification requirements. Using QPL-listed components simplifies procurement and provides confidence in component quality and reliability.

ITAR: International Traffic in Arms Regulations

The International Traffic in Arms Regulations (ITAR) control the export and import of defense articles and services on the United States Munitions List (USML). They are administered by the Directorate of Defense Trade Controls within the Department of State. ITAR compliance is mandatory for any organization handling defense articles, including many electronics used in military applications; Category XI of the USML covers military electronics specifically, while other categories capture spacecraft, guidance equipment, and related items. Violations can result in severe civil and criminal penalties.

ITAR affects electronics manufacturers in several ways. Defense-related technical data, including design documents, drawings, specifications, and software, is itself controlled, so the control attaches to information as well as to hardware. The regulations turn largely on whether an item is "specially designed" for a defense application, a defined term with a specific analytical test rather than a matter of intent or marketing. Components designed specifically for military applications may be controlled regardless of whether they incorporate classified information.

The deemed export rule is the provision that most often surprises engineering organizations. Releasing controlled technical data to a foreign national inside the United States, whether an employee, a contractor, or a visitor, counts as an export to that person's country of nationality and requires authorization in advance. Practical consequences include access-controlled engineering networks, restricted design reviews, careful handling of offshore contract manufacturing, and screening before a foreign-national engineer is assigned to a program. Organizations subject to ITAR must also register with the Department of State, implement documented export control procedures, maintain records, and obtain licenses or use license exemptions for covered activities.

EAR: Export Administration Regulations

The Export Administration Regulations (EAR) control dual-use items that have both commercial and military applications. They are administered by the Bureau of Industry and Security within the Department of Commerce. Many electronics, while not military-specific, fall under EAR controls because of their potential military applications. The Commerce Control List categorizes items by Export Control Classification Number (ECCN), with Category 3 covering electronics design, development, and production, Category 4 covering computers, and Category 5 covering telecommunications and information security. Exports may require licenses depending on the item, the destination country, the end user, and the end use.

Electronics commonly controlled under the EAR include high-performance computing hardware, encryption technology, radiation-hardened and space-qualified components, certain sensors and imaging equipment, and specialized test and measurement equipment. Organizations must classify their products, screen counterparties against the consolidated denied and restricted party lists, apply the end-use controls that prohibit certain transactions regardless of the item's classification, and obtain licenses where required. Determining whether a given item falls under the ITAR or the EAR is itself a recurring compliance question, since the boundary between the USML and the Commerce Control List has shifted repeatedly through export control reform.

Security Classifications and Handling

Defense electronics programs often involve classified information that must be protected according to security classification guides and handling procedures. Organizations handling classified information must maintain facility security clearances, employ personnel with appropriate security clearances, and implement physical and information security measures.

The National Industrial Security Program Operating Manual (NISPOM) governs the handling of classified information by contractors. It was formerly issued as the Department of Defense manual DoD 5220.22-M, but since February 2021 it has been codified as a federal rule at 32 CFR part 117, which gave it the force of regulation and extended it consistently across agencies. The Defense Counterintelligence and Security Agency administers the program. Cleared facilities must implement access controls, marking requirements, transmission procedures, storage requirements, and insider threat programs appropriate to the classification level of information they handle.

Controlled Unclassified Information and CMMC

Most defense electronics work involves no classified material at all, yet still handles information the government protects. Controlled unclassified information, which includes controlled technical information such as drawings, specifications, and test data, is governed for defense contractors by DFARS clause 252.204-7012. That clause requires contractors to safeguard covered defense information using the security controls in NIST Special Publication 800-171 and to report cyber incidents to the Department of Defense within 72 hours. A companion clause, 252.204-7020, requires contractors to record the results of a NIST SP 800-171 self-assessment in the Supplier Performance Risk System.

Self-attestation proved insufficient, and the Department of Defense responded with the Cybersecurity Maturity Model Certification (CMMC) program. The program rule took effect at 32 CFR part 170 in December 2024, and the corresponding acquisition rule, which revised DFARS clause 252.204-7021, took effect on 10 November 2025. CMMC defines three levels: Level 1 for basic safeguarding of federal contract information, verified by annual self-assessment; Level 2 for protection of controlled unclassified information against the NIST SP 800-171 controls, verified by self-assessment or by a third-party assessment organization depending on the contract; and Level 3 for the most sensitive programs, which adds controls from NIST SP 800-172 and is assessed by the government. Requirements are being phased into solicitations over roughly three years.

For electronics suppliers the practical effect is that cybersecurity has become a condition of eligibility rather than a discretionary investment, and it flows down to subcontractors that handle covered information. Small suppliers of machined parts, printed boards, or cable assemblies are affected whenever they receive controlled technical data, and the cost of segregating that data onto a compliant enclave is now a standard consideration in deciding whether to bid defense work.

AS6171: Test Methods for Counterfeit Detection

AS6171, "Test Methods Standard; General Requirements, Suspect/Counterfeit, Electrical, Electronic, and Electromechanical Parts," defines test methods for detecting counterfeit electronic components. Its slash sheets each cover an individual technique, and the base document provides a risk-based framework for deciding which techniques to apply given the part type, its criticality, and the confidence in its procurement history. Available methods run from external visual inspection and remarking-solvent tests, through X-ray and acoustic microscopy, to decapsulation and die verification, X-ray fluorescence and other material analysis, and full electrical characterization over temperature.

Counterfeit components pose serious risks in aerospace and defense applications where reliability is critical and where long production runs outlast the commercial availability of the parts they use. The threat takes several forms: recycled devices harvested from scrapped assemblies, cleaned, and remarked as new; production rejects or downgraded parts remarked to a higher grade or a wider temperature range; devices whose date codes are altered to disguise age; empty or wrong-die packages; and cloned parts with no connection to the original manufacturer. Because these defects typically escape ordinary incoming inspection and functional test, AS6171 exists to give a documented basis for detecting them before they reach a safety-critical system.

AS5553 and AS6081: Counterfeit Parts Avoidance

Where AS6171 covers detection, a second pair of standards covers the management system that prevents suspect parts from being purchased at all. AS5553 applies to organizations that design, manufacture, or integrate electronic equipment, and it requires a documented counterfeit electronic parts control plan covering purchasing practices, supplier assessment, receiving inspection, traceability, and the reporting and disposition of suspect material. AS6081 addresses the same subject from the distributor's side, setting requirements for independent distributors who source parts outside the manufacturer's authorized channel, which is precisely where the counterfeit risk concentrates.

The common thread is procurement discipline. Purchasing from the original component manufacturer or its franchised distributors, and maintaining unbroken traceability back to that source, eliminates most of the risk at negligible cost. Buying from the open market to solve an obsolescence or shortage problem reintroduces it, and the standards respond by requiring escalating verification as the traceability weakens. Suspect parts must be quarantined rather than returned to the seller, because returning them puts them back into circulation. Both standards are widely invoked in aerospace and defense contracts and are commonly cited as the means of satisfying regulatory counterfeit avoidance requirements.

DFARS Counterfeit Requirements

The Defense Federal Acquisition Regulation Supplement (DFARS) includes requirements for counterfeit electronic part detection and avoidance. DFARS clause 252.246-7007, which applies to contractors subject to the Cost Accounting Standards, requires contractors to establish and maintain systems to detect and avoid counterfeit parts, acquire from trusted suppliers, maintain part traceability, screen GIDEP and other credible reporting sources, report suspected counterfeits, and quarantine suspect parts. Failure to maintain an acceptable system can lead to disapproval of the contractor's purchasing system and disallowance of the costs of counterfeit parts and any related rework.

A companion clause, DFARS 252.246-7008, "Sources of Electronic Parts," addresses the procurement side directly. It establishes a preference for obtaining electronic parts from the original manufacturers, their authorized suppliers, or suppliers the contractor has identified as trusted, and it imposes notification and traceability obligations when parts must be sourced elsewhere.

These requirements flow down to subcontractors at all tiers, making counterfeit prevention a supply chain-wide responsibility. Contractors must demonstrate compliance through documented procedures, supplier qualifications, inspection records, and corrective actions when counterfeits are detected. Obsolescence management is the quiet companion to all of this: a program whose parts remain available from franchised sources rarely encounters counterfeits, so lifetime buys, authorized aftermarket sources, and planned redesigns are counterfeit avoidance measures in their own right.

GIDEP: Government-Industry Data Exchange Program

The Government-Industry Data Exchange Program (GIDEP) provides a mechanism for sharing information about nonconforming and counterfeit parts among government agencies and contractors. When counterfeit or nonconforming parts are detected, organizations report the findings through GIDEP to alert others who may have received similar parts.

GIDEP participation is required for defense contractors and provides valuable information for supply chain risk management. The program maintains databases of alerts, failure experience data, and product information that support quality and reliability assurance activities.

Gap Analysis and Planning

Organizations seeking to enter aerospace and defense markets should begin with a comprehensive gap analysis comparing current practices against required standards. This analysis identifies areas requiring process development, documentation creation, training, or infrastructure investment. A realistic implementation plan should address resource requirements, timelines, and certification milestones.

Many organizations find that achieving compliance requires significant cultural change in addition to process changes. The extensive documentation, rigorous verification, and independent review required by aerospace standards may be unfamiliar to organizations accustomed to commercial product development. Leadership commitment and employee engagement are essential for successful implementation.

Documentation and Traceability

Aerospace and defense standards uniformly emphasize comprehensive documentation and bidirectional traceability. Requirements must be traceable to system needs, designs must be traceable to requirements, verification activities must demonstrate that requirements are met, and all artifacts must be under configuration control. Establishing robust documentation practices and traceability systems is fundamental to compliance.

Modern product lifecycle management (PLM) and application lifecycle management (ALM) tools can support traceability requirements, but tools alone are insufficient. Organizations must establish processes for creating, reviewing, approving, and maintaining documentation throughout the product lifecycle.

Certification and Qualification

Most aerospace and defense standards require third-party certification or customer qualification. AS9100 certification is assessed by accredited certification bodies, and the audit process examines the organization's quality management system against standard requirements. DO-178C and DO-254 compliance is assessed by certification authorities such as the FAA or EASA as part of aircraft certification.

Airborne systems introduce an additional layer through delegation. The FAA delegates much certification work to designated engineering representatives and to organizations holding Organization Designation Authorization, and EASA operates a comparable design organization approval scheme. Under DO-178C and DO-254, the authority or its delegate reviews the program at defined stages of involvement, beginning with the plans and continuing through design, verification results, and the final conformity review. Agreeing the plans at the first stage is decisive, because a certification authority that rejects a proposed approach after the verification evidence has been produced leaves the program with little recourse but to redo the work.

Preparing for certification therefore requires thorough internal audits, management review, and corrective action well before the formal assessment. Organizations should engage certification bodies or designated representatives early, and should assume that the reviewers will ask to see the evidence trail rather than a summary of it.