SlimHeader

facebook_page_plugin
×
A preview of the upcoming Video Lecture Series (14 Mar 2019)

This video is a snippet of the third day of the IREX course and it covers the Provision of Alternates

vimeo.com/323619910/90d43d366c

× Welcome to the CPL Air Law question and answer forum. Please feel free to post your questions but more importantly also suggest answers for your forum colleagues. Bob himself or one of the other tutors will get to your question as soon as we can.

Two air law queries

  • Posts: 59
  • Thank you received: 2

HPOUND created the topic: Two air law queries

Two queries for the experts:

(1) AIP ENR 1.1 2.12.4 specifies a downwind report is required in CTA. Is there a similar requirement for when OCTA?

Some aerodromes do not require the carriage of radio, so a downwind call cannot be mandatory in all cases. Other than good airmanship and the general requirement in CAR 166C to make a broadcast wherever reasonably necessary to avoid a collision, is there any provision in the AIP that explicitly mentions a downwind broadcast when OCTA? Something similar to the 10NM broadcast when inbound (per AIP ENR 1.1 6.1.16.2).

(2) Where can I find a definition of "in the vicinity of the aerodrome"?

Thanks,

Haydn
#1

Please Log in or Create an account to join the conversation.

  • Posts: 1893
  • Thank you received: 98

bobtait replied the topic: Two air law queries

There are two different definitions of vicinity. For the sake of aerodrome traffic, vicinity is within 10nm.
CAR 166 (c),
AIP ENR 1.1 Page 54 para 6.1 (Note 4),
AIP Gen 2.2 Page 17.

For the purpose of Met messages vicinity is beyond 8km but less than 16km.
AIP GEN 3.5 para 12.110.5.

There is no specific requirement for a downwind call at a non-controlled aerodrome.
#2

Please Log in or Create an account to join the conversation.

  • Posts: 59
  • Thank you received: 2

HPOUND replied the topic: Two air law queries

Thank you. I had looked at GEN 2.2 Definitions but was searching under "vicinity", not "in the vicinity"!
#3

Please Log in or Create an account to join the conversation.

Time to create page: 0.336 seconds