曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
when providing SPFIB or for flight notifications.
3.2.4 Common names are stored in the NAIPS database in accordance with ERSA conventions.
Retrieval of locations from NAIPS using the common name function requires a correct
match with the name. Special cases are as follows:
a. In the case of two names separated by an oblique stroke, eg. Maroochydore
/Sunshine Coast, the location is retrieved by the first common name only.
b. For locations associated with a capital city aerodrome (eg PERTH/Jandakot,
BRISBANE/Archerfield) the location is retrieved by use of the second common name
( i.e. Jandakot, Archerfield).
c. Common names for airspace groups are retrieved by the use of the name plus the
word "airspace".
d. If the common name for a location is in doubt, a search directory is available.
3.2.5 NAIPS Pilot Access AVBL via 0198 304 767.
3.3 SPFIB
3.3.1 Using an SPFIB, either by request through the briefing offices or via the pilot access
facility, will allow retrieval of MET and NOTAM information relevant to the departure,
destination and en route locations of a flight, relevant to the planned flight altitude. The
SPFIB includes Head Office (Australia General) NOTAM, and for flights above 10000FT,
a wind and temperature profile.
3.3.2 An SPFIB briefing, using either a description of the route with turning points (called `ad
hoc'), or a stored route of up to ten stages of a flight, can be stored and retrieved as a
flight file. The default data from an SPFIB can also be transferred to a flight notification,
obviating the need to re-enter the default information.
3.3.3 An SPFIB using a stored route still requires a pilot to ensure that off-track NAVAID
information relevant to the flight is included in the briefing, if required. This additional
information is provided by requesting "additional locations" as required, once the stored
route data is requested.
3.4 Preflight Briefing - Stored Routes
3.4.1 What is Received When a Low Level Stored Route is Used:
© Airservices Australia, 2005 Licensed to: Preview Licence MyAIP678901234567890 SeqId
FIS: PREFLIGHT 24-Nov-2005 GEN - PF - 2
a. Low level stored routes are for briefings up to FL200. Low routes are prefixed with
` L' followed by a number. A list of stored routes can be retrieved when using pilot
access by inserting a question mark in the route field prompt and pressing the `enter'
key.
b. SPFIBs generated from low level stored routes will contain:
(i) Head Office NOTAM;
(ii) AIP SUP summary;
(iii) FIR NOTAM relevant to the route;
(iv) MET and NOTAM for departure and destination;
(v) NOTAM on PRD areas within 50NM radius of departure and destination;
(vi) NOTAM for all locations within 50NM either side of track, except surface NOTAM;
(vii) Area forecasts, Area QNH, AIRMET, SIGMET, AIREP special, relevant to the
route;
(viii) MET warning messages; and
(ix) Wind and Temperature profile defined from processed meteorological data in
the form of grid point values expressed in binary form (GRIB) (for flights above
10000FT).
3.4.2 What is Received When a High Level Stored Route is Used:
a. High level stored routes are for briefings above FL185. High routes are prefixed with
`H' followed by a number. A list of stored routes can be retrieved when using pilot
access by inserting a question mark in the route field prompt and pressing the enter
key.
b. SPFIBs generated from high level stored routes will contain:
(i) Head Office NOTAM;
(ii) AIP SUP summary
(iii) FIR NOTAM relevant to the route;
(iv) MET and NOTAM for departure and destination;
(v) NOTAM on PRD areas within 50NM radius of departure and destination;
(vi) NOTAM specific to the route except surface NOTAM;
(vii) SIGMET relevant to the route;
(viii) MET warning message; and
(ix) Wind and Temperature profile defined from gridded binary (GRIB) data.
c. NOTAM on off-track NAVAIDs, published as being required for position fixing or
track reference, are not included.
3.4.3 What is Received When an Ad Hoc SPFIB is Requested by Describing the Route:
a. Where a stored route is not available or not required, an SPFIB can be obtained by
entering the departure, destination, and by describing the route as being direct (DCT),
or by entering the turning points up to a maximum of 30.
b. Using this method, SPFIB will automatically contain:
(i) Head Office NOTAM;
(ii) AIP SUP summary;
(iii) MET and NOTAM for the departure and destination;
(iv) NOTAM on nominated turning points;
(v) NOTAM on PRD areas within 50NM radius of departure and destination, except
where the departure and/or destination is entered as a Latitude and Longitude,
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
澳大利亚ERSA(107)
