All work

Configural Conflict Display for En-Route Air Traffic Control

An animated radar scope, built in Figma from real flight data, where two converging aircraft form one shape that grows from a faint yellow hint into a solid red warning as a loss of separation becomes likely.

Final radar scope at 20:17:50 UTC with Conflict A at stage 4: overlapping red protected circles, a nearly closed time ring, and the legend beside the scope
The final design at 20:17:50 UTC, 56 seconds before a predicted loss of separation. Traffic data from The OpenSky Network (2019); DAL2214 is synthetic.
Course
ISE 6604: Human Factors of Visual Display Systems
Instructor
Dr. Joseph Gabbard
My role
Sole designer
Tools
Figma Smart Animate, OpenSky Network data, Claude
Date
Nov 2026

An individual project. I selected and filtered the data, designed every element, built all seven Figma frames and their Smart Animate transitions, and defined the risk calculation. Claude helped convert the flight data into Figma coordinates.

The problem

En-route controllers must keep aircraft at least 5 NM apart horizontally or 1,000 ft apart vertically. Today they judge that by mentally comparing positions, headings, and data-block numbers, then predicting where two aircraft will be minutes from now.

ERAM’s Conflict Alert flashes both data blocks about 2.5 minutes before a predicted loss of separation, but it’s either on or off and doesn’t show where or why. The distance reference indicator (DRI) ring helps only if the controller turns it on for each aircraft by hand.

Three panels of the current ERAM display: the situation display, distance reference indicator rings, and a blinking conflict data block
How ERAM shows separation today: (A) the situation display, (B) manually enabled DRI rings, and (C) a conflict data block that blinks.

A from Gallagher (2014), Ars Technica, image courtesy of Lockheed Martin. B and C from vNAS Documentation Team (n.d.).

My goal was a display that turns that mental calculation into something a controller can see. It answers the three questions a controller asks continuously:

  • Where is everyone?Position, heading, and altitude for every aircraft, from the glyph and data block.
  • Is a conflict forming?An early, faint warning, well before a loss of separation.
  • How urgent, and why?Urgency, and whether the problem is horizontal, vertical, or both, from color, the time ring, the circles, and the tags.

Real traffic and a risk score

The scope replays real ADS-B data from the OpenSky Network for 1 July 2019, in seven frames from 20:09:50 to 20:17:50 UTC, the busiest stretch of the hour. I kept airborne, en-route traffic above FL180 within 50 NM of the IAD/DCA midpoint, which put 19 to 25 aircraft on screen, and drew it on an 800 × 800 px Figma scope at 8 px per NM.

Real traffic is controlled, so no real pair lost separation. One synthetic aircraft, DAL2214, creates a full conflict with real UAL1484. It looks identical to real traffic, so it doesn’t give the conflict away.

How risk is scored

Each converging pair is projected forward at constant track, speed, and vertical rate. Within a 7-minute look-ahead, the moment of closest approach gives a predicted horizontal and vertical gap. Three factors, each from 0 to 1, are multiplied, so risk is high only when the aircraft will be close in both dimensions, and soon.

FactorRises from 0 atTo 1 at
Predicted horizontal gap15 NM5 NM, the separation standard
Predicted vertical gap3,000 ft1,000 ft, the separation standard
Time to closest approach7 minutes1 minute

Stages begin at a risk of 0.2, 0.4, 0.6, and 0.8. Stage 4 also requires a predicted loss of separation: under 5 NM and under 1,000 ft. Separation standards from FAA (2014a, 2014b).

What each element shows

Every calculated value has its own visible element, so a controller can see both the overall risk and the reason for it.

Display elementShowsFlight variables used
Projection linesPredicted path to closest approachPosition, track, ground speed
Altitude tagsPredicted flight level at closest approachAltitude, vertical rate
Protected circlesPredicted horizontal gap; overlap means under 5 NMPosition, track, ground speed
Circle outlineDashed if one gap is below standard, solid if both areAll five
Time ringTime until closest approachPosition, track, ground speed
Stage color and opacityOverall risk, stages 1 to 4All five

How the design evolved

The design went through four iterations over eight days. I started with a baseline scope with no warning at all, both as a comparison and as the base layer of the final design. The first warning version added projection lines, a connector, and an amber risk zone whose size encoded risk.

