Pre-Flight Aviation Security Risk Assessment: The Complete Guide

A pre-flight aviation security risk assessment is the structured process of deciding, before an aircraft departs, whether the security threats along a specific route and at its airports are acceptable for that specific flight. It answers one operational question — go, no-go, or go-with-mitigations — and it produces a record of why. This guide explains what the process is, what threats it weighs, the sources and reliability grading it depends on, and how a repeatable workflow turns raw intelligence into a defensible go/no-go decision. It is the parent guide to AeroVigil's coverage of flight risk assessment tools, conflict-zone overflight risk, and GNSS interference, and it sits under the broader discipline of aviation security.

What is a pre-flight aviation security risk assessment?

A pre-flight aviation security risk assessment is a documented judgement, made before departure, about whether the security-related hazards on a route are within an operator's tolerance. It is distinct from a safety risk assessment, which weighs weather, terrain, aircraft condition and crew fatigue. Security risk assessment weighs deliberate and conflict-related hazards: attacks on aircraft, contested airspace, electronic interference with navigation, and threats to the aircraft on the ground.

The process is a security discipline, not a formality. Its purpose is to surface hazards that are legal to ignore but dangerous to accept. Airspace over a conflict can be fully open and still be unsafe to cross. An airport can be operating normally and still sit inside a deteriorating security environment.

The output is a decision with three possible shapes. The first is go: the assessed risk is acceptable as planned. The second is go-with-mitigations: the flight proceeds with changes, such as a re-route, an altitude floor, a fuel or diversion contingency, or a schedule change. The third is no-go: the risk is not acceptable and the flight does not operate as planned.

Every serious assessment also produces a record. The record states what was known, which sources informed it, what was decided, and who decided it. That record is what makes the decision defensible after the fact.

Why does a pre-flight security assessment matter if the airspace is legally open?

It matters because legal access and actual safety are different things. A sovereign state controls its own airspace and may keep it open to overflight for political or economic reasons even while a conflict is active beneath it. The aircraft crossing that airspace is exposed to the conflict regardless of the legal status.

Two losses reshaped the industry's thinking on this point. Malaysia Airlines flight MH17 was destroyed over eastern Ukraine in 2014 by a surface-to-air missile while transiting airspace that remained open to civil traffic above a set flight level. Ukraine International Airlines flight PS752 was shot down shortly after departure from Tehran in 2020 during a period of acute military tension. In both cases the airspace was legally available.

After MH17, ICAO published Doc 10084, the Risk Assessment Manual for Civil Aircraft Operations Over or Near Conflict Zones. Doc 10084 established the expectation that operators conduct their own risk assessment rather than relying solely on the overflown state to declare its airspace unsafe. That expectation is the foundation of the modern pre-flight security assessment.

The regulatory anchor sits alongside it. ICAO Annex 17 sets the international standards for safeguarding civil aviation against acts of unlawful interference, and ICAO Annex 6 addresses the operator's responsibility for the safe conduct of flight. Together they place the duty to assess security risk on the operator, not only on the state being overflown.

What threats does a pre-flight security assessment weigh?

A pre-flight security assessment weighs the threats that can harm an aircraft in the air or on the ground because of deliberate action or conflict. These fall into a small number of recurring categories.

Conflict-zone and overflight threats

The first category is the risk of an aircraft being struck while transiting contested airspace. Strategic surface-to-air missile systems — the class of weapon that destroyed MH17 — can reach civil cruising altitudes, so altitude alone is not protection over an active conflict. Man-portable systems (MANPADS) are generally limited to the lower altitude bands, which is why minimum overflight levels have historically been used as a partial mitigation. AeroVigil's conflict-zone overflight risk guide covers this threat class in depth. Because the picture changes by the hour and by the country, current country-level exposure belongs in a live feed rather than a static article — AeroVigil maintains it on the flight risk surface.

GNSS interference

The second category is interference with satellite navigation. GPS jamming denies the aircraft a position signal; GPS spoofing feeds it a false one. Both are now routine features of the airspace near conflicts and militarised borders. Spoofing is the more insidious of the two because the aircraft may accept a plausible but wrong position without an obvious failure indication. AeroVigil's GNSS interference guide explains the mechanisms and the operational effects. A pre-flight assessment records where interference is being reported along the route so the crew can anticipate degraded navigation.

Airport and landside threats

The third category is the threat to the aircraft and its occupants on the ground. This includes the security environment at the departure, destination and alternate airports, the reliability of screening and access control, and the wider stability of the surrounding area. A route can be sound in the air and still carry unacceptable risk on the ground at one of its airports.

Insider and unlawful-interference threats

The fourth category is the classic aviation security threat: acts of unlawful interference, including attacks by people with legitimate access. This is the domain that ICAO Annex 17 was written to address, and it remains part of any complete security picture.

What sources feed the assessment, and how is their reliability judged?

A pre-flight security assessment is only as good as the intelligence behind it, so every source must be graded, not just collected. Sources range from official state notices to open-source reporting of varying quality.

Official sources carry the most weight. These include NOTAMs, state aeronautical information publications, conflict-zone information bulletins issued by aviation authorities such as those in the European system, and formal advisories. AeroVigil's guide to reading a NOTAM explains how these notices are structured and what they do and do not tell you.

Open-source intelligence (OSINT) fills the gaps that official channels leave, but it must be treated with discipline. A single unverified social-media report is a lead, not a finding. The core rule is that one uncorroborated OSINT source is not, by itself, an alert.

