BlueFlash
teach preview

ATC Flight Plan — Page 233, Lesson 231

ATC Flight Plan — Page 233, Lesson 231BlueFlash
I want to walk you through the ATC Flight Plan chapter. This is the formal document that tells Air Traffic Services exactly what you intend to do with your aircraft, and there are very specific rules about how it must be handled and filled out. Let's start with the operator's obligations when a flight is delayed. If you have submitted a Repetitive Flight Plan — that's an RPL, a plan filed for a series of regularly scheduled flights — and a specific flight is expected to be delayed by 30 minutes or more beyond the off-block time stated in that RPL, the operator must notify the ATS unit responsible for the departure aerodrome immediately. The off-block time is the time the aircraft is scheduled to start moving from the parking position. A delay of half an hour or more triggers this notification requirement. There's a serious consequence attached to this. Because of the stringent requirements of flow control — that's the system that manages traffic demand to prevent overload — if the operator fails to comply with this notification procedure, the RPL for that specific flight may be automatically cancelled at one or more of the ATS units concerned. So if you don't tell them about the delay, they can simply delete your flight plan from their system. Similarly, if the operator knows that any flight for which an RPL has been submitted is cancelled, the ATS unit responsible for the departure aerodrome must be notified. No exceptions. Now, operator/pilot liaison. The operator has a duty to ensure that the pilot in command receives the latest flight plan information. This includes both permanent and incidental changes that have been duly notified to the appropriate agency. So if the operator updates the flight plan with ATS, that updated information must also be made available to you, the pilot flying the aircraft. Moving into the formal instructions for completing the flight plan form itself. These come from ICAO DOC 4444, which is the Procedures for Air Navigation Services — Rules of the Air and Air Traffic Services, specifically Appendix 2. This is the standard you must follow. General instructions: you must adhere closely to the prescribed formats and the manner of specifying data. You start inserting data in the first space provided on the form. If there's excess space left over, you leave those unused spaces blank — do not fill them with dashes or zeros unless instructed. All clock times must be inserted in four figures using UTC — Coordinated Universal Time. So 2:15 in the afternoon becomes 1415. All estimated elapsed times must also be in four figures, hours and minutes. So an estimated flight time of 3 hours and 45 minutes is entered as 0345. There's a shaded area preceding Item 3 on the form. That area is to be completed by ATS and COM services — Air Traffic Services and Communications services — unless the responsibility for originating flight plan messages has been delegated to someone else. One important note: the term "aerodrome" as used in the flight plan is intended to also cover sites other than aerodromes that may be used by certain types of aircraft, for example helicopters or balloons. So a helipad or a balloon launch site is treated as an aerodrome for flight plan purposes. For the insertion of ATS data, you complete Items 7 through 18 as indicated in the instructions. You also complete Item 19 when required by the appropriate ATS authority, or when you otherwise deem it necessary. The item numbers on the form are not consecutive — they correspond to Field Type numbers used in ATS messages. So don't be confused if you see gaps in the numbering. Let's look at Item 7: Aircraft Identification. This is limited to a maximum of 7 characters. You insert one of the following identifications, not exceeding that limit. First option: the registration marking of the aircraft. Examples given are EIAKO, 4XBCD, N2567GA. You use the registration marking when, in radio-telephony, the call sign to be used by the aircraft will consist of this identification alone — for example OOTEK — or when it is preceded by the ICAO telephony designator for the aircraft operating agency — for example SABENA OOTEK. You also use the registration marking if the aircraft is not equipped with radio. Second option: the ICAO designator for the aircraft operating agency followed by the flight identification. Examples given are KLM511, NGA213, JTR25. You use this format when, in radio-telephony, the call sign to be used by the aircraft will consist of that agency designator followed by the flight number. So to summarise Item 7: you have two possible formats — either the registration alone or with the agency name, or the ICAO agency code plus flight number. Both are limited to 7 characters maximum, and the choice depends on how the aircraft will be called on the radio.

This is one saved preview. Continue from this exact book or paper with BlueFlash voice AI.

Continue in BlueFlash