Prescription of aircraft and ratings — CASR Part 61 (Edition 2)

The text uses a small set of recurring administrative concepts that organise the catalogue entries. These are: Type certificate (TC) holder or manufacturer, Models and variants, Type ratings, Differences training required, and Licence entry (for administrative use only). Each concept appears consistently as a heading or subheading in the supplied extract.

Type certificate (TC) holder or manufacturer: The document repeatedly identifies "Type certificate (TC) holders (see subsection 3.2) or manufacturer" alongside model groups. The repetition indicates that the instrument attributes model responsibility or source information to TC holders or manufacturers. The cross-reference to "subsection 3.2" is the only definitional pointer supplied in the text; subsection 3.2 itself is not included in the supplied material. The operational consequence of this heading is that whatever obligations, rights or administrative relationships flow from TC holder status are intended to be determined by reference to that subsection.

Models and variants: The catalogue specifies aircraft at a granular level , by model and sometimes by variant label. Examples include "Kingair 300 (all models)", "Kingair 350 (all models)", "Beech 1900 (all models)", "G-73 Mallard (all piston powered models)", "G-73T Turbo Mallard", and numerous military types. The label "all models" recurs, signalling that the entry covers a model family rather than a single serialised sub‑variant. Some entries appear duplicated or near‑duplicates (for example "C208 (Caravan)" and "C208"), suggesting the catalogue draws from multiple source identifiers or that administrative fields differ between model name variants.

Type ratings: The text includes the heading "Type ratings" in proximity to model listings. That placement indicates the document associates specific type ratings with the listed models or model groups. The extract does not show a formal definition of what a type rating confers, nor the procedural steps to obtain one. It does indicate that type rating annotations are part of the administrative data attached to models.

Differences training required: When the heading "Differences training required" appears, it functions as a tag attached to a model or variant grouping. The phrase indicates the catalogue flags certain models as requiring differences training when moving between variants within that family. No syllabus, duration or standard is present in these excerpts; the document simply records the requirement as an attribute.

Licence entry (for administrative use only): This annotation recurs in multiple model groupings. The parenthetical "for administrative use only" suggests the text is intended to be recorded on licences or internal registries but is not necessarily part of the public regulatory text that sets out rights and obligations. It implies an administrative gatekeeping function: entries influence licensing records or are intended for tracking on personal licences.

Classification by type: The catalogue is organised by aircraft class: helicopter models and variants, types and models of single‑engine aeroplanes, types and models of multi‑engine aeroplanes. This classification signals how type‑rating regimes or training regimes might be structured , by rotorcraft versus fixed‑wing, single‑engine versus multi‑engine.

Cross‑references and missing definition: The only internal cross‑reference in the supplied text is to "subsection 3.2". That implies the catalogue is part of a wider instrument where subsection 3.2 provides a definition or rule about TC holders. The catalogue itself does not supply definitions such as "type rating", "differences training", or the administrative process for licence entry.

Taken together, these concepts indicate the document functions as an administrative schedule mapping aircraft models to TC holders, type ratings, and training annotations. It acts as a data layer intended to support licensing administration and training compliance, rather than as a standalone rulebook that sets out procedural mechanics within these excerpts.

The entries and annotations in the catalogue have practical relevance for a fairly narrow set of participants in the aviation regulatory ecosystem. The text itself does not state policy objectives or remedial remedies; it instead identifies the entities and activities implicated by the entries.

Pilots and licence‑holders: The presence of "Type ratings" and "Differences training required" directly implicates individual pilots and licence‑holders. Where a model or model family is annotated with those headings, pilots who propose to act as pilot-in-command or otherwise require the type rating will be affected. The catalogue’s entry labels are the administrative flags that licensing authorities typically use to determine whether a pilot’s licence may record a type rating or a notation that differences training is required. The repeated label "Licence entry (for administrative use only)" indicates the database field on a licence that would record such status; it therefore affects pilots at the level of licence endorsements and record keeping.

Training organisations and instructors: The tag "Differences training required" signals obligations for approved training organisations (ATOs), flight schools, and instructors to provide or administer differences training for particular model transitions. Even though the supplied text does not include syllabi or standards, the presence of the tag creates a compliance point for those who deliver type‑specific instruction and for those approving the training.

Operators and aircraft owners: Operators of the listed models, particularly air operators who manage crew rostering and safety management systems, will need to observe whether their personnel hold the appropriate type ratings and where differences training is mandated. Owners and maintenance organisations may be affected insofar as licence entries and TC holder designations impact maintenance release privileges or delegation arrangements with the TC holder or manufacturer.

