ENR 1.10 FLIGHT PLANNING - AIP New Zealand · ENR 1.10 - 2 AIP New Zealand E Civil Aviation...

ENR 1.10 - 1AIP New Zealand

E Civil Aviation Authority

ENR 1.10 FLIGHT PLANNING

1 GENERAL

1.1 Requirements for Flight Plans

1.1.1 CAR Part 91 specifies the requirements relating to the submission,contents, adherence to, cancellation, and termination of flight plans.

1.2 IFR Flight Plans

1.2.1 The pilot of an aircraft must:

(a) submit a flight plan prior to any flight under IFR;

(b) submit the flight plan at least 30 minutes prior to the beginning ofthe flight, and not more than 24 hours before EOBT;

(c) advise the appropriate ATS unit as soon as possible of any delayexceeding 30 minutes in beginning the flight or departing from anyaerodrome of intended landing; and

(d) terminate the flight plan on completion of any flight at anyaerodrome without ATS.

1.3 VFR Flight Plans

1.3.1 The pilot of an aircraft must submit a VFR flight plan prior to thestart of any flight conducted under VFR if:

(a) it is planned for the aircraft to proceed more than 50 NM fromshore; or

(b) an alerting service is required.

1.3.2 In addition to 1.3.1, a VFR flight plan may be submitted for anyother flight conducted under VFR.

1.3.3 For VFR flights proceeding into the Auckland Oceanic FIR the ICAOflight plan format must be used.

1.3.4 The pilot of an aircraft for which a VFR flight plan has beensubmitted must:

(a) inform an appropriate ATS unit of any change to the details in theflight plan and of any change to the flight plan SARTIME before theexpiry of that SARTIME; and

(b) terminate the flight plan by advising an appropriate ATS unit beforethe flight plan SARTIME.

1.3.5 Only one VFR flight plan can be submitted or be active at any onetime for a particular aircraft. A new flight plan cannot be submitted untilthe previous flight plan has been cancelled or terminated.

Effective: 15 NOV 12

ENR 1.10 - 2 AIP New Zealand


1.3.6 When filing a VFR flight plan with the National Briefing Office, if theparticular aircraft does not already have a pre-allocated SSR code, an SSRcode will be allocated to that aircraft for this particular flight. This code willbe advised:

(a) If filing via IFIS — in the receipt message of a successful flight planrequest;

(b) If filing via phone — by the flight briefing officer;

(c) If filing via FAX — by inclusion in the acknowledgement message.

1.4 Change of Flight Rules IFR to VFR Flight Plans

1.4.1 These flight plans should only be filed when:

(a) The destination aerodrome is within the local area adjacent to anaerodrome or navigation aid at which an instrument approach isnecessary for the establishment of visual reference in order toproceed to the destination, e.g. NZPM VFR NZFI, NZCH VFR NZBW;or

(b) The pilot intends to establish visual reference at an en-routeposition then proceed VFR to destination where that destinationdoes not have an instrument approach available to that aircraft,e.g. H240 WEBER VFR NZYP.

1.4.2 These flight plans should not be used for flights where thedestination aerodrome is beyond the local area adjacent to an aerodromeor navigation aid at which an instrument approach can be flown. In thiscase separate IFR and VFR flight plans should be filed.

1.5 Cancelling IFR and Proceeding VFR

1.5.1 Pilots may change from IFR to VFR flight at a pre-planned point, ormay change from IFR to VFR flight by the pilot initiating a messagecontaining the specific expression “CANCELLING IFR FLIGHT”, together withany changes to be made to the flight plan being followed.

1.5.2 Except as indicated below, this is not a termination of a flight planbut a change of flight rules.

1.5.3 When IFR flight is cancelled en-route, the pilot may be requested toprovide a SARTIME for the remaining VFR portion of the flight. In this caseATS will terminate the original flight plan and create a VFR flight plan. Aflight information service will be provided by broadcast and/or request, andan alerting service will be provided. The pilot will be responsible foramending or terminating the VFR flight plan prior to the nominatedSARTIME.

1.5.4 When IFR flight is cancelled prior to departure, the IFR flight planwill be cancelled by ATS. Where required a new flight plan must besubmitted for any subsequent flight.




1.6 Changes of Flight Rules VFR to IFR Flight Plans

1.6.1 For SAR purposes, ATS will treat these flight plans as an IFR flightplan. An alerting service will be provided based on the EOBT of the flight.Pilots must notify ATS of any delay exceeding 30 minutes in beginning theflight. Pilots must make a departure report to ATS as soon as practicableafter take-off, indicating that they are on a flight plan and providing an ETAfor the point at which a change of flight rules is planned.

1.7 Content and Instructions for Completion of Flight Plans

1.7.1 A description of the content, and detailed instructions for completionof, both IFR and VFR flight plans are shown in tables ENR 1.10-1 and ENR1.10-2. This is also provided on the Airways Internet Flight InformationService (IFIS) website (www.ifis.airways.co.nz).

1.8 Advice to ATS of Number of Persons on Board

1.8.1 For all operations at aerodromes where an ATS unit is in operation,the pilots of radio equipped aircraft should pass POB as follows:

