faa-hf-std
FAA Human Factors Design Standard (HF-STD-001B)
Source: FAA (US Government work, approved for public release) | Chapters: 9
When to use
Use this skill when you are specifying, designing, or evaluating the human-facing parts of an FAA-domain system — an air-traffic console, an airway-facility equipment rack, an operator display, an alarm scheme, a computer-human interface, an input device, or a workstation — and you need concrete, citable, quantified human-factors design criteria rather than a process narrative. It is the design-rule layer that sits beneath HSI lifecycle guidance.
Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.
How to Use This Skill
- Without arguments — load the core frameworks below: the standard's design philosophy, the shall/should and order-of-precedence rules, the controlled vocabulary, and the recurring design moves (quantify the quality, two-layer error handling, reserved color/signal coding, consequence-scaled percentiles, design-for-maintenance).
- With a topic — ask about a design area (e.g. "automation authority", "alarm physics", "control-indicator integration", "anthropometric percentiles", "console geometry", "destructive-action confirmation") and route to the chapter via the Topic Index.
- With a chapter —
ch02(automation),ch04(displays/controls),ch05(alarms/audio),ch06–ch07(computer-human interface),ch08(input devices/workstations),ch09(safety/anthropometry/documentation/tailoring).
Supporting files: glossary.md, patterns.md, cheatsheet.md.
Design criteria, not a process model. HF-STD-001B tells you what an acceptable design must be — the millimetres, newtons, decibels, contrast ratios, and percentile rules. It does not tell you where in the lifecycle to address human factors. Pair it with
nasa-hsi(the HSI process layer) — the two interlock at the source level, since many HF-STD rules cite NASA-STD-3000A.