Type certificate (TC) holders and manufacturers: The instrument repeatedly references TC holders or manufacturers. That nominative assignment affects the entity recognised as the source of the type certificate, which has implications for continuing airworthiness responsibilities, technical support relationships, and the authority that may be consulted on differences or modifications. The text expressly directs readers to "see subsection 3.2" for the TC holder treatment, indicating TC holders have a defined role elsewhere in the larger instrument.

Licensing authority and administrative staff: The repeated annotation "Licence entry (for administrative use only)" and the list format indicate that the catalogue is intended to be used by licensing administrators to record endorsements, to validate applications and to maintain an authoritative roster of models and associated flags. Administrative staff who process licence applications, change records, or audit personnel files will be regular users of this schedule.

Regulatory compliance professionals, accountants and auditors: Those responsible for compliance monitoring, internal audits, or external oversight will rely on the list to confirm whether crew members possess necessary endorsements. The catalogue thus affects the design and execution of compliance checks, payroll approvals for restricted operations, and commercial risk assessments.

The text does not identify any other statutory bodies or third parties by name, and it does not include explicit licensing rights or fee mechanisms. It also does not specify penalties or enforcement actors in these excerpts. Therefore, the direct impacts are limited to actors involved in licensing, training, operation and TC holder relations, with the catalogue serving as a reference and administrative input to their decision processes.

The catalogue, as supplied, does not set out a standalone code of duties and rights in conventional statutory form. Instead it functions as an administrative mapping that attaches procedural attributes to listed aircraft models. From the headings and annotations that appear, the catalogue imposes or records the following practical duties and entitlements.

Recorded duties (administrative or practical) implied by the text:

• Fulfil differences training where flagged. Entries are annotated "Differences training required" adjacent to certain models and variant groupings. That flag is the only textual indicator in the extract that a training duty exists. The catalogue does not supply the training content, duration or approval process; it only records that differences training is required for the relevant model group.
• Hold or obtain a relevant type rating where a model is associated with "Type ratings". The catalogue marks models with "Type ratings", signalling that pilots intending to operate those types will need the appropriate endorsement recorded on their licence. The extract does not draft the procedural steps to obtain a type rating; it records the necessity.
• Maintain licence entries consistent with the administrative notation "Licence entry (for administrative use only)". The presence of this annotation indicates an administrative duty on registrars or licensing staff to record the model/type rating/difference annotations on licence records.

Recorded rights or administrative recognitions:

• Recognition of TC holder/manufacturer as the entity associated with each model. The repeated heading "Type certificate (TC) holders (see subsection 3.2) or manufacturer" assigns an administrative attribute to the model listing identifying the TC holder or manufacturer. That identification confers recognition in the catalogue context, which could be relied upon for technical queries and continuing airworthiness communications.
• Administrative entitlement to record endorsements on licences. Although the text does not specify legal rights, the phrase "Licence entry (for administrative use only)" implies that the catalogue is the basis for recording a licence holder’s entitlements (for example, type ratings) in an administrative database.

Constraints and absent provisions:

• The document does not include procedural mechanisms for enforcement, nor does it set out how duties are policed, audited or penalised. The catalogue records obligations but leaves the enforcement instrument or statutory power unspecified within the provided text.
• No express appeal or review rights are listed in these extracts. The catalogue does not describe a process to challenge an entry or request a deletion or amendment.

Role of subsection 3.2:

• The text repeatedly instructs readers to consult "subsection 3.2" in connection with TC holders. That cross‑reference is the only explicit procedural pointer in the supplied text, and it suggests the duties and rights attaching to TC holders or the rules for who qualifies as a TC holder are articulated there. Because subsection 3.2 is not present in the supplied extract, the precise duties or rights derived from TC holder status must be read in the broader instrument.

In practice, the catalogue performs an administrative duty‑assignment function: it records which models require certain training or endorsements and which TC holders or manufacturers are associated with them. The legal force of those recordings , whether they create enforceable obligations or merely provide administrative guidance , is not established within the text supplied. Users should therefore treat the catalogue as an operational list that feeds into licensing and training processes, with duties and rights realised via the broader regulatory framework to which this schedule belongs.

The supplied text contains no penalty, enforcement or sanctioning provisions. There are no monetary penalties, no criminal offences, no administrative sanctions, no delegated penalty‑making powers, nor any enforcement protocols described in these extracts. The catalogue is an enumeration of models, TC holder attributions, and administrative annotations ("Type ratings", "Differences training required", "Licence entry (for administrative use only)") without accompanying enforcement language.

Implications and practical mechanisms for enforcement, drawn from the document’s structure:

• Administrative enforcement via licence records. The repeated annotation "Licence entry (for administrative use only)" suggests the document is intended to be recorded on licences or internal registries. In practice, regulatory enforcement of type‑rating or differences requirements typically operates through refusal to record an endorsement or refusal to validate a licence for a particular role unless the endorsement is present. Although the supplied material does not state this explicitly, the catalogue’s role in provisioning licence entries indicates the administrative registry is a primary mechanism through which compliance is monitored.
• Reliance on other instruments for sanctions. Because no sanctions are given here, any penalty for non‑compliance with the training or type‑rating flags would depend upon the broader regulatory framework (acts, regulations or instrument provisions not included in the supplied text). For users of this schedule, the absence of sanctions within it means practitioners must seek the enforcement and penalty provisions elsewhere in the parent instrument or the overarching aviation law.
• Implementation risk from missing enforcement text. Where the schedule flags duties (for example differences training), absence of accompanying enforcement text in the schedule itself raises a practical risk: individuals or operators may misread the schedule as advisory. That risk increases if the schedule is used in isolation from the main regulatory text that gives it legal effect.

Administrative actors who would implement enforcement in practice are not named in the extract. The catalogue does not assign responsibility for audits, inspections, or licence checks within the supplied text. Nor does it provide reporting obligations or deadlines linked to the annotations.

In short, the document records obligations and administrative flags but contains no enforcement or penalty language. Any enforcement, sanctioning or compliance‑checking activity that follows from these flags must therefore rely on other provisions in the broader regulatory corpus, which are not present in the supplied material.

The catalogue includes one explicit internal cross‑reference: "Type certificate (TC) holders (see subsection 3.2) or manufacturer". That cross‑reference indicates the schedule is part of a larger legislative or regulatory instrument where subsection 3.2 contains relevant definitions or procedural rules about TC holders. The supplied text does not include subsection 3.2, nor does it name or quote any other statute, regulation, or external instrument. Therefore the document as provided is a partial schedule that depends upon other provisions for full operational effect.

Observable interaction mechanisms from the text:

• Referential dependency. The frequent instruction to consult "subsection 3.2" shows the schedule depends on that subsection to define who qualifies as a TC holder or what the TC holder’s responsibilities are. That makes the schedule a dependent instrument: it provides the data, the cross‑reference provides the legal rule‑frame.
• Administrative registry interaction. The repeated "Licence entry (for administrative use only)" tag indicates an interaction with licensing systems and administrative registries. The schedule is therefore intended to deliver data to a licence administration process that is set out elsewhere. That implies an interaction with the licensing rules and any legislation that governs licence records and endorsements.
• Training regime interface. The "Differences training required" headings indicate the schedule interfaces with training and certification rules. The training standards, syllabi, approval processes, and trainer/ATO certification requirements are not part of this schedule, but the schedule’s flags will be operationalised against those other regulatory instruments.
• Type certificate/continuing airworthiness domain. The assignment of TC holders or manufacturers alongside models suggests interaction with continuing airworthiness rules, manufacturer instructions for continued airworthiness, airworthiness directives, and the responsibilities of TC holders as set out elsewhere in aviation law. The schedule supplies the identity of the TC holder; the legal responsibilities and obligations of that TC holder are likely located in the broader regulatory code.

Absent direct textual cross‑references to external statutes, the supplied extract does not itself create cross‑jurisdictional obligations, fee provisions, or inter‑agency arrangements. It does not cite international standards, treaties, or foreign civil aviation authorities. Any such interfaces would need to be located in the parent instrument or external regulatory material that is not included here.

Practical consequence for users: Because the schedule lacks the operative machinery for licence issuance, training approval, technical support, or enforcement, users must treat it as a data component within a broader legal ecosystem. Determining how it changes legal obligations, licensing status, or compliance exposure requires consulting the parent instrument (including subsection 3.2) and any other rules governing licences, training approvals and TC holder responsibilities.

The supplied material contains no amendment history, no dates of enactment or commencement, and no versioning metadata. There are no marginal notes, no struck‑through text, no history of insertions or deletions, and no explanatory memorandum in the extract. The only temporal or provenance clues are repeated labels and inconsistent formatting that suggest the schedule may have been compiled from multiple sources or successive updates, but that is an inference from structure rather than a recorded amendment history.

Concrete observations from the text:

• No record of prior versions: The document does not include an insertion log, tracks of amendment, or "amended by" notes. Each model listing stands alone without historical annotations.
• Internal duplication and repetition: The schedule sets out many headings more than once and repeats the phrase "Type certificate (TC) holders (see subsection 3.2) or manufacturer" multiple times. Repetition without an accompanying amendment log can indicate either (a) compilation from multiple historical updates without consolidation, or (b) a template repeated across sections that is intended to be filled in by administrators. The extract does not resolve which.
• Missing definitional subsection: Because subsection 3.2 is referenced but not present, there is an implicit dependence on an unseen part of the instrument that might contain the amendment history or an effective date. The absence makes it impossible, from the supplied text alone, to identify when entries were added or last updated.

Practical consequence: For anyone relying on the schedule, the lack of an amendment trail increases legal and operational uncertainty. License administrators, operators and compliance professionals will need to obtain the parent instrument or the regulator’s database export that includes versioning and effective dates to confirm that the entries are current and authoritative.

The supplied extract contains no mention of litigation, judicial decisions, administrative determinations, or dispute resolution concerning the catalogue entries or their legal effect. There are no case citations, no references to tribunal findings, and no redacted enforcement proceedings. The schedule is a listing and does not itself narrate any adjudicative history.

Implications:

• No precedential context: Because the extract contains no litigation references, users cannot rely on judicial interpretation of the catalogue’s terms here. Any ambiguity in phraseology (for example, whether "Licence entry (for administrative use only)" creates legally enforceable entitlements) will not be clarified by judicial or tribunal guidance in this text.
• Potential for future disputes: The catalogue’s cross‑references and omissions (for example, the missing subsection 3.2) create possible grounds for administrative dispute if an operator or individual disagrees with a licence entry or a requirement flagged by the schedule. However, no decisions or litigation materials are included to indicate how such disputes have been handled.
• Operational practice remains authoritative: In the absence of litigation history in the extract, regulatory practice and administrative guidance from the licensing authority will be the operative source of precedent for day‑to‑day application. The schedule does not capture or summarise that practice.

For anyone assessing compliance risk, the absence of litigation history in the supplied text means legal interpretations must be tested against the parent instrument and any administrative policy or guidance notes maintained by the regulator.

The supplied schedule contains multiple structural and content features that create practical traps for users. These are not normative assessments but concrete points where reliance on the schedule as a standalone source can cause operational errors.

1. Repeated cross‑reference to subsection 3.2 without the subsection present. The schedule repeatedly uses the phrase "Type certificate (TC) holders (see subsection 3.2) or manufacturer". The absence of subsection 3.2 in the extract means the reader cannot determine who qualifies as a TC holder, how the TC holder is to be listed, or what legal roles attach to that designation. A user who treats the schedule as authoritative without consulting subsection 3.2 risks misidentifying the responsible TC holder.

2. Administrative tag labelled "for administrative use only". Several entries carry the annotation "Licence entry (for administrative use only)". That parenthetical suggests the field is an internal data label, not a statement of legal entitlement. A holder who sees the annotation on their licence could mistakenly infer an operational right or duty without verifying whether the parent regulatory text gives the entry legal force.

3. Inconsistent labelling and duplication. There are duplicated model entries or near‑duplicates (for example, "Kingair 300 (all models)" listed alongside "Kingair 300 (all models)" in different groupings, "C208 (Caravan)" and "C208", and repeated headings such as "Helicopter models and variants" and "Type certificate (TC) holders..."). These duplications create a risk of administrative mismatch when different registry fields are used in different contexts (licence entry versus training record). An operator could rely on one label while the regulator’s database uses another.

4. Presence of both military and civil types without contextual distinction. The catalogue lists military types (for example, MIG‑15, MIG‑17, Hunter, Canberra) alongside civil types. The schedule does not indicate whether military types are treated differently for licensing or training purposes. Users may misapply civil licensing rules to military types or vice versa.

5. Lack of procedural content for "Differences training required". The label exists, but the schedule provides no syllabus, credit conversion rules, or exemptions. Training providers and pilots must obtain the missing procedural material from another source; failure to do so risks flawed training plans.

6. Ambiguous scope tags such as "all models". Where an entry says "TBM700 (all models)" or "Beech 1900 (all models)", it covers a family broadly. But without a versioning or effecting date, it is unclear whether newly‑introduced subvariants are covered until the schedule is updated. Operators might assume new subvariants are covered and be surprised if the regulator requires a separate notation.

7. Repetition of "Type ratings" as a heading without the rating code. The schedule notes "Type ratings" but does not list specific rating codes or the licence endorsements to be recorded. That omission increases the likelihood of inconsistent recording (for example, differing type rating shorthand across jurisdictions).

8. Formatting and compilation artefacts. The supplied extract appears compiled from multiple sources or templates. The irregular ordering and duplication may reflect legacy data migration. Administrative personnel relying on automated parsing should be cautious: inconsistent formatting can break scripts that map inputs to licence fields.

