CASA SMS Deadlines for 2026: 1 September vs 2 December
CASA's current transition guidance separates the 1 September submission deadline from the 2 December implementation deadline. Here is what affected operators need to distinguish.
Organizational byline
Updated July 16, 2026
7 min read
CASA's current 2026 flight-operations transition guidance contains two dates that affected operators should not collapse into one:
- 1 September 2026: submit the required procedures and nominate the safety manager.
- From 2 December 2026: the systems must be implemented and the safety manager accepted by CASA.
The deadlines apply to the air transport or aerial work operators covered by the transition, including operators that relied on exemptions delaying the introduction of their safety management system. They should not be presented as a new obligation for every small aviation business in Australia.
This article is a reading guide to CASA's published transition material, not a compliance determination for a particular certificate holder. Operators should test their own approvals, exemptions and manual status against the current CASA instruments and guidance.
The two deadlines do different jobs
CASA's 1 June 2026 notice says operators must provide by 1 September:
- SMS procedures;
- a human factors and non-technical skills program;
- flight data analysis program procedures, if applicable; and
- the safety manager nomination, including evidence of competency.
Those documents form part of the operator's operations manual. The later date is not an extension for sending them. CASA says that, from 2 December, the systems must be implemented and the safety manager accepted.
| Date | CASA's stated milestone | Practical control |
|---|---|---|
| 1 September 2026 | Documents submitted and safety manager nominated | Submission receipt, controlled manual revision and competency evidence retained |
| 2 December 2026 | Systems implemented and safety manager accepted | Procedures in use, staff briefed or trained, records operating and acceptance status confirmed |
An operator can submit a polished manual and still miss the implementation requirement. It can also start using sound safety processes but still miss the formal submission and nomination milestone. Both tracks need owners.
Who should check applicability now
CASA's Part 119 material applies to Australian air transport operators, while Part 138 covers aerial work operators. The current transition page is the right starting point for identifying which requirements and exemption pathway apply.
The word "micro-operator" also needs care. CASA has published a dedicated micro-operator SMS sample manual, but eligibility for any micro-operator provision should be established from the current rules and exemption instruments, not from an informal headcount or the size of the aircraft fleet.
An operator should record:
- the certificates and CASR Parts under which it operates;
- whether it relied on the relevant SMS transition exemption;
- which HFNTS and FDAP requirements apply;
- whether it qualifies for any current micro-operator flexibility; and
- which key-person and safety-manager arrangements require approval, acceptance or notification.
That one-page applicability note gives the manual project a legal and operational boundary.
What a submission pack should demonstrate
CASA says the procedures must accurately reflect how the organisation operates. That is a higher bar than changing the company name in a sample manual.
A defensible pack should connect the written system to real people and records. Depending on the operation, that means showing:
- who is accountable for the SMS and who performs day-to-day safety work;
- how staff report hazards and occurrences;
- how risks are assessed, assigned and closed;
- how operational changes are evaluated before introduction;
- how safety performance is monitored;
- how findings and lessons return to staff;
- how HFNTS training is delivered and recorded; and
- how any applicable flight-data process is governed.
CASA's SMS setup guide identifies safety policy, risk records, a hazard register, safety reports, audit records and SMS training records among the documentation that supports the manual.
Use the sample manual as a framework, not the operating evidence
CASA publishes both a Part 119/Part 138 sample SMS manual and a micro-operator sample. It also supplies form templates and an emergency response plan template.
These resources are useful for structure. They do not know:
- the operator's routes, aircraft and task profile;
- who can stop an operation;
- where maintenance, rostering or contractor information enters the system;
- how hazards are discussed in a small team; or
- what evidence the organisation can realistically maintain.
The fastest useful method is to map existing practices before writing new ones. A small operator may already hold daily briefs, defect meetings, management-of-change discussions and recurrent training. The SMS task is to define which of those practices satisfy the required function, close the gaps and make the evidence repeatable.
A six-week implementation sequence
The following sequence is a project-control framework, not a CASA-mandated schedule.
Week 1: applicability and ownership
Confirm the transition path, appoint the document owner, identify the proposed safety manager and list the required submissions. Book access to the people who control operations, training, maintenance coordination and records.
Week 2: gap analysis
Use CASA's gap-analysis material against the current operation. Mark each SMS element as working, partly working or absent. Link every "working" answer to a record rather than relying on recollection.
Week 3: operating procedures
Write the reporting, risk, change, assurance and promotion processes around the way the organisation actually works. Remove template roles, meetings or forms that will not exist after submission.
Week 4: HFNTS, FDAP and competency evidence
Complete the applicable HFNTS and FDAP sections. Assemble the safety manager nomination and evidence. Resolve any uncertainty about key-person combinations or approvals before the pack is due.
Week 5: controlled review and test
Run one real hazard through the proposed process. Test a change decision, a report, an action owner and the feedback loop. Correct the manual where the process breaks.
Week 6: submit and move into use
Submit through the current CASA pathway, retain the receipt and issue the controlled manual revision. Start the training, reporting, review and assurance records needed to show that the system is implemented by December.
Starting earlier creates space for CASA questions without turning the final weeks into an uncontrolled rewrite.
Evidence of implementation after submission
The December milestone is operational. Evidence can include:
- staff induction or briefing records;
- opened and assessed hazard reports;
- an active risk register with owners and review dates;
- management-of-change records;
- internal review or audit activity;
- safety meeting or communication records;
- current HFNTS records; and
- confirmation that the accepted safety-manager arrangement matches the manual.
The purpose is not to manufacture paperwork. It is to show that the described safety loop is running: report, assess, act, verify and communicate.
Common failure modes to remove before submission
The sample-manual copy
Roles and forms appear in the manual but do not exist in the business. Fix this by mapping every procedure to a named role, system and record.
The dual-role blind spot
In a small operation, one person may carry production and safety responsibilities. Document how competing priorities are surfaced, who can review the safety decision and when an issue must be escalated.
The submission-only project
The team treats 1 September as the finish line. Create the implementation evidence plan at the same time as the submission plan.
The overbuilt system
The manual creates committees, reports and metrics that the operator cannot sustain. CASA's resources explicitly support scaling SMS for size and complexity. Keep the system proportionate, but make each control real.
Bottom line
For affected operators, 1 September is the submission and nomination deadline; 2 December is the implemented-system and accepted-safety-manager deadline. The useful work is not choosing between those dates. It is running the document and implementation tracks together.
Confirm applicability, adapt the correct CASA sample to the actual operation, test the process before submission and retain evidence that it is working.
