VFR in BeyondATC

VFR (Visual Flight Rules) lets you fly visual operations alongside IFR traffic with full ATC interaction — from startup and taxi through pattern work to landing and parking. BeyondATC models real-world procedures for three regions: the United States, the United Kingdom, and Australia. Other regions are planned for future development.

Work in progress

The wiki page is still a work in progress and may be incomplete. If you have any questions about VFR, please ask in our Discord server.

Experimental feature

This is Stage 1 of BeyondATC's VFR implementation, releasing on the experimental branch. Stage 1 lays the foundation for VFR operations at towered airports — circuits, pattern work, and controlled-zone entry and exit. Future stages will add control-zone transits, uncontrolled airports, VFR flight following, and enroute navigation assistance. As with any experimental release you may encounter bugs or instability — we appreciate your patience and support as we continue to develop and improve this feature.

What's Supported

BeyondATC's stage one VFR release covers controlled airport operations:

VFR departures from gate or ramp parking
Circuit/pattern work with full ATC sequencing
VFR arrivals joining the circuit from outside
Touch-and-go, full stop, low approach, stop and go (US/AU)
Integration with IFR traffic (go-arounds, orbit holds, extend downwind)
Intersection departures for shorter taxi
Regional phraseology and logic for US, UK, and Australia
Flight plan import — MSFS world map, .pln, .lnmpln (Little NavMap), or SimBrief
Callsign shortening for GA aircraft (region specific)
Change circuit intention, runway, or circuit direction mid-flight
Submenu action buttons for faster interaction (VFR)
Report Traffic In Sight when sequenced behind traffic
UK QFE calculation for circuit operations
Airframe name library (880+ aircraft types)

What's Not Supported Yet

These features are planned for future stages:

Uncontrolled airports — no CTAF, UNICOM, or self-announce procedures
VFR flight following — radar advisory service not yet implemented
Control zone transits — entering/exiting CTRs not fully simulated
Enroute VFR assistance — no reporting points or waypoint routing
AI VFR traffic — no AI VFR traffic currently

Regional Differences at a Glance

BeyondATC automatically detects the region from the airport's location and applies the correct phraseology throughout. Here is a summary of the key differences you'll encounter:

Feature	🇺🇸 United States (FAA)	🇬🇧 United Kingdom (CAP 413)	🇦🇺 Australia (AIP)
Startup	Not required — contact Ground directly	Optional — "Startup approved" + QNH	Optional — "Start approved" + QNH
Intentions wording	"Closed traffic" / "traffic pattern"	"Circuits"	"Circuits"
Squawk	1200 (assumed, not stated)	Discrete code assigned on clearance; "squawk conspicuity" on departure	3000 controlled / 1200 uncontrolled
Pressure reference	Altimeter (in. Hg)	QNH (hPa) — QFE can be asked for from ATC	QNH (hPa)
Circuit report point	Midfield downwind	Downwind	Downwind (clearance issued on base turn)
Landing clearance given	At downwind report (direct clearance)	On final	On base turn
Straight-in approach	✅ Available	✅ Available	✅ Available
Full stop landings	✅ Available	✅ Available	✅ Available
Low approaches	✅ Available	✅ Available	✅ Available
Stop and Go	✅ Supported	❌	✅ Supported
"The Option"	✅ Supported	❌	❌
Overhead join	❌	✅ Available	❌

Setting Up Your Flight

Using the MSFS World Map

BeyondATC can automatically import a flight plan you set up in the MSFS world map:

Set your departure and destination airports in the MSFS world map
Load into the sim
Departure and arrival airports are extracted; no SID/STAR procedures are used for VFR

You can also set the same airport as both departure and destination for circuit practice.

Using a .PLN or .LNMPLN File

You can import flight plan files generated by tools like Little NavMap. Select VFR on the BeyondATC main menu and choose the file import option.

Using SimBrief

SimBrief plans can also be loaded. For most VFR flights, you only need to set the departure and destination airports — no routes or procedures required. Make sure you set your flight rules to VFR in SimBrief.

The BeyondATC main menu now has separate IFR and VFR sections. When selecting VFR you choose your import method (MSFS, file, or SimBrief) before loading.

The Complete VFR Flow

The sections below walk through a full VFR departure and pattern flight step by step, with regional differences called out at each stage.

Step 1 – Startup

