xmlns:atom="http://www.w3.org/2005/Atom" xmlns:atom="http://www.w3.org/2005/Atom"

[F1ANNEX VIU.K.SPECIFIC REQUIREMENTS FOR THE PROVIDERS OF AERONAUTICAL INFORMATION SERVICES (Part-AIS)

SUBPART B – ADDITIONAL TECHNICAL REQUIREMENTS FOR PROVIDERS OF AERONAUTICAL INFORMATION SERVICES (AIS.TR)U.K.

SECTION 2 – DATA QUALITY MANAGEMENT

AIS.TR.200 GeneralU.K.
(a)

The accuracy of aeronautical data shall be in conformity with the ‘Aeronautical Data Catalogue’ referred to in ICAO PANS-AIM (Doc 10066).

(b)

The resolution of aeronautical data shall be commensurate with the actual data accuracy.

(c)

The integrity of aeronautical data shall be maintained. Based on the integrity classification specified in the aeronautical data catalogue, procedures shall be put in place so that:

(1)

for routine data as defined in ICAO PANS-AIM, corruption is avoided throughout the processing of the data;

(2)

for essential data as defined in ICAO PANS-AIM, corruption does not occur at any stage of the entire process and additional processes are included, as needed, to address potential risks in the overall system architecture to further assure data integrity at this level;

(3)

for critical data as defined in ICAO PANS-AIM, corruption does not occur at any stage of the entire process and additional integrity assurance processes are included to fully mitigate the effects of faults identified by thorough analysis of the overall system architecture as potential data integrity risks.

(d)

The traceability of aeronautical data shall be ensured.

(e)

The timeliness of the aeronautical data shall be ensured, including any limits on the effective period of the data.

(f)

The completeness of the aeronautical data shall be ensured.

(g)

The format of delivered data shall be adequate to ensure that the data is interpreted in a manner that is consistent with its intended use.

AIS.TR.210 Exchange of aeronautical data and aeronautical informationU.K.

Except for terrain data, the exchange format of aeronautical data shall:

(a)

enable the exchange of data for both individual features and feature collections;

(b)

enable the exchange of baseline information as a result of permanent changes;

(c)

be structured in accordance with the subjects and properties of the aeronautical data catalogue, and be documented through a mapping between the exchange format and the aeronautical data catalogue.

AIS.TR.220 VerificationU.K.
(a)

The verification shall ensure that:

(1)

the aeronautical data was received without corruption;

(2)

the aeronautical data process does not introduce corruption.

(b)

Aeronautical data and aeronautical information entered manually shall be subject to independent verification to identify any errors that may have been introduced.

AIS.TR.225 MetadataU.K.

The metadata to be collected shall include, as a minimum:

(a)

the identification of the organisations or entities performing any action of originating, transmitting or manipulating the aeronautical data;

(b)

the action performed;

(c)

the date and time the action was performed.

AIS.TR.235 Error reporting, error measurement and corrective actionsU.K.

The error reporting, error measurement and corrective mechanisms shall ensure that:

(a)

problems identified during origination, production, storage, handling and processing, or those reported by users after publication, are recorded;

(b)

all problems reported in relation to the aeronautical data and aeronautical information are analysed by the AIS provider and the necessary corrective actions are performed;

(c)

priority is given to resolution of all errors, inconsistencies and anomalies detected in critical and essential aeronautical data;

(d)

affected users are warned of errors by the most effective means, taking into account the integrity level of the aeronautical data and aeronautical information;

(e)

error feedback is facilitated and encouraged.

AIS.TR.240 Data limitationsU.K.

The identification of data not meeting the DQRs shall be made with an annotation or by explicitly providing the quality value.

SECTION 3 – AERONAUTICAL INFORMATION PRODUCTS

AIS.TR.300 General – Aeronautical information productsU.K.
(a)

Aeronautical information products intended for distribution shall be in English.

(b)

Place names shall be spelt in conformity with local usage and transliterated, when necessary, into the International Organization for Standardization (ISO) basic Latin alphabet.

(c)

International Civil Aviation Organization (ICAO) abbreviations shall be used in the aeronautical information products whenever they are appropriate.

Chapter 1 – Aeronautical information in a standardised presentation

AIS.TR.305 Aeronautical information publication (AIP)U.K.
(a)

The AIP, AIP amendments and AIP supplements shall be provided as an ‘electronic AIP’ (eAIP). The eAIP shall allow for displaying on computer screen and printing on paper. In addition, the AIP, AIP amendments and AIP supplements may also be provided on paper.

(b)

The AIP shall include:

(1)

a statement of the competent authority responsible for the air navigation facilities, services or procedures covered by the AIP;

(2)

the general conditions under which the services or facilities are available for use;

(3)

a list of significant differences between the regulations and practices of the United Kingdom and, where available, the Crown Dependencies, and the related ICAO Standards and Recommended Practices (SARPs) and Procedures;

(4)

the choice made by a State in each significant case where an alternative course of action is provided for in the ICAO SARPs and procedures.

(c)

The AIP shall contain information related to, and arranged under, the subject headings listed in the Contents of the Aeronautical Information Publication (AIP) in PANS-AIM (Doc 10066).

(d)

The issuer and AIS provider shall be clearly indicated.

(e)

Each AIP shall be self-contained and include a table of contents.

(g)

An AIP shall be organised in three parts (GEN, ENR and AD), sections and subsections, except when the AIP, or a volume of the AIP, is designed to facilitate operational use in flight, in which case the precise format and arrangement are not prescribed provided that an adequate table of contents is included.

(h)

Each AIP shall be dated.

(i)

The date, consisting of the day, month (by name), and year, shall be the publication date or the AIRAC effective date.

(j)

When describing periods of activity, availability or operation, the applicable days and times shall be specified.

(k)

Each AIP volume issued in printing format and each page of an AIP issued in printing format shall be annotated to clearly indicate:

(1)

the identity of the AIP;

(2)

the territory covered and its subdivisions, when necessary;

(3)

the identification of the issuing State and producing organisation (authority); and

(4)

page numbers/chart titles.

(l)

Any amendment to the volume of the AIP issued in printing format shall be clearly identifiable by means of replacement pages.

AIS.TR.310 AIP amendmentsU.K.
(a)

Any operationally significant changes to the AIP, in accordance with point AIS.OR.505, shall be issued under AIRAC and clearly identified as such.

(b)

Each AIP amendment shall be allocated a serial number, which shall be consecutive.

(c)

When an AIP amendment is issued, it shall include references to the serial number of the NOTAM which have been incorporated into the amendment.

(d)

The most current update cycles applicable to AIP amendments shall be made publicly available.

(e)

Recourse to hand amendments/annotations shall be kept to a minimum; the normal method of amendment shall be by reissuing or by replacement of pages.

(f)

Each AIP amendment shall:

(1)

include a checklist with the current dates and numbers of each loose-leaf page in the AIP; and

(2)

provide a recapitulation of any outstanding hand amendments.

(g)

New or revised information shall be identified by an annotation against it in the margin.

(h)

Each AIP amendment page, including the cover sheet, shall contain a publication date and, when applicable, an effective date.

(i)

The regular intervals between the AIP amendments shall be specified in Part 1 – General (GEN) of the AIP.

AIS.TR.315 AIP supplementsU.K.
(a)

AIP supplements issued in printing format shall be provided by means of distinctive pages.

(b)

The most current update cycles applicable to AIP supplements shall be made publicly available.

(c)

Each AIP supplement shall be allocated a serial number which shall be consecutive and based on the calendar year.

(d)

Whenever an AIP supplement is issued as a replacement of a NOTAM, a reference to the series and number of the NOTAM shall be included.

(e)

A checklist of valid AIP supplements shall be issued at intervals of not more than one month, as part of the checklist of NOTAM and also with distribution as for the AIP supplements.

(f)

Each AIP supplement page shall have a publication date. Each AIRAC AIP supplement page shall have both a publication and an effective date.

AIS.TR.320 Aeronautical information circular (AIC)U.K.
(a)

The AIC shall be provided as an electronic document.

(b)

The AIC shall be provided whenever it is desirable to promulgate:

(1)

forecasts of important changes in the air navigation procedures, services and facilities;

(2)

forecasts of implementation of new navigational systems;

(3)

significant information derived from aircraft accident/incident investigation which has a bearing on flight safety;

(4)

information on regulations related to the safeguarding of civil aviation against acts of unlawful interference that jeopardise the security of civil aviation;

(5)

advice on medical matters of special interest to pilots;

(6)

warnings to pilots concerning the avoidance of physical hazards;

(7)

information on the effect of certain weather phenomena on aircraft operations;

(8)

information on new hazards affecting aircraft handling techniques;

(9)

information on regulations related to the carriage of restricted articles by air;

(10)

references to the requirements of national and EU legislation and to the publication of changes therein;

(11)

information on aircrew licensing arrangements;

(12)

information on training of aviation personnel;

(13)

information on the implementation of, or exemption from, requirements in national and EU legislation;

(14)

advice on the use and maintenance of specific types of equipment;

(15)

the actual or planned availability of new or revised editions of aeronautical charts;

(16)

information on the carriage of communication equipment;

(17)

explanatory information related to noise abatement;

(18)

selected airworthiness directives;

(19)

information on changes in NOTAM series or distribution, new editions of AIP or major changes in their content, coverage or format;

(20)

advance information on the snow plan; and

(21)

other information of a similar nature.

(c)

The AIC shall not be used for information that qualifies for inclusion in AIP or NOTAM.

(d)

The snow plan issued in accordance with point AD 1.2.2 of the AIP shall be supplemented by seasonal information to be issued as an AIC well in advance of the beginning of each winter – not less than one month before the normal onset of winter conditions.

(e)

When the AIC is selected for international distribution it shall have the same distribution as the AIP.

(f)

Each AIC shall be allocated a serial number which shall be consecutive and based on the calendar year.

(g)

In the event that an AIC is provided in more than one series, each series shall be separately identified by a letter.

(h)

A checklist of AIC currently in force shall be issued at least once a year, with distribution as for the AIC.

(i)

A checklist of AIC provided internationally shall be included in the NOTAM checklist.

AIS.TR.330 NOTAMU.K.
(a)

A NOTAM shall be issued when it is necessary to provide the following information:

(1)

establishment of, closure of, or significant changes in the operation of aerodromes or heliports or runways;

(2)

establishment of, withdrawal of, and significant changes in, the operation of aeronautical services;

(3)

establishment of, withdrawal of, and significant changes in, the operational capability of radio navigation and air-ground communication services;

(4)

unavailability of backup and secondary systems, having a direct operational impact;

(5)

establishment of, withdrawal of, or significant changes to, visual aids;

(6)

interruption of, or return to operation of, major components of aerodrome lighting systems;

(7)

establishment of, withdrawal of, or significant changes to, procedures for air navigation services;

(8)

occurrence or correction of major defects or impediments in the manoeuvring area;

(9)

changes to, and limitations on, the availability of fuel, oil and oxygen;

(10)

major changes to search and rescue (SAR) facilities and services available;

(11)

establishment of, withdrawal of, or return to, operation of hazard beacons marking obstacles to air navigation;

(12)

changes in regulations applicable in the State(s) concerned that require immediate action from an operational perspective;

(13)

operational directives requiring immediate action or changes thereto;

(14)

presence of hazards that affect air navigation;

(15)

planned laser emissions, laser displays and search lights if pilots’ night vision is likely to be impaired;

(16)

erecting or removal of, or changes to, obstacles to air navigation in the take-off or climb, missed approach, approach areas as well as on the runway strip;

(17)

establishment or discontinuance of, including activation or deactivation, as applicable, or changes in, the status of prohibited, restricted or danger areas;

(18)

establishment or discontinuance of areas or routes, or portions of areas or routes, where the possibility of interception exists and where the maintenance of guard on the very high frequency (VHF) emergency frequency 121,500 MHz is required;

(19)

allocation, cancellation or change of location indicators;

(20)

changes in aerodrome/heliport rescue and firefighting (RFF) category;

(21)

presence of, removal of, or significant changes in, hazardous conditions due to snow, slush, ice, radioactive material, toxic chemicals, volcanic ash deposition or water on the movement area;

(22)

outbreaks of epidemics necessitating changes in notified requirements for inoculations and quarantine measures;

(23)

forecasts of solar cosmic radiation, where provided;

(24)

an operationally significant change in volcanic activity, the location, date and time of volcanic eruptions, or the horizontal and vertical extent of a volcanic ash cloud, including direction of movement, flight levels and routes or portions of routes that could be affected;

(25)

release into the atmosphere of radioactive materials or toxic chemicals following a nuclear or chemical incident, the location, date and time of the incident, the flight levels and routes, or portions of these, that could be affected, as well as the direction of movement;

(26)

establishment of operations of humanitarian relief missions, together with procedures or limitations that affect air navigation;

(27)

implementation of short-term contingency measures in cases of disruption, or partial disruption, of ATS and related supporting services;

(28)

specific loss of integrity of satellite-based navigation systems.

(29)

unavailability of a runway due to runway marking works or, if the equipment used for those works can be removed, a time lag required for making the runway available.

(b)

A NOTAM shall not be issued to provide any of the following information:

(1)

routine maintenance work on aprons and taxiways that does not affect the safe movement of aircraft;

(2)

temporary obstructions in the vicinity of aerodromes/heliports that do not affect the safe operation of aircraft;

(3)

partial failure of aerodrome/heliport lighting facilities where such failure does not directly affect aircraft operations;

(4)

partial temporary failure of air-ground communications when suitable alternative frequencies are available and are operative;

(5)

lack of apron marshalling services, road traffic closures, limitations and control;

(6)

the unserviceability of location, destination or other instruction signs on the aerodrome movement area;

(7)

parachuting when in uncontrolled airspace under visual flight rules (VFR), nor when in controlled airspace at promulgated sites or within danger or prohibited areas;

(8)

training activities performed by ground units;

(9)

unavailability of backup and secondary systems if these do not have an operational impact;

(10)

limitations to airport facilities or general services, with no operational impact;

(11)

national regulations not affecting general aviation;

(12)

announcements or warnings about possible/potential limitations, with no operational impact;

(13)

general reminders on already published information;

(14)

availability of equipment for ground units, without information on the operational impact on airspace and facility users;

(15)

information about laser emissions with no operational impact and about fireworks below the minimum flying heights;

(16)

closure of parts of the movement area in connection with locally coordinated, planned work of duration of less than one hour;

(17)

closure, changes, unavailability in the operation of aerodrome(s)/ heliport(s) other than in the aerodrome(s)/heliport(s) operation hours; and

(18)

other non-operational information of a similar temporary nature.

(c)

Except as provided for in points AIS.TR.330(f) and AIS.TR.330(g), each NOTAM shall contain the information in the order referred to in the NOTAM FORMAT in PANS-AIM (Doc 10066)

(d)

NOTAM text shall be composed of the significations/uniform abbreviated phraseology assigned to the ICAO NOTAM Code, complemented by ICAO abbreviations, indicators, identifiers, designators, call signs, frequencies, figures and plain language.

(e)

All NOTAM shall be issued in English language.

(f)

Information concerning snow, slush, ice, frost, standing water or water associated with snow, slush, ice or frost on the movement area shall be disseminated by means of SNOWTAM and shall contain the information in the order referred to in the SNOWTAM format in PANS-AIM (Doc 10066).

(g)

Information concerning an operationally significant change to volcanic activity, volcanic eruption or volcanic ash cloud shall, when reported by means of an ASHTAM, contain the information in the order referred to in the ASHTAM format in PANS-AIM (Doc 10066).

(h)

When errors occur in a NOTAM, a NOTAM with a new number shall be issued to replace the erroneous NOTAM or the erroneous NOTAM shall be cancelled and a new NOTAM shall be issued.

(i)

When a NOTAM is issued that cancels or replaces a previous NOTAM:

(1)

the series and number/year of the previous NOTAM shall be indicated;

(2)

the series, location indicator and subject of both NOTAM shall be the same.

(j)

Only one NOTAM shall be cancelled or replaced by a NOTAM.

(k)

Each NOTAM shall deal with only one subject and one condition of the subject.

(l)

Each NOTAM shall be as brief as possible and compiled so that its meaning is clear without the need to refer to another document.

(m)

A NOTAM containing permanent or temporary information of long duration (three months or longer) shall include appropriate references to the AIP or AIP supplement.

(n)

Location indicators included in the text of a NOTAM shall be those contained in ICAO Doc 7910. A curtailed form of such indicators shall not be used. Where no ICAO location indicator is assigned to the location, its place name shall be entered in plain language.

(o)

A series identified by a letter and a four-digit number followed by a stroke and a two-digit number for the year shall be allocated to each NOTAM. The four-digit number shall be consecutive and based on the calendar year.

(p)

All NOTAM shall be divided in series based on subject, traffic or location or a combination of these, depending on end-user needs. NOTAM for aerodromes allowing international air traffic shall be issued in international NOTAM series.

(q)

If NOTAM are issued in both English and national language, the NOTAM series shall be organised so that the national language series are equivalent to the English language series in terms of content and numbering.

(r)

The content and geographical coverage of each NOTAM series shall be stated in detail in the AIP, in point GEN 3.

(s)

A checklist of valid NOTAM shall be regularly provided.

(t)

One checklist NOTAM shall be issued for each series.

(u)

A checklist NOTAM shall also refer to the latest AIP amendments, AIP supplements, data sets and, at least, to distributed AIC.

(v)

A checklist NOTAM shall have the same distribution as the actual message series to which it refers and shall be clearly identified as a checklist.

(w)

Series allocation shall be monitored and, if required, appropriate measures shall be taken to assure that no series reaches the maximum possible number of issued NOTAM before the end of a calendar year.

Chapter 2 – Digital data sets

AIS.TR.335 General— Digital data setsU.K.
(a)

A standard for geographic information shall be used as a reference framework.

(b)

A description of each available data set shall be provided in the form of a data product specification.

(c)

A checklist of the available data sets, including their effective and publication dates, shall be made available to users to ensure that current data is being used.

(d)

The checklist of data sets shall be made available through the same distribution mechanism as the one used for the data sets.

AIS.TR.340 Metadata requirementsU.K.

The minimum metadata for each data set shall include:

(a)

the name of the organisations or entities providing the data set;

(b)

the date and time when the data set was provided;

(c)

the validity of the data set; and

(d)

any limitations on the use of the data set.

AIS.TR.345 AIP data setU.K.
(a)

The AIP data set shall include data about the following subjects, including the properties indicated, if applicable:

Data subjectsAssociated properties as a minimum
Aerodrome/heliportLocation, indicator, name, International Air Transport Association (IATA) designator, served city, certification date, certification expiration date, if applicable, control type, field elevation, reference temperature, magnetic variation, airport reference point.
ATS airspaceType, name, lateral limits, vertical limits, class of airspace
Final approach and take-off areaDesignation, length, width, threshold point
Radio navigation aidType identification, name, aerodrome served, hours of operation, magnetic variation, frequency/channel, position, elevation, magnetic bearing, zero bearing direction
RouteIdentifier prefix, flight rules, designator
Route segmentNavigation specification, start point, end point, track, distance, upper limit, lower limit, minimum en route altitude (MEA), minimum obstacle clearance altitude (MOCA), direction of cruising level, reverse direction of cruising level, required navigation performance
RunwayDesignator, nominal length, nominal width, surface type, strength
Runway directionDesignator, true bearing, threshold, take-off run available (TORA), take-off distance available (TODA), accelerate-stop distance available (ASDA), landing distance available (LDA), rejected TODA (for helicopters)
Special activity airspaceType, name, lateral limits, vertical limits, restriction, activation
Touch down and lift-off area (TLOF)Designator, centre point, length, width, surface type
Waypoint – en routeReporting requirement, identification, location, formation
(b)

When a property is not defined for a particular occurrence of the subjects listed in (a), the AIP data subset shall include an explicit indication: ‘not applicable’.

AIS.TR.350 Terrain and obstacle data – General requirementsU.K.

The coverage areas for sets of terrain and obstacle data shall be specified as:

(a)

Area 1: the entire territory of a State;

(b)

Area 2: within the vicinity of an aerodrome, subdivided as follows:

(1)

Area 2a: a rectangular area around a runway which comprises the runway strip plus any clearway that exists;

(2)

Area 2b: an area extending from the ends of Area 2a in the direction of departure, with a length of 10 km and a splay of 15 % to each side;

(3)

Area 2c: an area extending outside Areas 2a and 2b at a distance of not more than 10 km from the boundary of Area 2a; and

(4)

Area 2d: an area outside Areas 2a, 2b and 2c up to a distance of 45 km from the aerodrome reference point, or to an existing terminal manoeuvring area (TMA) boundary, whichever is nearer;

(c)

Area 3: the area bordering an aerodrome movement area which extends horizontally from the edge of a runway to 90 m from the runway centre line and 50 m from the edge of all other parts of the aerodrome movement area; and

(d)

Area 4: the area extending 900 m prior to the runway threshold and 60 m to each side of the extended runway centre line in the direction of the approach on a precision approach runway, Category II or III.

AIS.TR.355 Terrain data setsU.K.

When terrain data sets are provided in accordance with point AIS.OR.355:

(a)

terrain data sets shall contain the digital representation of the terrain surface in the form of continuous elevation values at all intersections of a defined grid, referenced to a common datum;

(b)

a terrain grid shall be angular or linear and shall be of a regular or irregular shape;

(c)

terrain data sets shall include spatial (position and elevation), thematic, and temporal aspects of the surface of the Earth, containing naturally occurring features, excluding obstacles;

(d)

only one feature type, i.e. terrain, shall be provided;

(e)

the following terrain feature attributes shall be recorded in the terrain data set:

(1)

area of coverage;

(2)

identification of the data originator;

(3)

data source identifier;

(4)

acquisition method;

(5)

post spacing;

(6)

horizontal reference system;

(7)

horizontal resolution;

(8)

horizontal accuracy;

(9)

horizontal confidence level;

(10)

horizontal position;

(11)

elevation;

(12)

elevation reference;

(13)

vertical reference system;

(14)

vertical resolution;

(15)

vertical accuracy;

(16)

vertical confidence level;

(17)

recorded surface;

(18)

integrity;

(19)

date and time stamp; and

(20)

unit of measurement used;

(f)

within the area covered by a 10-km radius from the ARP, terrain data shall comply with the Area 2 numerical requirements;

(g)

in the area between 10 km and the TMA boundary or a 45-km radius, whichever is smaller, data on terrain that penetrates the horizontal plane 120 m above the lowest runway elevation shall comply with the Area-2 numerical requirements;

(h)

in the area between 10 km and the TMA boundary or a 45-km radius, whichever is smaller, data on terrain that does not penetrate the horizontal plane 120 m above the lowest runway elevation shall comply with the Area-1 numerical requirements; and

(i)

in those portions of Area 2 where flight operations are prohibited due to very high terrain or other local restrictions or other local restrictions or regulations, terrain data shall comply with the Area 1 numerical requirements.

The following diagram contains a graphical illustration of Area 1 and Area 2 terrain data collection surfaces:

Terrain data collection surfaces – Area 1 and Area 2

AIS.TR.360 Obstacle data setsU.K.

When obstacle data sets are provided in accordance with point AIS.OR.360:

(a)

obstacle data items are features that shall be represented in the data sets by points, lines or polygons;

(b)

all defined obstacle feature types shall be provided and each of them shall be described according to the following list of attributes:

(1)

area of coverage;

(2)

identification of the data originator;

(3)

data source identifier;

(4)

obstacle identifier;

(5)

horizontal accuracy;

(6)

horizontal confidence level;

(7)

horizontal position;

(8)

horizontal resolution;

(9)

horizontal extent;

(10)

horizontal reference system;

(11)

elevation;

(12)

vertical accuracy;

(13)

vertical confidence level;

(14)

vertical resolution;

(15)

vertical reference system;

(16)

obstacle type;

(17)

geometry type;

(18)

integrity;

(19)

date and time stamp;

(20)

unit of measurement used;

(21)

lighting; and

(22)

marking;

(c)

obstacle data for Areas 2 and 3 shall be collected in accordance with the following obstacle collection surfaces:

(1)

the Area 2a obstacle collection surface has a height of 3 m above the nearest runway elevation measured along the runway centre line, and for those portions related to a clearway, if one exists, at the elevation of the nearest runway end;

(2)

the Area 2b obstacle collection surface has a 1.2 % slope extending from the ends of Area 2a at the elevation of the runway end in the direction of departure, with a length of 10 km and a splay of 15 % to each side; obstacles less than 3 m in height above the ground need not be collected;

(3)

the Area 2c obstacle collection surface has a 1.2 % slope extending outside Areas 2a and 2b at a distance of not more than 10 km from the boundary of Area 2a; the initial elevation of Area 2c shall be the elevation of the point of Area 2a at which it commences; obstacles less than 15 m in height above the ground need not be collected;

(4)

the Area 2d obstacle collection surface has a height of 100 m above the ground; and

(5)

the Area 3 obstacle collection surface extends 0.5 m above the horizontal plane passing through the nearest point on the aerodrome movement area;

(d)

in those portions of Area 2 where flight operations are prohibited due to very high terrain or other local restrictions or regulations, obstacle data shall be collected and recorded in accordance with the Area 1 numerical requirements;

(e)

the obstacle data product specification, supported by geographical coordinates for each aerodrome included within the dataset, shall describe the following areas:

(1)

Areas 2a, 2b, 2c and 2d;

(2)

the take-off flight path area; and

(3)

the obstacle limitation surfaces;

(f)

obstacle data sets shall contain the digital representation of the vertical and horizontal extent of the obstacles; and

(g)

obstacles shall not be included in terrain data sets.

The following diagram contains a graphical illustration of Area 1 and Area 2 obstacle data collection surfaces and criteria used to identify obstacles in Area 2.

Obstacle data collection surfaces – Area 1 and Area 2

AIS.TR.365 Aerodrome mapping data setsU.K.
(a)

Aerodrome mapping data sets shall contain the digital representation of aerodrome features.

(b)

ISO standards for geographic information shall be used as a reference framework.

(c)

Aerodrome mapping data products shall be described following the relevant data product specification standard.

(d)

The content and structure of aerodrome mapping data sets shall be defined in terms of an application schema and a feature catalogue.

AIS.TR.370 Instrument flight procedure data setsU.K.
(a)

Instrument flight procedure data sets shall contain the digital representation of instrument flight procedures.

(b)

The instrument flight procedure data sets shall include data about the following subjects, including all of their properties:

(1)

procedure;

(2)

procedure segment;

(3)

final approach segment;

(4)

procedure fix;

(5)

procedure holding;

(6)

helicopter procedure specifics.

SECTION 4 – DISTRIBUTION AND PRE-FLIGHT INFORMATION SERVICES
AIS.TR.400 Distribution servicesU.K.
(a)

A predetermined distribution system for NOTAM transmitted on the AFS shall be used whenever possible.

(b)

Distribution of NOTAM series other than those distributed internationally shall be granted upon request.

(c)

NOTAM shall be prepared in conformity with ICAO communication procedures laid down in ICAO Annex 10, Volume II (Seventh Edition, July 2016) to the Chicago Convention.

(d)

Each NOTAM shall be transmitted as a single telecommunication message.

(e)

The international exchange of ASHTAM and NOTAM where NOTAM is used for distribution of information on volcanic activity, shall include volcanic ash advisory centres and the world area forecast centres, and take account of the requirements of long-range operations.

AIS.TR.405 Pre-flight information servicesU.K.
(a)

Automated pre-flight information systems shall be used to make aeronautical data and aeronautical information available to operations personnel, including flight crew members, for self-briefing, flight planning and flight information service purposes.

(b)

The human machine interface of the pre-flight information services facilities shall ensure easy access to all relevant information or data in a guided manner.

(c)

Self-briefing facilities of an automated pre-flight information system shall provide access, as necessary, to the aeronautical information service for consultation by telephone or other suitable telecommunication means.

(d)

Automated pre-flight information systems for the supply of aeronautical data and aeronautical information for self-briefing, flight planning and flight information service shall:

(1)

provide for continuous and timely updating of the system database and monitoring of the validity and quality of the aeronautical data stored;

(2)

permit access to the system by operations personnel, including flight crew members, aeronautical personnel concerned and other aeronautical users, through suitable telecommunications means;

(3)

ensure the provision of the aeronautical data and aeronautical information accessed, in paper form, as required;

(4)

use access and interrogation procedures based on abbreviated plain language and ICAO location indicators laid down in ICAO Doc 7910, as appropriate, or based on a menu-driven user interface or other appropriate mechanism;

(5)

provide a timely response to a user request for information.

(e)

All NOTAM shall be made available for briefing by default, and content reduction shall be at user’s discretion.

SECTION 5 – AERONAUTICAL INFORMATION PRODUCTS UPDATES
AIS.TR.500 General – Aeronautical information products updatesU.K.

The same AIRAC cycle update shall be applied to the AIP amendments, AIP supplements, AIP data set and the instrument flight procedure data sets in order to ensure consistency of the data items that appear in multiple aeronautical information products.

AIS.TR.505 AIRACU.K.
(a)

Information concerning the following circumstances shall be distributed under the AIRAC system:

(1)

horizontal and vertical limits, regulations and procedures applicable to:

(i)

flight information regions (FIRSs);

(ii)

control areas (CTAs);

(iii)

control zones;

(iv)

advisory areas;

(v)

ATS routes;

(vi)

permanent danger, prohibited and restricted areas (including type and periods of activity, when known) and air defence identification zones (ADIZs);

(vii)

permanent areas or routes, or portions of these, where the possibility of interception exists;

(viii)

RMZ, TMZ or both;

(2)

positions, frequencies, call signs, identifiers, known irregularities and maintenance periods of radio navigation aids, and communication and surveillance facilities;

(3)

holding and approach procedures, arrival and departure procedures, noise abatement procedures and any other pertinent ATS procedures;

(4)

transition levels, transition altitudes and minimum sector altitudes;

(5)

meteorological facilities (including broadcasts) and procedures;

(6)

runways and stopways;

(7)

taxiways and aprons;

(8)

aerodrome ground operating procedures (including low-visibility procedures);

(9)

approach and runway lighting; and

(10)

aerodrome operating minima.

(b)

Special arrangements shall be made whenever major changes are planned and where advance notice is desirable and practicable.

(c)

When information has not been submitted by the AIRAC date, a NIL notification shall be distributed through a NOTAM or other suitable means, not later than one cycle before the AIRAC effective date concerned.

AIS.TR.510 NOTAMU.K.
(a)

A NOTAM shall be published with sufficient lead time for the affected parties to take any required action, except in the case of unserviceability, volcanic activity, release of radioactive material, toxic chemicals and other events that cannot be foreseen.

(b)

A NOTAM notifying unserviceability of aids to air navigation, facilities or communication services shall provide an estimate of the unserviceability period or of the time at which restoration of service is expected.

(c)

Within three months from the issuing of a permanent NOTAM, the information contained in the NOTAM shall be included in the aeronautical information products affected.

(d)

Within three months from the issuing of a temporary NOTAM of long duration (three months or longer), the information contained in the NOTAM shall be included in an AIP supplement.

(e)

When a NOTAM with an estimated end of validity unexpectedly exceeds the three-month period, a replacement NOTAM shall be issued unless the condition is expected to last for a further period of more than three months; in that case, an AIP supplement shall be issued.

(f)

A ‘trigger NOTAM’ shall briefly describe the content, the effective date and time, as well as the reference number of the amendment, or supplement.

(g)

A ‘trigger NOTAM’ shall come into force on the same effective date and time as the AIP amendment or supplement.

(h)

In the case of an AIP amendment, a ‘trigger NOTAM’ shall remain valid for a period of 14 days.

(i)

In the case of an AIP supplement that is valid for less than 14 days, the ‘trigger NOTAM’ shall remain valid for the complete validity period of the AIP supplement.

(j)

In the case of an AIP supplement that is valid for 14 days or more, the ‘trigger NOTAM’ shall remain valid for at least 14 days.

AIS.TR.515 Data set updatesU.K.
(a)

The update interval for the AIP data set and the instrument flight procedure data sets shall be specified in the data product specification.

(b)

Data sets that have been made available in advance, according to the AIRAC cycle, shall be updated with the non-AIRAC changes that occurred between the publication and the effective date.]