AD/EMY/2 Amdt 6 - Life Jackets and Inflatable Flotation Devices

The directive rests on a short set of core concepts. Each bears on who decides, who pays, what behaviour changes, and where discretion sits.

Applicability: "All life jackets and inflatable flotation devices not subject to a System of Maintenance which are installed or intended to be installed in an aircraft" (Applicability). The phrase "not subject to a System of Maintenance" creates a carve-out; devices covered by a System of Maintenance are outside the AD’s mandatory scope. The inclusion of items "intended to be installed" captures spares and inventory awaiting fitting.

Manufacturer instructions and approved maintenance data: The substantive inspection and testing tasks are to be carried out "in accordance with requirements in instructions issued by the manufacturer" (Requirement). The Compliance clause allows adherence to "the approved maintenance data" as one lawful route. The directive therefore sets manufacturer documentation as the primary technical authority, subject to an approval mechanism that validates maintenance data.

Approved organisations and regulatory approval: The directive expressly requires the inspections and tests "to be undertaken by an organisation approved for the purpose by the Authority" (Requirement). The Authority here is the Civil Aviation Safety Authority, named in the header. Approval is thus a regulatory gate that controls which entities may perform the mandated work.

Dual timing regime: Compliance may follow either approved maintenance data or the default timing: "within two years of date of manufacture and thereafter at intervals not exceeding one year" (Compliance). The Background clarifies that Amendment 6 permits inspection intervals to be "in accordance with manufacturer’s approved data if that allows a period greater than; two years from manufacture, then every year", indicating the AD allows manufacturer data to produce longer intervals than the default.

Component characterisation: The Background states "Life jackets fall within the definition of aircraft components." That labelling aligns life jackets and related inflatable devices with the regulatory regime that applies to aircraft components, bringing them within airworthiness oversight.

Timing and effect: The amendment took effect on 13 August 1998 (Effective date). Amendment 5 is recorded as having incorporated inflatable flotation devices; Amendment 6 amended the inspection interval rule. Those amendments are the textual source’s declared changes.

In short, the directive combines manufacturer-prescribed technical standards, regulator-approved maintenance data and organisations, a two-path timing regime, and a scope that excludes items already covered by a System of Maintenance. Those concepts determine who decides the technical standard (manufacturer), who authorises the performer (the Authority), which items are in scope, and the permitted periodicity for inspections.

The directive identifies three primary groups directly affected by its requirements, and several secondary parties with practical roles.

Aircraft operators and owners: Any operator or owner who has life jackets or inflatable flotation devices "installed or intended to be installed in an aircraft" and whose devices are "not subject to a System of Maintenance" falls within the AD’s applicability (Applicability). That includes aircraft with emergency equipment fitted and organisations that hold devices as spares for installation. These parties bear the practical responsibility to ensure the devices are inspected and tested in accordance with the AD's timing and procedural requirements.

Maintenance organisations: The AD requires that inspections and tests be "undertaken by an organisation approved for the purpose by the Authority" (Requirement). Maintenance organisations that wish to perform the mandated work must obtain approval from the Authority; the AD therefore imposes an authorisation barrier that maintenance providers must clear to service life jackets and inflatable flotation devices covered by the directive.

Manufacturers and holders of approved maintenance data: Because the technical inspection and test requirements are "in accordance with requirements in instructions issued by the manufacturer" and because compliance can be by "the approved maintenance data" (Requirement; Compliance), manufacturers who produce and issue inspection/testing instructions, and those who prepare "approved maintenance data", are central. Their documentation determines permissible inspection content and , under Amendment 6 , can affect inspection interval lengths where that data allows longer periods.

The Civil Aviation Safety Authority (the Authority): The Authority is the approving body that determines which organisations may carry out the inspections and which maintenance data is "approved". The AD does not specify the criteria or process for approval, but it places decisive authority with the regulator by requiring approval for organisations and relating compliance to "approved maintenance data" (Requirement; Compliance).

Suppliers and logistics providers: Firms that supply life jackets and inflatable flotation devices, or manage inventories of them for carriers, are affected operationally because the AD applies to items "intended to be installed" (Applicability). Their inventory management and procurement practices must accommodate periodic inspection and testing, and likely must track manufacture dates to calculate default inspection timing.

