MATS 104-C Flashcards
CARs 602.31 Compliance with Air Traffic Control Instructions and Clearances
the pilot-in command of an aircraft shall:
(1) Subject to subsection (3), the pilot-in command of an aircraft shall
(a) comply with and acknowledge, to the appropriate air traffic control unit, all of the air traffic control instructions directed to and received by the pilot-in-command; and (b) comply with all of the air traffic control clearances received and accepted by the pilot-in-command and
***know this^^^^^ below not so much
(i) subject to subsection (2), in the case of an IFR flight, read back to the appropriate air traffic control unit the text of any air traffic control clearance received, and (ii) in the case of a VFR flight, read back to the appropriate air traffic control unit the text of any air traffic control clearance received, when so requested by the air traffic control unit.
(2) Except if requested to do so by an air traffic control unit, the pilot-in-command of an IFR aircraft is not required to read back the text of an air traffic control clearance pursuant to paragraph (1)(b)(i) where
(a) the air traffic control clearance is received on the ground by the pilot-in-command before departing from a controlled aerodrome in respect of which a standard instrument departure procedure is specified in the Canada Air Pilot; or (b) the receipt of the air traffic control clearance is acknowledged by the pilot-in-command by electronic means.
FL
Flight Level
An altitude expressed in hundreds of feet indicated on an altimeter set to 29.92 inches of mercury or 1013.2 hectopascals
There are two ways a controller can determine the current altitude of an aircraft:
i. Ask the pilot for their current altitude.
ii. Look at the aircraft’s data tag on the situation display.
To ensure that altitude information is correct, controllers use a combination of both these methods. Normally a controller looks at the flight data tag on the display and observes the altitude. When the aircraft reports the altitude, the controller compares the two pieces of information for accuracy.
If required and not provided on initial contact…
ask the pilot to verify altitude.
If required, instruct a pilot to report:
- leaving an altitude “REPORT LEAVING”
- Passing an altitude “REPORT PASSING”
- Reaching an altitude “REPORT REACHING”
If an altitude report is necessary during a step-down procedure, you should specify an altitude that is 2000 feet or more from the altitude to which the aircraft has been cleared.
Consider an aircraft to be maintaining an altitude when
Its altitude readout is within 200 feet of its assigned altitude
Note: This is a key rule. It tells you that when an aircraft reports its altitude, you must correlate it immediately with the data block altitude readout and ensure that it is within the 200-foot parameter.
Consider an aircraft to have reached an altitude when
Consider an aircraft to have vacated an altitude when
Understand the “starting point” in the note below
Consider an aircraft to have passed an altitude when
Observed Deviations
Inform the pilot if you observe any of the following:
- It appears that the aircraft will deviate or has deviated from its assigned route or holding area.
- The altitude readout indicates that the aircraft has deviated by 300 feet or more from its assigned altitude.
- The altitude readout indicates that the aircraft has deviated by 200 feet from its assigned altitude and the VMI indicates that the aircraft is continuing its climb or descent away from the assigned altitude.
When an aircraft has deviated from assigned airspace, if necessary, assist it in returning to the assigned airspace.
In order for ATC to use Mode C altitude information for separation purposes….
the aircraft Mode C altitude readout must be verified.
Mode C altitude is considered valid if the readout value…..
The Mode C altitude is considered valid if the readout value does not differ from the aircraft reported altitude by more than 200 ft. The readout is considered invalid if the difference is 300 ft or more.
Therefore, it is expected that pilot altitude reports, especially during climbs and descents, will be made to the nearest 100-ft increment.
Alpha tags, or Full Data Blocks (FDB)
Vs
Limited tags also called Bravo Tags or Limited Data Blocks (LDB)
Alpha tags, or Full Data Blocks (FDB), are the aircraft that are under our control or jurisdiction. Targets will be displayed this way when they have been tagged with a flight plan and the flight plan’s CJS matches the display CJS.
Limited tags also called Bravo Tags or Limited Data Blocks (LDB) which usually means they are under another controller’s jurisdiction.
Data block:
MEDEVAC Symbol
If the flight plan remarks contain MEDEVAC, MED or HOSP, then the MEDEVAC symbol “+” appears in front of the ACID.
Data Block:
WT (Wake Turbulence Category)
This character appears to the right of the ACID field and may be one of the following:
“-“ Light
“/“ Medium
Treated as a heavy for wake turbulence if it is the leading aircraft (Note: only on mediums that fit this description, all other mediums have no symbol) eg 757
“+” Heavy
Super heavy:
A box around a “Heavy” aircraft as indicates a Super Heavy for wake turbulence purposes.
Data block:
SFI
SFI (SPECIAL FLIGHT INFORMATION)
The SFI is a single character (letter) that is added by the controller to supplement the data tag information. The explicit meaning for each letter is unit-specific and is established by arrangement. In Generic IFR training, the SFI is used to indicate the language of the pilot in bilingual environments.
The SFI field is displayed to the right of the WT field.
Data Block:
VMI
Vertical Movement Indicator (VMI). The VMI, when activated, presents an up or down arrow next to the altitude and indicates whether the aircraft is climbing or descending.
Data Block:
VMR
Vertical Movement Rate (VMR).
This tells us the rate at which the aircraft is climbing or descending, in hundreds of feet per minute.
History Trail Dots
Each dot represents
5 seconds of flight time for the aircraft (the radar turns 12 times per minute). ADS updates every 3 seconds. Therefore, the faster the ground speed of the aircraft the further apart the dots will be. Conversely, a slow-moving aircraft will have its history trail dots closer together. Controllers can select how many history trail dots they wish to see on their display. NARDS gives the option of selecting between 0 and 200.
Standard phraseology vs plain language
Relay messages in standard phrases or plain language without altering the sense of the message in any way.
Use standard phraseology contained in MATS whenever possible. Use standard phraseology in preference to plain language. If phraseology contained in MATS is not understood, use clear and concise plain language.
Limit communications to those operationally required and do not encourage or
participate in non-essential conversation while in an operational position.
CPDLC
A text-based communication system, known as Controller-Pilot Data Link Communications (CPDLC), is installed in some ACC specialties. It allows controllers and pilots to communicate via text messaging, thereby reducing the need for voice communication.
Correcting a Clearance or Instruction
Identify and correct any…
*know this!!
Identify and correct any errors made during delivery or readback of a clearance or instruction, even if a readback is not required. If there is any possibility of misunderstanding, cancel and restate the clearance or instruction in full.
Providing Readbacks to Other Controllers
When received from a Canadian controller or when requested by other agencies, read back verbatim any IFR clearance, IFR instruction, or any amendments to IFR clearances or IFR instructions.
Similarly, Canadian flight service specialists are also required to read back a clearance or instruction.
Foreign Controller Readbacks
With the exception of foreign NAT oceanic controllers, foreign agencies may not be required to give readbacks.