91.03.4

Air traffic service flight plan and associated procedures

(1) The owner or operator of an aircraft shall ensure that an ATS flight plan is completed if required in terms of subregulation (4).

(2) The items to be contained in the ATS flight plan shall be as prescribed Document SA-CATS 91.

(3) The ATS flight plan shall be filed with the appropriate ATSU unless other arrangements have been made for submission of repetitive flight plans and such unit shall be responsible for transmitting such ATS flight plan to all ATSUs concerned with the flight.

(4) The ATS flight plan shall be filed in respect of—

(5) An ATSU may instruct a flight for which an ATS flight plan is required in terms of subregulation (4) and for which an ATS flight plan has not been filed, to clear or to remain clear of controlled airspace, and not to cross the border of the Republic or to enter its airspace until such time as the required ATS flight plan has been filed.

(6) Unless otherwise authorised by the responsible ATSU, an ATS flight plan for a flight to be conducted in controlled or advisory airspace, shall be filed—

(7) The PIC of an aircraft operating an IFR or controlled VFR flight shall ensure that all changes which become applicable to an ATS flight plan before departure or in flight are reported, as soon as practicable, to the responsible ATSU. For other VFR flights, changes regarding fuel endurance or total number of persons carried on board shall, as a minimum, be reported.

(8) If an ATS flight plan has been filed with an ATSU prior to departure, and is not activated with an ATSU within one hour of original estimated time of departure or amended estimated time of departure, the ATS flight plan shall be regarded as cancelled and a new ATS flight plan shall be filed.

(9) Where an ATSU is not in operation at the aerodrome of intended landing, a report of arrival as prescribed in Document SA-CATS 91 shall be submitted to an ATSU, by the quickest means of communication available, immediately after landing, in respect of a flight for which an ATS flight plan was submitted and not as yet closed or for which search and rescue notification was requested and designated with a particular ATSU.

(10) When communication facilities at the arrival aerodrome are inadequate and alternate arrangements for the handling of arrival reports on the ground are not available, the PIC shall, prior to landing the aircraft or immediately thereafter, if practicable, transmit to the appropriate ATSU, a message comparable to an arrival report, in respect of a flight for which an ATS flight plan was submitted and not as yet closed or for which a search and rescue notification was requested with a nominated ATSU.

(11) Subject to the provisions of subregulation (12), the PIC shall ensure that the aircraft adheres to the current ATS flight plan filed for a controlled flight, unless a request for a change has been made and accepted by the ATSU responsible for the controlled airspace in which the aircraft is operating, or unless an emergency situation arises which necessitates immediate action, in which event the responsible ATSU shall, as soon as circumstances permit, be notified of the action taken and that such action was taken under emergency authority.

(12) In the event of a controlled flight inadvertently deviating from its current ATS flight plan, a PIC shall—

(13) When an automatic dependent surveillance (ADS) agreement is in place, the ATSU shall be informed automatically via data link whenever changes occur beyond the threshold values stipulated by the ADS event contract.

(14) If prior to departure it is anticipated that, subject to a reclearance in flight, a decision may be taken to proceed to a revised destination aerodrome, the appropriate ATSUs shall be so notified by the insertion in the flight plan of information concerning the revised route, where known, and the revised destination. The revised destination shall be subject to the fuel and oil provisions of regulation 91.07.12.

CLOSE