Charter and private aviation run on quick conversations: a call to an operator, a message to a broker, an email about an empty leg that might fit your dates. Those conversations go better when the question is clear. This FAQ answers the practical questions travellers most often have about how to ask a charter desk for what they need, so that the reply you get is specific, comparable and useful.
Why do vague charter requests get vague replies?
A message such as “How much to fly to the coast next week?” leaves out almost everything a desk needs: which airports, which day, how many passengers, how much luggage, how flexible you are. The responder either guesses or sends a generic answer. A clear request does the opposite. It says what the trip is, what you have already looked at, what you expected and what puzzled you, and it sticks to one concrete trip.
What should a good request include?
- Goal: the trip in a sentence, such as a day return for four people.
- Tried so far: other options you looked at, like scheduled flights or earlier quotes you can describe.
- Expectation: the kind of aircraft, timing or experience you assumed.
- What did not fit: the specific gap, for example “the earliest departure we saw was too late for the meeting”.
- Flexibility: dates, airports or times you can move.
How do I ask about empty-leg flights?
An empty leg happens when an aircraft has to reposition without passengers. If you are curious about them, the question to bring to a desk is not “Do you have any cheap flights?” but “I need to travel between these two areas within this window and can leave on short notice; do any positioning flights match?” To understand the idea first, you can read this explainer on the mechanics behind empty-leg flights, then phrase your request around the facts you learned. A second perspective in this walkthrough aimed at private jet travellers is helpful for the vocabulary that desks use.
What if the jargon is unfamiliar?
Say so, and describe what you observe instead. “The quote lists a positioning fee, and I do not know what that covers” is a perfectly good question. It shows what you have read, what you expected and what puzzled you. Desks would rather clarify one line item than lose a customer to confusion.
How do I describe a problem with a booking?
Use the same pattern. For example: “My confirmation lists departure from one airport, but the message from the operator mentions another. I expected the same field as in the first email. Can you confirm which one is correct?” This keeps the discussion on a single, verifiable detail. Avoid piling on several issues in one message; separate threads are easier to track and answer.
Is a longer message always better?
No. Length is not the aim; completeness is. A well-built request can be five short lines. What you want to avoid are two extremes: the one-liner that leaves out everything, and the long story that buries the question. Put the question near the top, then supply the background in a short list.
Where did this question habit come from?
Many technical fields have long relied on precise, structured questions. Learners and professionals in IT operations post such write-ups on Debug School, a members’ site where the posts that attract the best help usually describe the attempt and the outcome. The charter world is not the same industry, but the lesson holds: people help faster when they can see exactly where you are stuck.
Should I mention my budget?
You can mention a range if it helps the desk narrow the options, but frame it as a constraint rather than a test: “We would like to stay within a figure we will share on request, and we are open to a different departure time if it helps.” This is simply information about your trip, not financial guidance, and it lets the desk propose alternatives instead of guessing where your limits lie.
How soon should I expect a reply?
That depends on the desk and the time of day, so ask when you write: “When can we expect the details?” Giving your own deadline, such as a meeting that fixes the schedule, helps the responder prioritise honestly, and it spares you from chasing a reply that was never going to arrive in time.
What should I do when the answer is not clear?
Repeat what you understood and ask whether that is right. “So the aircraft would depart in the afternoon from the airport nearest the city, with luggage limited to soft bags. Is that correct?” Mix-ups surface at the point where fixing them costs nothing. If the answer changes, you have saved yourself a surprise at the airport.
Can I ask the same question to several desks?
Yes, and it is easiest when your request is written once, clearly. Send the same text to each and compare the replies against it. If one reply answers a different question, that tells you something about attention to detail. Keep in mind that comparing replies is only fair when each desk saw the same facts.
How do I keep a record of what was said?
Prefer written channels for anything involving times, locations or conditions. If you spoke by phone, send a short follow-up summarising it and ask for a reply to confirm. A one-paragraph note is enough, and it gives both sides something to point to if details drift.
What is a good closing line?
End with the specific thing you need: “Could you confirm the departure airport and the luggage allowance by tomorrow noon?” A closing request with a clear deliverable prompts a precise reply. It also lets the desk see at a glance whether they have answered everything you asked.
Quick recap
- State the trip in one line.
- List what you have already checked.
- Say what you expected, and what did not fit.
- Ask one question at a time.
- Confirm the answer in your own words.
A desk may see dozens of enquiries in a shift, and the memorable ones are written with care. Ask clearly and you will usually receive an answer that is clear in return.

