Air Defence Training Simulator

Ask for a change

How it behaves or how the screen looks — in your own words, in any language. You see exactly what would change before anything is saved.

Nothing is saved until you apply it.

approved

This is what exercises and the console are built from.

Identity

What Euro_AD is and what it is for.

Purpose

What the radar sees

complete

Detection range decides how much warning the operator gets; the arc decides whether they get any from a given direction. Both are yours — nothing reads them but the exercise generator.

Detection range (km)Close-in blind zone (km)Azimuth coverage (°)360 for a rotating radar.

Altitude covered (ft)

Anything the numbers do not carry

What can appear on the display

complete

Exercise generation may only produce tracks of these kinds, within these bands.

Description

Speed (kts)

–

Altitude (ft)

–

How it behaves

Transponder

Also replies on Mode 1 — two digits, 0–4 — which a civil transponder cannot.

Description

Speed (kts)

–

Altitude (ft)

–

How it behaves

Transponder

Also replies on Mode 1 — two digits, 0–4 — which a civil transponder cannot.

Description

Speed (kts)

–

Altitude (ft)

–

How it behaves

Transponder

Interrogating it returns silence — which is itself information, and usually the point.

Description

Speed (kts)

–

Altitude (ft)

–

How it behaves

Transponder

Four octal digits, as air traffic assigns. An airliner, a light aircraft, a medevac.

Identification states

complete

The only states a generated track may be in. The tone decides the colour the console shows it in.

Our Forces

What it meansWhat puts a track into it

Friendly

What it meansWhat puts a track into it

Enemy

What it meansWhat puts a track into it

Unknown

What it meansWhat puts a track into it

IFF interrogation

A separate capability from the radar. With this off the console has no interrogate command and an IFF column reads as a dash — an operator on such a system identifies by behaviour alone, which is a different skill and a deliberate one to train.

This system has an IFF interrogator.Turning it on asks each track class above what it replies, and gives the operator an Interrogate command during a run.

Which modes it can read

Mode 3/A — four octal digits, each 0–7Mode 1 — two digits, each 0–4. A military mission code.

Anything the boxes do not carryWho may interrogate, when, how long a reply takes.

What the operator can do

complete

Beyond selecting a track, identifying it, firing and ceasing — which every system does. Each of these is a rule the simulation enforces, so it costs what it really costs; the console can only offer what is switched on here.

Correct the track typeoffThe system's own typing can be wrong, and putting it right is the operator's call. Needs at least two track classes to choose between — and an exercise only presents a mis-typed track on a system that declares this.

Reload during a runoffThe magazine can be refilled without ending the run. The clock does not stop for it, which is the whole lesson: a reload buys rounds with the seconds the next track is using to close.

Choose which launcher firesoffMore than one launcher, each holding its own rounds. The magazine above is divided between them, so this adds a decision without adding rounds — an empty or reloading launcher cannot fire, and one with a round in the air cannot be reloaded.

Adjust the radar tiltoffA fixed array whose elevation the operator sets. Anything below where it points is not held at all — not on the scope, and not engageable — so raising it to reach something high gives up the low approach.

Anything the switches do not carryA command your system has that is not on this list — say so here. It will not appear in a run, but it is on the record.

What the operator reads for each track

complete

The console's columns, in display order. These become the table the trainee reads.

What it can reach

complete

Exercise geometry has to sit inside these, or the trade-off it presents is not a real one.

Minimum range (km)

Maximum range (km)

Interceptors in the air at onceThe hard limit. A further launch is refused until one resolves.Rounds the system holds altogetherAdded up from the magazines below. Not typed here.

Interceptor types

One entry per round the operator can choose between. A system with a single round needs one line. Speed sets the time of flight, which is how much earlier than impact the decision has to be made.

“Max held” is the most of that round this system can carry — hardware, not today's load. Each round keeps its own stock and its own counter during a run; how many a particular exercise issues is set when the exercise is planned, and never more than this.

min kmmax kmktsmax held

Time of flightSimultaneous engagementsAuthority to engage

Who does what

An exercise must never ask a trainee to do something the system does by itself.

The operator decidesOne per line.The system does automaticallyOne per line.Workflow, in orderOne step per line.

General notes

Everything that did not fit a field above.

Coverage: the radar does not rotate. It covers a fixed 120-degree sector whose tilt the operator can change. Detection range depends on target class — 150 km for jets, 100 km for helicopters, 50 km for UAVs. Track solutions can only be calculated while the target is inside the radar envelope, and targets cannot be intercepted below the radar tilt, so low-flying tracks may be undetectable or un-engageable until the tilt is adjusted.

Engagement rings: 70 km long range, 50 km medium range, 20 km short range. Note that the long-range interceptor (70 km) exceeds the detection range for helicopters (100 km is adequate) but is longer than the 50 km UAV detection range, so UAV engagements will in practice begin inside 50 km; this follows from the designer's own figures and is not a correction.

Assumptions made where the answers were silent: minimum engagement range was not stated and is recorded as 0 km — the real constraint the designer described is the radar tilt, not a minimum slant range, and this field should be confirmed. Speed and altitude bands for the three track classes were not given and have been generalised conservatively from the class names and the stated detection and engagement ranges.

Screenshot conflicts and cautions: the screenshots show a monochrome green console with hostile/unresolved rows highlighted in red, whereas the designer states own aerial forces are blue and enemy forces are red. The designer's answer is followed; the colour scheme should be confirmed against the live console. The screenshots' track table shows a 'Friendly / Unknown' identification column, which supports the presence of an Unknown state not named in the answers; it has been included as a neutral state and should be confirmed. The screenshots also show a trajectory-analysis panel, an engagement table with altitude, velocity, probability of kill and Ps columns, a diagnostics and logistics page with radar, launcher and communication subsystem status, and F1–F12 function keys. None of these were described in the answers, so no capability or operator responsibility has been derived from them; the extra engagement-panel figures are consistent with the automatic Pk and time-of-flight calculation the designer did describe. Nothing has been removed from this profile on the grounds that a screenshot did not show it — the screenshots capture single moments, not the full inventory of track classes or identification states.

Authority remains the weakest point in the record: the designer answered the authority question only with the two-rockets-in-the-air limit. Debrief material should not assume any external release authority.

Figures carried into the fields the simulation reads (this record was written before those fields existed, so they sat in prose here and nothing that runs could see them): azimuth coverage 120°, detection range 150 km, two engagements at once, and the three engagement rings as three interceptor types — long 70 km, medium 50 km, short 20 km, each from the stated 5 km minimum. All four are the designer's own figures, quoted above and in the authority answer. Two things were never stated by anyone and are still empty: how fast each interceptor flies, and how many rounds there are in total. Until they are given, the simulation uses its own defaults for both — 1600 kts and 8 rounds — which are not this system's numbers.

The simulation has every figure it runs on. Exercises and the console are being built from these numbers.

Saving a draft takes this profile out of use until it is approved again — training runs would fall back to the simulator's own defaults.