(a) Departing aircraft: prior to taxiing onto the manoeuvring area.

(b) Arriving aircraft: on establishing RTF communication withaerodrome control or AFIS.

1.8.2 Pilots of aircraft departing from aerodromes where an ATS unit isnot operating should pass POB information to the first ATS unit theycontact.

2 PROCEDURES FOR THE SUBMISSION OF A FLIGHT PLAN

2.1 General

2.1.1 All flight plans should be submitted to the National Briefing Officeusing IFIS, telephone or fax. During hours of watch and subject toworkload, local IFR and VFR flight plans that affect one ATC unit only maybe filed direct with that unit.

2.1.2 If necessary, a flight plan may be submitted during flight by RTFwith the ATS unit serving the airspace within which the aircraft is beingflown.

2.1.3 Flight plans for aircraft that are not radio equipped (NORDO) andthat are to operate within controlled airspace must be filed in person or bytelephone.

2.1.4 Pilots intending to operate IFR into unattended aerodromes,including attended aerodromes outside of ATS hours, must indicate in item18 (OTHER INFO) of the ICAO flight plan a contact number (and the nameof a person if necessary) that ATS can use to contact the pilot.




2.1.5 A flight plan submitted by fax is not accepted by ATS untilacceptance is confirmed by return fax. This is to guard against receipt ofunreadable faxes. All flight plans submitted by fax must include anoriginator’s fax number. If no return acknowledgement is received withinfive minutes of submitting the plan by fax, the pilot must ring the NationalBriefing Office to confirm that the plan has been received and is acceptableto ATS.

2.1.6 Where an airline has an operations section or utilises the facilities ofanother airline’s operations section, company operations officers maysubmit flight plans. This does not relieve the pilot from the responsibility ofensuring that the flight plan submitted accurately conveys the details ofthe intended flight.

2.1.7 IFR flight plans submitted prior to take-off, including flight plandetails for local IFR training flights, must be submitted at least 30 minutesprior to departure.

2.1.8 IFR flight plans submitted during flight should, as far as practicable,be transmitted to the appropriate ATS unit at least 10 minutes flying timebefore reaching the point of entry into controlled airspace or 20 minutes ifonward transmission of the flight plan to other ATS units is required.

2.1.9 The ATS unit receiving a flight plan, or change to a flight plan, will:

(a) check it for compliance with the format and data conventions;

(b) check it for completeness and, to the extent possible, for accuracy;

(c) take action, if necessary, to make it acceptable to the air trafficservices; and

(d) indicate acceptance of the flight plan, or change to the flight plan,to the originator.

2.2 Submitting an IFR Flight Plan

2.2.1 Except where operators use repetitive flight plans, an IFR flight plan(including flight rules Y [IFR then VFR] and Z [VFR then IFR]) must besubmitted on the ICAO flight plan form (AC 1565), or a computergenerated copy of this form.

2.2.2 Where multi-leg flights intend to carry out approach and departureprocedures at one or more aerodromes en-route, each approach procedureis considered as a landing for the purposes of flight planning. A separateflight plan must be submitted for each leg of the flight.

2.2.3 Some ATS units require verbal pre-coordination of instrumenttraining operations. Details are provided in ENR 1.9.

2.2.4 Pre-filed IFR flight plans will only be available to operatorsundertaking emergency flights in accordance with a prior writtenagreement with the Manager, Support Sector, Christchurch ATSC.

2.2.5 Pre-filed IFR flight plans can only be activated by contacting theNational Briefing Office on Tel 0800 626 756 (landline users only) or(03) 358 1509 (cellphone users).

Effective: 29 MAR 18



2.3 Nominating a VFR Flight Plan SARTIME

2.3.1 The time (in hours and minutes) entered in the SARTIME field of theVFR flight plan is the time that search and rescue action will commence ifthe flight plan is not terminated. When determining SARTIME, pilots shouldallow sufficient time, if required, to get to a telephone or Internet terminalto terminate the flight plan.

2.3.2 Pilots on multi-leg flights may nominate a SARTIME relative to thefirst destination, but must then amend the SARTIME after each landing ortake-off prior to SARTIME.

2.3.3 Pilots wishing to have a SARTIME covering the departure from anunattended or remote aerodrome/heliport, should nominate a SARTIMEwhich would allow them to reach an altitude or position at which a revisedSARTIME could be nominated.

2.3.4 Amending an ETA does not constitute a change of SARTIME. Aspecific request must be made to “AMEND SARTIME”, and any amendmentmust always be made before the existing SARTIME expires.

2.4 Identification of Operating Area

2.4.1 Pilots of aircraft intending to carry out aerial photography, aerialsurvey, aerial inspection, or aerial search operations may identify theirintended area of operations by grid reference using NZMS 260 sheet index.The area is identified using the NZMS 260 sheet number, followed by theletter identifying the quadrant(s) within the sheet cover, i.e.

2.4.2 This information should be included in the other information field ofthe VFR flight plan, e.g. “aerial photography area V15D”, or item 18 of theICAO flight plan, e.g. STS/PHOT area V15D.

3 REPETITIVE FLIGHT PLAN SYSTEM

