CASA 205/14 - Specification — examinations for aircraft maintenance engineer licence category electrical

The table introduces a concise set of concepts that a practitioner must treat as administrative primitives: subject, code, licence group, and association marker. Each concept appears in the table as follows.

• Subject. Rows are headed by subject names. The table divides subjects into Core subjects, Specific group subjects and Specific aircraft type. Core subjects listed are: "Airworthiness administration", "Electrical fundamentals", "Aerodynamics and maintenance practices", "Basic logic and semi-conductor theory", "AC theory and power systems" and "Digital techniques, computers and electronic devices". Specific group subjects listed are "General electrical systems" and "Electrical systems for multi generator powered systems". Specific aircraft type is split into "Written" and "Oral". These are the plain-language subject listings the administering authority uses for category electrical examinations.

• Code. Each subject has an adjacent code column giving a short alphabetic label: AA, QA, QB, QC, QD, QE, EB, ED, ES and EO. Note 1 explicitly states that "The code is an abbreviation for examination administration purposes", confirming these entries are administrative identifiers and not necessarily substantive definitions of subject matter. The table thus provides a stable shorthand for exam administration and recordkeeping.

• Licence groups. The table header labels three licence-group columns: 1, 2 and 20. The header cell is captioned "Licence groups", showing that the subsequent numeric columns are grouping identifiers used in the regulatory scheme. The table does not define those licence-group numbers within itself.

• Association markers. The cells at the intersection of subject rows and licence-group columns contain asterisks, blanks, or the symbol '#'. For example, in the Core subjects block many cells contain an asterisk under each of columns 1, 2 and 20. In the Specific aircraft type block the "Written" and "Oral" rows contain the symbol '#' in the intersection with column 20 only, and blank cells elsewhere. One subject row (Electrical systems for multi generator powered systems, code ED) is blank under licence group 1 but contains asterisks under groups 2 and 20. The table itself does not explain the exact legal operation of the asterisk or the hash symbol; however it is clear they are the device used in this schedule to indicate applicability or administrative relevance of that examination to the licence groups.

• Cross-reference. The row for "Digital techniques, computers and electronic devices" contains a note: "See subclause 1 (2) of Schedule 1." This shows the table is intended to be read with other schedule text that may qualify, constrain, or interpret that subject or the marking system.

Taken together, the main concepts amount to an administrative mapping: named subjects (and their short codes) are mapped to licence-group identifiers using a marking convention. The table is therefore a specification document for exam administration rather than a stand-alone set of normative rules. Any normative effect depends on how the parent regulation or Act imports and uses this specification.

The table affects four practical actor classes directly: examination candidates, licensing administrators, training providers (including registered training organisations and employer training programmes), and record-keeping or compliance teams within organisations that rely on electrical-category licences. Each effect flows from the table’s role as an administrative mapping of subjects to licence-group identifiers.

• Examination candidates. Candidates preparing for category electrical examinations will find the list of core subjects and specific group subjects that the administering authority recognises, together with the administrative codes used in examination paperwork. For example, a candidate preparing for the licence-group columns that show asterisks across core subjects (Airworthiness administration AA; Electrical fundamentals QA; Aerodynamics and maintenance practices QB; Basic logic and semi-conductor theory QC; AC theory and power systems QD; Digital techniques QE) can read these as the subjects the authority links to those licence groups in this schedule. Candidates for specific aircraft-type examinations should note that the Written (ES) and Oral (EO) codes are marked with "#" under licence group 20 only.

• Licensing administrators. The body tasked with administering examinations must use the codes and the table mapping when scheduling, marking, and recording results. Note 1 explicitly instructs that the code is an abbreviation for "examination administration purposes", which places the primary operational responsibility for using these codes with the examining authority or authorities.

• Training providers. Employers, mechanical and electrical training centres, and RTOs will use the table as the authoritative list of subjects to align curriculum, assessment tools, and training records with the codes the examining authority uses. The table groups core subjects and group-specific subjects; training providers designing course packages for licence groups 1, 2 or 20 will reference the table to ensure curricular coverage maps to the administrative codes.