Passengers and insurers (indirect): The AD does not address passenger rights or insurance directly. However, by regulating inspection and test regimes for life jackets and flotation devices, it can influence the operational availability and perceived reliability of emergency equipment, factors relevant to insurers and passenger-safety risk assessments. Those effects are inferential rather than explicit in the text.

Who does not fall within the AD: Any life jackets or inflatable flotation devices already "subject to a System of Maintenance" are excluded from the AD's mandatory scope (Applicability). The text does not define "System of Maintenance" further, so parties must check regulatory definitions or existing maintenance arrangements to determine whether devices are excluded.

In summary, primary costs and operational obligations fall on operators/owners and maintenance providers; decision-making power over technical content and acceptable periodicity rests with manufacturers and the Authority respectively, because the AD ties substantive inspection requirements to manufacturer instructions and to "approved maintenance data", and reserves approval functions to the Authority.

Duties

Inspect and test to manufacturer instructions: The central duty placed on relevant parties is to "inspect and test in accordance with requirements in instructions issued by the manufacturer" (Requirement). This means the substantive content of what must be inspected and how tests are performed is set by the manufacturer's instructions, not by detailed steps in the AD itself.

Use approved organisations: The inspections and tests "are to be undertaken by an organisation approved for the purpose by the Authority" (Requirement). The duty therefore includes using only those maintenance organisations that have the regulator’s approval to carry out the AD work.

Comply with timing regimes: Parties must comply with one of the two timing rules set out. Either follow "the approved maintenance data" or follow the default schedule: "within two years of date of manufacture and thereafter at intervals not exceeding one year" (Compliance). Amendment 6 allows compliance to follow manufacturer-approved maintenance data where that data permits intervals longer than the default (Background). Practically, this creates a duty to determine which timing regime applies and to schedule inspections accordingly.

Determine applicability: Before acting, parties must determine whether a device is "subject to a System of Maintenance". Devices that are subject to such a system are excluded from the AD; therefore operators must assess whether their devices fall inside the AD's scope (Applicability).

Rights and discretionary elements

Choice of timing path: The directive creates a choice: comply via "approved maintenance data" or via the default "two years from manufacture then annually" schedule (Compliance). That choice gives operators and maintenance planners the right to rely on approved maintenance data if it exists and has been approved; otherwise, the default timing applies. Amendment 6 broadens that right by permitting manufacturer-approved data to authorise longer intervals (Background).

Right to use approved organisations: The AD does not permit inspections by unapproved entities; it requires work by organisations the Authority has approved (Requirement). The right here is limited: an operator may choose any provider that holds the Authority's approval for the work in question.

Manufacturer as technical author: By tying inspection and test requirements to "instructions issued by the manufacturer", the AD entrusts technical specification to manufacturers. Operators and maintainers have the right to rely on those instructions as the basis for compliance, subject to the approval processes implied by "approved maintenance data" and the Authority's approvals.

Implied obligations to identify manufacture date: Because the default timing is "within two years of date of manufacture and thereafter at intervals not exceeding one year" (Compliance), operators must know the date of manufacture of each device to calculate compliance deadlines. The AD therefore imposes an implied operational duty to retain or obtain manufacture-date information.

Limits on delegation: While the AD allows maintenance organisations to perform inspections, that delegation is limited to organisations "approved for the purpose by the Authority" (Requirement). Operators cannot lawfully delegate inspection/testing to unapproved entities.

Unspecified elements and regulatory discretion

The AD leaves several implementation details to the Authority and to manufacturers. It does not specify approval criteria for organisations, it does not define what constitutes "approved maintenance data", nor does it set record-keeping, certification, or reporting obligations in the text. These unspecified elements create areas where regulatory discretion or downstream regulatory instruments will determine how duties are operationalised.

In sum, the directive creates clear affirmative duties to inspect and test in accordance with manufacturer instructions, to use regulator-approved organisations to perform that work, and to comply with one of two timing regimes; it gives rights to rely on manufacturer instructions and approved maintenance data, while delegating approval and granular procedural choices to regulator processes that are not detailed in the AD text.

The AD text itself does not specify criminal penalties, civil penalties, or administrative fines, nor does it set out a procedural enforcement scheme. The directive mandates inspection/testing requirements, approved organisations, and compliance timing, but it contains no explicit enforcement clauses, sanctions, or penalty schedules.