3.1 General

3.1.1 Repetitive Flight Plans (RPL) will be accepted on the following basis:

(a) For IFR flights only, operated on the same day(s) of consecutiveweeks and on at least 10 occasions OR operated every day over aperiod of at least 10 consecutive days;

(b) RPL listings must be submitted at least 7 days prior to their effectivedate;

Effective: 7 JUN 07

A

C

V15

D

B



(c) The route of the RPL must be the Standard Route Clearance for theaerodrome pair, or its equivalent, or where no applicable standardroute clearance is published, the route field must be in the sameformat as required in the ICAO flight plan form;

(d) Days of the week and EOBT are to be in UTC;

(e) Supplementary information (item 19 of ICAO flight plan) must bekept readily available by the operator and supplied to ATS onrequest;

(f) Amendments to RPL listings must be submitted at least 7 days priorto effective date.

3.2 Acceptance of RPL listings

3.2.1 RPL listings may be submitted by post, fax, or email to:

RPL OfficeAirways Corporation of New Zealand LtdPO Box 14-131Christchurch Airport 8544

Fax (03) 358 9192 (Attention: RPL Office)Email [email protected]

3.2.2 It is preferred that RPL listings be provided in electronic format. Fordetailed instructions for filing RPL listings, contact the RPL Office orNational Briefing Office.

4 CHANGES TO THE SUBMITTED FLIGHT PLAN

4.1 Changing a VFR Flight Plan

4.1.1 Any field in a VFR flight plan may be changed except the AircraftRegistration and the Aircraft Type. Any changes to the flight plan must bereferenced by the aircraft registration, not the aircraft callsign, and can bemade by contacting any ATS unit or the National Briefing Office. If theflight plan was filed via IFIS, the plan can also be changed using IFIS butonly via the same user-name.

4.2 Changes to Filed IFR Flight Plans (including RPL)

4.2.1 Pilots must advise any changes to a filed IFR flight plan or activeRPL to the National Briefing Office at least 30 minutes prior to EOBT oractual time of departure, whichever comes first, except that changes tocruising level only may be notified to an ATS unit on initial contact withthat unit.

4.2.2 Failure to notify changes of aircraft type may have an effect onflight plan route and ATC separation standards applied to flights.

Effective: 12 FEB 09



4.2.3 Change of Operator (Wet Leasing). When a flight, for which a flightplan exists for the original operator, is required to be carried out by asecond operator, the following procedures apply:

(a) The original operator is responsible for cancelling the flight planactivated for the intended flight.

(b) The operator who will actually carry out the flight is responsible forfiling a flight plan and ensuring that ALL aspects of the new plan arecorrect.

(c) The RTF designator used in the new flight plan will indicate thecompany responsible for all Air Navigation charges (for AirwaysServices) related to that flight.

5 TERMINATION OF FLIGHT PLANS

5.1 IFR Flight Plan

5.1.1 Flights arriving at aerodromes where ATS is in attendance will havetheir flight plans automatically terminated by ATS.

5.1.2 Flights arriving at other aerodromes must contact ATS within 15minutes of the last acknowledged ETA at that aerodrome, or terminate bySARTIME if one has been nominated.

5.2 VFR Flight Plan

5.2.1 Pilots must request that their VFR flight plans be terminated,because SAR action will be initiated at the nominated SARTIME unless theflight plan has been terminated.

5.2.2 On arrival at an ATS or UNICOM attended aerodrome, pilots wishingto terminate their flight plan must specify this to ATS or UNICOM andreceive an acknowledgement.

5.3 Contact Details

5.3.1 Flight plans may be terminated via:

(a) telephone 0800 626 756 (landline users only) or (03) 358 1509(cellphone users);

(b) request with any ATS unit, flight information sector or UNICOM; or

(c) IFIS, if the VFR flight plan was filed via IFIS, but only by the sameuser-name.




Table ENR 1.10 - 1Instructions for Completion of an ICAO Flight Plan Form

Note: The term ‘aerodrome’ as used in this table refers to any aerodrome,heliport or landing site which may be used.

ITEM 7: AIRCRAFT IDENTIFICATION (Maximum 7 characters)

INSERT one of the following aircraft identifications:

(a) the nationality or common mark and registration mark of the aircrafte.g. ZKNSK, NZ7571, N8735Y,

OR

(b) the designator for the aircraft operating agency followed by theflight identification e.g. ANZ14, QFA145.

Approved designators for aircraft operating agencies can be found on theCAA website.

ITEM 8: FLIGHT RULES AND TYPE OF FLIGHT (1 or 2 characters)

Flight Rules

INSERT a single character denoting the category of flight ruleswhich the pilot intends to comply:

I – if IFRY – if the flight initially will be operated IFR, followed by one ormore subsequent changes of flight rules

Z – if the flight initially will be operated VFR, followed by one ormore subsequent changes of flight rules

V – VFR

Flight rules V not available for flights that will operate wholly within theNew Zealand FIR. Use NZ domestic VFR flight plan.

For flight rules Y and Z it is necessary to specify in the route field (item 15)the point or points where the change of flight rules is planned.

Type of Flight

