Two shapes, one question
On the surface, route and radius briefings look like different products. They're not. They share the same underlying data — every European NOTAM, every airspace, every live AUP/UUP activation — and ask the same safety question: what can affect this flight?
The difference is only the geometry of the question. A route briefing defines a corridor between waypoints and filters everything outside it. A radius briefing defines a circle around a point and filters everything outside that. Same data layer, two different shapes.
A corridor for the route, a circle for the place.
When the question is a line
Use a route briefing when the flight has a defined path between two or more airfields. Cross-country VFR, multi-leg IFR, training nav legs — anywhere the question is what happens along the line.
Corridor width is the knob worth thinking about. A tight VFR corridor (5 NM either side) keeps the briefing focused but can miss zones that activate slightly off-track. A wider corridor (8–10 NM) captures more, including activations that might cause an ATC vector or re-route. Default to 5 NM for VFR, 8 NM for IFR.
When the question is a place
Use a radius briefing when the flight is local or place-bound. Circuit work, training sessions, tour flights, glider local sectors, balloon launches, photography work — anywhere the question is what's happening around here.
Radius briefings are also the right tool for departure, destination and alternate checks on a longer flight. A 10 NM radius around the departure airfield catches CTR-edge activations that a corridor briefing might not include if your route track doesn't pass through them. Cheap to run, expensive to skip.
Most flights need both
The honest answer to the title question is usually both. A typical cross-country plan calls for one route briefing for the corridor between airfields, plus radius briefings at departure, destination, and any planned alternates.
This pairing covers two different failure modes. The route briefing catches what's en route. The radius checks catch what's at each endpoint. Skip one and you'll eventually miss the activation that wasn't quite in scope for the other.
Each briefing takes under 30 seconds to run on NOTAMbriefing.com. The total cost is well under two minutes for a complete picture — far cheaper than the alternative of reading a regional PIB and hoping.
FAQ
Common pilot questions
Can both briefing types be useful for one flight?
Yes — and they usually are. Most pilots combine a route briefing for the corridor between airfields with radius briefings around departure, destination, and any planned alternates. Each takes under 30 seconds; together they cover both en-route and endpoint risks.
Do route and radius briefings share data?
Yes. Both pull from the same underlying fusion of Eurocontrol EAD (NOTAMs), NM B2B (AUP/UUP), and AIP/SUP schedules. The only difference is the geometry that filters the result.