Study the CASA instrument rating exam as one integrated IFR flight rather than six isolated subjects: trace each topic through the flight from clearance to missed approach, practise reading real procedure charts, and rehearse weather-linked go/no-go decisions on paper.
IFR in Australian airspace: clearance, route, and level rules you must be able to apply
Air law for instrument flying is about what an IFR pilot must hold, obtain, and comply with: an instrument rating endorsement, an ATC clearance to operate IFR, and level, route, and airspace requirements set out in the AIP.
Start with the structural distinction that organises everything else: VFR flight is largely self-conducted within visual rules, while IFR flight operates inside an ATC system that issues clearances, separates traffic, and expects compliance with published procedures. Learn which documents carry which rules. The Civil Aviation Act and Regulations set the legal framework; the AIP and its Enroute (ENR) sections contain the operational procedures; and CASA advisory material explains them. Knowing where a rule lives makes air law questions tractable instead of a fog of memorised fragments.
Then trace one flight through the rules instead of reading the regulations cover to cover. Follow a planned IFR flight from filing the flight plan, to requesting and receiving clearance, to amendments en route, to the approach clearance, and finally to the alternate and fuel obligations you planned before departure. At each step ask: who decides, what must I comply with, and what must I tell ATC? This converts air law from a list into a sequence you can reconstruct under exam pressure.
- Regulations state the legal requirement; the AIP states how to comply operationally.
- An IFR clearance is permission within constraints, not a blanket authorisation.
- Fuel, alternate, and holding requirements are planned before departure, not improvised en route.
Reading the IAL chart: the four approach segments and where each rule applies
Every instrument approach is divided into arrival, initial, intermediate, final, and missed approach segments. Each segment has its own track, altitude constraints, and protected airspace, so chart reading means locating which segment you are in at any moment.
The geometry is the point. The initial segment positions the aircraft from the en-route structure toward the intermediate fix; the intermediate segment aligns and configures the aircraft for the final descent; the final segment descends toward the landing threshold; and the missed approach segment protects the escape path if visual references are not obtained. On Australian Instrument Approach and Landing (IAL) charts these segments are shown through the plan view, profile view, and the missed approach text. Practise putting your finger on the chart and naming which segment a given fix, altitude, or note belongs to.
Now connect the geometry to procedure rules. A step-down fix only applies while you are established on the segment it protects. Minimum sector altitudes protect the arrival and initial segments, not the final. The missed approach point on a non-precision approach is where the final segment ends and the missed approach begins, and continuing past it without the required visual reference is a decision the chart has already drawn for you. When you can narrate the chart aloud segment by segment, questions that look like rule trivia become geography problems with an obvious answer.
DA versus MDA: how precision and non-precision minima change your decision logic
Precision approaches with vertical guidance use a decision altitude or height, while non-precision approaches use a minimum descent altitude or height. The distinction changes when you may descend and when you must begin a missed approach.
The two minima types impose different behaviours. At a decision altitude on a precision approach, you are continuously descending and must decide at that point: visual references available means continue, otherwise a missed approach begins immediately. At an MDA on a non-precision approach, you may descend only to that altitude and, under the applicable rules, must not go lower without the required visual reference, with the missed approach starting at the missed approach point if you remain instrument. Write both decision rules on one card and rehearse saying which applies to which chart type.
Compare the chart types side by side as in the table below. The mistake to rehearse against is treating an MDA like a DA: reading the minima as an authorisation to keep descending below it without the required visual reference, or starting the missed approach early instead of levelling at the MDA and holding until the missed approach point. Level flight at the MDA while remaining instrument is correct behaviour on a non-precision profile; descending through it is not. The better decision is to read the minima line on the chart first, identify the vertical guidance type, and state the descent rule before you fly the profile, exactly as you would in the aircraft.
| Feature | Precision / vertical-guidance approach | Non-precision approach |
|---|---|---|
| Vertical guidance | Continuous electronic descent path | Step-down or no vertical path; level segments permitted |
| Minima type | Decision altitude / decision height | Minimum descent altitude / height |
| Pilot decision point | At DA/H on the descent | At or after reaching MDA/H, only with required visual reference |
| Missed approach trigger | No required reference at DA/H | Missed approach point if reference not obtained |
| Typical chart reading task | Confirm glidepath and DA/H | Identify MDA/H, step-down fixes, and MAPt location |
Weather that changes the plan: forecasts, alternates, and a worked go/no-go decision
IFR meteorology study should end in decisions, not decodes. A TAF or SIGMET matters because it drives fuel, holding, alternate, and diversion choices, so practise converting each forecast element into an operational consequence.
Decode with intent. For a TAF, read validity period first, then significant changes: the transition groups such as TEMPO and INTER describe temporary or intermittent deteriorations, and each carries implications for arrival weather at your estimated time. Visibility and cloud base relate directly to the approach minima you will be flying; wind and gusts relate to runway selection and crosswind limits; prognostic charts and SIGMETs relate to whether the route itself remains flyable. For every element you decode, force yourself to state what it changes in the flight plan.
Worked scenario: you plan an IFR arrival with a TAF valid through your ETA, and it contains a TEMPO period of reduced visibility and a low cloud base overlapping your arrival time. The tempting decision is to note the TEMPO, depart, and hope the improvement arrives before you do. The better decision is to treat the deterioration as a planning input: carry fuel for the possibility of holding, or plan a suitable alternate, and confirm before departure that the alternate's own weather supports an IFR arrival. Why it matters: a temporary deterioration is precisely the condition that can remove your arrival options while the forecast later looks fine. Rehearse this as a rule: forecast uncertainty converts into fuel, alternates, or both, never into optimism.
Navigation systems under IFR: what each aid gives you and what its failure costs
Ground-based aids and GNSS support different phases of IFR flight with different accuracies, coverage, and failure behaviour. Study each system by its operational role, its limitations, and what the procedure requires you to do when it degrades.
Build a role-based comparison rather than four separate system summaries. VOR gives bearing information along radials with line-of-sight coverage, NDB gives bearing to the station but is sensitive to coastal effect, thunderstorm interference, and night effect, and the ILS provides course and glidepath guidance for precision approaches. GNSS provides position-based navigation supporting point-to-point routings and satellite-based approaches, with integrity monitoring and requirements that depend on the equipment's approval for the operation. For each, ask: what does it measure, what protects me from its errors, and which charted procedures depend on it.
Then study failures, because procedures are written around them. If a navaid fails en route, the operational question is which parts of the remaining plan still depend on it: an NDB-based approach requires an alternative arrival plan, while a GNSS outage may affect routings and approach types differently. On paper, practise tracing one flight through a hypothetical failure at a waypoint and writing the two decisions that follow: what must I tell ATC, and which alternate procedure or diversion keeps the flight inside the rules. This turns systems knowledge into the operational reasoning the procedure sections assume.
Instruments in cloud: scanning, failures, and unusual attitudes on paper first
Instrument flight rests on interpreting the attitude and performance instruments as a coordinated scan, recognising pitot-static and gyroscopic failure symptoms, and recovering from unusual attitudes by confirming attitude before moving controls.
Learn the instrument grouping functionally. Attitude is shown on the attitude indicator; performance is confirmed across the airspeed indicator, altimeter, vertical speed, and turn instruments; and heading ties the scan to the navigation task. Each instrument also has a failure signature: blocked static sources distort airspeed and altitude indications in characteristic ways depending on climb or descent, and a failing vacuum-driven gyro drifts slowly, which is why cross-checking the instruments against each other is itself a failure-detection method. Draw the cross-check as a habit: no single instrument is ever accepted alone when another can contradict it.
For unusual attitudes, keep the method paper-based and procedural. The classic mistake in written scenarios is acting on the first startling indication, for example pushing when the airspeed indicator alone suggests a dive. The better method is the confirm-then-correct sequence: establish airspeed trend and altitude behaviour together to confirm the true attitude, level the wings with coordinated control inputs, then correct the pitch, and only then restore cruise parameters. Why it matters: the instruments disagree during the very failures that cause unusual attitudes, so the recovery order, not the speed of reaction, is the skill being tested.
Threat and error management for IFR: a worked diversion decision and a self-check rubric
Threat and error management frames IFR challenges as external threats, pilot errors, and undesired aircraft states, each with countermeasures. Practise naming them explicitly during scenarios so the model shapes your decisions rather than sitting as vocabulary.
Worked scenario: you are en route IFR toward your destination when updated weather shows the destination now below minima for your planned approach, fuel is finite, and ATC offers a revised clearance toward a nearer alternate. The tempting error is continuing toward the original destination, treating the clearance offer as an obstacle rather than information. The better decision is to run the model aloud: the weather update is a threat, the temptation to continue is an error in progress, and low usable fuel margin is an undesired aircraft state; the countermeasure is an early, explicit diversion decision with a new fuel and approach plan for the alternate. Why it matters: the model exists to force the decision early, while every option is still open.
Close your preparation with a chart-and-weather drill. Take one Australian IAL chart and one sample TAF, then complete the task list below against the rubric: every item you cannot complete without notes marks a section of this article to re-study. Treat the rubric scores as learning milestones only, not predictions of exam outcomes; the goal is that each task feels mechanical rather than effortful before you sit the exam. Then repeat the drill with a different chart type, a precision chart one day and a non-precision chart the next, so the decision rules stay attached to the right chart family.
- Drill tasks: label the arrival, initial, intermediate, final, and missed approach segments on the chart; state the minima type and the descent rule it authorises; decode the TAF and list two operational consequences; write the alternate or fuel decision the forecast implies; name one threat, one error risk, and one countermeasure for the arrival.
- Rubric: all five segments named correctly, 2 points; correct minima type and rule, 2 points; decode plus consequences, 2 points; sound alternate or fuel logic, 2 points; complete TEM naming, 2 points. Aim for 9-10 before moving to a new chart; below 7 means re-study the relevant section.
- Readiness checks before the exam: you can narrate any IAL chart segment by segment without notes; you can state the DA and MDA decision rules from memory; you can convert any TAF element into a fuel, alternate, or diversion consequence; you can run a TEM loop on a written scenario in under a minute. Administrative matters such as exam scheduling are published by CASA, so link to casa.gov.au for those rather than relying on secondary summaries.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.