Enforcement locus and implied monitoring: The document identifies the "Authority" , the Civil Aviation Safety Authority , as the body responsible for approvals (Requirement) and is the issuing authority for the airworthiness directive (header). Because the AD requires approval by the Authority for organisations undertaking inspections and refers to "approved maintenance data", enforcement and oversight functions are implicitly invested in the Authority. The practical effect is that the regulator will be the actor that can verify approvals, and thereby detect non-compliance, but the AD does not describe enforcement mechanisms or remedies.

Consequences of non-compliance (textual limits): The AD does not state what happens if an operator fails to inspect or test devices in accordance with the AD or if work is performed by an unapproved organisation. The AD likewise does not state whether devices found defective after inspection must be withdrawn from service, nor does it prescribe reporting requirements for defects uncovered by inspections. All such consequences, if they exist, would derive from broader regulatory powers, airworthiness rules, or separate enforcement instruments rather than from this AD’s text.

Regulatory discretion and follow-up instruments: Because the AD establishes approval-based requirements without specifying enforcement mechanisms, practical enforcement will depend on the Authority’s broader statutory powers and its operational practice. The AD’s reliance on approvals and "approved maintenance data" gives the Authority leverage: the regulator controls which organisations are authorised to perform the mandated tasks and which maintenance data are accepted. The Authority can therefore influence compliance through approvals, audits, and whatever enforcement powers it holds elsewhere, but those powers are not articulated in this AD.

Practical issues for operators and maintainers: In the absence of express sanctions in the AD, operators and maintenance organisations are left to assume that non-compliance could carry regulatory consequences through related instruments or general aviation safety enforcement regimes. The AD therefore imposes compliance risk even though it does not tabulate specific penalties in the text.

Summary: The AD imposes mandatory inspection and approval requirements but does not itself contain an enforcement or penalty scheme. It places oversight functions with the Authority by making approvals central; practical enforcement will depend on the Authority’s wider regulatory powers and procedures not set out in the AD.

The AD is an instrument issued within the Civil Aviation regulatory architecture. The document’s header gives that context: "COMMONWEALTH OF AUSTRALIA (Civil Aviation Regulations 1998), PART 39 - 107 CIVIL AVIATION SAFETY AUTHORITY SCHEDULE OF AIRWORTHINESS DIRECTIVES" (header). That situates the AD as a directive under the Civil Aviation Regulations framework, though the text of the AD does not reproduce the statutory provisions that grant authority to issue ADs or define terms such as "System of Maintenance" or "approved maintenance data".

System of Maintenance carve-out: The AD applies expressly to devices "not subject to a System of Maintenance" (Applicability). That creates an interface with whatever regulatory or contractual regimes define and operate a System of Maintenance. Devices already governed by such a system are outside this AD’s remit. Therefore, whether a device is subject to a System of Maintenance will determine whether the AD’s requirements displace, supplement, or duplicate obligations under that other system. The AD does not define "System of Maintenance", so operators must refer to the applicable regulatory definitions or contractual arrangements to determine interaction.

Manufacturer instructions and approved maintenance data: The AD ties compliance to "instructions issued by the manufacturer" and to "approved maintenance data" (Requirement; Compliance). Those references create a cross-reference to any regulatory processes that set standards for what counts as "approved maintenance data", and to manufacturer documentation that may itself be shaped by standards or certification requirements under other parts of the Civil Aviation Regulations. The AD thereby interfaces with regulatory approval pathways for maintenance data.

Approval of organisations by the Authority: The requirement that inspections be undertaken by an "organisation approved for the purpose by the Authority" (Requirement) interacts with the Authority’s wider approval, certification and oversight frameworks. Approval criteria, privileges, and obligations that the Authority imposes on approved organisations will therefore determine how this AD operates in practice. The AD does not restate those approval rules; it delegates to the Authority’s approval processes.

Judicial and administrative review: The AD does not provide a mechanism for review or appeal of the Authority’s approvals or disapprovals. Any such review would have to be pursued under the general administrative law, judicial review, or statutory appeal provisions that govern decisions of the Authority, none of which are contained or referenced in the AD text.

Effect on supply chain and inventory rules: Because the AD applies to devices "intended to be installed in an aircraft" as well as those installed, it intersects with obligations governing supply, storage, and inventory management. Operators that maintain spares must align inventory procedures with inspection timing, manufacture-date tracking, and approvals. The AD does not spell out those interactions but creates the need to coordinate with existing logistics and maintenance regulations.

