IFATC.org
Menu

Help

IFATC.org is a companion site for Infinite Flight controllers on the Expert Server. Everything shown is worked out from the Infinite Flight Live API every 15 seconds.

  • Using the live map: terrain, the minimum safe altitude slider, traffic symbols, routes and tools
  • Questions: what the counts mean, where the terrain comes from, why updates pause
  • Contact: feedback, bug reports and requests
  • Privacy and terms

The pages

Page What it’s for
ATC status Airports with a controller on frequency, their traffic, and who is controlling
Inbounds Every airport with flights inbound, and when they arrive
Live map Terrain, approach cones, routes and live traffic around one airport
Airports Weather, live traffic lists, runways and approach details, and gates for one airport
Nav points Find a fix or VOR by name and open it on the map
Sector Pro: a centre controller’s view of one FIR
Planner Pro: where to open next, from traffic arriving in the next hour

Arrival manager (Pro)

On each airport page, the Arrival manager tab lists the next 30 or 60 minutes of arrivals in landing order. For each one it shows the gap to the arrival ahead, roughly how far behind it will be when that one lands, and how many minutes it needs to lose to keep the minimum gap you choose. Gaps under the minimum are amber and gaps under half of it are red. The timeline beside the table shows the same thing, with a hollow circle at a delayed arrival’s slot. Above both, a chart counts arrivals in each 10 minutes and turns a block amber when more arrive than fit at your gap.

Sector view (Pro)

The sector view shows one FIR the way a centre controller sees it. Search for a FIR by code or name, or pick a centre that’s online. The map shows:

  • every airborne aircraft in the FIR as a radar target. Auto shows full data blocks when zoomed in and only callsigns or targets further out. Green aircraft are landing at an airport in the FIR, and dim ones are just outside it.
  • airports with ATC or arrivals, red when controlled. Click one to open its map.
  • the neighbouring FIRs. Click one to go to it.

The panel shows the centre controllers online in the FIR, how many aircraft are in it below FL100, between FL100 and FL245 and above FL245, and the airports with ATC or arrivals. Click an aircraft to see its details and flight plan.

FIR boundaries come from the VATSpy Data Project under CC BY-SA 4.0. They follow real-world FIRs, so they can differ from Infinite Flight’s centre regions.

Sweatbox (Pro)

The Sweatbox is a practice radar with simulated traffic. It runs in your browser and never touches Infinite Flight. Its rules, menus and phraseology follow the Infinite Flight ATC Manual (version 26.4). Every point lost names the manual section it comes from and links to it.

Setup

Pick an airport and a runway end. Parallel runways landing the same way are used too (4.1.4). The ATIS options follow 4.1 and 4.2. For tower you can set pattern work, how many aircraft start in the pattern, transitions an hour, and straight-out or rolling departures. For approach you set the approach in use and how much VFR flight following there is.

Approach

Your airspace is 50 nm and up to FL180 (5.1).

  • Arrivals check in at its edge. Answer with Expect vectors (with a runway when more than one is in use) or Continue as filed (6.9.3). Continue as filed lets them descend on the arrival to the IAF, 20 nm out on the extended centreline. Some ask for radar vectors, which means vectors to the pattern, not an approach clearance (6.12.1).
  • Vectors use magnetic headings, altitudes, and speeds in indicated airspeed, optionally “until 5 mile final”. The scope shows groundspeed, which is higher at altitude (6.15).
  • Clear the ILS or RNAV approach with an altitude to keep until established, and optionally an intercept heading. Aim for about a 30° intercept and an altitude below the glideslope (6.10, 6.11).
  • Visual approaches start with Report airport in sight (6.13).
  • Hand arrivals to tower only once they’re established, with safe spacing behind the traffic ahead (6.14).
  • You can also hold at the IAF, the FAF or present position, make 360s, and send aircraft direct to a fix (6.7, 6.16).
  • Departures check in and must get Radar contact (6.4.4). VFR flights asking for flight following get Radar contact and a frequency change before they leave (6.5). Change everyone’s frequency before they leave your airspace.

Tower

