AIR TRAFFIC CONTROL
.pdf
464 |
AIR TRAFFIC CONTROL |
24 FEB 06 |
APPENDIX 2 — FLIGHT PLAN
5 EXAMPLE OF COMPLETED FLIGHT PLAN FORM
© JEPPESEN SANDERSON, INC. 2000, 2006. ALL RIGHTS RESERVED.
24 FEB 06 AIR TRAFFIC CONTROL |
465 |
APPENDIX 2 — FLIGHT PLAN
6 ICAO MODEL REPETITIVE FLIGHT PLAN (RPL) LISTING FORM
© JEPPESEN SANDERSON, INC. 2000, 2006. ALL RIGHTS RESERVED.
466 |
AIR TRAFFIC CONTROL |
24 FEB 06 |
APPENDIX 2 — FLIGHT PLAN
7INSTRUCTIONS FOR THE COMPLETION OF THE REPETITIVE FLIGHT PLAN (RPL) LISTING FORM
7.1GENERAL
List only flight plans that will operate in accordance with IFR. (Flight rules I in FPL format).
It is assumed that all aircraft are operating as scheduled flights (Type of flight S in FPL format), otherwise notify in Q (Remarks).
It is assumed that all aircraft operating on RPLs are equipped with 4096-code transponders with Modes A and C. Otherwise, notify in Q (Remarks).
List flight plan in alphabetical order of the location indicator of the departure aerodrome.
List flight plans for each departure aerodrome in chronological order of estimated off-block times.
Adhere closely to the data conventions as indicated for the Flight Plan Form (Appendix 3, 1.6) unless otherwise specifically indicated in 7.4.
INSERT all clock times in 4 figures UTC.
INSERT all estimated elapsed times in 4 figures (hours and minutes).
INSERT data on a separate line for each segment of operations with one or more stops; i.e., from any departure aerodrome to the next destination aerodrome even though call sign or flight number is the same for multiple segments.
Clearly identify additions and deletions in accordance with Item H at 7.4. Subsequent listings shall list the corrected and added data, and deleted flight plans shall be omitted.
Number pages by indicating number of page and total number of pages in submission.
Utilize more than one line for any RPL where the space provided for items O and Q on one line is not sufficient.
7.2A flight shall be cancelled as follows:
a.Indicate a minus sign in Item H followed by all other items of the cancelled flight;
b.Insert a subsequent entry denoted by a plus sign in Item H and the date of the last flight in Item J, with all other items of the cancelled flight unchanged.
7.3 Modification to a flight shall be made as follows:
a.Carry out the cancellation as indicated in 7.2; and
b.Insert a third entry giving the new flight plan(s) with the appropriate items modified as necessary, including the new validity dates in Items I and J.
NOTE: All entries related to the same flight will be inserted in succession in the order specified above.
7.4INSTRUCTIONS FOR INSERTION OF RPL DATA
Complete Items A to Q as indicated hereunder.
INSERT last date (year, month, day) upon which the flight is scheduled to operate as listed, or
© JEPPESEN SANDERSON, INC. 2000, 2006. ALL RIGHTS RESERVED.
24 FEB 06 AIR TRAFFIC CONTROL |
467 |
APPENDIX 2 — FLIGHT PLAN
UFN if the duration is unknown.
INSERT items of information as required by the appropriate ATS authority, items normally notified in Item 18 of the ICAO flight plan and any other information pertinent to the flight of concern to ATS.
(Item 15 of the ICAO flight plan)
a.Cruising Speed
INSERT the true airspeed for the first or whole cruising portion of the flight in accordance with Item 15A. of the ICAO flight plan.
b.Cruising Level
INSERT the planned cruising level for the first or whole portion of the route in accordance with Item 15B. of the ICAO flight plan.
c.Route
INSERT the entire route in accordance with Item 15C. of the ICAO flight plan.
© JEPPESEN SANDERSON, INC. 2000, 2006. ALL RIGHTS RESERVED.
468 |
AIR TRAFFIC CONTROL |
24 FEB 06 |
APPENDIX 2 — FLIGHT PLAN
8 EXAMPLE OF A COMPLETED REPETITIVE FLIGHT PLAN (RPL)
© JEPPESEN SANDERSON, INC. 2000, 2006. ALL RIGHTS RESERVED.
4 SEP 09 |
AIR TRAFFIC CONTROL |
469 |
APPENDIX 4 -- AIR TRAFFIC INCIDENT REPORT
1ICAO MODEL AIR TRAFFIC INCIDENT REPORT FORM
AIR TRAFFIC INCIDENT REPORT FORM
For use when submitting and receiving reports on air traffic incidents. In an initial report by radio, shaded items should be included.
A — AIRCRAFT IDENTIFICATION
C — THE INCIDENT
1.General
a) |
Date / time of incident |
|
UTC |
|
b)Position
2.Own aircraft
a)Heading and route
b) |
True airspeed |
|
measured in ( ) kt |
|
( ) km/h |
c)Level and altimeter setting
d)Aircraft climbing or descending
( ) Level flight
e)Aircraft bank angle
( |
) |
Wings level |
( |
) |
Slight bank |
( |
) |
Moderate bank |
( |
) |
Steep bank |
( |
) |
Inverted |
( |
) |
Unknown |
f)Aircraft direction of bank
( ) Left |
( ) Right |
( ) Unknown |
g)Restrictions to visibility (select as many as required)
( |
) |
Sun glare |
( |
) |
Windscreen pillar |
( ) Dirty windscreen |
( |
) |
Other cockpit structure |
( |
) |
None |
|
h)Use of aircraft lighting (select as many as required)
( |
) |
Navigation lights |
( |
) |
Strobe lights |
( |
) |
Cabin lights |
( |
) |
Red anti-collision lights |
( |
) |
Landing / taxi lights |
( |
) |
Logo (tail fin) lights |
( |
) |
Other |
( |
) |
None |
|
|
|
i)Traffic avoidance advice issued by ATS
( |
) |
Yes, based on ATS surveillance system ( ) Yes, based on visual sighting |
( ) Yes, based on other information |
( |
) |
No |
|
j)Traffic information issued
( |
) |
Yes, based on ATS surveillance system ( ) Yes, based on visual sighting |
( ) Yes, based on other information |
( |
) |
No |
|
k)Airborne collision avoidance system — ACAS
( |
) |
Not carried |
( |
) |
Type |
( ) Traffic advisory issued |
( |
) |
Resolution advisory issued |
( |
) |
Traffic advisory or resolution advisory not issued |
|
l)Identification
( ) No ATS surveillance system
m)Other aircraft sighted
( ) Yes |
( ) No |
( ) Wrong aircraft sighted |
* Delete as appropriate.
470 |
AIR TRAFFIC CONTROL 4 SEP 09 |
APPENDIX 4 -- AIR TRAFFIC INCIDENT REPORT
n)Avoiding action taken
|
( ) Yes |
( ) No |
o) |
Type of flight plan |
IFR / VFR /none* |
3.Other aircraft
a)Type and call sign / registration (if known)
b)If a) above not known, describe below
( |
) |
High wing |
( |
) |
Mid wing |
( |
) |
Low wing |
( |
) |
Rotorcraft |
|
|
|
|
|
|
( |
) |
1 engine |
( |
) |
2 engines |
( |
) |
3 engines |
( |
) |
4 engines |
( |
) |
More than 4 engines |
|
|
|
Marking, colour or other available details
c)Aircraft climbing or decending
( |
) |
Level flight |
( ) Climbing |
( ) Descending |
( |
) |
Unknown |
|
|
d)Aircraft bank angle
( |
) |
Wings Level |
( |
) |
Slight bank |
( |
) |
Moderate bank |
( |
) |
Steep bank |
( |
) |
Inverted |
( |
) |
Unknown |
e)Aircraft direction of bank
( ) Left |
( ) Right |
( ) Unknown |
f)Lights displayed
|
( |
) |
Navigation lights |
( |
) |
Strobe lights |
( |
) |
Cabin lights |
|
( |
) |
Red anti-collision lights |
( |
) |
Landing / taxi lights |
( |
) |
Logo (tail fin) lights |
|
( |
) |
Other |
( |
) |
None |
( |
) |
Unknown |
g) |
Traffic avoidance advice issued by ATS |
|
|
|
|
|
|
||
|
( |
) |
Yes, based on ATS surveillance system |
( |
) |
Yes, based on visual sighting |
( |
) |
Yes, based on other information |
|
( |
) |
No |
( |
) |
Unknown |
|
|
|
h) |
Traffic information issued |
|
|
|
|
|
|
||
|
( |
) |
Yes, based on ATS surveillance system |
( |
) |
Yes, based on visual sighting |
( |
) |
Yes, based on other information |
|
( |
) |
No |
( |
) |
Unknown |
|
|
|
i)Avoiding action taken
( ) Yes |
( ) No |
( ) Unknown |
* Delete as appropriate.
© JEPPESEN, 2000, 2009. ALL RIGHTS RESERVED.
4 SEP 09 |
AIR TRAFFIC CONTROL |
471 |
APPENDIX 4 -- AIR TRAFFIC INCIDENT REPORT
4.Distance
a)Closest horizontal distance
b)Closest vertical distance
5.Flight meteorological conditions
a)IMC / VMC*
b)Above / below* clouds / fog / haze or between layers*
c) |
Distance vertically from cloud |
m / ft* below |
m / ft* above |
d)In cloud / rain / snow / sleet / fog / haze*
e)Flying into / out of* sun
f) |
Flight visibility |
m / km* |
6.Any other information considered important by the pilot-in-command
D — MISCELLANEOUS
1.Information regarding reporting aircraft
a)Aircraft registration
b)Aircraft type
c)Operator
d)Aerodrome of departure
e) |
Aerodrome of first landing |
destination |
|
f) |
Reported by radio or other means to |
(name of ATS unit) at time |
UTC |
g)Date / time / place of completion of from
2.Function, address and signature of person submitting report
a)Function
b)Address
c)Signature
d)Telephone number
3.Function and signature of person receiving report
a) |
Function |
b) Signature |
* Delete as appropriate.
© JEPPESEN, 2000, 2009. ALL RIGHTS RESERVED.
472 |
AIR TRAFFIC CONTROL 4 SEP 09 |
APPENDIX 4 -- AIR TRAFFIC INCIDENT REPORT
2INSTRUCTIONS FOR THE COMPLETION OF THE AIR TRAFFIC INCIDENT REPORT FORM
Item
AAircraft identification of the aircraft filing the report.
BAn AIRPROX report should be filed immediately by radio.
C1 Date/time UTC and position in bearing and distance from a navigation aid or in LAT/LONG.
C2 Information regarding aircraft filing the report, tick as necessary.
C2 c) E.g, FL 350/1013 hPa or 2,500 ft/QNH
1007 hPa or 1,200 ft/QFE 998 hPa.
C3 Information regarding the other aircraft involved.
C4 Passing distance — state units used.
C6 Attach additional papers as required. The diagrams may be used to show aircraft’s positions.
D1 f) State name of ATS unit and date/time in UTC.
D1 g) Date and time in UTC and place of completion of form.
E2 Include details of ATS unit such as service provided, radiotelephony frequency, SSR codes assigned and altimeter setting. Use diagram to show the aircraft’s position and attach additional papers as required.
© JEPPESEN, 2000, 2009. ALL RIGHTS RESERVED.
AERONAUTICAL TELECOMMUNICATIONS
24 FEB 06 AIR TRAFFIC CONTROL |
473 |
AERONAUTICAL TELECOMMUNICATIONS
— AERONAUTICAL TELECOMMUNICATIONS.
5 AERONAUTICAL MOBILE SERVICE |
12000 |
one two thousand |
||
— VOICE COMMUNICATIONS |
||||
cloud height |
transmitted as |
|||
5.2 |
RADIOTELEPHONY PROCEDURES |
|||
|
|
|||
5.2.1 |
General |
2200 |
two thousand two |
|
|
hundred |
|||
|
|
|
||
5.2.1.2 |
Language to be Used |
4300 |
four thousand three |
|
|
|
|||
|
|
|
hundred |
|
|
|
visibility |
transmitted as |
|
|
|
1000 |
visibility one thousand |
|
|
|
700 |
visibility seven hundred |
|
|
|
runway visual |
transmitted as |
|
|
|
range |
|
|
|
|
600 |
RVR six hundred |
|
|
|
1700 |
RVR one thousand seven |
|
|
|
|
hundred |
|
5.2.1.4Transmission of Numbers in Radiotelephony
5.2.1.4.1Transmission of Numbers
5.2.1.4.1.1 All numbers, except as prescribed in 5.2.1.4.1.2, shall be transmitted by pro-
thousands followed by the word “HUNDRED” or “THOUSAND” as appropriate. Combinations of thousands and whole hundreds shall be transmitted by pronouncing each digit in the number of thousands followed by the word “THOUSAND” followed by the number of hundreds followed by the word “HUNDRED”
NOTE: The following examples illustrate the application of this procedure (see 5.2.1.4.3.1 for pronunciation.
Altitude |
transmitted as |
800 |
eight hundred |
3400 |
three thousand four |
|
hundred |
5.2.1.4.1.3 Numbers containing a decimal point shall be transmitted as prescribed in 5.2.1.4.1.1 with the decimal point in appropriate sequence being indicated by the word “DECIMAL”.
NOTE: The following examples illustrate the application of this procedure.
Number Transmitted as
100.3ONE ZERO ZERO DECIMAL THREE
38143.9 THREE EIGHT ONE FOUR THREE DECIMAL NINE
NOTE: For identification of VHF frequencies the number of digits after the decimal point are determined on the basis of channel spacing (5.2.1.7.3.4.3 refers to frequencies separated by 25 kHz, 5.2.1.7.3.4.4 refers to frequencies separated by 8.33 kHz.
5.2.1.4.1.4 PANS — When transmitting time, only the minutes of the hour should normally be required. Each digit should be pronounced separately. However, the hour should be included when any possibility of confusion is likely to result.
NOTE: The following examples illustrate the application of this procedure when applying the provisions of 5.2.1.2.2.
Time |
|
Statement |
0920 |
(9:20 A.M.) |
TOO ZE-RO or |
|
|
ZE-RO NIN-er TOO ZERO |
1643 |
(4:43 P.M.) |
FOW-er TREE or |
|
|
WUN SIX FOW-er TREE |
© JEPPESEN SANDERSON, INC. 2000, 2006. ALL RIGHTS RESERVED.