RF Drone Detection: Signals, Alerts and Direction Finding

No. The stated frequency span and instantaneous receiver bandwidth are different specifications. Scanning behaviour and revisit time also affect reception of short transmissions. Before selecting a receiver, ask how it monitors the frequencies relevant to your target aircraft and site.

No. Electrical equipment at oil and gas facilities still needs assessment against the applicable hazardous-area classification, even if it only receives signals. Confirm the installation requirements and supporting certification documents for the proposed equipment; an Ex enclosure marking alone is not proof of ATEX or IECEx certification.

No. RF detection relies on detectable radio transmissions, so RF-silent aircraft require complementary sensing. Buildings and radio congestion can also affect reception of transmitting aircraft. Describe your target aircraft, site layout and monitoring objectives so these limitations can be considered when defining the detection approach.

Compare like-for-like signals and receiver types. The handheld detector specifies 1.5–2 km; portable and fixed locating units specify 2–3 km for video or packet detection and 500 m–1 km for digital control signals. These figures are not interchangeable coverage guarantees. Provide a site plan and target aircraft types when discussing expected coverage and reception constraints.

The information depends on the receiver and aircraft type. The sensing station's position and track information is aircraft-dependent. The direction finder specifies 360° azimuth coverage and ≤5° angular accuracy, but a bearing is not a complete position. Ask what information the proposed receiver can provide for your target aircraft.

A handheld detector supports patrol alerts with sound and vibration. A sensing station provides allow/deny lists, track replay, event logs and statistics. For bearing information, discuss a direction finder. Share your site plan, target aircraft types and integration requirements so the quotation addresses your intended monitoring workflow.