When a recurring helicopter programme makes sense — and when on-demand requests are better
A planned recurring programme can make sense when a corridor shows steady frequency, predictable days, similar passenger numbers and a real time cost on the ground. On-demand requests fit irregular, low-frequency or highly variable trips.
- | | On-demand requests | Planned recurring programme | |---|---|---| | Best for | Irregular trips, changing groups | Stable corridor, regular days | | Planning effort | Low per trip, repeated each time | Higher at the st
- From your [corridor baseline](https://skymatchgroup.com/en/blog/analyse-company-travel-history-helicopter-corridors), take each candidate corridor and answer: Trips per month: is it stable, or does it swing widely?
- Count how many requests the corridor produced last year and how many hours your team spent arranging each one (emails, approvals, changes).
- SkyMatch does not publish prices; each quote depends on aircraft, routing, positioning and dates.
A planned recurring programme can make sense when a corridor shows steady frequency, predictable days, similar passenger numbers and a real time cost on the ground. On-demand requests fit irregular, low-frequency or highly variable trips. Decide with your own data: frequency, predictability, group size and lead time. A plan never guarantees availability; each flight in a series is still checked. Availability, price, permissions, landing sites, aircraft and mission capability are checked for every request. Nothing in this guide is a commitment.
Small change or big change? Two options compared
| On-demand requests | Planned recurring programme | |
|---|---|---|
| Best for | Irregular trips, changing groups | Stable corridor, regular days |
| Planning effort | Low per trip, repeated each time | Higher at the start, lower per flight |
| Flexibility | High | Lower: changes need notice |
| Risk | Each request checked from zero | Under-use if demand drops |
| Data needed | Basic trip details | 12+ months of corridor history |
Start small: an on-demand pattern with a standard brief is often the right first step before any programme.
Step 1: Test predictability
From your corridor baseline, take each candidate corridor and answer:
- Trips per month: is it stable, or does it swing widely?
- Day of week: do most trips fall on the same days?
- Group size: is the passenger count similar each time?
- Lead time: how many days before travel is the trip known?
Predictability score = share of trips on the two most common days × share of trips with the most common group size. Hypothetical example (invented figures): 70% of trips on Monday/Thursday and 60% with 3–4 passengers → 0.70 × 0.60 = 0.42. Below about 0.3, on-demand usually fits better; this threshold is a rule of thumb, not a standard.
Step 2: Compare the planning workload
Count how many requests the corridor produced last year and how many hours your team spent arranging each one (emails, approvals, changes). If the same brief is rewritten every time, a standard brief or a series plan reduces work even without changing the mode.
| Input | Your value |
|---|---|
| Requests per year | … |
| Team hours per request | … |
| Changes or cancellations per year | … |
| Typical lead time (days) | … |
Step 3: Think about cost without assuming prices
SkyMatch does not publish prices; each quote depends on aircraft, routing, positioning and dates. You can still structure the comparison:
- Total trip cost = flight quote + ground legs + traveller time cost + rebooking cost.
- Traveller time cost = hours saved (estimate) × number of travellers × your internal hourly value.
Ask for quotes on both patterns — single requests and a series — for the same corridor and dates, then compare like with like. Use the cost calculator to list the factors, not to predict a figure.
Step 4: Plan in phases
- Phase 1 (one season): on-demand with a standard brief; measure KPIs.
- Phase 2: if frequency and predictability hold, request a series quote for peak weeks only.
- Phase 3: review after a full cycle; extend, reduce or stop.
Each phase ends with a review against the KPIs below. Nothing moves to the next phase automatically.
KPIs to set before and after
| KPI | Before (baseline) | After |
|---|---|---|
| Median door-to-door time | from your records | measured per trip |
| Share of trips on time | from your records | measured |
| Cancellations / changes | from your records | logged |
| Team hours per trip | estimated | logged |
| Seats used vs seats requested | — | logged |
See how to measure service outcomes for definitions.
When data is missing
If you have fewer than 12 months or no reliable times, stay on-demand and collect data for one season with the KPI table above. A programme designed on guesses tends to be under-used or changed often.
Checklist: programme or on-demand
- Predictability score calculated per corridor
- Request count and team hours recorded
- Peak weeks identified
- Quotes requested for both patterns on the same dates
- Phase plan with review dates
- KPIs agreed before the first flight
Next step
Send your corridor, typical days, group size and season to SkyMatch through the request form. SkyMatch reviews the request and arranges the flight where it is feasible; every flight in a series is checked for availability, aircraft, weather, permissions and landing sites. For business travel, see executive transfers.
Sources
Guide: helicopter landing permission and approved sites →
FAQ
Does a recurring programme guarantee seats or aircraft?
No. A plan helps preparation, but each flight is still checked for availability, aircraft, weather, permissions and landing sites.
How many trips a month justify a programme?
There is no universal number. Look at frequency together with predictability, group size and lead time, and test with one season first.
Is a programme always cheaper per flight?
Not necessarily. Compare quotes for single requests and for a series on the same corridor and dates.
Can we run a programme only in peak season?
Yes. Many corridors are seasonal; a series for peak weeks with on-demand the rest of the year is a common pattern to evaluate.
What should we prepare before asking?
Corridor, typical days and times, passenger and baggage numbers, season, landing sites you already use, and your KPIs.
Conclusion
Let your data decide. Stable, predictable corridors are candidates for a planned series; everything else usually fits on-demand requests with a standard brief. Plan in phases, measure, and remember that every flight is checked on its own.
Planning this flight?
SkyMatch is an independent broker. Every request is reviewed by our team before any operator is approached.
Measure door-to-door time, mission fit, cancellations, schedule adherence and total cost with a before/after KPI template built from your own records.
Use your existing travel and request records to build a baseline, spot recurring corridors and seasonality, and see where a helicopter request is worth checking.
How to plan a helicopter charter for an investor roadshow or multi-meeting executive day: timings, landing sites, passengers, confidentiality and what to send for a tailored plan.
Plan helicopter missions for remote sites, infrastructure, crews and equipment with a requirements template, weighted priorities and a data checklist from your records.
Before adding a new region or destination, check landing sites, permissions, weather patterns and local aviation capability. A step-by-step checklist with scoring.
A 300-mile helicopter flight usually means about 2 to 2.5 hours in the air at typical cruise speeds, plus any fuel stop and weather routing. Estimate yours, then request a plan.