• Compliance and records teams. Organisations that must keep personnel certification records, or which audit staff licences for regulatory compliance, will rely on the codes and the subject mapping to interpret an employee’s examination record. The table’s codes and the presence/absence marks will be the key data points when reconciling documentation.

Indirectly, other stakeholders such as employers who must allocate labour to roles requiring particular licence groups, and insurers that underwrite operators whose staff hold these licences, will be affected to the extent they rely on the accuracy of examination records that this table is designed to standardise. The table itself does not stipulate who may issue licences or how the results are converted into legal entitlements; those matters would be set out in the broader instrument that incorporates this schedule.

The table itself does not set out explicit statutory duties or rights; it functions as an administrative schedule that allocates examination subjects to licence-group labels and provides administrative codes. Where duties or rights arise in practice, they will typically be generated by the broader legislative instrument that adopts this schedule. From the table, however, a number of practical duties and administrative rights can be identified or inferred with careful qualification.

• Duty to observe administrative codes. Note 1 states "The code is an abbreviation for examination administration purposes", which establishes an administrative expectation: examination authorities and recording systems will use the provided codes (for example AA, QA, QB, QC, QD, QE, EB, ED, ES, EO) in managing exam processes. The practical duty here rests on the examining authority to use these codes consistently and on candidates and training providers to refer to the correct code when applying or submitting administrative forms.

• Duty to consult cross-referenced provisions. The "Digital techniques, computers and electronic devices" subject contains the direction "See subclause 1 (2) of Schedule 1." That is an explicit signal that the treatment of that subject is qualified by another provision. Practically, administrators and applicants should treat the table as incomplete without consulting subclause 1(2) of Schedule 1. The duty is procedural: read the cross-reference and apply whatever qualification or definition it contains.

• Duty to map subject coverage to licence groups. The marked associations (asterisks and '#' symbols) create an administrative expectation that certain subjects are relevant to particular licence-group numbers. For instance, all core subjects bear an asterisk under licence group columns 1, 2 and 20; the practitioner should therefore expect that these core subjects are tied to those licence groups. The duty is operational: ensure candidates for those licence groups are assessed against the named subjects.

• Right of the administering authority to use abbreviations. The Note confers, at least administratively, a right or discretion to employ short codes in examination administration. That right is internal to the conducting authority: it simplifies record-keeping and communication.

• No explicit rights or remedies stated. The table contains no express procedural rights (such as appeals, re-sit entitlements, or grading thresholds) nor does it contain penalty clauses or enforcement mechanisms. Any such rights or duties must be located in the parent instrument that imports this schedule.

Because the table is a schedule, the normative duties and rights that affect candidates (for example, requirements to sit or pass particular exams to obtain a licence) will depend on how the licensing regime uses this schedule. Practitioners should not assume that an asterisk equals a legal obligation to sit and pass, nor that blank cells mean no administrative relevance, without checking the main text that defines the legal consequences of the schedule markings.

This schedule contains no standalone penalty provisions, enforcement mechanisms, or procedural sanctions. There are no sections, clauses, or notes within the table that prescribe fines, licence suspensions, or criminal offences for failing to comply with the table. Accordingly the table itself is not an enforcement instrument in the penal sense; it is an administrative specification.

That absence has practical implications for enforcement analysis. If an examiner, administrator or licensing authority intends to enforce compliance with the mapping in this schedule, the penal or administrative tools enabling enforcement must be located in the parent legislative instrument or regulations that incorporate this table. Practitioners should therefore expect enforcement to be effected via:

• Administrative decision-making. The parent instrument may require that licence issuance is conditional on passing examinations linked in schedules such as this. Where that is the case, the practical enforcement mechanism is the licensing decision itself: candidates who have not completed required subjects may be refused a licence or endorsement. That mechanism is not recorded in the table, so the schedule cannot by itself be used to infer the precise quality of administrative review, notice or appeal rights.

• Recordkeeping and audit. The codes in the table are administrative identifiers. Enforcing compliance with training or staffing rules will be a matter of record-keeping using those codes. Penalties for inaccurate records or misrepresentation would need to be provided elsewhere.