Where to start: We recommend you spawn at a GA ramp or parking stand.

🇬🇧 United Kingdom & 🇦🇺 Australia

Optional: Contact Ground (or Delivery) to request startup before calling for taxi. ATC will approve startup and pass the QNH.

UK example: "Bristol Ground, G-ABCD, Cessna 172 at Ramp 3, request startup for circuits." ATC: "G-ABCD, startup approved, QNH 1013."

AU example: "Bankstown Ground, VH-ABC, Piper Archer at Ramp 2, request start for circuits." ATC: "VH-ABC, start approved, QNH 1019."

🇺🇸 United States

There is no separate startup step. Contact Ground directly to request taxi (see Step 2). If you attempt a startup call, BeyondATC will redirect you to the Ground frequency.

Step 2 – Request Taxi

Contact Ground and state your intentions — circuits (pattern work) or a VFR departure. BeyondATC requires you to include your intentions in the startup or taxi request. If you don't, ATC will ask you to clarify before issuing taxi instructions.

US example (circuits): "Ground, N123AB, Cessna 172, request taxi for closed traffic."

US example (departure): "Ground, N123AB, Cessna 172, request taxi for VFR departure."

UK example: "Oxford Ground, G-ABCD, Piper PA-28, taxi for circuits."

AU example: "Bankstown Ground, VH-ABC, Piper Archer, request taxi for circuits."

ATC will respond with runway and taxi routing. Follow the assigned route to the hold-short point. BeyondATC will automatically hand you off to Tower when you reach it.

Button users

Clicking "Request Taxi" will expand into a sub-menu where you can select your intention (circuits, departure, or parking on arrival) before transmitting. Voice users can include their intention in the initial call to skip this step.

Step 3 – Intersection Departure (Optional)

If your aircraft's performance allows it, you can request to enter the runway at an intermediate taxiway intersection rather than taxiing to the full threshold.

Two ways to request:

Action button — The "Request Intersection Departure" button appears in the interface when valid intersections are available. Tap it to see the available options with remaining runway distance in feet.
Voice during taxi — Include the intersection in your taxi request: "Request taxi, can accept Hotel." or "Request intersection Alpha."

ATC will confirm the intersection and remaining runway available. The intersection is included in your takeoff clearance in the US, and in the taxi instructions only in the UK and Australia.

Only intersections that leave enough runway for your aircraft's performance are offered. A Cessna 172 will see many options; a heavier aircraft may see few or none.

Step 4 – Contact Tower & Request Departure

When you reach the hold-short point, switch to Tower. BeyondATC handles the handoff automatically.

Report ready for departure, stating your runway and intention.

US (circuits): "Tower, N123AB, ready for departure runway 27, closed traffic."

US (departure): "Tower, N123AB, ready for departure runway 27, VFR departure."

UK: "Oxford Tower, G-ABCD, runway 27, ready for departure, circuits."

AU: "Bankstown Tower, VH-ABC, runway 29, ready for departure, circuits."

ATC evaluates the runway state and will issue one of the following:

Hold short — traffic on or approaching the runway
Lineup and wait — enter the runway but hold for takeoff clearance
Cleared for takeoff — all clear, takeoff clearance issued

Step 5 – Takeoff

ATC will issue takeoff clearance with wind information. For circuits, a circuit direction (left or right traffic) is included.

US: "N123AB, wind 270 at 10, runway 27, cleared for takeoff, make left traffic."

UK: "G-ABCD, surface wind 270 degrees 10 knots, runway 27, cleared for takeoff."

AU: "VH-ABC, wind 270 degrees 10 knots, runway 27, cleared for takeoff, make left circuit."

If you are departing the area (not doing circuits), you can request to leave controlled airspace once airborne:

🇺🇸 You are automatically released from tower control when you reach approximately 6 nm from the airport — no frequency change request is needed. For departures closer in, request a frequency change as normal.
🇬🇧 Request a VFR departure. ATC will respond with "Cleared to leave the {airport} control zone at your discretion, squawk conspicuity."
🇦🇺 Request a frequency change. ATC will respond with "Squawk 1200, frequency change approved."

Step 6 – Joining the Circuit

After takeoff, fly the circuit at the airport's circuit altitude. The standard pattern consists of five legs:

   [Base]  ←————  [Downwind]  ————→  [Crosswind]
     |                                     |
     ↓                                     ↑
   [Final]  ————  [== Runway ==]  ————→  [Upwind]