To keep that discipline consistent, intelligence is graded on a two-axis scale derived from the long-established Admiralty (NATO) source-reliability system. One axis rates the reliability of the source, from consistently reliable down to untested or unreliable. The other axis rates the credibility of the specific information, from confirmed by independent sources down to improbable. A claim is only escalated when both axes are strong enough and, wherever possible, when more than one independent source agrees. AeroVigil's methodology describes how this grading is applied in practice.

This is where an analyst-in-the-loop model matters. Automated collection can surface a signal quickly, but a human analyst decides whether a graded, corroborated signal rises to the level of an operational alert. That combination — machine speed, human judgement — is what keeps the false-alarm rate low without missing real threats.

How does the pre-flight risk assessment process work step by step?

The process follows a repeatable sequence so that two analysts assessing the same route reach comparable conclusions. The steps below describe the workflow at a level that applies to airlines, business aviation operators and dispatchers alike.

Step 1 — Define the flight and its exposure

The first step is to state exactly what is being assessed. This means the specific route, the airports of departure, destination and planned alternates, the flight levels, the timing, and the FIRs the aircraft will cross. The flight information regions along the route define where to look, because airspace risk is managed at the FIR level.

Step 2 — Build the threat picture

The second step is to gather current intelligence for that exposure. This pulls NOTAMs, airspace restrictions, conflict-zone bulletins, GNSS-interference reports and relevant OSINT for every FIR and airport on the route. Each item is graded for source reliability and information credibility before it is used.

Step 3 — Assess likelihood and consequence

The third step is to judge, for each identified threat, how likely it is to affect this flight and how severe the consequence would be. A high-consequence, low-likelihood threat — such as a strategic SAM over a corridor — is treated differently from a low-consequence, higher-likelihood one such as intermittent GPS jamming. Structured tools help here; a flight risk assessment tool (FRAT) turns these judgements into a consistent, comparable score.

Step 4 — Decide and mitigate

The fourth step is the decision itself: go, no-go, or go-with-mitigations. Mitigations are concrete and route-specific. They include re-routing around a contested FIR, setting a minimum overflight level, adding fuel or a diversion plan, adjusting timing, or briefing the crew on expected navigation degradation. The decision is recorded with its rationale.

Step 5 — Monitor and re-assess

The fifth step recognises that the picture is not static. A go decision made at dispatch can be invalidated by an event two hours later. Continuous monitoring re-runs the assessment as new intelligence arrives, and a material change triggers a fresh decision. AeroVigil's platform is built around this monitor-and-re-assess loop.

Who is responsible for the pre-flight security risk assessment?

Responsibility sits with the operator, shared across specific roles. Under ICAO Annex 6 and the framework established by Doc 10084, the operator carries the duty to assess the security risk of its own operations. Regulators set the standard and audit compliance, but they do not make the per-flight decision.

Within the operator, the work is distributed. A security or intelligence function maintains the threat picture and the source grading. Flight dispatch or operations control applies the assessment to specific flights and integrates it with the operational flight plan. The pilot-in-command retains final authority for the conduct of the flight. Each of these roles depends on the same underlying assessment being current, graded and recorded.

Frequently asked questions

What is the difference between a pre-flight security risk assessment and a FRAT?

A pre-flight security risk assessment is the whole process of judging a route's security risk before departure. A flight risk assessment tool (FRAT) is one instrument used within that process to score identified risks in a consistent, comparable way. The assessment is the discipline; the FRAT is a tool that supports the decision. AeroVigil's FRAT guide covers the tool in detail.

Is a pre-flight security assessment legally required?

The duty to assess and manage the security risk of an operation rests with the operator under ICAO Annex 6 and Annex 17, reinforced by the conflict-zone risk-assessment expectation set out in ICAO Doc 10084 after MH17. National regulators translate these standards into binding requirements, so the specific legal obligation depends on the operator's state of registry. The direction is consistent: operators are expected to conduct their own assessment rather than rely solely on the overflown state.

How often should a route be re-assessed?

A route should be re-assessed whenever the threat picture materially changes, not only on a fixed schedule. Security risk near conflicts can shift within hours, so an assessment valid at dispatch may need revision before departure or in flight. Continuous monitoring, rather than a one-time check, is the standard a robust process is built to meet.

Can a flight be legal to operate but still fail a security assessment?

Yes. Airspace that a state keeps legally open can still be assessed as unacceptable to cross, and an airport operating normally can still sit in an unacceptable security environment. The purpose of the assessment is precisely to catch the risks that legal access hides. MH17 crossed airspace that was legally open at its flight level.

What makes a pre-flight security assessment defensible?

A defensible assessment is one whose sources are graded, whose reasoning is recorded, and whose decision can be reconstructed after the fact. It names the intelligence it relied on, states what was decided and why, and identifies who made the call. Attribution and record-keeping are what separate a defensible decision from a guess.

Methodology

AeroVigil produces aviation security intelligence using an analyst-in-the-loop model: automated collection surfaces signals, and human analysts grade, corroborate and escalate them. Sources are rated on a two-axis reliability-and-credibility scale derived from the Admiralty (NATO) system, and a single uncorroborated open-source report is never treated as an alert on its own. Volatile, country-specific exposure is maintained on the live flight risk feed rather than frozen into evergreen articles. For the full description of sources, grading and standards, see the methodology page.