GROL common mistakes
GROL · Understand the traps and how to avoid them.
Treats the GROL as the authorization for the vessel or aircraft station itself, answering 'the operator license covers it' when asked what license the station needs.
Both are called 'licenses' in the marine and aviation rules, and in daily practice the operator carries a certificate while the station is authorized separately, so the two blur together.
What to do instead
Drill the split until it is automatic: operator license = the person; station license = the transmitter, ship, or aircraft. On every rules question, first decide 'is this about a person or about a station?' before recalling any requirement.
Selects a frequency from general familiarity with 'the marine band' or 'the aircraft band' without checking whether that frequency is allocated to the service and ITU Region in the question.
Knowing a handful of working channels feels like knowing the allocation table, and allocation, assignment, and operational use are three different things that all sound like 'the frequency you may use'.
What to do instead
Answer from the table logic, in order: identify the service, then the ITU Region (1, 2, or 3), then decide whether the question asks about allocation, assignment, or authorization. Remember the trap: a frequency being widely used does not make it allocated.
Sends MAYDAY for a radio check or drill, or sends PAN-PAN when there is grave and imminent danger, and omits required content such as position and nature of distress.
The three priority levels share nearly identical formats, and routine practice on real equipment erodes the distinction between a test and an actual alert.
What to do instead
Build a three-row table and rehearse it: distress = grave and imminent danger needing immediate assistance; urgency = urgent but no immediate danger; safety = navigational or meteorological warning. Then rehearse the distress message in fixed order: MAYDAY three times, station identity, position, nature of distress, assistance required, persons on board, other information.
Adds and subtracts decibels as though they were linear gains, e.g., concluding that a 10 dB increase means ten times the meter reading, or that two cascaded 3 dB stages give 6 times.
The rules of thumb (3 dB doubles, 10 dB is ten times) get memorized as standalone facts without the logarithmic relationship behind them, so they are misapplied once stages are chained.
What to do instead
Convert to a ratio before ever combining: dB = 10 log(P2/P1) for power and 20 log(V2/V1) for voltage or current. Add dB across stages, then convert once at the end, and sanity-check that a 3 dB stage can never multiply by more than about 2.
Substitutes a peak or peak-to-peak voltage straight into a power or dissipation formula without converting to RMS.
Oscilloscope readings and schematic annotations are usually peak or peak-to-peak, while the familiar power formulas are written in RMS, and the conversion step is the first thing dropped under time pressure.
What to do instead
Write the conversion in the margin before substituting: Vrms = 0.707 x Vpeak, and Vrms = Vpeak-to-peak / 2.828. Use the reasonableness check that RMS dissipation must be lower than any number computed from a peak value.
On a low-output or high-current amplifier fault, answers 'replace the final transistor' instead of naming the bias, drive, or load condition that actually produced the symptom.
The final device is the visible, expensive, historically failure-prone part, so it attracts blame, while troubleshooting questions are written to reward the measurement path rather than the parts swap.
What to do instead
Work a fixed sequence every time: DC supply and bias at the device, then drive level at the input, then load and SWR at the output. Answer with the stage the evidence points to, not the component that usually dies.
Treats SWR, characteristic impedance, and load impedance as a single quantity, and cuts a dipole or phasing line to the free-space half wavelength without applying velocity factor.
All the impedance terms are expressed in ohms and appear in the same chapter, and the velocity factor of coax (roughly 0.66 to 0.9) is easy to skip when converting wavelength to physical length.
What to do instead
Keep the concepts separate: characteristic impedance belongs to the line, load impedance terminates it, and SWR is the resulting ratio. For any physical length, do it in three steps: wavelength = 300 / frequency in MHz (metres), multiply by velocity factor for line lengths, then apply the antenna's shortening factor.
Assumes HF skywave covers any distance on any band at any hour, ignoring the window between the MUF and LUF, daytime D-layer absorption, and the sunspot cycle.
A single rule of thumb from casual operating experience ('HF goes long at night') gets generalized to every band, distance, and season in the question.
What to do instead
Answer propagation questions by walking the path explicitly: which ionospheric layer, what time of day, what frequency relative to MUF and LUF, and what distance. Sketch the layer and absorption picture for the stated hour before choosing a band or predicting a result.
Attributes every interference complaint to the transmitter, even when the reported symptom fits receiver front-end overload, intermodulation, or an image response.
Interference is usually taught from the transmitter side (harmonics, spurious outputs), and the receiver-side mechanisms use similar vocabulary, so the first familiar cause wins.
What to do instead
Run a discriminator before answering: does the interference vanish with an attenuator or when the receiver is tuned slightly off frequency (front-end overload), does it appear only with two strong signals present (intermodulation), does it sit at the image frequency (image response), or does it radiate and appear on other receivers (harmonic or spurious emission)? Then match the corrective action to that mechanism.
Confuses radar pulse width, pulse repetition frequency, pulse repetition time, and duty cycle, and swaps maximum range with range resolution.
All four time-domain terms are derived from the same two numbers, and their formulas invert each other, so partly remembered relationships collide under exam pressure.
What to do instead
Anchor each term to one formula and one physical consequence: pulse width sets minimum range and range resolution, with a longer pulse giving worse resolution; PRT = 1/PRF sets the maximum unambiguous range; duty cycle = PW / PRT sets average power as peak power times duty cycle. State the physical effect along with the formula every time you use it.