Site patterns come first, instead of pretending one famous launch or one photo-friendly route should dominate every pilot decision.
Choose the terrain before the coordinates
Flying above a familiar coastal town, exploring an inland plateau and planning a mountain day pose different questions. The useful starting point is the type of terrain and your own level, not a ranking by height or view.
The matrix groups the documented places. It is a reading aid, not a permission or live-site board.
| Pattern | Example notes | Useful when | Do not assume |
|---|---|---|---|
| Coastal near-stay | Budva / Brajići, Petrovac / Buljarica, Bar / Vrsuta | You need a compact coastal read near towns, beaches, and holiday movement. | Easy wind, easy landing, simple retrieve, or simple airspace just because the coast looks close. |
| Bay / destination-led | Kotor / Zanjev Do, Herceg-Novi / Dizdarica | Terrain, Bay relief, destination identity, and airspace sensitivity shape the site question. | A strong view is permission, a briefing, or evidence that the site fits your level today. |
| Inland / plateau | Krnovo, Danilovgrad / Stubica, Kosanica, Tabla / Pljevlja, Tuzi / Decic, Andrijevica / Balj, Mojkovac / Gradac | You are looking beyond the coast toward thermal, landing, progression, or wider route context. | Local reading, retrieve planning, or top-landing caution becomes optional inland. |
| Mountain / support-dependent | Durmitor / Savin Kuk | Cable-car operation, mountain weather, altitude, and landing choices are central to the decision. | A known mountain name means current access, stable weather, or simple logistics. |
| Lake / progression context | Visitor / Plav | Microclimate, SIV context, education, or progression boundaries matter more than quick site choice. | Training value equals suitability without local pilot input and current conditions. |
Orientation only: a site pattern helps you choose the next question. It does not authorize a launch, replace rules checks, or replace a current briefing.
Why the places are different
Coastal ridges: Brajići, Buljarica and Vrsuta vary in access, landing conditions and return logistics, even though they belong to the same broad coast.
Kotor Bay and Orjen: Zanjev Do and Dizdarica need their own terrain and airspace reading. An impressive view does not settle permission, landing or convective weather.
Inland hills and plateaus: Krnovo, Stubica, Kosanica, Tabla, Dečić, Balj and the Mojkovac area raise different questions about access, thermal development, landing fields and sometimes top-landing difficulty.
Mountains and lake country: Savin Kuk and Visitor/Plav require attention to mountain weather, microclimate and whether the site fits the pilot’s experience.
What to check before a flight
A site note helps with preliminary orientation. The actual plan still needs current official airspace data, valid privileges and insurance where required, confirmed access and landing rights, current weather, equipment and a suitable local briefing. No saved wind direction or historic average flight can settle that on its own.
If the question is still broad, go to pilot orientation. For official-source and approval questions use rules and airspace. For briefing or retrieve questions, see pilot support.
Technical site notes
The current technical notes keep checked clues and caution points. They are not current flying decisions.
The pattern column comes first. Open an individual note when that pattern matches your real question.
| Site note | Pattern fit | Why it has its own note |
|---|---|---|
| Kotor / Zanjev Do | Destination-led Bay pattern | Permission, SMATSA / ATC approval, TMA context, and landing caution are too important to bury in a scenic paragraph. |
| Budva / Brajići | Near-stay coastal pattern | It needs solo-pilot access, landing, experience, and near-aerodrome/TMA cautions separate from Budva tandem context. |
| Herceg-Novi / Dizdarica | Destination-led / Orjen-side pattern | TMA context, strong thermals, and convective-weather cautions make it a briefing-led note. |
| Petrovac / Buljarica | Near-stay coastal pattern | Rocky take-off, line-protection note, GPS, and S / SW / W direction set deserve controlled technical context. |
| Bar / Vrsuta | Broader coastal movement pattern | Access, landing, and wider coastal movement logic are part of the site reading. |
| Durmitor / Savin Kuk | Support-dependent mountain pattern | Cable-car operation, mountain weather, and landing choices make it operationally sensitive. |
| Krnovo | Inland plateau progression context | Wide landing and progression value need current local reading before becoming a recommendation. |
| Danilovgrad / Stubica | Inland landing / local-briefing pattern | Landing meadows and inland route context need a separate technical record. |
| Kosanica | Inland / plateau pattern | Top-landing caution and forest coverage are central to the note. |
| Tabla / Pljevlja | Inland / local thermal pattern | Top landing is an advanced-skill question and should not be normalized. |
| Visitor / Plav | Education and progression context | Microclimate, SIV context, and local-pilot consultation need explicit boundaries. |
| Tuzi / Decic | Inland basin hill | Zeta-basin air, SMATSA takeoff caution, and last-stretch macadam stay separate from coastal and Durmitor notes. |
| Andrijevica / Balj | Inland higher-experience hill | Macadam access, two launch aspects, and Lim-valley air must not collapse into Visitor / Plav. |
| Mojkovac / Gradac | Tara-approach inland launches | Gradac live station plus Bojna Njiva access and Jalovište landing; not Savin Kuk. |
Why this helps
Pilots can compare site logic, trip shape, and support needs before moving into rules, services, or education detail.
Named technical notes stay visible without turning the national layer into an uncontrolled launch archive.
Last reviewed: October 5, 2026 · Review status: Next review scheduled
- Last reviewed
- Review due by
Quick answers
Quick answers
Is this a complete catalog of every site in Montenegro?
No. It orients readers to the main site patterns first instead of turning into an uncontrolled launch-by-launch inventory. Currently 14 solo-pilot technical notes sit under those patterns. That count is inventory, not a promise that any named site is flyable today.
Is this the same as tandem places in Montenegro?
No. [Tandem places](/tandem-paragliding-places-in-montenegro/) compare first-flight directions by stay and scenery. This page orients visiting and future pilots by site pattern before a briefing, rules check, or one exact note.
Should I choose one exact spot immediately?
Not usually. A stronger first move is understanding which type of Montenegro site pattern matches your goal, logistics tolerance, and support needs.
Is this only for advanced pilots?
No. It also helps future pilots understand how site logic differs before they turn that interest into a rules, education, or support question.
Do paragliding sites come before rules and airspace?
Often yes as a first step. Rules are easier to understand once the reader knows what kinds of sites and flying patterns they are comparing.
Does this replace local briefings or live site advice?
No. It prepares you to ask better local questions, not replace real briefings, weather judgment, or current site-specific guidance.
Are the listed sites flyable today?
No. This is not a current flying recommendation. Weather, access, airspace, site condition, pilot level, equipment, and local briefing still decide whether any named site is usable on a specific day.
Continue in this guide
Choose the next page
Specialist guides
Continue with the guide that fits your next question
These links open specialist guides for a place, scenic mood, or wider context. paragliding.me keeps the country-level answer and points you onward once the question becomes more specific.
