Amending Flight Plans: Difference between revisions

From TRvACC Wiki
Jump to navigation Jump to search
(fix formatting)
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Important Consideration ==
== Important Consideration ==
We only check the section of the route that is within Turkey. Anything outside of Turkey is not our concern.
We only check the section of the route that is within Türkiye. Anything outside of Türkiye is not our concern.


=== Altitudes ===
=== Altitudes ===
Line 11: Line 11:
Example
Example


If traffic is flying LTFM-EDDF and has filed FL350, note that Frankfurt is west of Istanbul, so the traffic must fly at an even level. You can correct this using the following phraseology.<blockquote>'''THY5EV:''' Istanbul Ground, THY5EV hello. Flying westbound, I can offer you FL340 or FL360.</blockquote>(Since FL350 is requested, it makes sense to suggest one level lower and one higher as the correct FL)
If traffic is flying LTFM-EDDF and has filed FL350, note that Frankfurt is west of Istanbul, so the traffic must fly at an even level. You can correct this using the following phraseology.<blockquote>'''Istanbul Ground:''' THY5EV, Istanbul Ground hello. Flying westbound, I can offer you FL340 or FL360.</blockquote>(Since FL350 is requested, it makes sense to suggest one level lower and one higher as the correct FL)


The traffic will either confirm or request a different level. Once you have a level, say:<blockquote>'''Istanbul Ground:''' THY5EV, roger, final level updated to FL340</blockquote>
The traffic will either confirm or request a different level. Once you have a level, say:<blockquote>'''Istanbul Ground:''' THY5EV, roger, final level updated to FL340</blockquote>
Line 22: Line 22:


=== Find a valid waypoint ===
=== Find a valid waypoint ===
Upper Section: Check the upper route section for a valid waypoint for a SID. If you find one, delete whatever is in front of it (IF YOU DON'T, APP or CTR WILL STILL SEE THE WEIRD ROUTE). You can now close the white box, and the rest will be done automatically.


Lower Section: If you don't find a valid waypoint in the upper section, check the lower section. On the right side of the waypoint, you'll see the airway it is in. Find that airway in the upper section, replace the waypoint in front of the airway with the valid waypoint, and again, delete anything in front of the valid waypoint. You can now close the white box, and the rest will be done automatically.
# Upper Section: Check the upper route section for a valid waypoint for a SID. If you find one, delete whatever is in front of it (IF YOU DON'T, APP or CTR WILL STILL SEE THE WEIRD ROUTE). You can now close the white box, and the rest will be done automatically.
# Lower Section: If you don't find a valid waypoint in the upper section, check the lower section. On the right side of the waypoint, you'll see the airway it is in. Find that airway in the upper section, replace the waypoint in front of the airway with the valid waypoint, and again, delete anything in front of the valid waypoint. You can now close the white box, and the rest will be done automatically.
# Coordinate if necessary: If you still can't find anything, coordinate with the upper sector to give the traffic radar vectors. If there is no upper sector, replace the SID and put "as filed" (e.g., "Cleared to destination XX, as filed, runway XX...").


'''Coordinate if necessary''': If you still can't find anything, coordinate with the upper sector to give the traffic radar vectors. If there is no upper sector, replace the SID and put "as filed" (e.g., "Cleared to destination XX, as filed, runway XX...").
=== Notify the pilot ===
If you give a pilot a reroute, they might decline it for '''safety reasons'''. These might be things like fuel, or general flight concerns.  


=== Notify the pilot ===
This is a full phraseology example:<blockquote>
Let the pilot know about the changes by saying the following example phraseology:<blockquote>THY9BC, cleared to XX via RATVU4D departure, after RATVU, UT35 AYT then as filed, runway 35L, climb 5,000 feet, squawk 6412.</blockquote>If the pilot doesn't understand, type it out and send it as a message.
'''THY5EV:'''  Istanbul ground THY18V request clearance Antalya information BRAVO
</blockquote><blockquote>
'''LTFM_GND:''' THY18V hello standby number 2
</blockquote><blockquote>
'''THY5EV:''' I have sent you a reroute let me know if you can accept that
</blockquote>Sending the '''reroute''' via text can '''save time. I'''f the pilot does '''NOT accept''' the reroute, you can ask them why. Not wanting to fly that route or something like "sir we already set everything up" is '''not an excuse.'''<blockquote>
  '''THY18V:''' Affirm we can accept that
</blockquote>'''Now''' change his flight plan with the '''correct/updated''' route<blockquote>
'''THY18V: C'''leared to destination RATVU4D departure, runway 35L, climb 5000feet, squawk 6413
</blockquote>


== Airways ==
== Airways ==

Latest revision as of 19:37, 15 August 2024

Important Consideration

We only check the section of the route that is within Türkiye. Anything outside of Türkiye is not our concern.

Altitudes

Right-click on the destination to open the flight plan, then check the direction of flight:

  • Westbound: Must fly at an even level (e.g., FL320, FL340, FL360).
  • Eastbound: Must fly at an odd level (e.g., FL310, FL330, FL350, FL370).


Example

If traffic is flying LTFM-EDDF and has filed FL350, note that Frankfurt is west of Istanbul, so the traffic must fly at an even level. You can correct this using the following phraseology.

Istanbul Ground: THY5EV, Istanbul Ground hello. Flying westbound, I can offer you FL340 or FL360.

(Since FL350 is requested, it makes sense to suggest one level lower and one higher as the correct FL) The traffic will either confirm or request a different level. Once you have a level, say:

Istanbul Ground: THY5EV, roger, final level updated to FL340

SIDs

If the traffic does not have a SID in the departure list:

Check the route

In the white flight plan dialogue (open by right-clicking on Destination), you can see a route section divided into two parts: the filed route and the filed route with waypoints in the airways.

Find a valid waypoint

  1. Upper Section: Check the upper route section for a valid waypoint for a SID. If you find one, delete whatever is in front of it (IF YOU DON'T, APP or CTR WILL STILL SEE THE WEIRD ROUTE). You can now close the white box, and the rest will be done automatically.
  2. Lower Section: If you don't find a valid waypoint in the upper section, check the lower section. On the right side of the waypoint, you'll see the airway it is in. Find that airway in the upper section, replace the waypoint in front of the airway with the valid waypoint, and again, delete anything in front of the valid waypoint. You can now close the white box, and the rest will be done automatically.
  3. Coordinate if necessary: If you still can't find anything, coordinate with the upper sector to give the traffic radar vectors. If there is no upper sector, replace the SID and put "as filed" (e.g., "Cleared to destination XX, as filed, runway XX...").

Notify the pilot

If you give a pilot a reroute, they might decline it for safety reasons. These might be things like fuel, or general flight concerns.

This is a full phraseology example:

THY5EV: Istanbul ground THY18V request clearance Antalya information BRAVO

LTFM_GND: THY18V hello standby number 2

THY5EV: I have sent you a reroute let me know if you can accept that

Sending the reroute via text can save time. If the pilot does NOT accept the reroute, you can ask them why. Not wanting to fly that route or something like "sir we already set everything up" is not an excuse.

THY18V: Affirm we can accept that

Now change his flight plan with the correct/updated route

THY18V: Cleared to destination RATVU4D departure, runway 35L, climb 5000feet, squawk 6413

Airways

Upper Airways

Airways with a "U" in front of them are upper airways, valid only above FL285.

Level Change

If traffic is flying at FL280 but has filed an upper airway, change their level to a valid one, such as FL300.

Filing Lower Airways

If the traffic cannot accept the higher level, instruct them to file a route with lower airways. Example:

  • Upper Airway: UT35
  • Lower Airway: T35