BeyondATC tracks your position within the circuit and sequences you against IFR traffic.

Step 7 – Circuit Reporting

You must report at the designated point for your region. At this point, you also declare your landing intention.

Region	Where to report
🇺🇸 US	Midfield downwind
🇬🇧 UK	Downwind
🇦🇺 AU	Downwind

Landing intentions:

Option	Description	Available
Touch-and-go	Land and immediately take off again	🇺🇸 🇬🇧 🇦🇺
Full stop	Land and taxi to parking	🇺🇸 🇬🇧 🇦🇺
Low approach	Fly along the runway without landing	🇺🇸 🇬🇧 🇦🇺
Stop and go	Land, come to a full stop, then take off from the same runway	🇺🇸 🇦🇺
The option	The landing intention is left down to the pilot	🇺🇸 only

US example: "Tower, N123AB, midfield downwind runway 27, touch and go."

UK example: "Oxford Tower, G-ABCD, downwind runway 27, request low approach."

AU example: "Bankstown Tower, VH-ABC, downwind runway 29, touch and go."

ATC responds with your sequence position and any traffic to follow: "N123AB, number 2, follow the Cessna 172 on downwind."

Changing your intention

After reporting, you can change your landing intention before clearance by using the "Change Intention" button or voice request. ATC will acknowledge and re-issue clearance with the updated intention.

Report Traffic In Sight

When sequenced behind traffic, ATC may ask you to report when you have the traffic in sight. A "Report Traffic In Sight" button will appear — you can also report it by voice.

Step 8 – Landing Clearance

When clearance is issued varies by region:

🇺🇸 United States

In the US, if there is no traffic conflict landing clearance is issued at the downwind report — there is no separate "report final" step. When you report midfield downwind with your intention, ATC responds directly:

No traffic ahead: ATC issues clearance immediately with wind and intention. "N123AB, wind 270 at 10, runway 27, cleared touch and go."
Traffic ahead: ATC sequences you — "N123AB, number 2, follow the Cessna 172 on 2 mile final, report traffic in sight." Once you report the traffic, ATC issues clearance.

If you want to change your intention after receiving clearance, you can do so inline — ATC will re-issue the clearance with your updated intention.

🇬🇧 United Kingdom

Report final as you turn onto the final leg. ATC issues clearance on final.

"Oxford Tower, G-ABCD, final runway 27." ATC: "G-ABCD, wind 270 degrees 10 knots, runway 27, cleared to land."

🇦🇺 Australia

You report your intentions at downwind (same as UK), and ATC will instruct you to report turning base. Clearance is then issued when you report your base turn.

"Bankstown Tower, VH-ABC, turning base runway 29." ATC: "VH-ABC, wind 270 degrees 10 knots, runway 29, cleared touch and go."

If the runway is occupied when you report final, ATC will respond with "Continue approach" and issue your clearance once the runway is clear. You can request a go-around at any time during this phase.

Step 9 – After Landing

Once you've slowed to taxi speed, ATC will instruct you to vacate the runway and contact Ground.

"N123AB, vacate right, contact Ground on 121.9."

On Ground, you choose your next action:

Taxi to parking — ATC asks your preferred parking area. You can select a specific ramp or choose "Any Ramp" for auto-assignment to the nearest suitable GA parking.
Another circuit — your state is reset and you re-enter the departure taxi flow
VFR departure — taxi to the runway for a departure from the area

Arriving from Outside the Airport

If you are flying inbound and want to join the circuit, contact Tower with a position report (distance, direction, and altitude from the airport).

US example: "Palo Alto Tower, N123AB, five miles west, 2,500 feet, request join."

UK example: "Oxford Tower, G-ABCD, eight miles north, 2,000 feet, request join."

AU example: "Bankstown Tower, VH-ABC, six miles south-west, 1,800 feet, request join."

Join types depend on your region:

🇺🇸 United States

In the US, pilots lead with a full position report including aircraft type, distance, direction, altitude, intentions, and ATIS code. ATC responds directly with pattern entry clearance — there is no "say position and intentions" back-and-forth.

"Palo Alto Tower, Cessna 123AB, Cessna 172, five miles west at 2,500, inbound for landing, information Alpha." ATC: "N-3AB, enter left downwind runway 27, report midfield downwind."