Amendment layering: The AD records prior amendments: Amendment 5 added inflatable flotation devices, and Amendment 6 modified inspection-interval treatment (Background). Those amendment steps indicate that the AD operates within an iterative rulemaking process, and that other parts of the regulatory code may have been amended in tandem. The AD text itself, however, does not set out cross-references to other specific provisions beyond the general Civil Aviation Regulations header.

In short, the AD interacts with other laws and regulatory instruments by: (1) excluding devices covered by a System of Maintenance and therefore deferring to that regime; (2) depending on regulatory processes for approving maintenance data and organisations; and (3) fitting within the Civil Aviation Regulations framework for airworthiness directives. The AD leaves key definitional and procedural details to those other instruments and processes.

The AD text includes a brief, explicit amendment history in the Background and header. The elements stated in the source are as follows.

Amdt 6 (this document): The header identifies the instrument as "AD/EMY/2 Amdt 6 Life Jackets and Inflatable Flotation Devices 9/98" and states "Amdt 6" and gives an effective date. The AD text records that "This amendment becomes effective on 13 August 1998." The Background explains the specific change effected by Amendment 6: it "has been raised to permit inspection intervals to be in accordance with manufacturer’s approved data if that allows a period greater than; two years from manufacture, then every year." In other words, Amendment 6 altered the timing regime to allow manufacturer-approved maintenance data to permit longer intervals than the default two-year-then-annual schedule.

Amendment 5: The Background records that "Amendment 5 was raised to include inflatable flotation devices." That establishes Amendment 5 as the step that broadened the AD’s scope beyond life jackets alone to include inflatable flotation devices. The source does not provide a date for Amendment 5 within the text.

Initial instrument: The header indicates AD/EMY/2 as the schedule entry for "Emergency Equipment" under the Civil Aviation Safety Authority's schedule of airworthiness directives. The AD text does not reproduce the original issuance date or text for AD/EMY/2 prior to these amendments, nor does it list any other prior amendments.

Effective date: Amendment 6 is stated to have become effective on 13 August 1998 (Effective date). The header also shows "9/98" which may be a reference or calendar marker but the text explicitly gives 13 August 1998 as the effective date.

Scope of amendments: The Background clarifies the conceptual reasons for the amendments: "Life jackets fall within the definition of aircraft components. Amendment 5 was raised to include inflatable flotation devices. Amendment 6 has been raised to permit inspection intervals to be in accordance with manufacturer’s approved data if that allows a period greater than; two years from manufacture, then every year." These sentences record the substantive adjustments: (a) inclusion of inflatable flotation devices and (b) adjustment of permissible inspection intervals.

Missing historical details: The AD does not provide dates for Amendment 5, nor does it reproduce prior version text for comparison, nor does it list reasons, consultations, or regulatory impact analysis beyond the one-paragraph Background. Any further historical tracing would require reference to the administrative record or to the body that issues ADs, which is not contained in the AD text.

Summary: The AD’s amendment history, as contained in the document, consists of a prior step (Amendment 5) that added inflatable flotation devices and the present Amendment 6 that adjusted permissible inspection intervals, with Amendment 6 effective on 13 August 1998. The AD does not include a fuller history or dates beyond what is stated.

The AD text does not record any litigation history. It contains no citations to cases, no references to judicial decisions, and no mention of disputes or appeals related to this AD. The text does not indicate that any matters arising from AD/EMY/2 Amdt 6 have been the subject of litigation or published rulings.

Practical implication of silence: Because there are no cases or litigation references in the document, the AD itself does not provide judicially-tested interpretations of its terms such as "System of Maintenance", "approved maintenance data", or the extent of the Authority’s approval powers. Any legal disputes about the meaning or application of the AD,whether over whether a device is "subject to a System of Maintenance", what constitutes "approved maintenance data", or whether an organisation qualifies for approval,would therefore rely on general administrative law, the Civil Aviation Regulations framework, and possibly case law outside the AD text. The AD does not supply that material.

What to do if litigation is anticipated: Parties seeking legal certainty about ambiguous elements in the AD (for example, the exact calculation of intervals or the scope of Authority approval) would need to look beyond the AD to the Civil Aviation Regulations, to the Authority’s published approval criteria, and to any relevant administrative decisions or court rulings. None of those materials are contained in the AD text, and therefore the AD does not itself report any litigation that interprets it.

