Aerodrome Emergency Plan: evidence, not a static file
An Aerodrome Emergency Plan is the obligation to prepare, drill and evidence response at the aerodrome. Under ICAO Annex 14, a document on a shelf is not enough. Drills, activation and occurrences must be recorded in the same operational trail.
What the emergency plan requires
Start with preparedness and responsibilities. To make the work reviewable, preserve scenario, available resources and response ownership. The information becomes useful when the team can identify who observed the condition, when it was recorded and what happened next. A record does not replace professional assessment: it provides the operational context needed to make that assessment.
An operational record should distinguish the observed fact from a later interpretation. For preparedness and responsibilities, record what happened first, associate teams and procedures and keep the sequence of decisions visible. If information is corrected, its history matters too. Without that sequence, a final document may look complete while leaving the source of its conclusions unclear.
In day-to-day work, records of preparedness and responsibilities need definitions that fit the aerodrome. Capturing data during the operation avoids rebuilding context from memory, messages or separate spreadsheets. That connection matters when a shift changes, a responsible person changes or someone needs to examine an earlier occurrence without losing the original circumstances.
The same foundation can hold scenario, available resources and response ownership alongside other operational records while keeping each activity identifiable. This is not an automatic regulatory approval or a substitute for human judgement. It is a reviewable trail through which the team can consult, assess and follow up, with people remaining responsible for the decisions and information they present.
For preparedness and responsibilities, a completed form alone is not enough: it should reflect what actually happened. The team should also be able to consult teams and procedures and verify plan review. That distinction lets a manager separate an initial observation from an assessment and check whether a proposed action was completed.
Explore the Auter airport management foundation and how operational records connect.
Drills, activation and records
Start with drills and activation. To make the work reviewable, preserve date, participants, sequence of activation and observations. The information becomes useful when the team can identify who observed the condition, when it was recorded and what happened next. A record does not replace professional assessment: it provides the operational context needed to make that assessment.
An operational record should distinguish the observed fact from a later interpretation. For drills and activation, record what happened first, associate training and occurrence records and keep the sequence of decisions visible. If information is corrected, its history matters too. Without that sequence, a final document may look complete while leaving the source of its conclusions unclear.
In day-to-day work, records of drills and activation need definitions that fit the aerodrome. Capturing data during the operation avoids rebuilding context from memory, messages or separate spreadsheets. That connection matters when a shift changes, a responsible person changes or someone needs to examine an earlier occurrence without losing the original circumstances.
The same foundation can hold date, participants, sequence of activation and observations alongside other operational records while keeping each activity identifiable. This is not an automatic regulatory approval or a substitute for human judgement. It is a reviewable trail through which the team can consult, assess and follow up, with people remaining responsible for the decisions and information they present.
For drills and activation, a completed form alone is not enough: it should reflect what actually happened. The team should also be able to consult training and occurrence records and verify later assessment. That distinction lets a manager separate an initial observation from an assessment and check whether a proposed action was completed.
Read about Airport SMS: safety evidence born in the operation on the same operational foundation.
Relationship with SMS and inspections
Start with emergencies and operational routines. To make the work reviewable, preserve observed event, related inspection and movement. The information becomes useful when the team can identify who observed the condition, when it was recorded and what happened next. A record does not replace professional assessment: it provides the operational context needed to make that assessment.
An operational record should distinguish the observed fact from a later interpretation. For emergencies and operational routines, record what happened first, identify the response team and keep the sequence of decisions visible. If information is corrected, its history matters too. Without that sequence, a final document may look complete while leaving the source of its conclusions unclear.
In day-to-day work, records of emergencies and operational routines need definitions that fit the aerodrome. Capturing data during the operation avoids rebuilding context from memory, messages or separate spreadsheets. That connection matters when a shift changes, a responsible person changes or someone needs to examine an earlier occurrence without losing the original circumstances.
The same foundation can hold observed event, related inspection and movement alongside other operational records while keeping each activity identifiable. This is not an automatic regulatory approval or a substitute for human judgement. It is a reviewable trail through which the team can consult, assess and follow up, with people remaining responsible for the decisions and information they present.
For emergencies and operational routines, a completed form alone is not enough: it should reflect what actually happened. The team should also be able to consult response team and verify context of the occurrence. That distinction lets a manager separate an initial observation from an assessment and check whether a proposed action was completed.
Follow the source of records on the airport management platform.
A common standard across the airport portfolio
Start with airports in one group. To make the work reviewable, preserve common record definitions and local conditions. The information becomes useful when the team can identify who observed the condition, when it was recorded and what happened next. A record does not replace professional assessment: it provides the operational context needed to make that assessment.
An operational record should distinguish the observed fact from a later interpretation. For airports in one group, record what happened first, associate management at each aerodrome and keep the sequence of decisions visible. If information is corrected, its history matters too. Without that sequence, a final document may look complete while leaving the source of its conclusions unclear.
In day-to-day work, records of airports in one group need definitions that fit the aerodrome. Capturing data during the operation avoids rebuilding context from memory, messages or separate spreadsheets. That connection matters when a shift changes, a responsible person changes or someone needs to examine an earlier occurrence without losing the original circumstances.
The same foundation can hold common record definitions and local conditions alongside other operational records while keeping each activity identifiable. This is not an automatic regulatory approval or a substitute for human judgement. It is a reviewable trail through which the team can consult, assess and follow up, with people remaining responsible for the decisions and information they present.
For airports in one group, a completed form alone is not enough: it should reflect what actually happened. The team should also be able to consult management at each aerodrome and verify comparison without mixing units. That distinction lets a manager separate an initial observation from an assessment and check whether a proposed action was completed.
Explore multi-airport management and review airport operations cases.
Frequently asked questions
What is an Aerodrome Emergency Plan?
An Aerodrome Emergency Plan sets out preparation and response arrangements for events at the aerodrome. Evidence of the plan includes drills, activations, participants and observations recorded as the work happens. A written plan remains important, but a document on its own does not show how people prepared, responded or reviewed an actual event.
What evidence does Annex 14 expect for an AEP?
Annex 14 provides the international aerodrome context for emergency planning. Reviewable evidence can include the planned response, exercises, activation records and subsequent observations. The operator should distinguish what was planned from what happened and check the requirements applying to its own aerodrome. A completed template alone is not evidence of an effective response.
Should drills and real occurrences share the same record?
Drills and real occurrences may be recorded on the same operational foundation while retaining separate classifications. A drill tests a scenario; a real occurrence documents an actual event. Both benefit from dates, participants, activation sequence and follow-up, but an exercise must not be presented as proof that a response was carried out in an actual incident.
Can AEP evidence live on the operations platform?
Emergency-plan evidence can live alongside movement and occurrence records if the operator can identify each activity and its responsible team. Linking related records helps recover the sequence without reconstructing it later. The platform organises the trail; it cannot replace the plan, the response procedures or the assessment made by qualified people.
Can an airport group standardise AEP evidence across airports?
An airport group can standardise how it records drills and activations while respecting local resources and responsibilities. Each aerodrome keeps its own scenarios, people and occurrence history. A portfolio view helps managers compare the completeness of records, but it cannot assume that a response suitable for one airport applies unchanged to another.