INSERT one of the following letters to denote type of flight:

S – if Scheduled Air ServiceN – if Non-scheduled Air Transport OperationG – if General AviationM – if MilitaryX – if other than any of the above categories

Where necessary specify status of the flight using indicator STS/ in item 18,or when necessary to denote other reasons for specific handling by ATS useindicator RMK/ in item 18.




ITEM 9: NUMBER AND TYPE OF AIRCRAFT AND WAKE TURBULENCECATEGORY

Number of Aircraft

INSERT the number of aircraft if more than one, otherwise leave blank.

Aircraft type

INSERT the aircraft type designator — refer IFIS aircraft type designatortable or ICAO Doc 8643, for type designators and waketurbulence category.

If the type of your aircraft does not match anything listed then enter ZZZZand specify type in item 18 under TYP/.

Wake Turbulence Category

INSERT the wake turbulence category for the aircraft type. Use H(heavy) or M (medium) or L (light).




ITEM 10: EQUIPMENT AND CAPABILITIES

Capabilities comprise the following elements:

(a) presence of relevant serviceable equipment on board the aircraft;

(b) equipment and capabilities commensurate with flight crewqualifications; and

(c) where applicable, authorisation from the appropriate authority.

Radio Communication, Navigation and Approach Aid Equipment andCapabilities

INSERT one letter as follows:

N – if no COM/NAV/approach aid equipment for the route to be flown iscarried, or the equipment is unserviceable.

S – if standard COM/NAV/approach aid equipment for the route to beflown is carried and serviceable.

Standard equipment is considered to be VHF RTF, VOR and ILS.

AND/OR one or more of the following to indicate the serviceable COM/NAV/approach aid equipment and capabilities:

A – GBAS landing system K – MLSB – LPV (APV with SBAS) L – ILSC – LORAN C M1 – ATC SATVOICE (INMARSAT)D – DME M2 – ATC SATVOICE (MTSAT)E1 – FMC WPR ACARS M3 – ATC SATVOICE (Iridium)E2 – D-FIS ACARS O – VORE3 – PDC ACARS P1 CPDLC RCP 400F – ADF P2 CPDLC RCP 240G – GNSS (see Note 1) P3 SATVOICE RCP 400H – HF RTF P4–P9 Reserved for RCPI – Inertial Navigation R – PBN approved (see Note 2)J1 – CPDLC ATN VDL Mode 2 T – TACANJ2 – CPDLC FANS 1/A HFDL U – UHFJ3 – CPDLC FANS 1/A VDL Mode A V – VHFJ4 – CPDLC FANS 1/A VDL Mode 2 W – RVSM approvedJ5 – CPDLC FANS 1/A SATCOM X – MNPS approved

(INMARSAT) Y – VHF with 8.33 kHz channelJ6 – CPDLC FANS 1/A SATCOM spacing

(MTSAT) Z – Other equipment carried orJ7 – CPDLC FANS 1/A SATCOM other capabilities

(Iridium) (see Note 3)

Effective: 14 SEP 17



Note 1 Inclusion of the letter G indicates that an aircraft meets theconditions and requirements for the use of GNSS (GPS)equipment. Types of external GNSS augmentation, if any, arespecified in Item 18 following the indicator NAV/ separated bya space.

Note 2 Inclusion of the letter R indicates that an aircraft meets theRNP type prescribed for the route segment(s), route(s), orarea concerned. The performance based navigation levelsthat can be met are specified in Item 18 following theindicator PBN/.

Note 3 If the letter Z is used, the other equipment carried or othercapabilities are specified in Item 18 following the indicatorCOM/, NAV/, or DAT/ as appropriate.

Surveillance Equipment and Capabilities

INSERT N – if no surveillance equipment for the route to be flown iscarried, or the equipment is unserviceable,

OR

one or more of the following descriptors, to a maximum of 20 characters,to describe the serviceable surveillance equipment and/or capabilities onboard:

SSR Modes A and C

A Transponder — Mode A (4 digits — 4 096 codes)CAR 91.247 does not permit Mode A only operations in NZ

C Transponder — Mode A (4 digits — 4 096 codes) and Mode C

SSR Mode S

E Transponder — Mode S, including aircraft identification,pressure-altitude and extended squitter (ADS-B) capability

H Transponder — Mode S, including aircraft identification,pressure-altitude and enhanced surveillance capability

I Transponder — Mode S, including aircraft identification,but no pressure-altitude capability

L Transponder — Mode S, including aircraft identification,pressure-altitude, extended squitter (ADS-B) and enhancedsurveillance capability

P Transponder — Mode S, including pressure-altitude,but no aircraft identification capability




S Transponder — Mode S, including both pressure altitude andaircraft identification capability

X Transponder — Mode S with neither aircraft identification norpressure-altitude capability

Note — Enhanced surveillance capability is the ability of the aircraft todown-link aircraft derived data via a Mode S transponder.

ADS-B

B1 ADS-B with dedicated 1090 MHz ADS-B “out” capability

B2 ADS-B with dedicated 1090 MHz ADS-B “out” and “in” capability

U1 ADS-B “out” capability using UAT

U2 ADS-B “out” and “in” capability using UAT