9. Missing effective dates and amendment history. Because the extract contains no effective dates, users cannot tell if an entry is current. That uncertainty can impact operational approvals, insurance underwriting, or contracting where currency of a pilot’s endorsement matters.

10. No enforcement or sanction language. The absence of penalty provisions in the schedule means users must check the parent regulatory instrument for enforcement consequences. Assuming that the schedule alone creates legal obligations is a practical pitfall.

Each of these "gotchas" arises from the structure and content of the supplied text. Practitioners should treat the schedule as a data component that requires corroboration with the parent instrument, regulatory guidance, and administrative databases to avoid compliance and operational errors.

Given the catalogue’s role as an administrative mapping of models, TC holder designations and training/type‑rating flags, the following practical compliance checklist is grounded in the document’s text and the administrative inferences that follow. The checklist is a pragmatic set of actions for pilots, operators, training organisations and administrators working with the schedule as part of a licensing regime.

1. Confirm the parent instrument and consult subsection 3.2. The catalogue repeatedly instructs readers to consult "subsection 3.2" in connection with TC holders. Obtain the parent legislative or regulatory instrument that contains subsection 3.2, read the definition and rules for TC holders, and confirm how the catalogue’s TC holder attributions are to be applied administratively.

2. Treat "Licence entry (for administrative use only)" as a database field, not as self‑standing legal advice. Before taking operational action solely on the basis of a catalogue entry, verify with the licensing authority whether the catalogue entry has been reflected on the licence record and whether that entry carries operational legal effect.

3. Verify type rating endorsement requirements with the licensing authority. Where the catalogue is annotated "Type ratings", do not assume the specific endorsement code or the required examination/flight test outcome. Contact the licensing authority or consult the relevant licensing standards for the procedure to obtain or record the type rating for the named model.

4. Where the catalogue flags "Differences training required", obtain the approved training syllabus and recordkeeping requirements. Training providers and pilots should request the detailed differences training requirements (syllabus, hours, assessments, recurrent intervals) from the regulator or from the approved training organisation standards referenced by the parent instrument.

5. Cross‑check model identifiers and variant labelling. Because the catalogue contains duplicate and inconsistent labels (for example "C208 (Caravan)" and "C208"), match the ICAO type designator or the manufacturer’s type certificate identifier against the operator’s or regulator’s database to ensure consistent recording. If in doubt, provide serial number, variant designation and TC holder name when making licence or training applications.

6. Maintain contemporaneous training and licence records. Given the catalogue’s administrative orientation, ensure training completions and type‑rating checks are recorded both in the pilot’s logbook and in the licence administration system. Where the catalogue’s annotation reads "for administrative use only", make sure the licence entry actually includes the annotation and obtain written confirmation from the licensing officer.

7. Seek clarification for military or non‑standard types. If the schedule lists military types or legacy types (for example, MIG series, Hunter, Canberra), contact the licensing authority to determine whether civilian type ratings apply, whether exemptions exist, or whether special operating limitations apply. Do not assume civilian licensing rules automatically apply.

8. For operators: incorporate the catalogue’s flags into rostering and competence matrices. Use the schedule to map which crew need type ratings and differences training before rostering them on particular types. Ensure maintenance of currency and recency records aligns with the catalogue’s expectations (assuming these are elaborated elsewhere).

9. For training organisations: obtain regulator approval or validation for any differences training you deliver. The catalogue gives the flag but not the content. Seek the regulator’s approval process and keep evidence of approval readily available for audit.

10. Preserve change control and versioning evidence. Because the extract lacks amendment history, operators and administrators should retain dated copies of the schedule as used at the time of any licence decision or rostering. Where entries are used to justify hiring, training, or operations, contemporaneous documentary evidence will reduce later disputes about which entries were in force.

11. Use conservative interpretations where uncertainty exists. Where the schedule is ambiguous (for example, "all models" or duplicated labels), adopt a conservative operational rule: require explicit confirmation from the regulator before permitting operational activity that depends on a type rating or difference training record.

12. Escalate anomalies to the regulator. If you identify conflicting entries, missing TC holder information, or differences between the catalogue and the regulator’s licence database, raise the matter with the licensing authority and obtain a written determination or correction.

These steps translate the catalogue’s administrative annotations into operational compliance tasks. The schedule is not self‑sufficient: effective compliance requires cross‑referencing the parent instrument (notably subsection 3.2), obtaining procedural details from the regulator, and confirming that licence entries are recorded and accepted by the licensing authority.