Bilateral Aviation Safety Agreement (BASA)

A Bilateral Aviation Safety Agreement, or BASA, is an agreement between the governments of two states that establishes a framework for their civil aviation authorities to accept parts of each other's safety findings and approvals, so that a product certified in one jurisdiction does not have to be certified entirely from scratch in the other. The high-level BASA is an executive-level agreement between the two governments; on its own it sets intent and scope rather than operational detail. The real substance lives in the Implementation Procedures that sit beneath it, which spell out precisely which approvals each authority will accept, under what conditions, and through what interface between the two technical staffs.

The Implementation Procedures come in several forms depending on the domain. Implementation Procedures for Airworthiness (IPA) — called Technical Implementation Procedures (TIP) in the specific case of the agreement between the United States and the European Union — cover design approval, production, export airworthiness approvals, and continued support of type-certificated products. Maintenance Implementation Procedures (MIP), documented for the EU–US relationship in the Maintenance Annex Guidance (MAG), cover reciprocal acceptance of maintenance-organization approvals. Where two authorities go further, Implementation Procedures for Licensing (IPL) can address personnel licensing, though this is far less common than airworthiness and maintenance cooperation. The distinction matters: the BASA is the umbrella, and the IPA/TIP, MIP/MAG, and any IPL are the working documents that make it operate.

The FAA–EASA relationship is the principal example. It rests on the U.S.–European Union Bilateral Aviation Safety Agreement, with airworthiness cooperation governed by the Technical Implementation Procedures and maintenance cooperation by the Maintenance Annex Guidance. Under this framework the FAA and EASA validate and, increasingly, simply accept each other's design and production approvals within an agreed scope, which is why a type certificate, a supplemental type certificate, or a maintenance-organization approval issued on one side of the Atlantic can be recognized on the other far more efficiently than an independent, full re-certification would allow. The agreement underpins the flow of certificates and approvals — type certificates, parts approvals, export certificates of airworthiness, and maintenance approvals — across the border.

Two distinctions are essential. First, a BASA is not the same as pilot-licence recognition. Even where a comprehensive BASA exists, a pilot generally still has to convert a licence through the receiving authority's own process — for EASA, the third-country licence conversion route under Part-FCL — because personnel licensing is usually outside the airworthiness-and-maintenance core of these agreements. The presence of a BASA between two states says little about how easily a pilot can fly on the other side's certificate. Second, a BASA is broader and more active than the mutual recognition already built into the Chicago Convention. Article 33 of the Convention obliges each contracting state to recognize certificates of airworthiness and licences issued by the State of Registry, provided they meet ICAO standards — but that is recognition of the registering state's own documents on aircraft it has registered. A BASA goes further, letting one authority accept the certification and approval work of the other for products and organizations, which Article 33 alone does not provide.

For most flight schools and training organizations, a BASA operates in the background rather than the foreground: it is the reason the aircraft, parts, and maintenance approvals the school depends on move efficiently between the FAA and EASA systems, keeping fleet acquisition, spares supply, and maintenance arrangements workable across borders. A school buying a European type into a US operation, or the reverse, benefits directly from the airworthiness and maintenance acceptance the agreement provides.

The distinction that most often trips up schools and their students is the licensing one. Prospective pilots frequently assume that because a strong FAA–EASA BASA exists, an FAA certificate will simply transfer to EASA or vice versa. It does not: licence conversion remains a separate process governed by each authority's own rules, such as the EASA third-country licence conversion pathway. A school advising international students, or one running combined operations across both systems, needs to keep the airworthiness benefits of a BASA clearly separated from the personal-licensing steps its students still have to complete.

Aviatize's Digital Data & Records and Maintenance Control modules keep an aircraft's certification and airworthiness documentation — type-certificate basis, airworthiness certificates, and maintenance approvals — organized and current, which matters when a fleet spans authorities whose acceptance of each other's approvals rests on a BASA and its implementation procedures.

On the licensing side, Aviatize's Training Management module tracks each pilot's and student's certificates, ratings, and the conversion steps still required to fly under a given authority, so a school advising international students can keep the airworthiness recognition a BASA provides separate from the licence-conversion work that remains each student's own responsibility.