Prepare
Review the route, source documents, fuel picture and operational setup before departure.
Vortiq Studios product
Vortiq EFB is built around one clear idea: an EFB should feel like one product, not a collection of disconnected pages. It brings briefing, weather, route context, source documents, performance and cockpit support into a single environment designed for a full flight from preparation to post-flight review.
Workflow
Review the route, source documents, fuel picture and operational setup before departure.
Keep weather, dispatch context, runway inputs and planning references in one place.
Use overview, route awareness, ACARS and cockpit support without leaving the product.
Close the flight with post-flight continuity instead of an abrupt stop.
Systems
Overview
The overview page brings live status, sync state, key timings, route context, airport data and weight-and-fuel figures into one operating surface. It is built to answer the questions pilots check most often during a session, and it can also show live VATSIM tracking when enabled.
Briefing
The briefing page turns SimBrief release data into a more readable preflight review, with dedicated sections for flight summary, fuel, weather, route, alternates and airport-specific NOTAM notes. The goal is to reduce scrolling through raw dispatch text and make the important items easier to brief.
Weather
Departure, arrival, alternate and manually searched airport weather are kept in one place, with METAR, TAF and ATIS source handling built around operational use rather than raw text alone. Wind, visibility and pressure details are formatted in a way that is easier to scan quickly during planning and arrival review.
Map
The map page keeps route structure, airport positions and waypoint order visible without leaving the EFB. Pilots can review the route visually, inspect selected waypoints and combine the map with optional live VATSIM aircraft tracking for better situational awareness during the flight.
Performance highlight
These pages go far beyond a basic form with generic output. The performance system is built around structured reference tables, runway-condition logic, wind and slope adjustments, brake-energy limits, obstacle and climb limits, dispatch padding and crosswind penalties.
For the Airbus A320 alone, Vortiq EFB includes a detailed takeoff speed table across 46 weight points, with flap-dependent V1, VR and V2 references as well as altitude-based minimum speed triplets. On the landing side, the logic goes further still with engine-specific reference data, runway-condition tiers from dry through poor braking, flap options, autobrake levels, reverse-thrust credit and adjustments for weight, altitude, temperature, wind and slope.
In practice, that gives the performance pages far more depth than a typical simulator calculator. They are positioned much closer to an FCOM-style reference workflow, which is exactly why performance deserves to stand as one of the headline features of Vortiq EFB.
ACARS
The ACARS page is built as an operational console rather than a decorative extra. It includes session setup for callsign, company and stand, link checks and polling control, Hoppie logon support and a structured inbox and outbox for message traffic during the flight.
That matters because it keeps the EFB useful after preflight. Quick-action messages, loadsheet uplinks, takeoff-performance requests, arrival information, free-text company traffic and saved message history all help the product feel active while the flight is actually happening.
Supporting modules
Alongside the screens shown here, the product also includes a dedicated Settings page for SimBrief sync, display units, VATSIM tracking, nav log reminders and Hoppie setup.
OFP
The OFP page presents the full flight plan document with native PDF rendering, caching and annotation support. That makes it practical to use as an active reference during the flight instead of treating the release as something to open once and forget.
Nav log
The nav log page follows the route waypoint by waypoint with planned times, estimated times, actual overflight entries and fuel checkpoints. It keeps timing and fuel monitoring connected directly to the imported flight plan instead of splitting them into a separate tool.
Takeoff
The takeoff page combines runway data, METAR import, aircraft configuration, runway condition logic, stored runway presets and reference-table performance outputs in one workflow. V-speeds, thrust mode, stop margin, limit status and advisory notes are all generated in a way that gives this page real depth.
Landing
The landing page is built for arrival planning with runway condition, wind, slope, braking setup, reverse-thrust use and landing weight all factored into the result. It produces distance, margin, VREF and VAPP context, recommended braking and warning logic that makes runway changes easier to assess.
Loadsheet
The loadsheet page brings payload, ZFW, taxi fuel, trip fuel, reserve and extra fuel into one workspace with synced, edited and computed values clearly separated. It also tracks structural margins and status so pilots can review the numbers before using the performance pages.
ACARS
ACARS handles operational traffic with quick messages, loadsheet exchange, polling, link checks, free-text company traffic and inbox or outbox history. It is designed to feel like a working communications page rather than a simple message viewer.
Checklist
The checklist page includes briefing lists, Airbus and Boeing normal flows and custom checklist creation. Saved completion state gives it more continuity than a static list and makes it useful for both quick sessions and longer procedures.
Scratchpad
The scratchpad is designed for fast operational note-taking, with templates for ATIS, clearance, taxi, approach and turnaround notes as well as a blank page for freehand writing or sketches. That makes it useful for the messy moments that are hard to cover with fixed fields alone.
Logbook
The logbook page gives the product a proper end point by storing completed flights with route, aircraft, timing and notes. It turns post-flight review into part of the workflow instead of leaving the session without a usable record.
Support
The Support page works as an in-app help center, not just a placeholder screen. It guides users through getting started, flight data, performance pages, operations tools, common actions, troubleshooting and best-practice workflow. That makes the app easier to understand for first-time users and easier to stay productive with over time.
Technical foundation
A compact view of the underlying stack, current data coverage and performance-model depth behind the product.
Live dataset figures verified on April 21, 2026.
Integrations
7 external servicesSimBrief, VATSIM, AviationWeather.gov, IVAO ATIS, SayIntentions, Hoppie and OurAirports.
Airport dataset
85,202 airportsLive airport reference connected to the runway and weather workflow.
Runway coverage
72,303 runway endsDrawn from 47,794 runway surfaces, filtered into 38,000 usable surfaces across 30,806 airports.
Aircraft support
31 aircraft variantsAcross Airbus A320-family narrowbodies, Airbus widebodies, Boeing 737 and Boeing 777 variants.
Takeoff model
900 speed references + 120 runway-distance anchorsBuilt from aircraft-specific tables and FCOM reference logic to produce more consistent takeoff outputs than a lightweight generic calculator.
Landing model
213 landing reference casesBased on braking, runway-condition and aircraft-specific landing tables, with FCOM reference logic behind the arrival planning workflow.
Native stack
MapKit, PDFKit, PencilKitNative route display, OFP rendering and scratchpad input for the core experience.
Operational tools
25 built-in checklist templatesBuilt-in briefing, Airbus and Boeing flows, plus support for custom checklist creation.
Community
Development updates, previews, support and discussion are shared through the Vortiq Discord community.