Airport expansions create a multi-service workload. Build firefighting, operations and medical support together.
Three capabilities, not one airport checkbox
Airfield firefighting, airfield operations and aviation policing appear as separate requirements in UK mission records. Treat them as separate commissioning decisions. A runway POI and one airport appliance are not enough to make every airport incident workable.
Our recommended starting point is a defined airport cluster with nearby ordinary fire, police and ambulance support. Inspect the current airport-related vehicle market and train personnel before activating the relevant extensions. Include the surrounding road network and hospital journey in the coverage plan: an airport at the edge of your map can expose weak support coverage immediately.
Aircraft Accident — Code A
The Code A record (586) lists a Small Airport (Runway) POI, seven Fire Stations, seven Rescue Stations, eight Police Stations, one Aviation firefighting Extension, one Mass Casualty Extension and one HART Base among its generation conditions. This is already a mixed-service incident.
Its response includes three Fire Engines-or-RIVs, one RIV-or-Major Foam Tender, three Fire Officers-or-Airfield Firefighting Command Vehicles, rescue support, water, ambulance command, HART and police. There are 2–10 patients, with 50% transport and 80% critical-care probabilities. Preserve the separate alternative rows instead of compressing all airport vehicles into a single count.
Aviation policing can depend on operations vehicles
Airside Tresspasser (869), added in September 2026, uses runway or terminal POIs. Its record lists both Airfield Operations and Aviation policing extensions. The response is one Airfield Operations Supervisor, one Airfield Operations Vehicle and two Police Cars, with up to one prisoner.
This is why an airport police rule should be based on a mission requirement rather than a general assumption that two patrol cars will do. The specialist operations vehicles can be the missing pieces even when police arrive first.
Practical fleet design and fault-finding
- Create separate rules for an aircraft emergency, an operations task and an airside policing incident.
- Keep the ordinary engine requirement and the aircraft-specific appliance requirement visible as separate rows in your plan.
- Provide enough command resources for the actual rows; do not assume the same single vehicle will satisfy independently counted groups.
- Check water, foam, rescue and hazardous-material requirements on larger variants rather than scaling every Code A number mechanically.
- Test patient throughput while routine ambulance calls continue.
- When a call stalls, inspect the precise missing resource and the vehicle’s education, assignment and availability.
Expand by airport workload
Add the next airport capability only after you know which resources remain occupied longest. A rarely used large appliance may not be the bottleneck; shared command, welfare or medical transport often deserves examination first. Keep exceptional major incidents as a planned alliance contingency until the local response can support them without abandoning the rest of the account.
Sources and further reading
Latest editorial change: Added an answer-first summary, action checklist and related planning/reference link. Detailed source dates remain independent.
Official sources establish game rules; practical build orders and planning examples are TKB recommendations. Follow the UK game’s current requirement panel where a later update differs.