V1 ADS-B “out” capability using VDL Mode 4

V2 ADS-B “out” and “in” capability using VDL Mode 4

ADS-C

D1 ADS-C with FANS 1/A capabilities

G1 ADS-C with ATN capabilities

Note — Additional surveillance equipment or capabilities are to be listed inItem 18 following the indicator SUR/.

ITEM 13: DEPARTURE AERODROME AND TIME (8 characters)

Departure Aerodrome

INSERT The ICAO 4 letter location indicator of the departure aerodrome.

OR If no location indicator has been assigned, insert ZZZZ andspecify in item 18 the name and location of the aerodromepreceded by DEP/.

Time

INSERT The estimated off-block time (EOBT) expressed in UTC hhmmformat.




ITEM 15: SPEED/LEVEL/ROUTE

Cruising Speed (maximum 5 characters)

INSERT The true airspeed for the first or whole portion of the flight, interms of:

Knots — N followed by 4 figures (e.g. N0485); or

Mach number — M followed by 3 figures (e.g. M086).

Cruising Level (maximum 5 characters)

INSERT The planned cruising level for the first or whole portion of theflight, in terms of:

Flight Level — F followed by 3 figures (e.g. F240); or

Altitude — A followed by 3 figures (e.g. A090); or

For uncontrolled VFR flights — VFR

Route (including changes of speed, level and/or flight rules)

Note: For flights operating within the New Zealand FIR do not insert SID orSTAR designators into this item of the flight plan.

Domestic flights using the Standard Route Clearance Delivery System

INSERT the name for the designated route consisting of the standardroute clearance designator without spaces or gaps, e.g. WNHN2

Standard Route Clearances, where designated, are listed in the AIP witheach ADES. Standard Route Clearances constitute the ATS preferred routeswithin New Zealand.

Standard Route Clearance designators may only be used in the route fieldof a flight plan if they describe the route fully from ADEP to ADES. If otherroute segments need to be added, the route field of the flight plan mustcontain full route data applicable to that standard route clearance withother segments added.

Flights along designated ATS Routes

INSERT If the departure aerodrome is located on, or connected to theATS route, the designator of the first ATS route.

NOTE: A departure aerodrome is connected to the ATS route if the last twoletters of the aerodrome location indicator are the same as the ident of theNAVAID in the route description e.g. flight departing NZAA and ‘AA’ VOR inroute description.

OR If the departure aerodrome is not located on, or connected to theATS route (e.g. flight departing NZDN and ‘SW’ VOR in route description),the letters DCT followed by the point of joining the first ATS route (whichalso may be the NAVAID serving the ADES), followed by the designator ofthe ATS route.

Effective: 26 MAY 16



THEN INSERT each point at which either a change of speed and/or level isplanned to commence, or a change of ATS route, and/or a change of flightrules is planned.

NOTE: When a transition is planned between a lower and upper ATS routeand routes are orientated in the same direction, the point of transitionneed not be inserted.

FOLLOWED IN EACH CASE by the designator of the next ATS routesegment, even if the same as the previous one,

OR by DCT if the flight to the next point will be outside a designated route,unless both points are defined by geographical co-ordinates.

The route fields of Standard Route Clearances listed in the AIP areconstructed in the manner described above.

Flights outside designated ATS Routes

INSERT points normally not more than 30 minutes apart, including eachpoint where a change of speed or level, a change of track, or a change offlight rules is planned.

OR define the track of the flight by reference to significant points locatedat half or whole degrees of latitude and/or longitude. Points should be nomore than 1 hours flying time apart, and include each point where achange of speed or level, a change of track, or a change of flight rules isplanned.

INSERT DCT between successive points unless both points are defined bygeographical coordinates or by bearing and distance.

USE ONLY the conventions below and separate each sub-item with aspace:

(a) ATS ROUTE (2 to 7 characters)

The designator assigned to the route or route segment, includingthe designator assigned to the standard departure or arrival route.

(b) SIGNIFICANT POINT (2 to 11 characters)

The coded designator assigned to the point, or if one has not beenassigned:

(i) Latitude and Longitude (7 to 11 characters)

2 figures describing the latitude in degrees, or 4 figuresdescribing latitude in degrees and minutes, followed by N orS, followed by 3 figures describing the longitude in degrees or5 figures describing the longitude in degrees and minutes,followed by E or W, or any combination thereof.(e.g. 42S168E or 4230S16809E or 4230S168E or 42S16809E)




(ii) Bearing and distance from a reference point (8 to 11characters)

The identification of the reference point/navigation aid (max5 characters), THEN the bearing from that point in the formof 3 figures giving degrees Magnetic, THEN the distance fromthat point in the form of 3 figures expressing nautical miles(AA180040).

(c) CHANGE OF SPEED OR LEVEL (maximum 21 characters)

The point at which a change of speed or a change of level is plannedto commence, expressed as in (b) above, followed by an obliquestroke and both the cruising speed and cruising level, without aspace between them, even when only one of these quantities will bechanged,

(e.g. ...MEKEP/N0420F330... or ...4602S07805W/N0500F350...)

(d) CHANGE OF FLIGHT RULES (maximum 3 characters)