The menus are the ones in Infinite Flight.

  • Without radar, inbounds call 10 to 15 nm out. Give them a pattern entry (left or right downwind, left or right base, or straight in) with a runway (3.3). One that reaches the pattern without an entry orbits outside and costs points (3.3.2). Unable answers a runway change you can’t give.
  • To sequence, pick the traffic to follow. The pilot gets the number and that aircraft’s position (“number 2, traffic to follow is a C172 on left base”), and won’t turn base until the one ahead is far enough down final.
  • On downwind you can extend downwind (“I’ll call your base”) and later turn base. On upwind it’s extend upwind and turn crosswind. Left and right 360s and Maintain slowest practical speed are there too.
  • Cleared to land is for a full stop and Cleared for the option for touch and goes, with make left/right traffic after a fresh pattern entry (3.3.5, 3.3.6). Pattern traffic flies the circuit at 1,000 ft above the field for props and 1,500 ft for jets, and calls you on downwind.
  • With radar online, ILS arrivals only need a landing clearance. Radar-vectored traffic needs an entry, a sequence if required and a clearance, and visual traffic a sequence if required and a clearance (3.6.3).
  • Departures call ready at the holding point. Number 1 gets Hold short and the rest a departure sequence (3.2.2). Then give Line up and wait or a takeoff clearance: as filed, straight out until 1,000, 3,000 or 5,000 ft above the field, immediate, or with left or right traffic for aircraft staying in the pattern (3.2). Switch them about half a mile past the end, not during rotation (3.2.11).
  • VFR transitions ask to cross your airspace. Approve them at an altitude inside tower airspace and at least 500 ft above the pattern; 1,000 ft is better (3.4).
  • Go-arounds always come with runway heading or left or right traffic (3.5.4). Exit runway is given below about 70 kt, with expedite only when traffic is close (3.5.1).

The scope tags show the pattern leg (L/R DW for downwind, BS for base, FIN, UPW, XWD; + when extended), the sequence number, and CL or OPT once cleared.

Scoring

You can give clearances in anticipation, because the score counts the separation that actually happens (3.1.2).

Rule broken Manual Points
Takeoff roll or arrival at the threshold with the runway not clear 3.1.1 25
Aircraft inside 3 nm and 1,000 ft 6.2.2 20
Vectored or assigned below 1,000 ft above terrain 6.2.1 20
Pattern aircraft inside 0.5 nm and 300 ft of each other 7.3.4 15
Collision alarm, inside 1.5 nm and 500 ft 6.2.4 10 more
Go-around because there was no landing clearance 3.3.1 10
Transition below 500 ft above the pattern 3.4.3 10
Established above the glideslope, or left too high to land 6.11.4 8
Handed to tower before established 6.14.1 8
No traffic alert within 30 seconds of a conflict 6.2.4 5
Inbound reached the pattern without a pattern entry 3.3.2 5
Radar-vectors traffic cleared for an approach 6.12.1 5
Transition above tower airspace 3.4.3 5
Handed over too close to, or closing too fast on, the aircraft ahead 6.14.3 5
Cleared while not number 1 without a sequence, with radar online 3.6.3 3
“Cleared to land” to touch-and-go traffic 3.3.5 3
Option after a new pattern entry without left or right traffic 3.3.6 3
Number 1 for departure given a sequence instead of “Hold short” 3.2.2 3
A departure’s check-in not answered with “Radar contact” 6.4.4 3
Not handed to tower by 2 nm 6.14 3
A request left for more than a minute — 3
Left your airspace without a frequency change 3.2.11, 5.1.1, 6.5.4 2

“Should” items, such as intercept angles, a missing sequence without radar, expediting without need or a late cancel of a takeoff clearance, show in the debrief as advice and cost nothing. Space pauses, and the clock runs at 1×, 2× or 4×. Free accounts can try a 10-minute light session.

Ground control (pushback, taxi, crossings), Center, intersecting runways and formation flights aren’t simulated.

My ATC (Pro)

My ATC shows your total operations, IFATC rank, recent sessions, ops per hour and where you control most. Link your Infinite Flight Community username on your account page first. Stats are fetched from Infinite Flight when you open the page, kept for 15 minutes, and never stored. Frequencies you opened together count as one session.

Session planner (Pro)

The planner has three lists:

  • Open a tower: Bravo, Charlie and Delta airports with arrivals in the next hour and no ATC at all
  • Fill a gap: airports with some ATC open but Ground or Tower missing
  • Add radar: towers with five or more arrivals in the next hour and no approach or departure. Tick I can control approach and departure to see it.

Each list is ordered by traffic arriving soon. Set Most inbounds I’ll take to hide airports busier than you want.

What the traffic numbers mean

These are the same on the ATC status page, the inbounds page, the airport page and the map.

Column Counts
Ground Aircraft moving at 45 kt or less within 5 nm of the airport, not including flights inbound to it
Tower Airborne aircraft below 10,000 ft within 25 nm, not including flights inbound to it
< 20 min Inbound flights arriving in under 20 minutes
20–60 min Inbound flights arriving in 20 to 60 minutes
Total Every flight with this airport as its destination, including ones still on the ground at their origin

An arrival time is the straight-line distance to the airport divided by the aircraft’s current groundspeed. It doesn’t follow the flight plan, so long descents and holds make real arrivals later than shown.