In short, the AD contains no litigation history; no cases are named, and readers must consult other sources to find any adjudications that might clarify contested points.

The AD is short, but it contains several textual features and silences that create practical pitfalls for operators, maintenance providers and compliance teams. The following are concrete issues drawn from the text that merit attention.

1. Applicability hinges on "not subject to a System of Maintenance"

   • The AD applies only to devices "not subject to a System of Maintenance" (Applicability). Whether a device is "subject to a System of Maintenance" will determine whether the AD applies. The AD does not define "System of Maintenance", so operators must verify whether their maintenance regime or an existing regulatory scheme already classifies devices as subject to such a system. Misclassification can lead to either unnecessary inspections or regulatory non-compliance.

2. "Installed or intended to be installed" is broad

   • The applicability covers devices both installed and "intended to be installed in an aircraft" (Applicability). That captures spares, stock, and items awaiting installation. Organisations that hold inventories of life jackets or flotation devices need to track manufacture dates and inspection schedules for items not yet fitted, which can be overlooked in routine maintenance planning.

3. Manufacturer instructions are the substantive standard, but approval is required

   • The AD instructs inspections to be "in accordance with requirements in instructions issued by the manufacturer" (Requirement). However, compliance can also be via "approved maintenance data" (Compliance), and the inspections must be "undertaken by an organisation approved for the purpose by the Authority" (Requirement). The interplay of manufacturer instructions, what counts as "approved maintenance data", and the Authority’s approval processes creates potential misalignment: following manufacturer instructions alone may not be sufficient unless the manufacturer instructions have been incorporated into "approved maintenance data" or the performing organisation is Authority-approved.

4. Two possible timing regimes can confuse scheduling

   • Compliance can follow "the approved maintenance data" or "within two years of date of manufacture and thereafter at intervals not exceeding one year" (Compliance). Amendment 6 permits manufacturer-approved data to allow longer periods than the default (Background). Operators must determine which path applies to each device and record the manufacture date to calculate default deadlines. Confusion over which timing applies risks missed inspections.

5. Unspecified approval criteria for organisations

   • The AD requires use of an "organisation approved for the purpose by the Authority" (Requirement) but does not state approval criteria or approval categories. Maintenance providers may need to clarify with the Authority whether existing approvals cover life-jacket work or whether a specific approval is required. Assuming an approval covers this AD without confirmation is risky.

6. No record-keeping, reporting or defect handling spelled out

   • The AD does not require retention of inspection records, nor does it specify defect reporting or corrective-action protocols. Operators should not assume that no records are required; other regulatory instruments may impose such obligations. The absence of guidance here can lead to inconsistent practice or disagreements with the Authority about what constitutes compliance evidence.

7. Effective date timing vs manufacture-date calculations

   • Amendment 6 became effective on 13 August 1998. For devices manufactured before that date, it may be unclear how the "within two years of date of manufacture" rule is to be applied if the device is older than two years at the effective date. The AD text does not address grandfathering or transitional arrangements; that creates operational uncertainty for legacy equipment.

8. Scope includes inflatable flotation devices only after Amendment 5

   • The inclusion of inflatable flotation devices was effected by Amendment 5 (Background). If an operator has documentation or procedures predating Amendment 5, they may have missed that change. Organisations must confirm that inflatable flotation devices in inventory are treated consistently with the AD.

9. The directive is silent on penalties and enforcement

   • The AD contains no penalties or enforcement mechanisms in its text. Operators therefore do not have a clear statement of sanction risk in the AD itself, but enforcement likely exists through the Authority’s wider powers. Assuming no sanction risk because none is specified would be a misreading of the AD’s practical force.

10. Manufacturer-approved data may allow longer intervals , risk allocation

    • Amendment 6 permits following manufacturer-approved data that allows inspection intervals longer than the default schedule (Background). That relaxes periodicity but shifts performance risk toward the operator and manufacturer: longer intervals reduce inspection frequency, which may lower maintenance cost but can increase the interval during which defects go undetected. The AD’s text does not stipulate conditions for approving longer manufacturer intervals.