Four iterations: empty scope, baseline traffic, first emergent version with an amber zone, and the final design
(A) Empty scope. (B) Baseline traffic, where UAL1484 and DAL2214 are about to lose separation with nothing on screen saying so. (C) First warning version. (D) Final design. Traffic data from The OpenSky Network (2019); DAL2214 is synthetic.
ChangeWhy
Predict the closest approach instead of using current distancePrediction uses all five variables and warns minutes earlier.
Replace the size-coded zone with 5 NM protected circlesZone size was a code viewers had to learn. The circles are the separation standard drawn to scale.
A dashed or solid outline instead of a side viewA side view would add an element and repeat the altitude tags.
Four stage colors, yellow to red From class feedbackColor now rises with urgency, alongside opacity and ring size. The steps also darken, so they stay distinct with red-green color blindness.
Altitude shown by dot size and line thickness From class feedbackAltitude reads from the symbol itself. I used thickness, not line length, because on ERAM line length means speed.
A legend beside the scopeIt explains every encoding so first-time viewers can read the display.
The risk feature at stage 4 in the first iteration and in the final design
The warning at stage 4, first iteration versus final: the connector and size-coded zone became protected circles, an outline that shows which gaps are below standard, and a shrinking time ring. Traffic data from The OpenSky Network (2019); DAL2214 is synthetic.

The final design

Step through the seven frames to watch Conflict A build to a predicted loss of separation while Conflict B appears and then resolves.

Radar scope at 20:09:50 UTC

20:09:50 UTC. Traffic only. Two streams cross the scope, northeast and southwest, and no pair is converging closely enough to show risk.

Stage 4 arrives about 2 minutes ahead, close to when ERAM’s Conflict Alert would fire. Stages 1 to 3 add about three minutes of earlier, gradual warning.

Reading the display

Annotated final design showing global, intermediate, and local levels of emergent features
Three levels work at once: traffic streams show where everyone is, the conflict shape shows where the risk is, and each glyph and data block gives the details. Traffic data from The OpenSky Network (2019); DAL2214 is synthetic.

Conflict A builds. Real UAL1484 heads northeast at FL350 while synthetic DAL2214 heads southeast, descending from FL390. Their predicted paths meet less than 1 NM and a few hundred feet apart, and every one of the five variables can be traced within the one shape.

Conflict B resolves. Real RPA4581 overtakes real NKS140 while descending through its altitude. The vertical gap shrinks to about 200 ft, but the horizontal gap stays near 5.4 NM, so the circles stay dashed and never overlap. The shape fades by 20:16:50.

Conflict A at 20:17:50 annotated element by element
Conflict A at full strength, element by element. Traffic data from The OpenSky Network (2019); DAL2214 is synthetic.
At 20:15:50, Conflict A closing in both dimensions beside Conflict B closing only vertically
At 20:15:50, the shapes alone show that Conflict B is closing vertically but not horizontally, while Conflict A is closing in both. Traffic data from The OpenSky Network (2019); DAL2214 is synthetic.

Try it. The Figma prototype animates between all seven frames.

Open the prototype in Figma

Why it works

Six display design concepts from Bennett and Flach (2011) and the course lectures (Gabbard, 2026) shape every element.

ConceptHow the display applies it
Emergent featuresAt three levels: track lines form traffic streams; projection lines, circles, tags, and the ring form the conflict shape; dot, line, size, and color form each aircraft glyph.
Semantic mappingEach protected circle has a 2.5 NM radius, so two circles touch at exactly 5 NM, and the outline turns solid only when both gaps fall below the FAA standards.
Proximity compatibilityA conflict integrates ten values, five per aircraft, so every conflict element shares one place and one warm color. Cool-colored aircraft details stay in separate data blocks.
Analogical formatThe scope is a scaled map: projection length is distance flown, circle overlap is the horizontal gap, and ring size is time remaining. Data blocks keep exact values.
Redundant codingAltitude is coded by color and symbol size. Urgency is coded by color, opacity, and ring size, so the display still reads with color vision deficiency.
SalienceYellow to red and faint to opaque, so salience rises only as risk rises and the most urgent conflict draws the eye first.

Compared with ERAM

ERAM Conflict AlertERAM DRI ringThis design
TriggerAutomatic, about 2.5 min aheadManual, per aircraftAutomatic, up to 7 min ahead
SignalData blocks flashFixed ringBuilds through four stages
Shows whereNoCurrent position onlyPredicted meeting point
Vertical gapRead from data blocksNot shownAltitude tags and outline style
Shows whyNoHorizontal distance onlyTraceable to all five variables
ResolutionAlert stopsNot shownShape visibly fades

What’s new: the shape sits at a place that doesn’t exist yet, the predicted meeting point, and it’s graded, so a controller sees a conflict forming rather than a threshold being crossed.

What I learned and next steps

A good emergent feature has to mean something in the domain. My first risk zone was striking but abstract; redrawing it as the separation standard itself made the shape explain the conflict instead of just flagging it. Building it also showed me how much Smart Animate depends on structure: every layer must be named and nested identically across frames.

  • LimitationsMotion is straight-line between frames 1 to 2 minutes apart, and the prediction assumes steady track, speed, and vertical rate. Only two conflicts are shown, one with a synthetic aircraft, and tracks use true rather than magnetic north.
  • Next stepsTest the display against ERAM’s Conflict Alert for detection time and accuracy, check clutter with several simultaneous conflicts, and build a continuously updating version in code.
Sources Show all 9Hide
See all projects

Questions about this project? jbrazina2324@gmail.com