10.4 GNSS, Radio Theory & Transponders
Key Takeaways
- GNSS (e.g., GPS and multi-constellation receivers) provides position, velocity, and time by ranging to satellites; RPAS automation and mapping depend on healthy GNSS geometry and integrity.
- Signal loss and error sources include multipath, masking/urban canyons, interference/jamming, spoofing risk, and poor satellite geometry—plan degraded modes and visual navigation backup.
- Radio waves: lower frequencies generally travel farther and diffract more; VHF/UHF dominate many comm/datalink bands with largely line-of-sight behaviour at RPAS heights.
- Interference comes from other transmitters, harmonics, saturation near high-power sites, onboard electronics, and illegal jammers—spectrum discipline protects C2 links and GNSS.
- ATC transponders (Mode A/C/S concepts) make aircraft more visible to SSR and collision-avoidance systems; RPAS pilots need the awareness context for shared airspace even when not equipping a full manned Mode C set.
10.4 GNSS, Radio Theory & Transponders
Quick Answer: GNSS fixes position by timing signals from multiple satellites; protect it from multipath, masking, and interference. Radio bands behave differently: LF/HF can travel long distances; VHF/UHF are workhorses for line-of-sight comm and many C2 links. Interference degrades control and navigation. Transponders (Mode A/C/S) help ATC and traffic systems see equipped aircraft—know the concept for operations near manned traffic. Locator aids help recover a downed RPA.
Modern RPAS navigation is a fusion of GNSS, inertial sensors, barometers, and magnetometers. When GNSS degrades, automation can fail dramatically—RTH to a wrong point, unstable hover, or uncontrolled drift. Advanced pilots must understand the RF world enough to plan sites, brief risks, and talk intelligently about conspicuity near controlled airspace.
GNSS / GPS principles
GNSS (Global Navigation Satellite System) is the umbrella term for satellite navigation constellations (GPS, GLONASS, Galileo, BeiDou, and regional systems). Many consumer and professional RPA receivers are multi-constellation and sometimes multi-frequency, improving availability in hard environments.
How a fix is made
- Satellites broadcast precise time and orbital data.
- The receiver measures time of flight → range (pseudorange) to each satellite.
- With enough satellites in good geometry, the receiver solves for 3D position and time (typically four unknowns → at least four satellites for a basic 3D fix).
- Velocity comes from Doppler/carrier changes; time from the solution clock bias.
Dilution of Precision (DOP) describes geometry quality: clustered satellites → poor geometry → larger position error for the same ranging noise. Apps that show satellite count and HDOP/PDOP are more useful than count alone.
What RPAS use GNSS for
- Horizontal position hold and autonomous waypoints
- Return-to-home and geofencing
- Mapping/survey geotags and accuracy claims
- Groundspeed and wind estimation aids
- Time stamps for logs and some authorization/telemetry systems
Integrity matters as much as accuracy: a confidently wrong fix (spoofing or severe multipath) can be worse than a flagged “no fix” state that forces the pilot to land visually.
Signal loss, multipath, and interference
| Hazard | Mechanism | Operational sign |
|---|---|---|
| Masking / urban canyon | Buildings/terrain block sky view | Satellite count drops; position jumps along streets |
| Multipath | Signals reflect off glass, water, metal | Position wander, altitude blips near structures |
| Foliage / hangars | Attenuation under canopy or indoors | Fix lost after launch from deep cover |
| Poor geometry | Satellites clustered low on horizon | High DOP even with “enough” satellites |
| Jamming | Strong noise in GNSS bands | Sudden loss of GNSS across all craft in area |
| Spoofing | Counterfeit signals pull the solution | Plausible but wrong track—dangerous if trusted blindly |
| Onboard EMI | Poor wiring, damaged shields, some payloads | Intermittent GNSS when payload powers up |
Mitigations for Advanced operations
- Survey sky view; avoid launching from deep courtyards when possible.
- Wait for stable GNSS before precision missions; heed manufacturer readiness indicators.
- Set RTH and geofence with obstacle-aware altitudes; do not assume GNSS perfection.
- Maintain visual navigation skill—VLOS is the legal and practical backup.
- Treat unexplained simultaneous multi-aircraft GNSS loss as possible interference; land and assess.
- Keep firmware and GNSS modules current per manufacturer service instructions.
Exam trap: believing “GPS always works below 400 ft” or that telemetry map position is infallible near skyscrapers.
Radio wave characteristics by band
Electromagnetic waves used for communication and navigation differ by frequency and wavelength. Higher frequency → shorter wavelength → generally more line-of-sight behaviour and higher free-space path loss for a given antenna design, but also more bandwidth for data.
| Band | Frequency order (teaching) | Propagation traits | Typical aviation relevance |
|---|---|---|---|
| LF | Low frequency (tens–hundreds of kHz class) | Ground wave, long range possible | Legacy long-range nav concepts |
| HF | High frequency (3–30 MHz class) | Skywave ionospheric skip; long range variable | Long-range voice (manned oceanic/remote), not primary small RPAS C2 |
| VHF | Very high frequency (30–300 MHz; aviation voice ~118–137 MHz) | Mostly line-of-sight; reliable local voice | ATC/air-to-ground voice, many traffic frequencies |
| UHF | Ultra high frequency (300 MHz–3 GHz class) | Line-of-sight; building attenuation; common for data | Many RC/C2 links, some telemetry, GNSS ~1.2–1.6 GHz band region |
Line-of-sight reality for RPAS
At typical VLOS heights, Earth curvature is rarely the first limit—trees, buildings, and your own body are. Raising the control station antenna, maintaining orientation of directional antennas, and avoiding human-body shielding improve link margin. Beyond-visual strategies require more than “I still have video”; they require legal authority and robust C2 design.
Bands for nav vs com (conceptual)
- Navigation: GNSS microwave bands; traditional ground navaids (VOR/ILS) in VHF/UHF regions for manned aviation context; RPAS primarily GNSS + inertial.
- Communication: VHF-AM aviation band for ATC/MF/ATF monitoring and ROC-A phraseology practice; RPAS command-and-control often on manufacturer ISM/UHF/Wi-Fi-like bands subject to spectrum rules.
- Do not transmit on aviation voice frequencies with non-approved equipment; hold appropriate radio operator credentials when required for the operation you conduct.
Causes of radio interference
Interference is any unwanted energy that degrades a desired signal:
- Co-channel / adjacent-channel users on shared ISM bands (other drones, cameras, Wi-Fi congestion at events).
- Harmonics and spurious emissions from damaged transmitters or cheap electronics.
- Receiver desensitization near high-power broadcast, radar, or cellular sites.
- Onboard coupling between video transmitters, poorly shielded payloads, and C2 antennas.
- Illegal GNSS or C2 jammers—criminal tools that can drop many aircraft at once.
- Physical multipath that is not “noise” but still destroys symbol integrity on digital links.
Controls: frequency planning when the manufacturer allows channel selection; distance from known RF hazards; healthy antennas and connectors; EMI-aware payload installation; immediate land-and-assess when control quality collapses.
ATC transponders: Mode A/C/S awareness
Manned aircraft often carry ATC transponders that reply to secondary surveillance radar (SSR) interrogations so controllers (and traffic systems) see a reinforced target with identity and, for altitude-reporting modes, pressure altitude.
| Mode (teaching) | What it provides |
|---|---|
| Mode A | Identity code (squawk) reply |
| Mode C | Mode A + pressure altitude reporting |
| Mode S | Selective addressing, enhanced data; supports modern surveillance and TCAS/ACAS ecosystems more richly |
Why Advanced RPAS pilots still care
- Controlled-airspace and aerodrome environments are full of Mode C/S equipped traffic; your authorization and see-and-avoid planning assume fast, IFR-capable aircraft may be present even if you never hear them on a loudspeaker.
- Some airspace rules for manned aviation are framed around transponder equipment (Mode C veils / transponder airspace concepts in broader air law). Know the vocabulary when reading airspace and CFS materials.
- RPAS generally are not substitutes for a full certified Mode C installation unless a specific equipped system and approval path says otherwise—do not invent equipage. Conspicuity technologies for drones (remote ID, network tracking, approved ADS-B IN awareness devices where used) are evolving; exam and field practice follow current Canadian rules and manufacturer approvals.
- When ATC issues instructions to manned traffic based on radar/MLAT/ADS-B pictures, your small RPA may be invisible to that picture—another reason authorization, altitude limits, and lateral confinement matter.
Exam focus: Explain that Mode C adds altitude reporting; Mode S is addressable/enhanced; transponders support ATC surveillance; RPAS pilots need shared-airspace awareness even when not squawking as an airliner.
Locator devices
After a flyaway, fly-down, or forced landing in crops/forest/water margins, recovery depends on locating the aircraft:
| Aid | Role |
|---|---|
| Integrated GNSS + app last-known position | First search cue; may be wrong if GNSS failed mid-event |
| Aircraft LEDs / sound | Short-range visual/aural find in dusk grass |
| External Bluetooth/RF trackers | Independent of flight controller if battery still lives |
| Bright airframe colours / flags on tethers (where used) | Passive conspicuity on the ground |
| VHF/UHF direction-finding on a beacon (specialized) | Search teams for larger systems |
Plan locator strategy before the mission for high-value or hard-to-access sites. A medium RPA lost without a locator plan is an expensive lesson and a potential public hazard if it landed near people or infrastructure.
Integrated RF/nav preflight checks
- GNSS status green; sky view acceptable; home point verified on the map against visual reality.
- C2 and video link quality at range points you will actually use; antenna orientation correct.
- No known jamming/event RF chaos (races, dense Wi-Fi festivals) without mitigations.
- Failsafe / lost-link behaviour matches the site survey (climb, RTH, land, hover) and energy budget.
- Crew knows that map position can lie; eyes remain primary under VLOS.
- Near controlled airspace: authorization complete; traffic awareness plan includes the fact you may not appear on ATC radar the way Mode C traffic does.
Common exam traps
- Assuming four satellite icons guarantee a safe autonomous mission in an urban canyon
- Confusing multipath with “stronger signal is always better”
- Thinking VHF aviation voice and RPAS C2 are the same radio service
- Believing Advanced certificate automatically includes Mode C equipage privileges
- Ignoring interference as a cause of simultaneous GNSS/C2 anomalies
Bottom line: GNSS and radios make modern RPAS powerful and fragile. Understand how fixes are made, how bands propagate, how interference bites, and how manned transponders shape the surveillance picture you share. Plan for degraded navigation the same way you plan for wind—before takeoff, not after the icon freezes.
A basic 3D GNSS position solution typically requires ranging to at least how many satellites, and why?
Which statement best describes multipath error affecting GNSS near glass-walled buildings?
In manned ATC surveillance teaching, what does Mode C add compared with Mode A alone?