Automation index
How much of a Air traffic controller’s job can AI already do?
Labels and alerts already help. Separating two aircraft in fog, and talking to both, is not something you hand off.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Air traffic controller
17%
AI can already do 17% of this job.
#588 / 633
View rankingAir traffic controller
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Plan sequences and read traffic forecasts.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 32% | +5.8 |
Strips, tickets and inter-unit coordination.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Tactical control of aircraft on frequency.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 6% | +1.3 |
Resolve conflicts, radio failures and weather.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 10% | +1.6 |
Train and supervise a controller under instruction.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
Reports, incidents and shift fatigue.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 15% | +2.1 |
| Total | 100% | 17% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Plan sequences and read traffic forecasts
- Tactical control of aircraft on frequency
- Reports, incidents and shift fatigue
- controlador aereo
- air traffic
- atc
- torre de control
Sources for this job· O*NET 53-2021.00· ESCO/ISCO 3154
IS WORK OVER?
Mobile developer
28%
#92 / 633
View rankingMobile developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514