The point at which the change of flight rules is planned, expressedas in (b) or (c) above as appropriate, followed by a space and oneof the following:

VFR — if from IFR to VFR

IFR — if from VFR to IFR

(e.g. MAMUS VFR TU/N0284A070 IFR)

(e) CRUISE CLIMB (maximum 28 characters)

The letter C followed by an oblique stroke; THEN the point at whichcruise climb is planned to start, expressed exactly as in (b) above,followed by an oblique stroke; THEN the speed to be maintainedduring cruise climb, followed by the two levels defining the layer tobe occupied during cruise climb; OR the level above which cruiseclimb is planned followed by the letters PLUS, without a spacebetween them.

(e.g. C/APORO/M082F290F350, C/APORO/M083F360PLUS)




ITEM 16: DESTINATION AERODROME, TOTAL ELAPSED TIME,DESTINATION ALTERNATE AERODROME(S)(12 characters)

Destination Aerodrome

INSERT The ICAO 4-letter location indicator of the destination aerodrome,or for intended multi-leg flights, the 4-letter location indicator ofthe aerodrome at which the first instrument approach will bemade.

If no location indicator has been assigned, insert ZZZZ andspecify in item 18 the name and location of the aerodromepreceded by DEST/.

Total Elapsed Time

INSERT The total estimated elapsed time from take-off to arrive over thedestination aerodrome.

Destination Alternate Aerodrome(s)

INSERT The ICAO 4 letter location indicator of not more than twodestination alternate aerodromes.

If no location indicator assigned to one or both destinationalternate aerodromes, insert ZZZZ and specify in item 18 thename and location of the destination alternate aerodrome(s)preceded by ALTN/.

Refer CAR 91 for New Zealand alternate requirements.




ITEM 18: OTHER INFORMATION

INSERT 0 (zero) if no other information,

OR

Any other necessary information in the sequence shown hereunder, in theform of the appropriate indicator followed by an oblique stroke and theinformation to be recorded:

STS/ Reason for special handling by ATS, e.g. a search and rescuemission, as follows:

ALTRV for a flight operated in accordance with an altitudereservation;

ATFMX for a flight approved for exemption from ATFMmeasures by the appropriate ATS authority;

FFR fire-fighting;

FLTCK flight check for calibration of Navigation Aids;

HAZMAT for a flight carrying hazardous material;

HEAD for a flight with Head of State status;

HOSP for a medical flight declared by medical authorities;

HUM for a flight operating on a humanitarian mission;

MARSA for a flight for which a military entity assumesresponsibility for separation of military aircraft;

MEDEVAC for a life critical medical emergency evacuation;

NONRVSM for a non-RVSM capable flight intending to operate inRVSM airspace;

SAR for a flight engaged in a search and rescue mission; and

STATE for a flight engaged in military, customs or policeservices.

For NZ domestic use only:

IFT instrument rating flight test — initial issue

PHOT photography

T1A IFR training one approach.Insert different number if more than one approach.

Other reasons for special handling by ATS shall be denoted under thedesignator RMK/.

PBN/ Indication of RNAV and/or RNP capabilities. Include as many ofthe descriptors below, as apply to the flight, up to a maximum of8 entries, i.e. a total of not more than 16 characters.

If there are more than 8 applicable entries, identify thoseconsidered least relevant to the flight and insert them within item18 under NAV/.

Effective: 4 APR 13



RNAV SPECIFICATIONS

A1 RNAV 10 (RNP 10)

B1 RNAV 5 all permitted sensors (except LORANC)

B2 RNAV 5 GNSS

B3 RNAV 5 DME/DME

B4 RNAV 5 VOR/DME

B5 RNAV 5 INS or IRS

B6 RNAV 5 LORANC

C1 RNAV 2 all permitted sensors

C2 RNAV 2 GNSS

C3 RNAV 2 DME/DME

C4 RNAV 2 DME/DME/IRU (C4 = C3 and C4)

D1 RNAV 1 all permitted sensors

D2 RNAV 1 GNSS

D3 RNAV 1 DME/DME

D4 RNAV 1 DME/DME/IRU (D4 = D3 and D4)

RNP SPECIFICATIONS

L1 RNP 4

O1 RNP 1 all permitted sensors

O2 RNP 1 GNSS

O3 RNP 1 DME/DME

O4 RNP 1 DME/DME/IRU (O4 = O3 and O4)

S1 RNP APCH

S2 RNP APCH with BARO-VNAV

T1 RNP AR APCH with RF (special authorisation required)

T2 RNP AR APCH without RF (special authorisation required)

insert S1 or S2, subject to capability

insert T1 or T2, subject to capability

Effective: 29 MAY 14



NAV/ Significant data related to navigation equipment, other thanspecified in PBN/, as required by the appropriate ATS authority.Indicate GNSS augmentation under this indicator, with a spacebetween two or more methods of augmentation, e.g. NAV/GBASSBAS.

COM/ Indicate communication equipment and capabilities not specifiedin Item 10a.

DAT/ Indicate data communication equipment and capabilities notspecified in 10a.

