Touch & Win Creator allows eligible SimFly users to create, configure, schedule and publish their own precision-landing competitions for the community.
As a Creator, you define the mission identity, route requirements, aircraft, runways, scoring geometry, schedule, Entry Fee and Creator Economy settings available through the Mission Builder. Missions do not all have to follow the same style: they can be simple, technical, unusual, highly competitive or deliberately challenging.
The important point is that the information shown to pilots must accurately describe the challenge, public content must comply with SimFly rules, and the Creator feature must not be used for fraud, abuse or deliberate exploitation of platform errors.
Who Can Create a Touch & Win Mission? #
An active Premium Membership is required to create a new Touch & Win Draft and to publish a mission.
If a Premium Membership expires after a Draft has already been created, the Draft is not lost. It can still be opened, edited and saved, but an active Premium Membershiap is required again before publication.
Important
Premium is a requirement for the Creator. In the current user-created workflow, Allowed membership is shown as All, so the mission can be open to the wider SimFly community according to the current platform rules.
Creator Workspace and Limits #
The Touch & Win Submissions page is the main workspace for creating and managing your missions. From here you can create a mission, reopen Drafts, review published missions, search, filter by status and open individual mission pages.
The workspace also displays the Creator limits currently applied by the Brain. The current reference values are:
| Limit | Current reference value |
|---|---|
| Open Drafts per Creator | 5 |
| Published / Scheduled missions per Creator | 1 |
| Concurrent user-created missions across the platform | 5 |
These values are configurable. The limits displayed directly by SimFly are always the authoritative current values.
A Scheduled or Active mission occupies the Creator’s Published slot until the mission lifecycle releases it. The Draft limit is separate, so you may continue preparing Drafts while another mission is already published, provided you still have Draft capacity.
Mission lifecycle: Draft → Scheduled → Active → Ended → Payout Pending → Paid. A mission may also become Cancelled when cancellation is permitted.
Mission Builder and Mission Identity #
The Mission Builder is organized into five main steps:
- Mission — Identity & aircraft
- Requirements — Weight & route
- Runways — Thresholds & scoring
- Schedule — Dates & economy
- Review — Final checks & publish
You can save your Draft and return later. Review Mission is the Creator’s final verification step; it is not a normal manual approval queue.
Mission Name
The public name of the competition. The current interface allows up to 80 characters. Use a clear, recognizable name connected to the airport, challenge or theme.
Public Description
The public explanation of the challenge. The current interface allows up to 800 characters. Use it to explain the idea, difficulty or special characteristics of the mission without repeating technical information that is already shown automatically by the platform.
Entry PAX
The Entry Fee charged for a paid participation according to the normal Touch & Win participation workflow. Entry PAX contribute to the mission economy and prize pool.
Allowed Membership
For the current user-created workflow this is shown as All.
Mission Origin
Automatically set to User-created.
Allowed Airplane
In the current Creator version, one airplane can be selected per mission. The Analyzer still validates the aircraft actually used by the pilot.
Challenge Image / Runway Challenge Cover
Every user-created mission requires a public Challenge Image. The current UI accepts WEBP or JPG/JPEG and shows a maximum image size of 1672 × 940 pixels. A 16:9 image, for example around 1600 × 900 px, is recommended for a clean presentation.
Separate images for Runway #1 and Runway #2 are not required. Runway visualization is generated from the interactive runway configuration.
Public Content and Image Rules #
The Creator is responsible for the images, text, names, logos and other public material associated with the mission. Only use content you own, content you are authorized to use, or material covered by a licence that permits its use. An image being available on the internet does not automatically mean that it is free to reuse.
Content is not allowed if it includes, promotes or contains:
- pornographic, sexually explicit or sexually exploitative material;
- content involving or sexualizing minors;
- hate, racism, discrimination, extremist or terrorist propaganda;
- graphic gore, credible threats, harassment or intimidation;
- illegal, fraudulent or deliberately deceptive content;
- copyright, trademark, privacy or other third-party rights violations;
- unauthorized private or personal information;
- impersonation of SimFly, another User, an airline, company or organization;
- false claims that a user-created mission is an official or sponsored SimFly event;
- phishing, malware, spam or malicious links.
A mission being difficult, easy, unusual or highly creative is not a violation by itself. Creative freedom is an intentional part of Touch & Win Creator.
Flight Requirements and Route Rules #
The Requirements step defines the operational conditions of the flight, including landing weight, route rule and the mandatory Arrival ICAO.
Landing Weight
Minimum and maximum landing weight are expressed in kilograms (kg). The minimum value cannot be greater than the maximum value.
Defined Departure
With Departure ICAO, the Creator defines a specific departure airport and a required Arrival ICAO. The pilot must depart from the selected airport and finish at the required arrival airport.
Minimum Distance
With Minimum distance, the Creator does not require one specific departure airport. Instead, a minimum distance in NM is configured while the Arrival ICAO remains mandatory.
Important
The Analyzer measures the actual flown distance. Airport-to-airport distance alone does not guarantee that the requirement has been met. If the actual recorded flight distance is below the configured minimum, the applicable Touch & Win penalty may be applied.
Runway Configuration #
Every user-created Touch & Win mission requires Runway #1. Runway #2 is optional.
A runway configuration such as 06/24 represents both ends of the same physical runway. You do not need to create one configuration for 06 and another for 24.
The Builder intentionally separates physical runway data from Touch & Win scoring geometry. Physical endpoints, physical length and physical width describe the real runway; thresholds, effective coordinates and scoring limits define the challenge.
Scoring Threshold Positions
Threshold A and Threshold B are expressed in feet and move the effective scoring threshold inward from the corresponding physical runway end. The Builder recommends threshold offsets as the main editing method.
Reset thresholds to runway defaults returns both threshold offsets to zero and restores the effective coordinates to the physical runway references currently loaded for that runway.
Effective Scoring Coordinates (Advanced)
A latitude/longitude and B latitude/longitude update automatically when the threshold offsets change. They remain manually editable for advanced adjustments. The UI displays these coordinates with five decimals.
Required Scoring Limits
The current UI labels are:
- Max rollout deviation from centerline (ft)
- Longitudinal zero-score distance (ft)
Both values must be greater than zero. Physical runway width and physical runway length must not be confused with these scoring limits.
Interactive Runway Preview
The map visualizes the physical runway, effective thresholds, centerline, scoring bands and lateral guides. Changing offsets, coordinates or scoring guides redraws the geometry without intentionally resetting the Creator’s current zoom or pan. Use Fit Runway to recenter the runway when needed.
Runway #2 is independent
If Runway #2 is configured, it has its own threshold positions, effective coordinates and scoring limits. The Analyzer uses the values associated with the runway actually selected during flight analysis.
How Touch & Win Scoring Works #
The Builder includes a dynamic Score Guide for the active runway. The tables use the values of the selected runway and correspond to the scoring bands displayed on the map.
In the Scoring V2 contract shown by the Builder:
Total Touch Score = Longitudinal Score + Max Lateral Rollout Score
The separate touchdown Lateral Score may remain visible to the pilot, but it is not added directly to the Total Touch Score.
The map can show the best possible score based on touchdown position, while the real result can fall if the aircraft moves farther from the centerline during rollout.
The Mission Builder is a configuration guide. The official flight result is always calculated by the Analyzer using the actual data recorded during the flight.
Landing on an unconfigured runway
If a pilot reaches the correct destination airport but lands on a physical runway that was not configured for the mission, the Touch & Win participation can remain recorded and visible in the leaderboard, while a 100% Touch & Win score penalty is applied. The final Touch & Win result becomes 0. The normal SimFly flight and its normal XP/PAX handling remain separate from this Touch & Win penalty.
Schedule and Calendar Availability #
Creator mission dates use UTC / Zulu.
- Start Date begins at 00:00:00Z.
- End Date remains active through 23:59:59Z.
- The date range is inclusive.
The current reference duration is 3 to 30 days. These limits are configurable, so the values displayed in the Mission Builder are authoritative.
The current global reference capacity is 5 concurrent user-created missions. Capacity is checked day by day across the entire requested range.
Check Availability does not reserve the dates. It checks the current situation at that moment. The Brain rechecks Creator and global capacity when the mission is actually published.
If even one day in the requested range has reached full capacity, the entire requested range cannot be published.
When possible, SimFly may suggest the first available consecutive range with the same duration. Dates are never changed silently: the Creator chooses whether to use the alternative.
Creator Economy and Prize Distribution #
The Creator Economy explains how Entry PAX are handled for a user-created mission. The applicable values are managed by the Brain and stored in the mission’s economic snapshot at publication.
The main elements are:
- Entry Fee — PAX charged for a paid participation according to the normal mission workflow.
- Live / Gross Pool — Entry PAX generated by paid participations considered by the system.
- Fee Threshold — current reference value: 10 valid paid participations.
- Creator Share — current configurable range: 1%–20%, default 10%.
- Burn — current reference value: 15%.
- Leaderboard Pool — the remaining pool available for winner rewards.
How the fee threshold works
At or below the fee threshold, Creator Share and Burn are not applied. Once the threshold is exceeded, Creator Share and Burn apply to the entire mission pool according to the economic snapshot.
Example
20 paid participations × 5 PAX = 100 PAX Gross Pool.
With Creator Share 10% and Burn 15%:
- Creator Share: 10 PAX
- Burn: 15 PAX
- Leaderboard Pool: 75 PAX
Standard winner distribution
| Position | Standard share |
|---|---|
| 1st | 30% |
| 2nd | 20% |
| 3rd | 15% |
| 4th | 10% |
| 5th | 7% |
| 6th | 5% |
| 7th | 4% |
| 8th | 3% |
| 9th | 3% |
| 10th | 3% |
If fewer eligible winning positions exist, the payout system may normalize the distribution across the actual eligible winners according to the active Touch & Win rules.
Snapshot at publish
The economic settings applicable to the mission are stored when the mission is published. A later change to SimFly’s global default values does not retroactively change the published mission’s economic configuration.
Review and Publish #
The Review step summarizes the mission before publication, including the mission, arrival, route, aircraft, landing weight, runways, dates, economy and expected lifecycle.
Before publication, review all critical values carefully. The current Review workflow also includes confirmations relating to the applicable Terms and to the accuracy of runway coordinates, scoring guides, dates and reward settings.
At Publish, the Brain rechecks the conditions that must still be true at that moment, including Draft completeness, Creator eligibility, mission duration, Creator Share, Creator limits, global capacity, Challenge Image and runway configuration.
If Publish succeeds, the Draft becomes an operational mission and receives the appropriate lifecycle, normally Scheduled when the start date is in the future. If Publish is rejected, the mission remains a Draft so the problem can be corrected.
What Pilots See Before Participating #
The public mission page gives pilots the information needed to decide whether they want to participate before starting the mission and paying the applicable Entry Fee.
Depending on the mission, the public page may show the Creator, Challenge Image, Start and End dates, route, arrival airport, aircraft, Entry Fee, current pool, runway configuration, scoring information, leaderboard and public description.
Public runway maps are read-only and represent the configuration published by the Creator.
Pilot responsibility and Entry Fee
Pilots are responsible for reviewing the mission information before participating. A mission being very difficult, very easy or different from another Touch & Win mission is not, by itself, grounds for an Entry Fee refund.
A refund is not due merely because a pilot did not read the published conditions, changes their mind, does not achieve the desired result, does not win, or later disagrees with a condition that was correctly visible before participation.
Once the pilot starts or attempts to start the mission, the general SimFly rules for Entry Fees, official results, scoring and mission validation also apply.
Cancelling a Published Mission #
A Creator can cancel a published mission only when the platform makes the cancellation action available.
Under the current Creator workflow, normal Creator cancellation requires:
- the mission has not started yet;
- there are no paid PAX participations associated with the mission;
- the system considers the mission cancellable (canCancel = true).
Cancellation is performed from the individual mission page. If the Cancel action is not shown, the Creator can no longer cancel the mission through the normal workflow.
The cancellation action requires explicit confirmation.
After the mission starts, or after a paid PAX participation exists, the Creator cannot cancel it through the normal Creator workflow. SimFly retains separate administrative and moderation powers for technical, safety, integrity or rule-enforcement reasons.
Repeatedly publishing and cancelling missions in order to occupy dates, block platform capacity or disrupt other Creators may result in Creator restrictions.
Leaderboard and Official Results #
The leaderboard is built from results processed by the Analyzer and can display Position, Pilot, Reward, Landing Rate, Landing, G Force, Touch, Wind, Bounce, Penalty and Total.
A final Total of 0 does not automatically mean the participation was deleted. Some Touch & Win penalties keep the participation recorded and visible in the leaderboard while reducing the final competition result to zero.
Understanding the Touch & Win Flight Report #
The Flight Report keeps the normal SimFly flight information and adds Touch & Win-specific analysis.
The report may show Landing Weight, Landing Rate, G-Force, Crosswind, Bounces, detected Runway, recorded touchdown coordinates, distances, Touch Score components, Weighted Score Summary and Log Penalty.
Landing Score and Touch & Win Score are separate views. The normal Landing Score remains part of the flight report, while the Touch & Win Scoring Details explain the result of the competition.
Map, touchdown and rollout
The Landing Score Detail map can also display the Touch & Win overlay together with the actual touchdown data. The map may show the configured scoring geometry, touchdown marker and rollout information, helping the pilot understand where the aircraft landed relative to the Creator’s challenge.
Unconfigured Runway example
If the mission allows runways 06/24 and 14L/32R but the pilot lands on 14R/32L, the report can show the actual detected runway and the related Log Penalty. The Analyzer may still calculate internal Touch components, but the 100% Unconfigured Runway penalty makes the final Touch & Win weighted result 0.
The normal SimFly flight result, XP and PAX handling remain separate from this specific Touch & Win penalty.
Settlement, Paid Status and Creator Share #
The end of a mission does not mean immediate payment.
At least 24 complete hours must first pass from the mission end date and time (endAt). The automatic Touch & Win settlement process runs once per day at:
00:30:00 UTC / Zulu
The mission can be processed during the first 00:30 UTC cycle that occurs after the full 24-hour eligibility period has already passed.
Example
Mission end: 3 September, 23:59:59Z
24 complete hours reached: 4 September, 23:59:59Z
First eligible settlement cycle: 5 September, 00:30:00Z
Settlement therefore does not necessarily happen exactly 24 hours after the mission ends.
The settlement uses the final validated results and the mission’s published economic snapshot. SimFly may delay settlement where technical, anti-fraud, scoring, security, moderation, compliance or maintenance checks are required.
Creator Share in the PAX Wallet
When the mission economy provides a Creator Share, the credited amount appears in the Creator’s PAX Wallet as a transaction identifying the mission and the applicable percentage.
Creating a mission does not guarantee a minimum number of participants, a specific Live Pool or a minimum Creator earning. Values shown before settlement should be considered provisional.
Fair Use, Moderation and Sanctions #
Normal competition, strategy, creative mission design, difficult scoring, unusual airports and experimental configurations are allowed.
The Creator feature must not be used to:
- generate rewards fraudulently;
- artificially manipulate mission results;
- intentionally exploit bugs or unintended platform behaviour for improper benefit;
- deliberately mislead participants about the actual mission conditions;
- repeatedly publish and cancel missions to reserve platform capacity or disrupt other Creators;
- publish prohibited public content.
If the platform permits the Creator to participate in their own mission, that participation is allowed under the normal mission and platform rules.
Where required, SimFly may remove or replace content, prevent publication, suspend or cancel missions, invalidate results, restrict Creator functions, suspend an Account or permanently remove Creator privileges. Serious violations may result in permanent Account termination.
Frequently Asked Questions #
Why can’t I create another Draft?
Check the Open Drafts limit in the Creator Workspace. You may have reached the current limit.
Can I prepare Drafts while I already have a published mission?
Yes, provided you still have available Draft capacity. Draft and Published limits are separate.
Why can’t I publish?
Possible causes include an inactive Premium Membership, Published limit reached, missing required information, invalid Challenge Image or runway configuration, unavailable dates, invalid duration or Creator Share outside the current allowed range.
Does Check Availability reserve my dates?
No. Capacity is reserved only after a successful Publish.
Why can’t I cancel my mission?
Normal Creator cancellation requires canCancel=true, the mission must not have started and there must be no paid PAX participation.
Can I select multiple airplanes?
Not in the current Creator version. One airplane is selected per mission.
Do I need separate images for Runway #1 and Runway #2?
No. Only the general Challenge Image is uploaded. Runways use interactive maps generated from the mission configuration.
Why can a pilot have Total 0 and still remain in the leaderboard?
Some penalties, such as Unconfigured Runway, keep the participation recorded while reducing the final Touch & Win result to zero.
Why was I not paid exactly 24 hours after the mission ended?
After the full 24 hours have passed, the mission waits for the first eligible automatic settlement cycle at 00:30 UTC.
Final Checklist Before Publish #
- Mission Name and Public Description are correct.
- Challenge Image is valid and you have the right to use it.
- Entry PAX is correct.
- Allowed Airplane is correct.
- Minimum and Maximum Landing Weight are correct.
- Route Rule, Departure / Minimum Distance and Arrival ICAO are correct.
- Runway #1 is fully configured.
- Runway #2 is correct if used.
- Threshold A/B and Effective Scoring Coordinates are correct.
- Scoring limits and runway maps have been reviewed.
- Start and End dates are correct in Zulu.
- Mission duration is valid.
- Check Availability has been completed.
- The requested date range is still available.
- Creator Share, Fee Threshold, Burn and Leaderboard Pool are understood.
- The Review summary matches the mission you intend to publish.
When all information is correct, you can proceed with Publish Mission.
Related Pages #
- Touch & Win
- Flight Analysis & Score
- Landing Details
- PAX Tokens
- PAX Wallet
- SimFly Terms and Conditions
Important
This page explains the practical Touch & Win Creator workflow. When a limit, economic value or availability rule is configurable, the value currently displayed by the SimFly platform is the authoritative value.
