Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AECTP-300
Defence programme offices and test facilities that write and execute a materiel item's climatic test programme
AECTP-300 is NATO's family of climatic test methods, one per condition, used to test defence materiel against the environments defined in its Life Cycle Environmental Profile.
AECTP-300, Climatic Environmental Tests, is NATO's family of test methods for exposing defence materiel to the climatic conditions it is expected to meet across its service life. It is not a stand-alone document: it draws its climatic category and worldwide climatic data from its companion, AECTP-230, and the process that decides which of its methods a programme actually needs comes from AECTP-100. AECTP-300 itself opens with a shared Method 300 that sets the general conditions, tolerances, documentation and evaluation rules every later method incorporates by reference, then continues as one method per climatic condition: heat, cold, humidity, rain, solar radiation, icing, sand and dust, and the rest. The current edition is Edition E, Version 1 (June 2025), which supersedes the prior edition; the Letter of Promulgation instructs nations to destroy the superseded copy under their own local document-destruction procedure.
AECTP-300 is one of two documents carried by STANAG 4866: "the agreement of nations to use this publication is recorded in STANAG 4866." Its companion under that STANAG is AECTP-230, which supplies the conditions and data AECTP-300's methods test against. AECTP-300 is also meant to be used alongside STANAG 4370, which carries AECTP-100 (the tailoring guidance) and AECTP-600 (a ten-step method for evaluating whether materiel already in service can meet an extended life requirement). The wider AECTP family covers other environments the same way, in pairs of a conditions document and a test document: mechanical conditions under STANAG 4867 (AECTP-240 and AECTP-400), and electrical and electromagnetic conditions under STANAG 4868 (AECTP-250 and AECTP-500).
Every later method incorporates Method 300's rules by reference rather than restating them, and Method 300 says as much of itself: it "includes information which should be considered when adapting the generic test methods of AECTP-300 for any specific environmental test program." It covers pre-conditioning, stabilisation and post-test recovery guidance; item configuration, mounting, chamber and monitoring requirements; the records that must exist before a test starts; what to do when a test is interrupted; how a programme is built from an item's Life Cycle Environmental Profile; and how results are evaluated. Where a specific test method or the project's own Environmental Test Specification states something different from Method 300's general conditions, "they shall take precedence over those stated in this document," so Method 300 is a floor, not an override.
AECTP-300 does not hand a programme a fixed severity to test to. Its requirements documents "must, in all cases, define the anticipated operational scenarios for the test item, so that the environmental test conditions can be derived," using the tailoring process Method 300 says "shall be used to determine the appropriate tests and test variables based upon the Life Cycle Environmental Profile (LCEP)." Individual methods repeat the pattern: a method such as Contamination by Fluids leaves the choice of exposure scenario to the requirements document, "based on the anticipated life cycle scenario." Method 317 (Combined Environments) shows how far this tailoring goes: it runs three separate procedures depending on where a programme sits, one for engineering development before a design is fixed, one for mission support or troubleshooting materiel already in service, and one for demonstrating a mature design meets its full platform specification.
A Test Specifier and a Stakeholder Panel sit above the day-to-day running of a test. Any deviation from stated conditions or tolerances needs the Test Specifier's agreement and a recorded reason in the Environmental Test Report. Where a test is interrupted, the test conductor is instructed to "inform the relevant Stakeholder Panel to obtain approval of the required course of action," and the same Panel approval applies to over-test interruptions, failure investigation, and the more consequential of the method's retest options, which range from a fresh test item through to a component-level retest. Where a test item's operation fails, the root cause is to be determined and the remedial action recorded before the test restarts.
A handful of methods carry obligations beyond the shared pattern. Method 308 (Mould Growth) is to be performed only by technically qualified personnel, because the procedure and its analysis "involve highly specialized techniques and potentially hazardous organisms," and calls for the test item, protective equipment and facility to be decontaminated afterwards. Method 316 (Explosive Atmosphere) requires that "the Test Facility Operators must ensure that they comply with Local and National Regulations, especially with respect to the personal exposure levels, pollution, and hazardous material disposal." Method 313 (Sand and Dust) requires "a risk assessment by the organization responsible for the system under test" before an expensive or unique failed subsystem is replaced and testing resumed. Method 317's electrical-power testing is tied directly to STANAG 3456: aircraft electrical systems used by member countries "shall have the characteristics as defined in either of MIL-STD-704, ISO 1540 or EN 2282."
Beyond Method 300, the rest of the series addresses a single condition each: low pressure and altitude, high temperature, low temperature, air-to-air thermal shock, solar radiation, humid heat, immersion, mould growth, salt fog, rain and watertightness, icing, sand and dust, contamination by fluids, freeze/thaw, explosive atmosphere, combined environments, and acidic atmosphere. Each follows Method 300's own shape: scope, test guidance, the information a test instruction must state, the test conditions and procedure, and how results are evaluated. AECTP-300 also states its own scope boundary: it excludes the near-space and space environment, pointing a programme that needs that instead toward specialist standards outside this document.
AECTP-300 names no certification, accreditation or audit scheme, and nobody is assessed "against AECTP-300" as such. What is checked is the test-and-report cycle itself: functional checks and examinations of increasing depth carried out before, during and after a test; measurements confirming the required conditions were actually achieved; and results evaluated against the failure criteria the requirements document defines, with a small set of excepted causes, such as tooling failure, operator error or government-furnished equipment failure, that do not by themselves count as a failure of the test item. The only calibration certification named anywhere in the document is for test instruments themselves, which is equipment traceability the test facility maintains, not a scheme a supplier or the test item is certified against.
AECTP-300 is an operational and technical standard: the work of meeting it, conditioning a chamber, mounting and instrumenting an item, running the exposure, examining and writing up the result, happens in a test facility, not in software. ComplyTrain does not conduct environmental testing and does not decide which method, condition or tailoring choice a given item needs; those calls stay with the programme's Test Specifier, its design authority, and the test facility carrying out the work.
What ComplyTrain supports is the documentation a programme like this generates: the Environmental Test Specification, test instructions and the resulting Environmental Test Reports held as controlled documents with a version history; a record of which method was selected for a given requirement and the clause used to justify it; Stakeholder Panel approvals for deviations, interruptions and retests kept as auditable decisions; and training records for the personnel running or supervising a test, which matters directly for a method such as Mould Growth that names specifically qualified personnel as a requirement.
The tier and the wider set of AECTPs and STANAGs that apply to a given programme are set by the contract and the customer's quality clause, not by this page. Use the standards explorer to see what sits alongside AECTP-300, and if you want to talk through how the documentation side of a climatic test programme fits around your existing process, get in touch.
Tell us how you need to work with AECTP-300 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
Not on its own. AECTP-300 is a set of test methods, not a legal requirement. It reaches a nation through ratification of STANAG 4866, and it reaches an individual supplier only when a specific tender, contract or Environmental Test Specification calls a method up.
AECTP-230 describes the climatic conditions and the data behind them: what a piece of materiel might meet, and where. AECTP-300 is the companion publication that holds the test methods and procedures used to reproduce those conditions in a test facility. AECTP-230 supplies the conditions to test to; AECTP-300 supplies the methods for testing to them.
The programme itself, through its own requirements documents and Life Cycle Environmental Profile, using the tailoring process set out in AECTP-100. AECTP-300 does not select its own methods for an item; it provides the methods a tailoring process chooses from.
No such certification exists to hold. AECTP-300 names no certification body and describes no conformity scheme against which an organisation, or a compliance tool, could be certified.
The document requires the root cause of a failure to be determined and the remedial action recorded before a test restarts, and sets out retest options ranging from a fresh test item through to a component-level retest, with the more consequential options needing a risk assessment and Stakeholder Panel approval.
NATO publishes AECTP-300 free of charge through the NATO Standardization Document Database, and it is not sold. See the explorer entry for the current source link, and credit NATO if you reproduce anything from it.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.