Start with the emitted cloud
- Spray plume
- A spray plume is the airborne cloud that forms after a liquid, suspension, powder, or propellant-driven formulation leaves an actuator, pump, valve, mouthpiece, or nozzle. In testing, the plume measurement depends on the device event, air path, image or sampling plane, capture timing, and the basis used to report the result.1,2,3
Spray behavior changes quickly after actuation. The plume may start as a narrow jet, widen into a developed cloud, shed droplets or particles, evaporate, deposit on nearby surfaces, or continue as a respirable aerosol fraction. Before interpreting the data, the method should define the trigger, delay time, capture distance, orientation, environmental condition, and sizing basis.1,2,5
For pharmaceutical delivery, the practical question is rarely whether a spray exists. What matters is whether the device and formulation produce reproducible geometry, spray pattern, particle or droplet size, and delivered output under the use condition being claimed or compared.1,3,4
Pattern, plume, and PSD are not interchangeable
| Measurement | What it shows | What it does not prove by itself |
|---|---|---|
| Spray pattern | The shape, area, ovality, or distribution deposited or visualized on a plane perpendicular to the spray axis | The full side-view plume, particle size, or delivered dose |
| Plume geometry | The side view of the aerosol cloud, often reported as angle, width, and height at defined timing | The drug-specific distribution inside the plume or the particle-size spectrum |
| Particle or droplet size distribution | The size spectrum by optical, aerodynamic, mobility, or collected-mass basis | The plume shape or target-plane coverage pattern |
| Delivered dose or spray content | How much active or formulation is emitted per actuation or dose event | Where the cloud travels after leaving the device |
FDA nasal bioequivalence guidance treats spray pattern as an image-based comparison at defined distances and plume geometry as a side-view measurement of the aerosol cloud. FDA nasal CMC guidance also notes that plume geometry describes the whole plume without separating drug substance particles from formulation droplets. It therefore complements, rather than replaces, spray pattern and PSD.1,2
Why drug delivery teams combine measurements
- For MDIs, FDA draft quality guidance lists aerodynamic particle size distribution and spray pattern among potential product quality attributes, and it links actuator orifice geometry to APSD, spray velocity, plume geometry, and spray pattern.3
- For nasal mucosal sprays, FDA guidance frames spray pattern and plume geometry as product-performance evidence, with capture distance, image scale, delay time, and analysis settings affecting interpretation.1,2
- For oral or buccal spray programs, spray throw, target coverage, pump repeatability, and droplet spectrum can be scoped as product-specific performance questions rather than assuming an inhalation-only evidence package.1,5
- For consumer aerosol and spray products, FDA research on OTC spray products shows why particle-size assessment can matter when fine aerosol fractions and inhalation exposure are part of the product question.7
MDI and oral inhalation products
MDI development ties together the formulation, container closure system, metering valve, actuator, and patient handling. A change in any device constituent part can shift the emitted aerosol or the amount available to the patient. For that reason, plume data, spray pattern, APSD, and delivered-dose records are often interpreted together.3,6
Nasal and mucosal spray products
Nasal spray measurements are sensitive to distance, orientation, pump design, formulation, and image processing. FDA nasal CMC guidance treats the container, closure, pump, formulation, and spray-producing components as linked parts of drug-product performance throughout shelf life.1,2
Storage and aging can move the result
Spray performance can drift during storage as formulation properties, suspended particles, container closure components, pump parts, valve behavior, or packaging protection change. FDA nasal CMC guidance discusses stability studies as a way to assess physical and chemical stability, device compatibility, and performance for nasal and inhalation spray products.1,8
For suspension spray drug products, FDA nasal CMC guidance specifically calls out how storage time and conditions can affect particle size distribution through unit life. Paired stability pulls can therefore help determine whether aging changes PSD, spray pattern, plume geometry, or dose delivery.1,8
What to define before requesting testing
- Name the product type, such as MDI, oral spray, nasal spray, pump spray, pressurized aerosol, or consumer spray, and identify whether the study supports development, comparison, quality control, or stability review.1,3
- State which endpoint matters first: spray pattern, plume angle and width, PSD, emitted dose, target deposition, or a paired method package.2,4,5
- Define actuation conditions, orientation, capture distance, delay time, environmental condition, replicate plan, and any beginning, middle, or end-of-life sampling positions.1,2
- If aging is part of the question, define storage conditions, pull points, package state, post-pull handling, and the same spray or PSD endpoints to repeat at each pull.1,8
How ARE Labs uses this in scoping
ARE Labs scopes spray and plume work by separating the product question from the measurement. A nasal spray comparison may call for spray pattern, plume geometry, and droplet PSD. An MDI program may pair APSD and spray pattern with actuator-change context and delivered-dose records. For a consumer aerosol, the starting point may be plume behavior and fine aerosol fraction screening.2,3,4,7
The practical output is a method plan that identifies what was actuated, when the event was captured, how the spray was sized or imaged, which controls were used, and what the result can support. When the study includes stability or accelerated aging, the same plan connects storage history with the repeated spray or PSD endpoint.1,5,8