APEX-DCS by Borin

APEX-DCS by Borin V66

  • A AAR & Airfield Data
  • P Performance (Takeoff & Landing / TOLD)
  • E Environment & Route Mapping
  • X Exchange (DTC Import & Integration)
Welcome

My next flights

All upcoming flights

Administration

Choose a flight day to open the booking and the route planner.

Weather

Reads the DCS server file (map, date, QNH, OAT, winds, clouds). The fields below are filled in; you can still change them.

QNH as set in the mission editor. For the takeoff and landing calculations and the QNH on the MDC and the strips every field gets the value corrected for the DCS altimeter error: QNH + elevation/1000 ft × (0.030 + 0.00117 × (T − 15)).

Wind
Altitude (ft)from (°)Speed

Wind direction accepts 0 to 360 only. The 1640 ft wind is not entered: DCS sets it to twice the ground wind speed.

Departure airfield & takeoff
Departure briefing

Arrival airfield & landing
Arrival briefing

Weather is the same as at the departure field.

Loadout
Station list
%

%

Fuel planning
Navigation

Route

Import and export

The A-10C has no DTC. Its mission-editor route presets (Lua, "presets = { … }") can be imported here; the export writes the current route as a preset into the imported file (or a new file) so it can be copied back into the DCS folder.

CombatFlite-Import reads the Lua file of one flight from CombatFlite: the turning points (position, altitude, speed), the departure and arrival airfield, the aircraft type and the callsign. The map is detected from the positions; if that fails, choose the map in the list and import again.

Mouse wheel or pinch to zoom, drag to move.

The DTC import takes, for the F/A-18C, the waypoints of routes R1, R2 and R3 (sorted by waypoint number), their speeds and altitudes, and the time of the first waypoint, and lists the radio presets. For the AH-64D BLK.II it takes the route of Mission 1 (first enabled route with waypoints) and the radios of Preset 1.

The route starts at the departure airfield and ends at the arrival airfield. Waypoints in between can be moved with the arrows. The time of the first waypoint is entered in its ETA cell.

Import Geo-Daten: a list with one point per line: name, latitude, longitude (decimal degrees, comma or semicolon separated). Points are kept per map.

#PointLeg (NM)Heading (M)WCAAlt (ft)Speed (kt)MachETANavaidPosition

Altitude and speed can be edited. An empty field takes the value of the previous waypoint (grey). The position can be overwritten: type coordinates (DD, DDM, DMS, MGRS) or the name of an intersection, navaid or airfield, for example XIBEL; + inserts a waypoint after the row. Mach uses true airspeed and the ISA temperature at the altitude. The ETA of each leg uses the speed of the waypoint it flies to.

Tanker advice

Altitude profile

Takeoff Conditions

Takeoff Data

Loadout

Climb speed schedule
Alt (1000 ft)KCASMach
Drag index by Mach
MachDrag index

Fuel

Climb, cruise and descent use the DCS flight-test data.

Landing Conditions

Landing Data

Calculation steps
Notes on the Excel file (please check)