SUR/ Indicate surveillance applications or capabilities not specified inItem 10b. Indicate as many RSP specification(s) as apply to theflight, using designator(s) with no space. Multiple RSPspecifications are separated by a space. Example: RSP180RSP400

DEP/ Name and location of departure aerodrome, if ZZZZ is inserted inItem 13, or the ATS unit from which supplementary flight plan datacan be obtained, if AFIL is inserted in Item 13. For aerodromes notlisted in the relevant Aeronautical Information Publication, indicatelocation as follows:

With 4 figures describing latitude in degrees and tens and units ofminutes followed by “N” (North) or “S” (South), followed by 5figures describing longitude in degrees and tens and units ofminutes, followed by “E” (East) or “W” (West). Make up thecorrect number of figures, where necessary, by insertion of zeros.

Example: 4724S17905E (11 characters)

OR,

Bearing and distance from the nearest significant point, asfollows:

The identification of the significant point followed by the bearingfrom the point in the form of 3 figures giving degrees magnetic,followed by the distance from the point in the form of 3 figuresexpressing nautical miles. In areas of high latitude where it isdetermined by the appropriate authority that reference to degreesmagnetic is impractical, degrees true may be used. Make up thecorrect number of figures, where necessary, by insertion of zeros,e.g. a point of 160° magnetic at a distance of 40 nautical milesfrom VOR ‘GS’ should be expressed as GS160040.

OR,

The first point of the route (name or LAT/LONG) or the markerradio beacon, if the aircraft has not taken off from an aerodrome.




DEST/ Name and location of destination aerodrome, if ZZZZ is insertedin Item 16. For aerodromes not listed in the relevant AeronauticalInformation Publication, indicate location in LAT/LONG or bearingand distance from the nearest significant point, as describedunder DEP/ above.

DOF/ The date of flight departure in a six figure format (YYMMDD,where YY equals the year, MM equals the month and DD equalsthe day).In NZ flight plans cannot be submitted more than 24 hours inadvance of EOBT.

REG/ The nationality or common mark and registration mark of theaircraft, if different from the aircraft identification in Item 7.

EET/ Significant points or FIR boundary designators and accumulatedestimated elapsed times from take-off to such points or FIRboundaries, when so prescribed on the basis of regional airnavigation agreements, or by the appropriate ATS authority.

Example: EET/YBBB0010 NZZO0123 NZZC0211

SEL/ SELCAL Code, for aircraft so equipped.

TYP/ Type(s) of aircraft, preceded if necessary without a space bynumber(s) of aircraft and separated by one space, if ZZZZ isinserted in Item 9.

Example: TYP/5CT4

CODE/ Aircraft address (expressed in the form of an alphanumerical codeof six hexadecimal characters) when required by the appropriateATS authority. Example: “F00001” is the lowest aircraft addresscontained in the specific block administered by ICAO.

MODE S equipped aircraft must include the MODE S address.

Example: CODE/C81111

DLE/ Enroute delay or holding, insert the significant point(s) on theroute where a delay is planned to occur, followed by the length ofdelay using four figure time in hours and minutes (hhmm).

Example: DLE/NISET0030

OPR/ ICAO designator or name of the aircraft operating agency, ifdifferent from the aircraft identification in item 7.

ORGN/ The originator’s 8 letter AFTN address or other appropriatecontact details, in cases where the originator of the flight planmay not be readily identified, as required by the appropriate ATSauthority.

Note — In some areas, flight plan reception centres may insertthe ORGN/ identifier and originator’s AFTN address automatically.




PER/ Aircraft performance data, indicated by a single letter as specifiedin the Procedures for Air Navigation Services — AircraftOperations (PANS-OPS, Doc 8168), Volume I — Flight Procedures,if so prescribed by the appropriate ATS authority.

ALTN/ Name of destination alternate aerodrome(s), if ZZZZ is inserted inItem 16. For aerodromes not listed in the relevant AeronauticalInformation Publication, indicate location in LAT/LONG or bearingand distance from the nearest significant point, as described inDEP/ above.

RALT/ ICAO four letter indicator(s) for enroute alternate(s), as specifiedin Doc 7910, Location Indicators, or name(s) of enroute alternateaerodrome(s), if no indicator is allocated. For aerodromes notlisted in the relevant Aeronautical Information Publication,indicate location in LAT/LONG or bearing and distance from thenearest significant point, as described in DEP above.

TALT/ ICAO four letter indicator(s) for take-off alternate, as specified inDoc 7910, Location Indicators, or name of take-off alternateaerodrome, if no indicator is allocated. For aerodromes not listedin the relevant Aeronautical Information Publication, indicatelocation in LAT/LONG or bearing and distance from the nearestsignificant point, as described in DEP/ above.

RIF/ The route details to the revised destination aerodrome, followedby the ICAO four-letter location indicator of the aerodrome. Therevised route is subject to reclearance in flight.

Example: RIF/AA H211 NZHN

RMK/ Any other plain language remarks when required by theappropriate ATS authority or deemed necessary.




ITEM 19: SUPPLEMENTARY INFORMATION

Endurance

After E/ INSERT a 4 figure group giving the fuel endurance in hours andminutes.

