Air traffic operational procedures

Detects air traffic operational procedures: ATC unit, local operating or separation procedure wording with populated sector, frequency, waypoint, transfer-level and restriction fields and operational values (flight levels, runways, frequencies, distances). Topic wording alone is discovery-only.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium confidence: the topic phrase alone is discovery-only; enforcement needs populated structure (an operational value (flight level, runway designator, VHF frequency, NM distance, altitude in ft, squawk code) or a populated procedure field (sector, frequency, waypoint/fix, holding, transfer point/level, release point, handoff, clearance limit, restrictions)), and 85 needs two distinct structures plus independent ATC-operations (controller, coordination, transfer of control, approach/tower, vectoring) evidence, so policies, blank forms and training text stay below 75.
Detection quality: Not detected
Jurisdictions: global
Regulations: Security of Critical Infrastructure Act 2018 (Cth)
Frameworks: ISO 27001, NIST CSF
Data categories: security
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:air\s+traffic\s+(?:operational|control|management|services?)\s+(?:procedures?|instructions?|manual|orders?)|ATC\s+(?:procedures?|unit\s+procedures|instructions?)|manual\s+of\s+air\s+traffic\s+services|local\s+(?:operating|operational)\s+procedures?|(?:tower|approach|terminal|en[\s-]route|centre)\s+(?:control\s+)?operating\s+procedures?|separation\s+(?:minima|standards?)|contingency\s+procedures?\s+for\s+air\s+traffic)\b

Corroborative evidence keywords

controller, coordination, transfer of control, approach control, tower, departures, arrivals, vectoring, conflict, airspace

Proximity: 300 characters

Should match

Local operating procedures for the tower are reviewed every six months. — Discovery probe (65)
ATC unit procedures - Brisbane Approach Sector: BN APP North Frequency: 125.600 MHz — Medium-tier probe (75) - populated procedure fields and a frequency
Local operating procedures - Brisbane Approach / Centre coordination Sector: BN APP North Transfer level: FL130 at waypoint GOMOL Runway 19L arrivals: descend to 5000 ft, 10 NM spacing on final Frequency: 125.600 MHz Transfer of control occurs at the release point after coordination with the approach controller; vectoring for departures resolves any conflict. — High-tier probe (85) - several operational values, procedure fields and ATC-operations context

Should not match

unrelated generic text — No relevant phrase context
placeholder value 12345 — Random text should not match
Policy statement: air traffic control procedures are approved by the Chief Controller before publication. — Policy text
ATC unit procedure template Sector: ________ Frequency: [insert] — Blank template
Course module 6: separation minima - 5 NM radar separation on runway 19L arrivals at FL130. — Training framing
The ICAO overview explains the purpose of air traffic control. — Public overview

Known false positives

Public AIP/ICAO material and aviation training cite runways and flight levels. Mitigation: Guidance/training framing is excluded; 85 needs two operational values plus populated procedure fields and ATC-operations context.