It can provide the AIS itself — Page 353, Lesson 473

Let’s pick this up right where the material gets interesting — the legal and operational framework of the Aeronautical Information Service, or AIS. First, I want to clarify the opening point about how a State can provide this service. A Contracting State — that’s a country that has signed the Chicago Convention — has three options. It can provide the AIS itself. It can join with one or more other Contracting States to provide a joint service. Or it can delegate the authority for the service to a non-governmental agency — but only on one strict condition: that the Standards and Recommended Practices of Annex 15 are adequately met. Annex 15 is the ICAO document that governs aeronautical information services, so even if a private company runs the service, the standards don’t get watered down. Now, section 18.4 — Responsibilities. This is the heart of accountability. The State concerned shall remain responsible for the information published. That means even if it delegates the work, the State still owns the legal responsibility. Aeronautical information published for and on behalf of a State must clearly indicate that it is published under the authority of that State — so there’s never any doubt who is accountable for what you’re reading. Each Contracting State must take all necessary measures to ensure that the aeronautical information and data it provides is adequate, of required quality, and timely. And note the scope of that duty — it covers the State’s own territory, plus areas outside its territory where the State is responsible for air traffic services. So if a State controls airspace over the ocean, it still has to feed good data to the AIS for that area. This also includes arrangements for the timely provision of required information to the AIS by each of the State services associated with aircraft operations — things like air traffic control, meteorology, and aerodrome operators all have to get their data to the AIS on time. Section 18.5 — Availability. Generally, the AIS operates on a 24-hour-a-day basis. But if a 24-hour service is not provided, there’s a specific rule. The service must be available during the whole period an aircraft is in flight in the area of responsibility of that AIS, plus a period of at least two hours before and after such a period. So if an aircraft is flying in that area from 10:00 to 12:00, the AIS must be open from 08:00 to 14:00 at minimum. And the service must also be available at such other times as may be requested by an appropriate ground organization — so a ground handler can ask for extended hours and the AIS has to comply. Section 18.6 — Sources of Information. The AIS is required to provide a pre-flight information service — that’s the briefing a crew gets before departure — as well as in-flight information. And the information comes from the aeronautical information services of other States and from other sources that may be available. So the AIS is not just a local office; it’s a hub that pulls in data from abroad. Section 18.7 — Requirements of the Service. This is where the quality control gets strict. Aeronautical information distributed by the AIS must be verified by and attributable to the State of Origin. The State of Origin is the State that produced the information in the first place. If that verification is not possible when the information is distributed, then the information must be clearly identified as such — meaning it has to be flagged as unverified so nobody mistakes it for authoritative data. The AIS also has a duty to make available any information necessary for the safety, regularity, or efficiency of air navigation to any other State that requires the information. So it’s a sharing obligation — no hoarding data that another country needs. And finally, the information provided must be in a form suitable for the operational requirements of flight operations personnel — and the excerpt names them specifically: flight crews, flight planning, and flight — that last one trails off into flight operations generally. The point is, the data has to be packaged the way the people who actually fly and plan flights need it, not in some abstract format. So the whole picture here is: the State is accountable, the data must be traceable to its origin, the service must be available when aircraft are moving, and the output must be usable by the people who depend on it for safe and efficient flight.