These gotchas are textual or procedural features in the AD. They derive directly from its phrasing and silences and indicate places where operators and maintenance providers will need clarification, confirmation or operational controls to be certain of compliance.

The AD prescribes a short list of concrete compliance steps. Below is a practical checklist, with references to the originating AD text, to translate the AD’s requirements into actionable steps for operators, maintenance organisations, and compliance officers.

1. Identify covered devices

   • For each life jacket or inflatable flotation device in inventory, determine whether it is "installed or intended to be installed in an aircraft" (Applicability). Items identified as spares for future installation are within scope.
   • Determine whether each device is "subject to a System of Maintenance". If it is, the AD does not apply to that device (Applicability). If it is not, proceed with the following steps.

2. Establish manufacture date

   • Record the "date of manufacture" for each device, because the default timing schedule is "within two years of date of manufacture and thereafter at intervals not exceeding one year" (Compliance). Accurate manufacture dates are necessary to calculate deadlines where the default schedule is used.

3. Obtain and review manufacturer instructions and approved maintenance data

   • Collect the "instructions issued by the manufacturer" that define inspection and test requirements (Requirement).
   • Determine whether "approved maintenance data" exists for the device and whether it has been accepted by the Authority for compliance purposes (Compliance). Where approved maintenance data exists, it may set a different inspection interval and procedural content.

4. Decide which timing regime to follow

   • Choose between following the approved maintenance data, or applying the default schedule (within two years of manufacture, then at intervals not exceeding one year) (Compliance).
   • If relying on manufacturer-approved data that would allow intervals longer than the default, confirm that the maintenance data is indeed "approved" for compliance with the AD (Background).

5. Use an Authority-approved organisation to perform work

   • Engage only an "organisation approved for the purpose by the Authority" to undertake the inspections and tests (Requirement).
   • If your current maintenance provider is not clearly approved for this purpose, obtain written confirmation from the provider or a formal approval record from the Authority before permitting them to perform the work.

6. Schedule inspections and tests

   • Based on the chosen timing regime and manufacture dates, schedule the initial and subsequent inspections so they fall within the mandated intervals (Compliance).
   • For items inspected under manufacturer-approved data that permits longer intervals, document the basis for each inspection date and retain evidence that the maintenance data is approved.

7. Document compliance actions

   • Although the AD does not specify record-keeping requirements, retain records showing: device identification and manufacture date; the manufacturer instructions or approved maintenance data relied upon; proof of the performing organisation’s Authority approval; dates and results of inspections and tests; and any corrective actions taken after inspection.
   • These records will be the primary evidence to demonstrate compliance in any regulatory review or audit.

8. Clarify ambiguous or transitional issues with the Authority

   • For uncertainties , for example, whether a particular organisational approval covers the required inspections; how to treat devices manufactured many years before the effective date; or whether particular manufacturer instructions qualify as "approved maintenance data" , seek written clarification from the Authority. The AD’s text delegates approvals and the meaning of "approved maintenance data" to the Authority without specifying criteria.

9. Update supply-chain and inventory controls

   • Treat inventory items "intended to be installed" as in-scope, and ensure procurement and storage processes account for inspection scheduling and manufacture-date tracking (Applicability).
   • Integrate inspection scheduling with maintenance planning systems so that upcoming deadlines are visible and actionable.

10. Review insurance and operational risk protocols

    • Because inspection periodicity is adjustable by reference to approved maintenance data, assess whether any longer intervals will affect operational risk assessments, insurance terms, or internal safety management systems. Document the rationale for relying on longer manufacturer intervals and keep supporting approvals.

11. Monitor for further AD amendments

    • The AD has been subject to prior amendments (Amendment 5 and Amendment 6). Maintain a process to monitor for further amendments, because the AD can be updated and those updates may affect scope, timing or procedural requirements (Background).

12. Coordinate with other maintenance systems

    • If a System of Maintenance applies to some devices, align record-keeping and inspection regimes to avoid duplication or conflict. Confirm whether the System of Maintenance’s rules satisfy the AD or whether additional action is required.

Following these steps will operationalise the AD’s directives: inspections and tests executed in accordance with manufacturer instructions, performed by Authority-approved organisations, and scheduled according to approved maintenance data or the default manufacture-date/annual schedule. Given the AD’s silences about approval mechanics, record-keeping and enforcement, obtaining written confirmation from the Authority where doubts exist is a prudent compliance measure.