A capability is only useful when it can be executed: clear procedures, consistent phraseology, and training that matches real sector workflow.
AIRS is an ADS-B In spacing capability that depends on standardization to scale safely. My role at ZAB was to help translate program intent into controller-usable operations: what to do, what to say, and how to train it so it becomes consistent and defensible in day-to-day work.
Role
NATCA Project Lead (ZAB)
Deliverables
Procedures · Phraseology · Training
Reference
Year 1 Operational Evaluation (PDF)
What I did at ZAB
- Procedures: Developed en route procedures aligned to sector workflow and traffic reality.
- Phraseology: Standardized communications designed for clarity, brevity, and consistency.
- Training: Built training materials and delivery approach for adoption and proficiency.
- Implementation: Coordinated NATCA inputs and supported operational rollout with stakeholders.
Attribution & documentation
The linked Year 1 Operational Evaluation Report is provided as supporting documentation for the program’s context and evaluation. I did not author the report; my contribution was facility-level NATCA project leadership and operational implementation work at ZAB.
Why it matters
In high-volume operations, new capabilities succeed when the human system succeeds. AIRS adoption required unambiguous standards and practical training that matched how controllers actually work. My focus was making AIRS executable, teachable, and consistent at the facility level.