• Cross-reference enforcement. The explicit cross-reference to "subclause 1 (2) of Schedule 1" indicates that some subjects are governed by additional text, which may include qualifying requirements or variations. It is in that cross-referenced material that any enforcement nuance (for example, scope limits, exemptions, or alternative assessment modalities) would appear.

Because none of the above is present in the table, the schedule neither prescribes enforcement modalities nor creates new fines or offences. Practitioners must consult the parent instrument to determine what enforcement consequences flow from the mapping recorded in the schedule and what appeal rights or review mechanisms are available to candidates adversely affected by administrative decisions that use this table.

The table is a dependent instrument: its legal meaning and operational effect depend on its incorporation into, and interpretation within, a broader legislative or regulatory framework. The table itself provides two explicit interactors: the label "Table 1 , Examinations for category electrical", which implies placement within a structured regime of categories and examinations, and the inner cross-reference "See subclause 1 (2) of Schedule 1", which binds its interpretation to other schedule text.

Concrete points of interaction to check in the parent instrument are:

• Incorporation by reference. The schedule is likely incorporated into a regulation or an Act as a Schedule or Annex. Its effectiveness, and whether the asterisks or '#' symbols have binding legal effect, depends on the clause of the parent instrument that imports "Table 1 , Examinations for category electrical" into operative law. Practitioners should identify the clause that brings this table into force and determines how its entries affect entitlement to licences.

• Definitions. The table uses short codes and symbols without defining them within the table. Definitions of the terms "category electrical", "licence groups", "1, 2, 20", the meaning of the asterisk and '#', and the legal status of the codes are likely defined in other parts of the instrument. The instruction "See subclause 1 (2) of Schedule 1" is an explicit instance of such definitional cross-referencing.

• Examination administration rules. The presence of codes described as "abbreviation[s] for examination administration purposes" means that procedural rules governing exam delivery, grading, re-sits, transfer of results between jurisdictions, record retention, and privacy of candidate data are set out elsewhere. The table is a data map that interacts with those procedural rules.

• Licensing rules. The table’s associations between subjects and licence groups will interact with licensing criteria in the primary instrument. For instance, a licensing provision may require passing particular subjects listed in this schedule as a condition of licence grant, or may permit experience or alternative routes to substitute for certain subjects. Those substitution, equivalence or grandfathering rules will be found outside the table.

• External regulatory regimes. If the licence groups interface with certification regimes administered by multiple agencies (for instance, an aviation safety regulator and a civil aviation training or safety oversight agency), the table's codes may be used to transfer records between agencies. The cross-reference to Schedule 1 indicates nested regulation; practitioners should confirm whether the schedule is adopted identically across jurisdictions or modified locally.

In short, the table is a component of a regulatory architecture. Its practical effect on rights, duties and compliance is realised through its incorporation and interpretation by the parent instrument and any subordinate procedural instruments. The schedule cannot be read for legal effect in isolation; one must read it in tandem with the instrument that adopts it, the definitions that govern its symbols, and any procedural rules that govern examinations and licensing.

The schedule as provided includes no internal history of amendments, no dates of commencement, no marginal notes indicating prior iterations, and no versioning information. It is presented as a standalone "Table 1 , Examinations for category electrical" without any annotation identifying whether it has been inserted, replaced, or amended from a prior schedule. Consequently:

• There is no in-table record of when this particular table was created or last revised. The table does not include any date or version stamp.

• There are no recorded amendment markers (for example, struck-through entries, parenthetical notes of repeal or insertion, or footnotes indicating earlier text).

• The cross-reference to "subclause 1 (2) of Schedule 1" suggests that the schedule sits within a larger schedule structure where amendment history might be recorded. However, this table does not itself record such history.

Practical consequences for practitioners are twofold. First, a reliable amendment history must be sought in the consolidated or official version of the parent instrument that adopted the schedule. The parent law or regulation (and any amending instruments) will indicate dates of effect, repeals, and any transitional arrangements. Second, if a practitioner is relying on this table for compliance, record-keeping or litigation, they must verify that they are using the current, consolidated version of the schedule; because the provided extract has no amendment metadata, it cannot be relied upon to show whether the mapping is current.

