Treat every commercial-exam question as a two-layer problem. First ask what the licence permits under Part IV. Then ask what the operation requires under the applicable operating rules. Trace each answer to a specific regulation or standard in your notes rather than relying on a memorized one-line summary.
Why licence privileges and operator requirements are two different layers
A commercial licence grants privileges under the personnel licensing rules. Paid flying also implicates commercial air services requirements covering operational control, maintenance, and flight duty. Answer licence questions and operation questions separately.
The Canadian Aviation Regulations place personnel licensing in Part IV. A commercial pilot licence confers privileges, such as acting as pilot-in-command of an aeroplane for compensation within the licence category, class, and ratings, subject to validity and recency conditions. The licence itself does not authorize a flight as a commercial operation; fee-based flying points toward the commercial air services framework, which applies to operators and imposes its own requirements. A scenario can therefore be answered correctly at the licence layer and incorrectly at the operator layer.
Build a tracing habit from the start. When a question stem mentions compensation, hire, aerial work, or a client mission, ask two questions in order: does the pilot hold the privileges and ratings needed for this flight, and does this flight occur under the operating rules that apply to commercial work? Write the Part or subpart beside each answer in your notes. If you cannot name where a rule lives, that uncertainty is your next study target, not a detail to skip.
- Exercise: take one scenario - a commercial licence holder is paid to ferry a client's single-engine aeroplane to another airport. List the licence checks (category, class, ratings, recency), the likely operating framework, the documents needed, and which weather minima source applies.
- Expected observations: you should be able to name Part IV as the source of the licence rules and recognize that payment points to the commercial air services framework. Any subpart you cannot identify is a genuine gap to close; the value of the exercise is finding it, not scoring well on the first pass.
Recency versus currency: the two clocks running on your licence
Two independent clocks govern your legality. Recency provisions under the licensing rules keep privileges alive across years through minimum experience. Passenger-carrying currency requires recent takeoffs and landings within months, with stricter conditions at night.
Recency and currency answer different questions. Recency asks whether you have maintained the minimum experience the licensing rules require to keep exercising your privileges over the long term. Currency asks whether you have flown recently enough, and made the required takeoffs and landings in the category and class, to carry passengers. A pilot can satisfy one and fail the other: perfectly legal to fly solo, yet not legal to carry a passenger that day. Night carriage of passengers adds a further, more demanding set of conditions.
Worked scenario: a commercial licence holder last flew at night eight months ago and is asked to take a client on a night aerial photography flight. The plausible mistake is concluding that a commercial licence plus a night rating automatically covers any night mission, and booking it. The better decision is to check the passenger-carrying currency requirements for night flights, confirm the required recent night landings have been met, and verify the operating-side conditions before accepting. This matters because the two checks protect different things: the licence check confirms your qualifications, the currency check confirms your recent proficiency, and both must be current on the day of the flight.
- In your notes, keep recency and currency in one table with the provision reference, the time window, and what activity counts toward it.
- When reviewing questions, read the timeline phrases first: 'last year,' 'three months ago,' 'six months.' These phrases signal which clock the question is testing.
VFR over-the-top is not VFR on top: planning a flight above a cloud layer legally
VFR over-the-top is the CARs-defined term for VFR flight above a cloud layer, not an instrument flight. It requires specific cloud separation and a forecast of VFR conditions at destination around arrival; VFR on top is a separate IFR clearance concept.
Keep the two terms apart. Canadian regulations define VFR over-the-top with its own requirements for a VFR flight above a cloud layer. The phrase 'VFR on top' describes a separate IFR clearance concept, used when an IFR flight is operated in visual conditions above a cloud layer. The wording is close enough that blending the two changes the legal analysis: the over-the-top definition attaches weather and forecast requirements to a VFR flight plan, while an on-top clearance belongs to the IFR system with different conditions entirely. Anchor each term to its own source in the CARs rather than to a general aviation dictionary, and the same caution applies to Class B operations, where specific equipment and clearance requirements attach on top of the minima.
Worked scenario: a pilot plans to cruise two thousand feet above a forecast stratus layer to a coastal strip and return beneath the same layer. The plausible mistake is checking the destination forecast only for the departure time and assuming the return leg is legal because the outbound leg was. The better decision is to obtain the forecast covering the destination at the estimated time of arrival, confirm VFR conditions are forecast there for the arrival window, and identify a legal descent path before departure. This matters because over-the-top legality hinges on the arrival picture: the plan can be legal at cruise and illegal at descent if the layer closes underneath you.
- Practice by sketching a vertical profile: departure surface, cloud base and tops, cruise altitude, descent corridor. Label where each requirement applies.
- Rebuild the profile from the destination forecast, not the departure forecast, and identify the decision point where a deteriorating layer would abort the plan.
VFR minima change with airspace class, and with day versus night
VFR weather minima are set by airspace class and time of day. Controlled airspace uses one basic set of minima; Class G day is more permissive, night is more restrictive, and Class A is an IFR environment.
The mistake pattern here is memorizing one set of minima and applying it everywhere. Learn the structure first: controlled-airspace minima, Class G day minima, Class G night minima, and class-specific entry conditions such as clearance or equipment requirements. Then attach the current values to that structure from the regulations, so conditional cases such as altitude-dependent minima have an obvious place to live in your notes instead of floating as isolated numbers.
Cross-reference the minima with meteorology in one step. A decode of a METAR, TAF, or area forecast should produce numbers - ceiling height, visibility, cloud bases and tops - that you compare against the minima for each airspace class on the route. 'Good weather' is not a legal conclusion. If your decode produces no number for a segment, treat that segment as an open question, because a missing value is exactly where a conditional minima case hides.
| Airspace class | VFR entry condition | Minima notes |
|---|---|---|
| A | IFR environment | VFR generally not permitted |
| B | ATC control applies | Controlled-airspace minima; equipment requirements apply |
| C | ATC clearance required | Controlled-airspace minima |
| D | ATC clearance required | Controlled-airspace minima |
| E | No clearance in most cases | Controlled-airspace minima |
| F | Special-use airspace | Check the specific designation before planning |
| G | No entry condition | Day: 1 SM visibility, clear of cloud; night: additional minima - verify CAR 602.115 |
From TAF and GFA decode to a go/no-go number
Canadian preflight weather runs through METAR and SPECI reports, aerodrome TAFs, and Graphic Area Forecast charts for route segments. The goal of each decode is the same: ceiling, visibility, and cloud tops expressed as numbers you compare against minima.
Decode with discipline. From a TAF, extract the prevailing ceiling and visibility plus each forecast change period, because the value at your actual arrival time may differ from the value at issuance. From a GFA, extract cloud bases and tops along the route where no aerodrome forecast exists. Remember what each product covers: a TAF describes conditions around an aerodrome, while a GFA covers broad geographic areas. Using a destination TAF to justify over-the-top flight over a mountain pass mixes the two coverage areas and produces a false clearance picture.
Adopt a fixed output format: for every leg, write three numbers - lowest forecast ceiling along the leg, lowest forecast visibility, and highest cloud tops. These feed directly into the airspace-class minima table and the over-the-top vertical profile. Numbers you cannot fill in are marked as open questions in the plan. A written three-number summary also makes review efficient, because a single missing value exposes the weak link faster than rereading the whole forecast package.
Human factors: applying a decision framework to the specific moment
Human factors questions present decision situations, not vocabulary. Learn named frameworks such as PAVE and DECIDE, then practice applying them to the exact moment a scenario describes, testing each answer option against the highest identified risk.
PAVE organizes risk into pilot, aircraft, enVironment, and external pressures; the DECIDE model runs detect, estimate, choose, identify, do, and evaluate. A framework earns its place in your notes only if you practice the second step: restate a scenario in its categories, then evaluate each answer option against the dominant risk you identified. An option that is generically cautious may still be wrong if it addresses a minor risk while the scenario's dominant hazard goes unmanaged.
Several air law concepts double as human factors concepts. The pilot-in-command's responsibility for flight safety and the authority that comes with that role mean that an option describing a pilot declining a flight deserves careful analysis, not dismissal as overly conservative. Check what the regulations empower a pilot-in-command to do before judging the option. Practice by pairing each air law principle you learn with the human factors situation where it would apply, so the two subjects reinforce each other rather than sitting in separate mental boxes.
A five-stage preparation sequence with a self-check rubric
Work through five stages in order: build the two-layer regulation map, drill recency and currency timelines, practice vertical flight profiles, decode weather products against minima, then run full scenario reviews against a rubric. Weight the stages toward your weakest layer.
The sequence is adaptable because each stage produces a reusable artifact rather than a finished study session: the two-layer map from Section 1, the recency-currency table from Section 2, a set of vertical profiles, and a three-number weather decode sheet. If a later stage exposes a gap, return to the matching artifact instead of restarting your notes. A short note on administration: eligibility, scheduling, and other administrative details sit with Transport Canada, so verify them there before building a preparation timeline around them.
Use these milestones as learning checkpoints, not as predictions of any result. Milestone one: you can trace a paid-flight scenario to both the licensing provision and the operating layer, naming where each rule lives. Milestone two: you can state both time-based requirements - recency and passenger-carrying currency - without notes, including the night conditions. Milestone three: you can sketch an over-the-top profile and point to where the arrival forecast controls legality. Milestone four: a raw TAF and GFA produce your three numbers within a few minutes. Milestone five: for any decision scenario, you can name the dominant risk and defend the best option against it.
- Stage 1: map Part IV licensing provisions against the commercial air services framework; run the ferry-mission tracing exercise.
- Stage 2: build the recency-currency table with provision references and time windows; drill timeline-based stems.
- Stage 3: sketch three vertical profiles (above-layer outbound and return, below-layer, mixed) and label each legality condition.
- Stage 4: decode TAF and GFA products into three-number leg summaries; compare each against the airspace-class minima table.
- Stage 5: run full scenario review, restating each stem in PAVE categories and testing options against the dominant risk.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.