Strike Fighter League · Document Control
Every framework document moves to v2.0 together: the Charter, Appendix A, Appendix B and the four SPINS. The set carries every change made between OTS-2 and OTS-3. The largest are below.
Charter & Appendices — one combined competitor reference
Foundational Document
Appendix A
Appendix B
Each Trial's 0–100 display score is pinned by two anchors, and neither is a guess. The 100-point anchor is a measured perfect run: flown, recorded, and extracted from flight data, plus a small pad for competition realities — PRECISION's includes the measured, unavoidable time above the altitude cap in the attack pops; ACCURACY's includes a 10-rounds-per-kill gun standard. The zero-point anchor is a ruled span below it. 100 sits at our assessed physical limit — a score above it is treated as exceptional and draws an automatic review of the run's scoring.
The spans were set through a purpose-built scoring simulation: the canonical scoring formulas, seeded with the measured baseline flights, generating more than 30,000 simulated runs per candidate clamp value and re-tested with every field assumption pushed both tighter and sloppier than expected, so the selected values had to hold everywhere, not under one guess. Those values converge the three Trials' score spread at sigma 0.65 / 0.67 / 0.70 (SPEED / PRECISION / ACCURACY) — near-identical, so each Trial carries equal weight in the Total Trials Score — and the imbalance they corrected was visible in the measured spread of the OTS-2 qualification submissions. Clamp values are re-tuned only between competition windows; every change is versioned, published, and recorded in the Release History.
Special Instructions — the per-event competitor brief. Fly what's published here.
Trial 1
Trial 2
Trial 3
Dogfight Phase
Every published change to the competition framework, newest first
Every framework document moves to v2.0 together: the Charter, Appendix A, Appendix B and the four SPINS. The set carries every change made between OTS-2 and OTS-3. The largest are below. One path for every pilot. Register once at pilots.the-sfl.com, enter each OTS from your pilot account, and fly one scheduled qualification run per Trial on SFL servers. The top eight compete in the Dogfight Phase. Each Trial produces a 0–100 display score, and the Total Trials Score is the sum of the three. The anchors behind each scale were set from measured flight data and tested across more than 30,000 simulated runs per value. SPEED and PRECISION are timed from the Start Gate. Each set is won on UIS, and winning two of the three sets wins the matchup. A tied set is decided inside that set. The SFL Virtual Pilot Kit (VPK) is required to fly on SFL servers and carries the broadcast webcam feed during live OTS events. The UCID-Verify Tool links your DCS account once, when you register. Appendix B states what the VPK collects, when it collects it, and how long SFL keeps each kind of data. Competition-integrity data never goes into any dataset SFL licenses. RULED by Trailer (AC2), 2026-09-18.
The DOGFIGHT SPINS state the matchup the way Appendix A v1.4 § A.4 scores it: the higher UIS wins each set, the pilot who wins two of the three sets wins the matchup, and the four tie-breakers apply within the set, with a set still tied after all four re-flown. The TechAdmin pane points at Appendix B without a pinned version and lists § B.2 in the TechAdmin standard form. RULED by Trailer (AC2), 2026-09-28; the rest of the DOGFIGHT text stays with the pre-December BFM pass.
Appendix B § B.5.2 states the SFL Virtual Pilot Kit (VPK) collection scope — DCS mods, DCS telemetry, and DCS state, all competition-integrity data, never for marketing, never licensed — with its two boundaries: the broadcast webcam feed streams only during live OTS broadcast events under the face-camera consent, and control inputs are read by the integrity check as integrity data and never recorded as licensable competition data unless a later version of the Pilot Data Royalties Rider offers it as its own switch. It sets out when the kit collects (install, session start, during a run, run end, verification) and how long SFL keeps each kind of data. The Charter § 6.2.4 points retention of the authoritative record to the SFL Privacy Notice, and § 6.5 makes on-camera engagement a condition of the live bracket, under the face-camera consent signed at qualification. Per the League’s legal rulings of 22 SEP 2026; RULED by Trailer (AC2), 2026-09-28. Closes the last open tech-round item in § B.5.2.
Appendix B § B.5.2 states what a Competitor needs to run the SFL Virtual Pilot Kit (VPK) — Windows 10 or 11, DCS World installed and signed in at least once, the League’s DCS version standard (§ B.4.2), and a webcam for the broadcast function during live OTS broadcast events; VR and standard displays both supported; no administrator elevation — how it installs and updates (SFL-VirtualPilotKit-Setup-<callsign> to C:\SFL\PilotKit, same path every time, staged zip if blocked, removal from Settings → Apps), and the support route (install and launch logs sent to SFL, Ctrl+Alt+Shift+K to stop, sfl-kitc doctor to check the rig, CLASSIC on the event voice channel during live execution). Facts taken from the shipping kit. RULED by Trailer (AC2), 2026-09-18. Three of the four open § B.5.2 tech-round items close; data-collection timing and retention remains with the legal cell.
The SPEED TechAdmin pane carries the standard form (the DOGFIGHT SPINS TechAdmin form is the standard for all four events): SFL Charter Appendix B — TechAdmin SOP as the authoritative source, mandatory in its entirety, § B.7 as the Trial-specific reference, and a Relevant SOP Sections list citing Appendix B’s sections by number and title. The TacAdmin pane follows the FENCT standard — Fires / Expendables / Navigation / Comm / Threats — with Navigation leading with Nevada Test & Training Range (NTTR) and Comm stating None (SPEED has no automated in-mission calls). The scoring pane’s Cleared Gate Definition moves off the red penalty-callout to the standard tech-block treatment, its text set to the ruled wording (RULED by Trailer, AC2, 2026-09-07). Pane restructure and wording only — no scoring, constant, or execution change.
The ACCURACY TechAdmin pane carries the standard form (the DOGFIGHT SPINS TechAdmin form is the standard for all four events): SFL Charter Appendix B — TechAdmin SOP as the authoritative source, mandatory in its entirety, § B.7 as the Trial-specific reference, and a Relevant SOP Sections list citing Appendix B’s sections by number and title. The TacAdmin pane follows the FENCT standard — Fires / Expendables / Navigation / Comm / Threats — with Navigation leading with Nevada Test & Training Range (NTTR) and Comm stating None (ACCURACY has no automated in-mission calls). Pane restructure only — no scoring, constant, or execution change.
Appendix A § A.1/§ A.2 are framed around the two tournament phases — the Trials Phase (three Trials, aggregated into the Trials Ranking) and the Dogfight Phase (the live head-to-head bracket) — with new § A.2.4 stating advancement: the top eight advance and seed the bracket. § A.4 scores the Dogfight per set: the higher UIS wins the set; the match winner wins the majority of three sets (best two of three). § A.4.4 (Set Tie Resolution) decides a drawn set by the four-step tie-break cascade within that set, terminal step a sudden-death re-fly of the set. Executes CF-05 (BFM set format) — RULED by Trailer (AC2), 2026-08-22; drawn-set disposition ruled 2026-09-07.
Appendix B § B.2 defines the competitor path — register / enter / qualify / compete — across the Trials Phase (SPEED · PRECISION · ACCURACY) and the Dogfight Phase (the live eight-competitor bracket): register once, ever, at the SFL pilot portal; enter once per cycle; qualify by flying scheduled qualification runs on SFL servers during the published qualification window, one official run per Trial. Account verification (§ B.2.3) confirms identity via email, Discord, and DCS UCID through the UCID-Verify Tool downloaded from the pilot portal. The SFL Virtual Pilot Kit (§ B.5.2) is required to fly on SFL servers — event execution, event integrity, network baseline, and broadcast — with its collection scope stated. § B.7 states the Trials Execution Standard; § B.9.1 sets first-come, first-served qualification-slot scheduling; § B.9.2 scopes live-event timing to the OTS event.
Charter § 6.2 (Qualification Process) states the qualification standard: Competitors qualify by flying scheduled qualification runs on SFL servers during the published qualification window — one run per Trial, which stands as the official score for that Trial — and the SFL server-recorded ACMI is the authoritative record of performance (§ 6.2.4), with capture and handling standards in Appendix B. § 3.3.3 publishes the DOGFIGHT bracket re-seed standard: after each round the remaining Competitors are re-paired by seed, highest remaining versus lowest remaining — pairings by seed, not fixed bracket lines. § 6.2.7 Returning Competitors: the League may pull a Competitor from the immediately preceding OTS forward at its sole discretion; a pulled-forward Competitor is exempt from qualification but still enters the cycle, selecting their aircraft and executing the required League paperwork at entry.
Target assignment runs fully automated on SFL servers: clearing a target set’s Pull-Up Point (PuP) gate triggers that set’s assignment call — an audio callout with matching on-screen text, “Visual, hit the [N / E / S / W] [Atk Boat | BTR-60 | BMP-2]” — and the callout and the scorer consume the same assignment. Run timing is published as flown: the course clock runs from Start-Gate crossing on the KLSV 03R takeoff roll to the finish-gate crossing (no scored value changes — the scorer has always run the course clock from the Start Gate). The overview names each target set’s actual targets, and the TechAdmin pane cites the TechAdmin SOP (Appendix B) directly — pane text only; no change to the course, scoring formula, or constants.
The Accuracy Display Score panel states the clamp convention — floor at 0, ceiling open, with a score above 100 triggering an automatic scoring review because ABEST sits at the measured physical limit (anchors unchanged: ABEST 85.19 s = 100, AZERO 335.19 s = 0). The overview publishes target activation: all three targets spawn and enter their orbits at Start-gate crossing, and the target areas are empty until then. Brief corrections — the SPLASHED subject (the target, not the aircraft), the Saved Rounds Bonus award condition (all three targets splashed), Missed Targets wording — are pane text only; no constant, formula, or scored value changes.
Run timing is published as flown: the course clock runs from Start-Gate crossing on the departure runway centerline — on the takeoff roll or airborne, whichever comes first — to the finish-gate crossing. The Start Gate is not one of the 18 course gates: it cannot be missed and carries no penalty. Total Course Distance is corrected to the course as measured from the Start Gate (35,505.78 → 34,897.38 m; course length 18.8 NM) — no completed run's score changes, since the flown-distance term equals the course distance on a completion. Brief corrections are pane text only; the scoring formula, weights, penalties, and baseline are unchanged.
The PRECISION scoring pane publishes the Precision Display Score normalization — PDS = 100 × (TZERO − Tprec) / (TZERO − T100), with T100 = 340.5 s and TZERO = 1,840.5 s. PRECISION had been the only Trial publishing a raw score with no 0–100 conversion, leaving no published path from a Precision Raw Time to the Total Trials Score. Every term in the raw-time formula now carries its constant, and the MRP/URP wording is corrected from “% × 100” to the ratio the specification defines — a text defect only, no scored value changes.
The normalized-score anchors for PRECISION and ACCURACY are re-anchored to measured perfect-run flight data plus a small pad, sized so all three Trials contribute comparable score spread to the Total Trials Score (PRECISION T100 340.5 s / TZERO 1,840.5 s; ACCURACY ABEST 85.19 s / AZERO 335.19 s; SPEED unchanged; penalty values untouched). Appendix A now publishes the aggregation method as flown: Total Trials Score = the sum of the three normalized display scores — the placement-points table is retired.
The overshoot defeat-precedence rule is corrected to one-sided suppression: only a defeat that would credit within 1.0 s after a credited overshoot is suppressed — the overshoot maneuver itself never also pays a defeat. A defeat credited before the overshoot stands, because defeating the gun employment and forcing the flush that follows are two separate defensive achievements. No scorer change — the scorer has always applied the one-sided rule; the earlier “±1.0 s” spec/SPINS wording was the error.
A Forced Overshoot is now credited only to a competitor reversing out of a defensive state — the crediting competitor must have been on Defense within 10 s before the earlier of the two role-reversal crossings; an overshoot cannot be forced from Neutral. The scorer's overshoot detector was rebuilt to anchor on the two published angle-off-nose crossings (scorer v13.31), with hold, cooldown, and defeat-precedence unchanged.
The DOGFIGHT scoring pane now publishes the complete Forced-Overshoot detection — the two angle-off-nose crossings that define a role reversal, the timing window between them, the ≥ 0.50 s hold, cooldown, and defeat-precedence — matching the full-detail treatment of every other term (it was award-level only before). In the same pass the pairing window between the two crossings was widened (0.60 s → 1.5 s, scoring spec BFM v1.8) so a slower, wider flush still scores; award (+15 s), hold, and cooldown unchanged.
Pursuit now requires 8 continuous seconds of chase geometry before it credits or activates scoring, up from 5. At 5 seconds the gate was firing on ordinary post-merge extensions — a fought set that separated for ~15–20 seconds could hand the chaser a set-dominating Pursuit Time that had nothing to do with running the clock. Eight seconds filters normal extensions and reattacks while still punishing a genuine one-sided run, which lasts far longer. Chase cones, the 5.0 kft range gate, and the 3.0 s-per-second rate are unchanged.
Scoring now activates the instant a competitor holds pursuit geometry for 5 continuous seconds — Fight’s On triggers and Pursuit Time accrues right then, instead of waiting for the 20-second Merge Window. A runner no longer gets an unpenalized head start; the Merge Window now governs only mutual refusal (0-0 and stands).
The DOGFIGHT scoring pane now publishes the complete Unified Impact Score specification the scorer runs — engagement states, all term definitions, activation and Merge Window logic, Gun Solution and Weapons Defeated detection thresholds, kill handling, tie-breakers, and a constants reference — replacing the earlier simplified subset. Broadcast nicknames removed from the scoring terms; Control Zone floor stated as 800 ft.
Running from the fight is now scored against the runner: a pursuing competitor accrues Pursuit Time while chasing a fleeing opponent, and one-sided running activates scoring at the Merge Window rather than banking a 0-0. Makes refusing to fight strictly losing at any cumulative lead.
Discord replaces SRS as the required voice platform for OTS participation. Live event voice communications run in the SFL Discord event voice channel; the BLACK 01 / YELLOW 02 / BLUE 03 frequency nets are retired.
UIS scoring and the match clock start at Scoring Activation — first closure inside 1.0 NM after "Fight's On." A set with no activation inside the 20-second Merge Window is terminated by CLASSIC and recorded 0-0. Defensive spoil time now credits at half rate (0.5 × TDENY) — offensive pressure out-pays denial.
Dogfight tie resolution restored to the four-step cascade ending in a sudden-death re-fly. Charter § 3.3.4 corrected: set-1 altitude assignment is fixed by seeding — higher seed takes the high fighter.
All four event SPINS republished in the interactive HTML format — the baseline for the current SPEED, PRECISION, and ACCURACY briefs.
Charter and Appendices migrated from PDF to interactive HTML. Competition-framework figures updated; § 6.2.8 Returning Competitors added to the Online Tournament Series qualification process.
One framework. One standard. Where Flight Becomes Sport.