Where legislative drafting practice provides internal amendment indicators (for example, in a consolidated compilation showing tracked changes or a legislative history database), those will be the correct sources. The absence of that information in the table itself means the schedule is a snapshot lacking provenance; users should verify the schedule against the official, consolidated instrument or gazette notices that record amendments.

The table contains no references to any litigation, case citations, judicial interpretations, or reported disputes. There are no marginal notes referring to judicial decisions that interpret the meaning of the asterisk or hash symbols, no explanatory notes citing authority or precedent, and no mention of related appeals or tribunal decisions.

Consequences for practitioners:

• There is no basis within the table to assert that any court or tribunal has interpreted its markings. If any dispute arises about the meaning of the asterisk, the '#' symbol, or the cross-reference to subclause 1(2) of Schedule 1, the table does not provide guidance on prior adjudications that could be persuasive or binding.

• Any litigation history relevant to the table will therefore need to be researched outside the table: search for case law dealing with the parent instrument that adopts this schedule, or any disputes about the administration of category electrical examinations. The schedule itself gives no signals about contested points or settled interpretations.

• In absence of in-table litigation references, questions about the legal force of the code abbreviations, the legal effect of the presence or absence of asterisks, or disputes about examination coverage will turn on statutory construction of the parent instrument and on administrative practice. Litigated issues are most likely to focus on (i) whether passing an examination listed in this schedule is a condition precedent to licence grant, (ii) whether the schedule's markings are mandatory or advisory, and (iii) the interpretation of any cross-referenced subclauses.

For practitioners advising clients who may be in a position to litigate or defend enforcement action (for example, a candidate denied a licence on the basis of an exam mapping), the absence of any litigation history in the table means primary-source research must proceed to the parent instrument and to judicial databases; the table itself provides no precedential guidance.

The schedule contains several points of potential ambiguity or misinterpretation which practitioners should treat as "gotchas" when using it to plan compliance, training, record-keeping or litigation strategy. These are matters that arise directly from the table text and layout, not from any external assertion.

• Symbol meaning not defined in-table. The table uses at least two marking devices: an asterisk and the symbol '#'. The table does not define either symbol within its own text. Therefore one must not assume what asterisk or '#' means without consulting the parent instrument. Asterisks might indicate mandatory subjects for a licence group, optional subjects, or subjects offered for examination; the table alone does not say.

• Cross-reference without content. The instruction "See subclause 1 (2) of Schedule 1" appears only against the "Digital techniques, computers and electronic devices" row. Absent the text of subclause 1(2) of Schedule 1, the professional cannot interpret any qualification, limitation, or alternative paths that subclause might provide. That means reliance on this row without reading subclause 1(2) risks non-compliance.

• Codes are administrative. Note 1 states codes are abbreviations for "examination administration purposes". Practitioners must note that codes such as "AA" or "QA" are operational labels; licences or legal definitions may reference subject matter rather than the code. Record-keeping systems must map both code and subject name to avoid confusion.

• Blank cells may be meaningful. Several intersections are blank (for example, some specific group subject rows are blank under licence group 1). The absence of a mark is not explained in the table. It may indicate non-applicability, lack of assessment, or the absence of a requirement. Do not assume "no mark = no requirement" without checking the parent instrument.

• Specific aircraft type mapping is limited. The Written (ES) and Oral (EO) rows show '#' under licence group 20 only, and blanks elsewhere. If practitioners assume all groups require written and oral type exams they may be mistaken; conversely if they assume group 20 is not special they may miss the requirement. Only the parent instrument will resolve this.

• Group numbering is opaque. Licence groups are labelled simply 1, 2 and 20 without explanation in the table. The numbers may not correspond to obvious categories (for example, "1" is not necessarily "senior", "2" is not necessarily "junior"). Users must check the definitions elsewhere to understand what those group numbers represent in practice.

• Potential for mismatch between training content and code usage. Training providers who map curricula to subject names but ignore the codes risk administrative mismatches: an application form or exam registration may require a code. The table’s Note 1 makes clear the codes are central to administration.

