TECHNICAL LIBRARY / 543
Acoustic False Alerts: Birds, Transformers and the Limits of a Single Tone
A sound resembling an aircraft is not yet a verified aircraft, and a verified aircraft is not automatically an unauthorised one. Industrial acoustic evidence needs that distinction: transformer tones, animal sounds, machinery and changing conditions can all complicate interpretation without supporting a universal rejection rule.
ARTICLE SUMMARY
A familiar frequency is context, not a verdict
Transformer magnetostriction helps explain twice-supply-frequency sound components, but not every machine's full spectrum or a detector's confusion rate. Animal sounds are diverse, and little apparent movement does not exclude an aircraft. Meaningful false-alert evidence separates classification errors, unresolved observations and legitimate traffic, with intelligible records and attention to human review rather than guaranteed permanent suppression.
01 / FALSE IN WHICH SENSE
An aircraft classification and a threat judgment can fail differently
The definition of a false report determines what the evidence is actually evaluating.
A non-aircraft sound reported as an aircraft is a classification problem. A real, legitimate aircraft described as unauthorised is a different evidential problem. An unresolved contact is different again: the available record may not support a firm classification. Combining all three under one nuisance label can hide whether the difficulty lies in acoustic interpretation, identity information or an unsupported permission judgment.
A credible report keeps these categories intelligible. It states what the system claimed and what independent information later supported or contradicted that claim. An uncertain record should not be retrospectively called a false aircraft merely because its identity remained unavailable. Conversely, a correct aircraft indication does not become a false detection simply because the flight was authorised. This separation makes technical and governance limitations easier to discuss without exaggerating either success or failure.
02 / TRANSFORMER PHYSICS
Why twice the supply frequency can appear in transformer sound
The familiar 100 Hz or 120 Hz explanation concerns physical excitation, not an aircraft-detection rule.
Magnetostriction describes changes in a magnetic material's dimensions associated with its magnetic state. Siemens' engineering explanation describes periodic vibration and magnetic-force components whose fundamental is twice the power frequency: approximately 100 Hz for a nominal 50 Hz supply, or 120 Hz for a nominal 60 Hz supply. This provides a physical reason for familiar transformer sound components, not proof that every recorded tone comes from a transformer.
Transformer sound can also involve construction, materials, mechanical behaviour and other contributing sources. Harmonic strengths and the radiated sound are not universally identical across equipment or conditions. The Siemens source explains engineering physics and simulation context; it does not measure a C-UAS confusion rate. A familiar component can therefore inform a source discussion, but should not be converted into a detector band, an automatic aircraft verdict or a guarantee that the entire source is permanently recognisable.
03 / ANIMAL SOUND
Birds and insects are not one acoustic category
Broad biological labels do not justify a single claim about tonal structure, harmonics or recognisability.
Animal sounds arise from diverse behaviours and sound-production mechanisms. A bird call is not the same phenomenon as wing movement, and an insect's sound need not share the structure of either. The comparative-bioacoustics review emphasises variability across animal sounds and the need for comparable terminology and acoustic units. It supports caution about sweeping claims that every biological sound has one structure or that a whole taxonomic group lacks useful tonal complexity.
That diversity also prevents a simple universal ranking of birds, insects and machines as easier or harder for a detector. Difficulty belongs to the recorded context and evaluated system, not the category name alone. The relevant evidence should explain which sound-producing circumstances were represented and what classification was supported. The biological review is not an aircraft-detector trial, so it cannot establish a nuisance probability or a guaranteed separation between animal and rotor sounds.
04 / THE INDUSTRIAL MIXTURE
A known machine does not make the surrounding scene fully known
Persistent equipment, intermittent activity and environmental sound can combine into a changing observation context.
Industrial surroundings may include plant machinery, vehicles, ventilation, weather-related sound and activity outside the facility. Some contributions are persistent while others change with operations or conditions. Knowing that a particular machine exists does not explain every received sound, and an unfamiliar component does not establish an aircraft. A source description must remain distinct from the system's eventual classification and the independent evidence supporting it.
A reference recording from one operating state should not be treated as a permanent description of the whole site. Changes can alter the mix without implying either inevitable detector failure or a new threat. The useful review question is what environment the evidence represents and which cases remain unexamined. It is not a public recipe for suppressing plant sounds, nor a claim that a source can be safely discarded forever after one familiar observation.
05 / APPARENT MOVEMENT
Little bearing change does not prove that a source is not an aircraft
Stationary-looking evidence and source identity should not be collapsed into a single automatic conclusion.
An aircraft may hover or produce little apparent bearing change during an observation. Conversely, changes in an observed direction need not independently establish that a reported contact is an aircraft. A statement about apparent movement describes the evidence available, not a universal identity test. The blanket rule that a stationary-looking report must be a ground source therefore exceeds what that observation alone can prove.
Movement can be relevant context without being the sole possible basis for interpretation. A credible report distinguishes an observed pattern, a source hypothesis and an independently supported conclusion. It should also make uncertainty visible when the available record cannot resolve the hypothesis. This is an evidential distinction, not an instruction for tracking logic, motion gates or source-selection algorithms; none of those mechanisms is prescribed here.
06 / MEANINGFUL ERROR RECORDS
An example collection is not a measured false-alert rate
Memorable nuisance cases and comparable performance evidence serve different purposes.
A collection of troublesome sounds can explain why industrial interpretation is difficult, but it does not establish how often a system issues incorrect reports. An event-rate statement needs a clear event definition and observation exposure. A selected example set may overrepresent memorable mistakes or omit quiet periods, misses and unresolved cases. Without that context, a number can appear authoritative while describing only the chosen collection.
Evidence should preserve the reported output, relevant circumstances, independent review conclusion and unresolved limitations. Comparisons between releases or sites also need comparable definitions and scope. A lower displayed total may reflect different accounting rather than improved interpretation. These documentary distinctions help a customer understand the result without publishing operating settings, demanding unrestricted recordings or making a zero-false-alert promise that the evidence cannot support.
07 / HUMAN FACTORS
An intelligible record matters as well as a technical label
Repeated irrelevant indications can burden attention, but human behaviour should not be reduced to an invented universal timetable.
The UK Health and Safety Executive's alarm-management guidance emphasises useful, relevant indications and accommodation of human capabilities and limitations. Its process-industry context helps explain why unclear reports can create attention burdens. Applying that perspective to low-altitude information review is an editorial connection, not a measured C-UAS finding or proof that staff will behave in one predictable way after a fixed number of alerts.
A report becomes more useful when the person reading it can distinguish confirmed findings, uncertain observations and the limits of the available evidence. That clarity supports accountable review without assuming that every indication deserves the same interpretation. Claims about trust loss, staffing burden or response outcomes still need their own evidence. Neither an anecdote nor a general human-factors principle establishes a product's operational effectiveness.
08 / RESPONSIBLE IMPROVEMENT
Better evidence does not mean permanent, cost-free source rejection
A reviewed limitation can guide a scoped improvement claim without becoming a guarantee about every future scene.
An observed classification difficulty can be documented and investigated within the applicable project, data and version boundaries. It does not prove that every future occurrence can be removed without affecting other outputs. Changing the way a system reports one source may have wider consequences that require evidence. A credible improvement statement names the result assessed and retains the conditions and uncertainty attached to it.
Complementary observations may add different information, but they do not erase the need to explain each contribution or authorise data use. For industrial projects and PCBA partnerships, the most useful discussion concerns what the acoustic output means, what evidence supports it and which responsibilities remain with the integrator and customer. That is a stronger foundation than a universal promise to reject birds, transformers or all fixed sources permanently.
SOURCE ATTRIBUTION
The evidence behind this discussion
Sources are named here without outbound links. Research findings and reported events do not establish New Ark product performance or site suitability.
Behzad Forghani, Siemens Simcenter, Magnetostriction: A Source of Noise in Transformers · 28 April 2021
The corporate engineering explanation describes magnetostriction and force components at twice the power frequency, around 100 Hz or 120 Hz. It is not a C-UAS classification test and does not establish universal spectra or false-alert rates.
Comparative Bioacoustics: A Roadmap for Quantifying and Comparing Animal Sounds Across Diverse Taxa, Biological Reviews · First published 2 March 2021
The scientific review emphasises diverse animal sound structures and comparable terminology. It supports qualified discussion of biological variation, not a guaranteed aircraft/animal discriminator or detector nuisance ranking.
UK Health and Safety Executive, Alarm Management · Page date 29 October 2024
Official process-industry guidance discusses relevance and human capabilities in alarm design. Its application here is a human-factors perspective, not a C-UAS alert-rate study, New Ark operational result or prescribed response procedure.
PUBLIC REFERENCE BOUNDARY
A clearer project discussion, not an operating instruction.
01The information roles described here depend on lawful purpose, environmental conditions and independent project evidence. No detection, coverage, identification, interoperability or safety outcome is guaranteed.
02Passive reception is not a hazardous-area certification. Qualified professionals must review equipment approval, site permissions, protected services and the written scope before any engineering decision.
03This article supplies no sensor layout, signal-processing method, threshold, target-selection method, RF-control procedure or operational response instruction. Data rights and decision authority remain with the responsible parties.
ARTICLE FAQ / 543
Questions on Acoustic False Alerts: Birds, Transformers and the Limits of a Single Tone
Answers address evidence, limitations and written project scope, not operational instructions.
RECORDACOUSTIC TECHNICAL LIBRARY
PROJECT DISCUSSION
Take the evidence questions into a written project scope.
Explore the PCBA delivery references or discuss your procurement, compliance and information-rights questions with New Ark. Available documents are project references, not a performance or certification commitment.
Review the full ARC-PERIMETER perimeter solution.
A consolidated reference from microphone-array networking to layered perimeters and project validation.
Microphone Array Drone Detection: Technology, Applications and C-UAS Integration
Microphone-array drone detection combines a physical sensing context with an integration and governance question. This guide brings together technology, application, and existing C-UAS-system integration without treating a public description as a design or operating manual.
Passive Acoustic Drone Detection for Low-Altitude Security
Low-altitude security is a site-specific information challenge. This guide explains how passive acoustic inputs may be considered within perimeter review, safe-offset planning, and multi-sensor corroboration without publishing deployment instructions or field-performance claims.