Aerodrome Security Programme and Contingency Planning
The ASP as a living document
The Aerodrome Security Programme translates the NCASP into aerodrome-specific measures: layout, restricted areas, access points, screening points, patrols, communications, training and records. It must be approved, reviewed regularly, and amended when the threat or layout changes. Contingency planning covers foreseeable disruptions: bomb threats, hijack, sabotage, hostage situations, suspicious items, and also natural events affecting security. Plans should define command structure, notification trees, evacuation and cordon distances, media handling, and recovery.
Concepts to master
- Risk assessment: threat, vulnerability, consequence; drives proportionate measures.
- Critical parts of restricted areas: the most sensitive zones requiring the strictest control.
- Tabletop and live exercises: frequency, participants, lessons learned.
- Business continuity: how security resumes after an incident.
- Confidentiality: the ASP is sensitive; distribution is controlled.
Traps
- Treating the ASP as a one-time document - it is reviewed and version-controlled.
- Confusing an exercise (test of plans) with an inspection (compliance check).
- Forgetting that contingency plans must be tested, not just written.
- Assuming contingency planning is only about terrorism; it includes any event that disrupts security.
Rule of thumb
A plan is only as good as its test and its lessons-learned loop. Worked example: a bomb threat is received. The plan should specify who is notified first, who decides on evacuation, the cordon distance, and who speaks to the media - all decided before the event.