• Incomplete metadata. The table provides no commencement, amendment or provenance metadata. Practitioners relying on the table must verify they are using the current version of the schedule; failure to do so could lead to non-compliance based on outdated subject mappings.

Each of these gotchas derives from the table’s concision and dependence on other provisions. The practical remedy is process: always read the parent regulation or Act, find the clause that imports this table, and locate any definitions, symbol keys, transitional rules and amendment history referenced elsewhere.

To convert the schedule into an operational compliance workflow, practitioners should adopt a short checklist-driven approach that ensures no reliance on ambiguous in-table signals. The following steps are grounded in what the table provides and in the explicit cross-references it contains.

1. Locate the parent instrument and relevant clauses. Do not rely on the table alone. Identify the Act or regulation that incorporates "Table 1 , Examinations for category electrical" and read:

   • the clause that imports the table into law,
   • definitions of "licence groups" and the specific numbers 1, 2 and 20,
   • the key that defines the asterisk and the symbol '#',
   • any provisions for exemptions, alternative assessment routes, transfer of credit, or transitional arrangements.

2. Read subclause 1(2) of Schedule 1. The table itself instructs "See subclause 1 (2) of Schedule 1" in relation to the "Digital techniques, computers and electronic devices" subject. That subclause may modify the scope or form of that subject, set content or equivalence rules, or define delivery modalities. Treat that cross-reference as mandatory reading for candidates and training providers.

3. Map subjects to curricula and assessment tools using both subject name and code. The table confirms codes are administrative abbreviations. When designing learning outcomes, assessments, or record-keeping, map both the full subject name (for substantive coverage) and the code (for administrative filings and examination entries). For example:

   • AA , Airworthiness administration,
   • QA , Electrical fundamentals,
   • QB , Aerodynamics and maintenance practices,
   • QC , Basic logic and semi-conductor theory,
   • QD , AC theory and power systems,
   • QE , Digital techniques, computers and electronic devices,
   • EB , General electrical systems,
   • ED , Electrical systems for multi generator powered systems,
   • ES , Written (specific aircraft type),
   • EO , Oral (specific aircraft type).

4. Confirm the legal effect of table markings. Do not assume an asterisk equals a pass/fail requirement or that '#' indicates a different standard. Obtain the interpretive clause that defines how passing or attempting these examinations relates to licence issuance. If that clause is silent or ambiguous, ask the administering authority for written guidance or an official policy statement.

5. Build administrative processes reflecting code usage. Ensure application forms, exam registration systems, transcript templates and personnel files include a field for the examination code as well as the subject name. That reduces the risk of data mismatch at the point of licence application or audit.

6. Document cross-border or inter-agency recognition. If licences are used in multiple regulatory contexts, confirm whether the codes and subject mappings are recognised consistently. Where asterisks are present across multiple groups, confirm whether that reflects shared standards or parallel but separate assessments.

7. Maintain version control and audit trails. Because the table itself contains no amendment metadata, keep a copy of the official parent instrument and the date of access. When a client relies on a particular examination mapping for a licensing deadline, retain the specific version of the instrument that was current at that time.

8. Prepare for specific aircraft-type assessments. The Written (ES) and Oral (EO) rows are marked with '#' under licence group 20 only. If advising a candidate in group 20, incorporate specific aircraft-type written and oral assessment steps into the training plan and administrative checklist, but confirm the legal status of the '#' symbol first.

9. Raise clarifications in writing. If any ambiguity remains after consulting the parent instrument and Schedule 1 subclauses, submit written requests for clarification to the examining authority and retain responses. These will be important if the client later faces an adverse administrative decision based on interpretation of the table.

10. Train compliance teams and examiners. Ensure the staff who administer examinations and review licence applications understand the mapping, the codes and the need to consult cross-referenced provisions. Build an internal pocket guide that replicates the mapping with hyperlinks to the parent instrument and to subclause 1(2) of Schedule 1.

Following these steps will align practical compliance activity to the data the table supplies while guarding against misinterpretation of its concisely recorded markings. The key operational principle is to treat the table as a specification that must be read together with the parent regulatory text.