How to measure service and planning outcomes: door-to-door time, mission fit, cancellations, punctuality and total cost
Measure outcomes the same way before and after any change: define each KPI, take a baseline from your own records, log every trip with the same fields, and compare medians over equal periods. Five KPIs cover most needs: door-to-door time, mission fit, cancellations and changes, schedule adherence and total cost.
- | KPI | Definition | Formula | |---|---|---| | Door-to-door time | From leaving the start point to arriving at the final destination | arrival − departure, median per corridor | | Mission fit | Did the trip meet the brie
- Take the same 3–12 months before the change.
- Use one trip log with fixed columns: trip ID, corridor, planned window, actual departure and arrival, passengers and cargo planned vs actual, brief met (yes/no + why), cancellation or change reason, cost lines.
- Compare equal periods and the same seasons.
Measure outcomes the same way before and after any change: define each KPI, take a baseline from your own records, log every trip with the same fields, and compare medians over equal periods. Five KPIs cover most needs: door-to-door time, mission fit, cancellations and changes, schedule adherence and total cost. Do not expect a set saving; let your data show what changed. Availability, price, permissions, landing sites, aircraft and mission capability are checked for every request. Nothing in this guide is a commitment.
The five KPIs and how to calculate them
| KPI | Definition | Formula |
|---|---|---|
| Door-to-door time | From leaving the start point to arriving at the final destination | arrival − departure, median per corridor |
| Mission fit | Did the trip meet the brief (people, cargo, site, window)? | trips meeting all brief items ÷ all trips |
| Cancellations and changes | Trips cancelled or materially changed | cancelled or changed ÷ planned |
| Schedule adherence | Arrived within the agreed window | on-time trips ÷ completed trips |
| Total cost per trip | All costs, not only the flight | flight + ground + traveller time + rebooking |
Step 1: Build the baseline
Take the same 3–12 months before the change. Use the travel-history method for door-to-door times. Record cancellations and their reasons: weather, client change, availability, internal decision. Keep the reason; it shows what was controllable.
Step 2: Log every trip the same way
Use one trip log with fixed columns: trip ID, corridor, planned window, actual departure and arrival, passengers and cargo planned vs actual, brief met (yes/no + why), cancellation or change reason, cost lines. Fill it within 48 hours of each trip while details are fresh.
Step 3: Compare fairly
- Compare equal periods and the same seasons.
- Use medians and the slowest 10%, not averages.
- Separate weather cancellations from others; weather is not a service failure.
- Count small samples honestly: fewer than about 10 trips per corridor gives a direction, not a proof.
Hypothetical before/after example
Assumptions (invented, for illustration only): one corridor, 20 trips before and 20 trips after.
| KPI | Before | After |
|---|---|---|
| Median door-to-door | 3 h 40 min | 1 h 50 min |
| Schedule adherence | 14/20 = 70% | 17/20 = 85% |
| Changes or cancellations | 3/20 | 4/20 (2 weather) |
Reading it: time and punctuality improved; cancellations rose slightly, half because of weather. Total cost per trip must be compared with real invoices, not estimates.
Total cost without guesswork
Total cost per trip = flight invoice + ground transport + accommodation changes + rebooking fees + traveller time cost. Traveller time cost = hours × travellers × your internal hourly value; agree that value with finance before you start. SkyMatch does not publish prices; use actual quotes and invoices only.
What to do when data is missing
- No baseline times: collect four to six weeks of ground trips before changing anything.
- No cost lines: start the log now; do not back-fill with estimates.
- No cancellation reasons: add a required reason field from today.
KPI template (copy into a spreadsheet)
| Field | Example entry |
|---|---|
| Trip ID | 2026-11-03-A |
| Corridor | Head office – plant |
| Planned window | 08:00–08:30 |
| Actual departure / arrival | 07:05 / 08:20 |
| Passengers planned / actual | 4 / 4 |
| Brief met | Yes |
| Change or cancellation reason | — |
| Cost lines | from invoices |
Checklist: outcome measurement
- KPI definitions agreed
- Baseline period chosen and recorded
- One trip log with fixed fields
- Reasons for every change or cancellation
- Internal hourly value agreed with finance
- Review every quarter with medians and the slowest 10%
Next step
Share your KPIs when you send a request; SkyMatch reviews each request and arranges the flight where it is feasible. Estimate time differences in the time-savings calculator, then replace estimates with logged trips.
Sources
- EASA — Air operations regulations
- Aviation Weather Center (NOAA) (to record weather-related changes consistently)
Guide: helicopter landing permission and approved sites →
FAQ
Which KPI matters most?
Usually door-to-door time and schedule adherence for executives, and mission fit for B2B missions. Choose before you start, not after.
Should weather cancellations count against the service?
Record them, but report them separately. Weather decisions are part of safe flying.
How many trips do I need before drawing conclusions?
There is no fixed number; with fewer than about ten trips per corridor, treat results as a direction only.
Can I use estimates for total cost?
Only for planning. For outcome measurement use actual quotes and invoices.
Will SkyMatch guarantee a KPI result?
No. Results depend on availability, weather, permissions, landing sites and each request. Measurement shows what actually happened.
Conclusion
Define five KPIs, take an honest baseline, log every trip the same way and compare equal periods. That turns opinions about travel into evidence, without promising any result in advance.
Planning this flight?
SkyMatch is an independent broker. Every request is reviewed by our team before any operator is approached.
Decide between a planned recurring helicopter programme and on-demand requests using your own trip data, a simple break-even style test and clear KPIs.
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.