Helps pilots and clubs avoid a vague first message that cannot be checked against dates, level, equipment, insurance, area, or group size.
Pilot request route
Use this page when the pilot question is already concrete
This route is for visiting pilots, clubs, instructors, small groups, corrections, and public-interest messages that need pilot context. It is not a general tourist tandem contact path, and it does not confirm weather, permission, insurance, or flight readiness.
How requests are handled
- Default
- Structured email
- Include
- Status, licence, insurance, dates, area, group size
- Not
- Clearance, permission, or weather approval
Why this is a useful start
Why this page helps
Separates orientation, rules, site notes, pilot services, education, corrections, and urgent support before the request becomes a loose contact thread.
Keeps responsibility clear: this route can help with public routing, but it does not replace current local judgment, official sources, permissions, insurance, or pilot decisions.
Structured email form
Build the pilot request before opening email
The form does not submit to a hidden booking system. It prepares a structured email so the request can be read with the pilot, club, route, date, insurance, and responsibility context visible.
Email fallback
Use the structured form above when a short public page is no longer enough and the request needs a person to read the context before answering. The form prepares an email; it does not send the request to a hidden booking system.
If the form, JavaScript, or your email client does not open cleanly, send a normal email to [email protected] with the subject Pilot or club request - Montenegro paragliding.
Copy this fallback template into the message body:
Request type:
Name:
Email:
Country / club:
Pilot status: student / licensed pilot / instructor / club representative
Licence or rating, if relevant:
Insurance status:
Planned dates:
Area of interest:
Number of pilots:
Equipment type:
Main question:
I understand this request does not create flight clearance, site permission, weather approval, insurance confirmation, or instructor responsibility.These are the same fields used by the structured form. Keeping them visible on the page matters because pilot-support requests should still work if a browser, script, or email client fails.
Request types
Use one clear request type in the first line. If you are unsure, use pilot-orientation and explain the question plainly.
pilot-orientation- you need the right starting point for flying, learning, sites, rules, or support in Montenegroclub-group- a club or small pilot group is considering dates, area, briefing, retrieve, or coordination needsinstructor-training- the question is about instructor-backed support, training context, or education routingsite-correction- you found an outdated detail, source issue, safety note, or local-site correctionsafety-weather-question- the issue is current conditions, weather, safety process, or responsibilitymedia-ngo- the request comes from media, NGO, public organisation, research, or public-interest cooperationwrong-site-route- the question reached paragliding.me but probably belongs to another site or owner route
That first line matters. It shows whether the request belongs to general orientation, rules and airspace, site notes, practical pilot support, public-interest cooperation, or a correction.
What happens after you send it
The request is read as a routing and clarification request, not as a confirmed flying plan.
Depending on the context, the next useful answer may be:
- a request for missing pilot, insurance, date, area, or equipment details
- a pointer back to pilot orientation, rules and airspace, site notes, pilot services, education, or technical support
- a note that the question needs current official sources, local briefing, or direct operational confirmation before anyone can rely on it
- a simple correction or wrong-route handoff if the message belongs somewhere else
This is why a full email is better than a short chat message. The first reply can be more useful when the missing safety and routing context is already visible.
No fixed response time is promised on this page. If the issue is genuinely time-sensitive and already pilot-related, use urgent WhatsApp escalation after the pilot context is clear.
When WhatsApp is appropriate
Use WhatsApp only for urgent pilot escalation:
That means a clearly time-sensitive pilot matter where normal email routing is too slow. It does not mean general availability checks, first-time tourist tandem questions, broad travel planning, or casual site comparison.
What this request does not do
Submitting a pilot request does not create:
- flight clearance
- site permission
- weather approval
- airspace approval
- insurance confirmation
- instructor responsibility
- permission to ignore local briefings or current official sources
The request can help route the question. It cannot replace the pilot’s responsibility or the current local and official information that real flying decisions require.
Better context makes a better answer
Short messages often create slower answers for pilot requests.
For example, “Can we fly in Budva next week?” may actually mean several different things:
- a visiting pilot wants site orientation
- a club wants a group briefing
- someone needs tandem or instructor-backed support
- the question belongs to airspace, insurance, equipment, or weather
- the person is actually a first-time tandem passenger and belongs on the tandem route instead
The structured intake keeps those different requests from collapsing into one vague contact thread.
Quick answers
Quick answers
Who should use this route?
Visiting pilots, future pilots with a concrete support question, clubs, instructors, small pilot groups, media or NGO contacts, and people reporting site or safety corrections.
What is the best channel?
Structured email is the default because pilot requests need context. WhatsApp is only for urgent pilot escalation after the request is clearly time-sensitive.
What happens after I send the request?
The request can be read for routing, missing context, and the next useful check. A reply may point you to pilot orientation, rules, site notes, pilot services, education, or a follow-up question. It is not flight clearance.
What if the form or email client does not work?
Send a normal email to [email protected] with the same subject and paste the visible fallback template from this page into the message body.
Can this route approve a flight?
No. It can help route and clarify a request, but it does not approve weather, airspace, launch access, insurance, supervision, or pilot readiness.
What if I only want a tandem flight?
Use the tandem and local route guidance instead. This structured intake route is not the main path for first-time tourist tandem contact.
Continue in this guide
Choose the next page
Broader contact routing Return to the contact routing page if the request is not specifically pilot, club, instructor, group, or pilot-support intake. Pilot orientation in Montenegro Read this first if the request is still broad and you are not yet sure which pilot branch you need. Pilot services in Montenegro Use this when the request is about briefings, retrieves, permit-support routing, weather consultation, or local coordination. Rules and airspace in Montenegro Use this when the unresolved question is legal, airspace, current-source, or responsibility-related. Paragliding sites in Montenegro Use this when you need national site-pattern orientation before naming one exact local support request. Tandem first-flight guide Use this if the real question is a first guided tandem flight rather than a pilot, club, instructor, or support request.