Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AOP-4674
Propellant manufacturers and national defence research establishments characterizing burning rate during propellant screening, development or qualification
A NATO technical review of non-intrusive methods for measuring how a solid rocket propellant burns, and which methods are mature enough for routine use.
AOP-4674 is a NATO review, not a test method. It surveys the non-intrusive techniques national laboratories and propellant manufacturers have used to work out how fast a solid rocket propellant burns, without disturbing the combustion itself, and it assesses which of those techniques are mature enough for everyday use. The material comes from a NATO Research and Technology Organisation task group that ran from October 1997 to August 2001, and section 1.1 is explicit that the AOP does not present any specific standardized instrument for the job.
Where AOP-57 defines the conventional small motor test for burning rate, and AOP-58 covers analysing the data those tests produce, AOP-4674 reviews an alternative family of approaches that avoid intruding on the burning propellant while a measurement is taken. The point of doing this as a shared NATO document rather than leaving it to individual national programmes is comparability: when different nations report burning-rate results using different non-intrusive methods, a common view of which methods can be trusted is what makes those results meaningful to compare.
The document does not address a supplier the way a quality-assurance publication does. It reports on the community it surveys: national defence research establishments and propellant manufacturers running burning-rate characterization as part of propellant screening, development and qualification work. It names SNPE, a French propellant manufacturer, as one organisation already using one of the surveyed techniques in an industrial procedure, alongside national research programmes in France, the Netherlands, the United States and Italy, and at least one non-NATO participant.
Chapter 2 works through six technique families - ultrasonics, X-ray, microwave, plasma capacitance gauges, acoustic emission, and recoil - one section each, naming the national programmes that have applied each one. Section 2.8 draws these into a critical assessment: it recommends ultrasonic instrumentation for immediate application to routine propellant characterization, endorses acoustic emission as a routine method for propellant strand testing, recommends plasma capacitance gauges for further development, and does not recommend the X-ray or microwave methods for routine use, keeping them as research tools instead. Section 2.9 sets out where the task group thinks further investment should go. Chapter 3 is a reference list; nothing in it is itself a NATO standard other than AOP-57 and AOP-58.
AOP-4674 acquires force the way any Allied Ordnance Publication does: through the STANAG that covers it. It sits under STANAG 4674, and it reaches a supplier only when a national defence contract or a customer's quality requirement invokes that agreement or names a burning-rate measurement method the review discusses - never simply by existing. The edition in front of you is Edition A, Version 1, published May 2018.
There is no assessment scheme here. AOP-4674 carries no certification, government-surveillance, or self-declaration mechanism, and no accredited body or notified body appears in it. Where a burning-rate measurement matters to an assessment, that comes from whatever contract, customer quality clause, or national procurement requirement specifies the method, not from this document.
AOP-4674 does not create a compliance obligation of its own, so there is no mapping from it to a ComplyTrain feature. What it touches is upstream: once a contract or a customer's quality clause specifies which burning-rate measurement approach a supplier is to use, ComplyTrain holds the resulting test records, the method-selection rationale, and the calibration and training records that go with them as controlled documents, retrievable when a customer or a government quality representative asks for them.
The measurement work itself - running the test equipment, reading and validating a burning-rate result - happens in the laboratory, not in software, and ComplyTrain does not perform or replace it. It does not choose a measurement method on a supplier's behalf, and it does not interpret a burning-rate result.
The applicable tier for a defence contract, and which standards come with it, is set by the contract and the customer's quality clause, not by us. If you want to see what sits alongside AOP-4674, from STANAG 4674 to the tests it complements, explore the full standards catalogue or talk to us about how the underlying records get held.
Tell us how you need to work with AOP-4674 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.
AOP-4674 does not state a general mandate. It sits under STANAG 4674, the agreement NATO nations ratify, and a supplier meets it only where a contract or a national defence quality requirement invokes that agreement or specifies one of the measurement methods it reviews.
AOP-57 defines the conventional small motor test for measuring solid rocket propellant burning rate. AOP-4674 reviews non-intrusive alternatives to that test, techniques that measure the burning surface without disturbing combustion, and assesses which of them are ready for routine use.
No. Section 1.1 states plainly that the AOP does not present a specific standardized instrument. It reviews and assesses techniques nation by nation without prescribing a design.
No. The document names no certification, surveillance, or audit scheme, and nothing in it is held by an organisation the way an ISO 9001 certificate is. Any assessment of a burning-rate measurement comes from the contract or customer requirement that calls for it, not from this document.
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.