Traffic call phrasing
Clock position:
- Relative to aircraft's observed surveillance track, not nose.
- Two o'clock = 60 degrees right of track (PSTAR 3.16).
- Strong crosswind: aircraft crabs, so clock position can disagree with pilot's view.
Call content depends on whether ATC has identified the traffic:
| Traffic | Position relative to | Also given |
|---|---|---|
| Identified | Receiving aircraft's observed track | Direction of flight; type (if unknown: relative speed, and altitude if known) |
| Non-identified | A fix | Direction of flight; same type/speed/altitude clause |
Phrasing conventions (both):
| Element | Form |
|---|---|
| Direction of flight | May be OPPOSITE DIRECTION or SAME DIRECTION |
| Altitude | May be feet above or below receiving aircraft, not absolute |
| Altitude not known | "altitude unknown" (PSTAR 3.16 key 2) |
Pilot response:
- Acknowledge; state whether traffic in sight.
- ATC may keep updating until traffic sighted or no longer a conflict (TP 1102, Advice of Conflicting Traffic).
| Phrase | Use |
|---|---|
| LOOKING FOR TRAFFIC | Traffic not seen |
| TRAFFIC IN SIGHT | Only once actually seen |
- Lose sight after reporting: inform ATS (NAV CANADA VFR Phraseology, Traffic).
Trap: "relative to observed track" is identified traffic; "relative to a fix" is non-identified; mixing them up is the classic error.
References
- TC AIM RAC 1.5.3
- TP 1102 Aeroplane Flight Training Manual, Advice of Conflicting Traffic
- TC PSTAR 3.16 (answer key 2)
- NAV CANADA VFR Phraseology, Traffic