Persons on Board

After P/ INSERT the total number of persons (passengers and crew) onboard.Insert TBN if not known at time of filing.

Emergency and Survival Equipment

R/ (Radio)CROSS OUT U if UHF on frequency 243.0 MHz is NOT available.CROSS OUT V if VHF on frequency 121.5 MHz is NOT available.CROSS OUT E if emergency locator transmitter (ELT) is NOTavailable.

S/ (Survival Equipment)CROSS OUT all indicators if survival equipment is NOT carried.CROSS OUT P if polar survival equipment is NOT carried.CROSS OUT D if desert survival equipment is NOT carried.CROSS OUT M if maritime survival equipment is NOT carried.CROSS OUT J if jungle survival equipment is NOT carried.

J/ (Jackets)CROSS OUT all indicators if life jackets are NOT carried.CROSS OUT L if life jackets are NOT equipped with lights.CROSS OUT F if life jackets are NOT equipped with fluorescein.CROSS OUT U or V or both as in R/ above to indicate radiocapability of jackets, if any.

D/ (Dinghies)CROSS OUT indicators D and C if no dinghies carried; orINSERT number of dinghies carried; andINSERT total capacity, in persons, of all dinghies carried; andCROSS OUT C if dinghies are NOT covered; andINSERT colour of dinghies if carried.

A/ (Aircraft colour and markings)INSERT colour of aircraft and significant markings.

N/ (Remarks)CROSS OUT indicator N if no remarks; orINDICATE any other survival equipment carried and any otherremarks regarding survival equipment.

C/ (Pilot)INSERT name of pilot-in-command.

Filed by

INSERT name of unit, agency or person filing the flight plan.




Table ENR 1.10 - 2Instructions for Completion of a Domestic VFR Flight Plan

(to be used only when flight is contained within the New Zealand FIR)

When submitting a VFR flight Plan the following details must be provided:

1 Aircraft Registration (between 4 and 7 characters)Insert the registration marking of the aircraft.This is the unique reference for this plan and all further references to thisflight plan must quote this registration.

2 Aircraft Callsign (between 1 and 20 characters)To be inserted only if this is different to the aircraft’s registration.The callsign is to be used in RTF communication except that any referenceto the flight plan must reference the aircraft registration.

3 Aircraft Type (between 2 and 4 characters)Insert the appropriate ICAO or NZ only designator. Refer IFIS —PLANNING INFO for appropriate designator.

4 Route Details including destinationInsert details of the proposed flight. The degree of detail provided willdetermine the ease with which any subsequent search and rescue actionwill be carried out. Points of departure and landing, aerodromes overflown,elapsed times, and brief landing times should be included.

5 SARTIME (4 or 6 characters)This is the time that an alerting service will be initiated. Insert 4characters as HHMM for hours and minutes, or 6 characters as DDHHMMfor day, hours and minutes. Time must be in UTC.

6 Fuel Endurance (4 characters)7 Number of Persons on Board

Use oblique strokes (/) to separate multi-leg flights where the POB willchange.

8 Other InformationInsert information useful for search and rescue e.g. NORDO (non-radio)

9 Pilot-in-Command10 Contact Number

Insert telephone/cellphone contact numbers for search and rescuepurposes.

11 OperatorInsert name of operator if the operator is not the Pilot-in-Command.

SARTIME:D Time in minutes only is not acceptable to ATS.D Pilots on multi-leg flights may nominate a SARTIME relative to the firstdestination, and then must amend the SARTIME after each landing ortake-off.

D Pilots wishing to have a SARTIME covering the departure from an unattendedor remote aerodrome/heliport, should nominate a SARTIME which wouldallow them to reach an altitude or position at which a revised SARTIME couldbe nominated.

D Amending an ETA does not constitute a change of SARTIME. A specificrequest must be made to “AMEND SARTIME”.

D Amendments to SARTIME must always be made before the existing SARTIMEexpires.




Table ENR 1.10 - 2Instructions for Completion of a Domestic VFR Flight Plan

1. Aircraft Registration:

2. Aircraft Callsign:

3. Aircraft Type:

4. Route:_____________________________________________

____________________________________________________

____________________________________________________

5. SARTIME:

6. Fuel Endurance:

7. Persons on Board:

8. Other Information:_________________________________

____________________________________________________

____________________________________________________

9. Pilot-in-Command:

10.Contact Number:

11.Operator:

File on http://www.ifis.airways.co.nz; orPHONE 0800 NBO PLN (0800 626 756) landline users only; or

PHONE (03) 358 1509 (cellphone users); orFAX 0800 NBO FAX (0800 626 329)

If submitting by FAX, include originators FAX number. If no return acknowledgement isreceived within 5 minutes of submitting the plan, the pilot must ring the National

Briefing Office (see numbers above) to confirm that the plan has been received and isacceptable to ATS.


ENR 1.10 FLIGHT PLANNING - AIP New Zealand · ENR 1.10 - 2 AIP New Zealand E Civil Aviation...

Documents

Transcript of ENR 1.10 FLIGHT PLANNING - AIP New Zealand · ENR 1.10 - 2 AIP New Zealand E Civil Aviation...