AVSEC Organization and Governance
How AVSEC is organized
AVSEC organization runs along a chain: the State designates a competent authority (often a civil aviation security authority or department within the CAA); that authority writes the National Civil Aviation Security Programme (NCASP) and approves each aerodrome's Aerodrome Security Programme (ASP). Internationally, ICAO sets Standards through the Assembly and Council, supported by the Aviation Security Panel and regional offices; AVSEC Panel working groups develop guidance. At the aerodrome, the operator establishes a security committee, appoints a security manager, and coordinates with police, immigration, customs and air traffic services.
Concepts to master
- NCASP (State level), ASP (aerodrome level), air carrier security programme: know which document belongs to whom.
- Security restricted area designation and the critical part concept.
- Quality control functions: audits, inspections, tests, surveys - and who performs each.
- National AVSEC instructor/approval schemes: instructors are usually certified by the competent authority.
Traps
- Assuming the aerodrome operator writes the NCASP - it does not; the State does.
- Confusing a security survey (baseline assessment) with a security audit (compliance check).
- Believing the security committee has enforcement power; it is advisory and coordinating.
- Forgetting that law enforcement response is normally a State/police function, not the operator's.
Rule of thumb
Match the document to the level: State → NCASP; aerodrome → ASP; airline → carrier programme. Worked example: a question asks who approves the ASP. The competent authority approves it; the operator drafts and maintains it.