The US button is labelled "Report Inbound" and expands into a sub-menu: Landing (full stop) or Pattern Work (circuits — intention deferred until downwind).

🇬🇧 United Kingdom

Three join types are available. ATC will issue one based on traffic and conditions:

Downwind join — join the downwind leg at circuit altitude; QFE provided
Overhead join — full overhead procedure (see section below)
Straight-in — fly directly to final; report when established

🇦🇺 Australia

ATC will direct you to join the circuit and report downwind. "VH-ABC, join left circuit runway 29, report downwind."

UK Overhead Join

The overhead join is a UK-specific procedure where you cross the airfield at circuit altitude + 1,000 ft before descending to join downwind on the non-traffic (dead) side.

Full sequence:

Clearance — ATC clears you to join overhead at the stated altitude with QFE "G-ABCD, join overhead at 2,000 feet, QFE 1005, runway 27."
Report overhead — When over the airfield, report overhead ATC: "G-ABCD, report descending deadside."
Report descending deadside — Descend on the non-traffic side ATC: "G-ABCD, join left-hand downwind, report downwind."
Report downwind — You are now in the standard circuit; proceed as normal from Step 7

Action buttons guide you through each step of this procedure.

Traffic Sequencing & Circuit Holds

BeyondATC integrates VFR circuit traffic with inbound IFR traffic. When an IFR aircraft is on approach, ATC may issue a hold instruction to keep you clear.

Extend Downwind

Used for lighter IFR conflicts when you are on the downwind leg.

Region	Instruction
🇺🇸 US	"Extend your downwind, I'll call your base."
🇬🇧 UK	"Continue downwind, I'll call your base."
🇦🇺 AU	"Extend downwind."

ATC will call you back when it's safe to turn base: "Turn base, report final."

Orbit

A 360-degree turn in place, used for heavier IFR conflicts.

Region	Instruction	Direction
🇺🇸 US	"Make a right three-sixty."	Opposite to circuit direction
🇬🇧 UK	"Orbit right."	Opposite to circuit direction
🇦🇺 AU	"Orbit right."	Opposite to circuit direction

Circuit Breakout

If your extend or orbit lasts too long (due to continuous traffic), ATC may instruct you to report back to the downwind:

After an extended downwind: ATC will break you out of the circuit — "Turn right, rejoin and report downwind, due to traffic." You re-enter the circuit from scratch.
After an extended orbit: ATC will advise the airport is busy — "Airport very busy, delay is not determined, you may want to leave the circuit and come back at another time." Your orbit continues and the advisory can repeat.

Go Around

If the runway becomes unavailable while you are on final, ATC will issue a go-around instruction. You will re-enter the circuit from the beginning.

Region	Instruction
🇺🇸 US	"Go around, make left traffic."
🇬🇧 UK	"Go around, make left-hand circuit."
🇦🇺 AU	"Go around, make left circuit."

Runway & Direction Changes

Changing Your Runway

You can request a different runway at any time:

Before departure (on the ground): Use the "Request Runway Change" button or say "Request runway change." ATC will re-issue taxi instructions for the new runway.
During arrival (in the circuit): ATC will re-sequence you for the requested runway.

A sub-menu shows the available active runways when using buttons.

Changing Your Circuit Direction

You can request the opposite circuit direction on the ground (after departure clearance) or in the air (after join clearance). Use the button or say "Request right traffic" / "Request left-hand circuit".

ATC will acknowledge and re-issue your clearance with the updated direction. Regional wording:

🇺🇸 "Right traffic approved."
🇬🇧 "Right-hand circuit approved."
🇦🇺 "Right circuit approved."

Callsign Shortening

BeyondATC shortens GA callsigns after your first transmission with each controller, matching real-world practice:

Region	Full callsign	Shortened	Style
🇺🇸 US	N42PC (Piper Comanche)	Piper 2PC	Type prefix + last 3 of N-number
🇬🇧 UK	G-ABCD	G-CD	First letter + last 2
🇦🇺 AU	VH-BVM	BVM	Last 3 (VH prefix dropped)

Your shortened callsign appears alongside the full form at the bottom right of the flight interface (e.g. "G-ABCD (G-CD)"). You can use either form when transmitting.

This tutorial covers the features available in the first experimental VFR release. Additional capabilities — including uncontrolled airport procedures, VFR flight following, and enroute ATC assistance — will be added in future updates.