Status: Planning_Tool_4.xlsx of 24 Oct 2026. Points you have closed are no longer listed.

  • Navigation data. Grey points, MOA / training areas and procedures come from Points-NV/PG/CA/CNMI and navpunkte_Deutschland.json, Airports.json and Latn_und_R2508.geo.json. Not found in the point files (procedure points skipped): TIMBR (KLSV), JOTNU and NAVHO (KLAS), EED (KIFP). GermanyCW, Persian Gulf, Syria and Afghanistan have no procedures yet. Navaids come from the beacons.lua files of all seven maps (Anapa VORTAC: wrong positionGeo in the file, the DCS position is used).
  • Magnetic variation (please check). The values per map are my estimates (east positive): Caucasus +6.0, Syria +4.5, Persian Gulf +2.5, NTTR +12.0, GermanyCW +1.0, Mariana Islands +1.0, Afghanistan +2.0. You can overwrite them in the Mission panel; your value is kept per map.
  • Runway headings. The runway headings are treated as magnetic 2026 and converted with the 2026 variation (switch in Navigation). The bearing between the two end coordinates of a runway equals the heading of the sheet, which looks like true north. Please check once; the switch "true" turns the conversion off.
  • C-101EB. The refusal chart covers only 4000 to 7500 ft of runway; both c101ground run names point to BX5; the total weight does not change with the crew (only the CG chart does). Climb, cruise, descent and the fuel constants (taxi, bingo, joker) are estimates.
  • Carrier CASE. CASE I: day, ceiling 3000 ft or more, visibility 5 NM or more. CASE II: day, ceiling 1000 ft or more. CASE III: night, or ceiling below 1000 ft, or visibility below 5 NM. Day = sun above the horizon at the ETA.
  • F/A-18C fuel. Takeoff, climb and cruise use the sheet "FA-18C - Fuel". Descent = climb calculation halved. The distance flown in climb and descent is not credited to the route (assumption), the weight falls with the fuel burned.
  • Measured F/A-18C fuel (test). In Route & fuel the model "Measured DCS data (test)" replaces climb, cruise and descent by your recordings (tools/f18src): cruise at about 355 kt TAS from 500 to 40000 ft, CRT climb, idle descent, FFW x 2 (per engine). Fuel scales with weight (from the AGM test, stores and weight not separable) and with the sea-level temperature (20 and 40 C). Takeoff stays from the sheet. Only one weight pair, one descent and no other speeds were recorded.
  • Weights. A-10C empty 25,629 lb, F/A-18C empty 25,223 lb (read from the sheet). The F/A-18C default loadout carries the PYLON item on the four wing stations (2, 3, 7, 8 of the tool, 311 lb each); you named stations 3, 4, 7, 8, please check the numbering. The pylon weight of the game weapons is included in their game weight.
  • Climb speed schedule. The sheet takes the Mach column of the schedule from the upper drag-index column (FT22 = GC22) while KCAS is interpolated (FS22 = FO22). The tool interpolates both; the Mach values can therefore differ by a few hundredths from the sheet.
  • Helicopters, JTAC, ATC. UH-1H and AH-64D BLK.II can be reserved, a route can be planned, and the loadout (stores per station, weights from the sheet Ordnance) is shown on the pictures; there are no takeoff or landing tables yet. JTAC and ATC are reservation types without aircraft calculation.
  • Station pictures. Every loadout shows the aircraft from behind or from the front (switch above the picture); click a station marker to change the store there. The UH-1H station side (stations 1 to 3 on the left, as seen from behind) follows the order of the columns in your sheet, please check it.
  • Loadout and route lists. In the station picture the store list has a search field: type letters (several words allowed) to narrow the list. "Symmetric loading" copies stations 1 to the middle to the opposite stations (a store that does not exist there becomes empty). The coordinates of the waypoint list can be shown as DDM, DMS, DD or MGRS with 6 or 10 digits. The border of the DCS map is the dashed orange line.
  • Germany areas. The restricted areas (ED-R) and the danger areas (EDD, LFA, ATZ, laser areas) of GermanyCW are areas you can reserve, like the training areas on other maps; hover shows the base and top. The control zones (CTR) are background only, with their own colour, and cannot be reserved. Outlines are the floor outline of each volume, slightly simplified.
  • Carrier departure and recovery. With a carrier as departure or arrival, the procedure list offers CASE I, II and III (CV NATOPS standard). CASE III departure: radial to the rendezvous; CASE II and III recovery: marshal radial and angels. Both radials are suggested (toward the next waypoint; closest to the direction you come from) and can be overwritten. The allowed ranges are my assumption: marshal radial = reciprocal of the final bearing (BRC − 9°) ±30°, departure radial = BRC ±135°. Heights, speeds and the points are in the route table and can be changed.
  • Still open: CG of the new items, carrier wind over deck (the 25 kt ship speed is used only for the carrier position), max S/E gross and recovery weight, ice chart, S/E RoC (A2-3), minimum idle core RPM, ground run wind table of the F/A-18C, C-101 landing data. The Kobuleti coordinates in the airfield list (41.80 N, 41.77 E) are about 9 NM away from the DCS position (41.93 N, 41.88 E).
Briefing

Flights on this day

    Linking with other flights (deconfliction, shared tanker and frequencies, evaluation) follows later.

    Flight log (Tacview import)
    NOTAM

    NOTAMs for the flight day and the map above, in ICAO format. They are shown on the route map and checked against the route (hint only).

      Route check

        The route check looks at the position and the altitude of the legs (not at the times). Once the server version has user accounts, only the administrator will enter NOTAMs; until then this tool is open to everyone.

        Brevity codes library
        Air Tasking Order (ATO)

        Xchange