Pre-Flight Planning resources

Pre-Flight Planning

Pre-flight briefing and notification

Domestic flight notification

Forms AIP ENR 1.10

An example of the Australian Domestic Flight Notification Form is shown on page 2.92.

Instructions for completion of the Domestic Flight Notification Form for both IFR and VFR flights start on page 2.93. In a number of cases (particularly in Item 19), completion is recommended as good practice. If mandatory Items are left incomplete, delays may occur.

The reverse side of the Flight Notification Form has a flight log/template to assist pilots in planning and navigation. It is not intended to be mandatory or prescriptive, and pilots may use any template, or other device, of their choice.

Flight Notification forms are available from the Airservices website: www.airservicesaustralia.com/flight-briefing

The suggested format for a Flight Note is on page 2.106.

Flight rules AIP ENR 1.10

Flight rules must be indicated in any flight notification, except for VFR flights operating wholly outside controlled airspace and nominating a SARTIME.

PBN notification AIP ENR 1.10

No indication on the Flight Notification form is required for visual navigation or DR substitute applications of GNSS.

• Notification of PBN capabilities requires a combination of entries in Item 10 (Equipment and Capabilities) and Item 18 of the flight notification form. Guidance is provided in the Domestic flight notification form user guide.

Prior to conducting RNP AR operations in Australian administered airspace, foreign operators must apply to CASA (International Operations) for an “Authorisation: RNP-AR operations”. Foreign operators should not include any RNP AR capability in flight plan notification until so authorised by CASA.

POB

Pilots of VFR flights must include POB when submitting flight notification or when leaving a flight note, and are encouraged to notify ATS of any subsequent changes.

General

For flights not operating along an ATS route, estimated elapsed times should be provided for locations approximately 30 minutes or 200 nm apart.

Location data

Any location abbreviations used should be authorised abbreviations (that is, published in AIP).

If a common name is entered into NAIPS in lieu of an aerodrome abbreviation or navigational aid/waypoint, the flight notification output will assume that the aircraft is tracking over a navigational aid/waypoint and not the aerodrome, for example: the location Holbrook will translate to HBK, not YHBK.

Pilots entering details in terms of latitude and longitude, or using polar coordinates, must adhere to the correct format, for example: 2730S15327E.

Flight notification amendment AIP ENR 1.10

When flight notification details have been previously notified to ATS, pilots should advise, as soon as possible, when there is any significant change to the following items: 

Item

Details

VFR in  CTR/CTA

VFR wholly OCTA nominating a SARTIME

7

Aircraft ident and/or registration

X

X

8

Flight rules to which flight will be operating

X

10

Serviceability of equipment carried

X

13

DEP aerodrome and EOBT: if the change exceeds 30 minutes

X

X  (DEP aerodrome only)

15

Route, landing points or alternates

X

X

16

15

Cruising level

X

15

Speed and estimated total elapsed time

X

18

Any change to: STS/PBN/NAV/RMY/(includes
SARTIME)

X

X

19

POB

X

Back to top