Amending Flight Plans - Revision history

Trvacc at 19:37, 15 August 2024

2024-08-15T19:37:54Z

← Older revision		Revision as of 19:37, 15 August 2024
Line 31:		Line 31:

	This is a full phraseology example:<blockquote>		This is a full phraseology example:<blockquote>
	'''THY5EV:''' Istanbul ground ~~thy18v~~ request clearance Antalya ~~info bravo~~		'''THY5EV:''' Istanbul ground THY18V request clearance Antalya information BRAVO
	</blockquote><blockquote>		</blockquote><blockquote>
	'''LTFM_GND:''' ~~thy18v~~ hello standby number 2		'''LTFM_GND:''' THY18V hello standby number 2
	</blockquote><blockquote>		</blockquote><blockquote>
	'''THY5EV:''' I have sent you a reroute let me know if you can accept that		'''THY5EV:''' I have sent you a reroute let me know if you can accept that

Trvacc: chenged notify the pilot section to support better understanding

2024-08-15T19:36:53Z

chenged notify the pilot section to support better understanding

@@ Line 28: / Line 28: @@
 === Notify the pilot ===
-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.
+If you give a pilot a reroute, they might decline it for '''safety reasons'''. These might be things like fuel, or general flight concerns.
 == Airways ==

Trvacc: Changed THY5EV to Istanbul Ground.

2024-08-15T19:22:29Z

Changed THY5EV to Istanbul Ground.

← Older revision		Revision as of 19:22, 15 August 2024
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>

Trvacc: Turkiye naming

2024-08-15T04:15:22Z

Turkiye naming

← Older revision		Revision as of 04:15, 15 August 2024
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 ===

Trvacc: fix formatting again

2024-08-15T04:14:55Z

fix formatting again

← Older revision		Revision as of 04:14, 15 August 2024
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 ===		=== Notify the pilot ===

Trvacc: fix formatting

2024-08-15T04:13:21Z

fix formatting

← Older revision		Revision as of 04:13, 15 August 2024
Line 1:		Line 1:
	== ~~Editing Flight Plans~~ ==		== Important Consideration ==
			We only check the section of the route that is within Turkey. Anything outside of Turkey is not our concern.

	=== ~~<u>'''1. Important Consideration:'''</u> ===~~		=== Altitudes ===
	~~'''Note''': We only check the section of the route that is within Turkey. Anything outside of Turkey is not our concern.~~		Right-click on the destination to open the flight plan, then check the direction of flight:

	~~=== <u>'''2.~~ Altitudes~~:'''</u>~~===
	Right-click on the destination to open the flight plan.

	~~'''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:~~

	~~"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~~:

	~~"THY5EV, roger, '''final level updated to FL340'''."~~

			* 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.<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)

			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>

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

	=== ~~<u>'''1. If the Traffic Does NOT Have a SID in the Departure List:'''</u> ===~~		=== 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.
	~~=== <u>'''2.~~ Check the ~~Route:'''</u>~~ ===
	- 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.

	~~=== <u>'''3. Finding a Valid Waypoint:'''</u> ===~~
	- 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...").

	~~=== <u>'''4. Notify the Pilot:'''</u> ===~~
	~~- Let the pilot know about the changes by saying:~~

	~~"THY9BC~~, ~~cleared to XX via RATVU4D departure~~, ~~after RATVU, UT35 AYT then as filed, runway 35L, climb 5,000 feet~~, ~~squawk 6412~~."		=== 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.

	~~If the pilot doesn~~'t ~~understand~~, ~~type~~ it ~~out~~.		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...").

			=== Notify the pilot ===
			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.

	== Airways ==		== Airways ==

	=== ~~<u>'''1.~~ Upper Airways~~:'''</u>~~ ===		=== Upper Airways ===
	- Airways with a "U" in front of them are upper airways, valid only above FL285.		Airways with a "U" in front of them are upper airways, valid only above FL285.

	=== ~~<u>'''2.~~ Level Change~~:'''</u>~~ ===		=== Level Change ===
	- If traffic is flying at FL280 but has filed an upper airway, change their level to a valid one, such as FL300.		If traffic is flying at FL280 but has filed an upper airway, change their level to a valid one, such as FL300.

	=== ~~<u>'''3.~~ Filing Lower Airways~~:'''</u>~~ ===		=== Filing Lower Airways ===
	- If the traffic cannot accept the higher level, instruct them to file a route with lower airways.		If the traffic cannot accept the higher level, instruct them to file a route with lower airways. Example:

	~~- Example:~~		* Upper Airway: ''UT35''
	- Upper Airway: UT35		* Lower Airway: ''T35''
	- Lower Airway: T35

Trvacc at 02:53, 15 August 2024

2024-08-15T02:53:21Z

← Older revision		Revision as of 02:53, 15 August 2024
Line 50:		Line 50:

	If the pilot doesn't understand, type it out.		If the pilot doesn't understand, type it out.

	~~{{DEFAULTSORT~~
	}}


Line 70:		Line 67:
	- Upper Airway: UT35		- Upper Airway: UT35
	- Lower Airway: T35		- Lower Airway: T35

	~~{{DEFAULTSORT~~
	}}

Trvacc at 02:52, 15 August 2024

2024-08-15T02:52:42Z

@@ Line 50: / Line 50: @@
      If the pilot doesn't understand, type it out.
 {{DEFAULTSORT
 }}

Trvacc at 02:51, 15 August 2024

2024-08-15T02:51:24Z

← Older revision		Revision as of 02:51, 15 August 2024
Line 46:		Line 46:
	=== <u>'''4. Notify the Pilot:'''</u> ===		=== <u>'''4. Notify the Pilot:'''</u> ===
	- Let the pilot know about the changes by saying:		- Let the pilot know about the changes by saying:
	"THY9BC, cleared to XX via RATVU4D departure, after RATVU, UT35 AYT then as filed, runway 35L, climb 5,000 feet, squawk 6412."
			"THY9BC, cleared to XX via RATVU4D departure, after RATVU, UT35 AYT then as filed, runway 35L, climb 5,000 feet, squawk 6412."

	If the pilot doesn't understand, type it out.		If the pilot doesn't understand, type it out.

	{{DEFAULTSORT		{{DEFAULTSORT
	}}		}}

Trvacc at 02:50, 15 August 2024

2024-08-15T02:50:54Z

← Older revision		Revision as of 02:50, 15 August 2024
Line 24:		Line 24:

	"THY5EV, roger, '''final level updated to FL340'''."		"THY5EV, roger, '''final level updated to FL340'''."






			== SIDs ==

			=== <u>'''1. If the Traffic Does NOT Have a SID in the Departure List:'''</u> ===

			=== <u>'''2. Check the Route:'''</u> ===
			- 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.

			=== <u>'''3. Finding a Valid Waypoint:'''</u> ===
			- 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...").

			=== <u>'''4. Notify the Pilot:'''</u> ===
			- Let the pilot know about the changes by saying:
			"THY9BC, cleared to XX via RATVU4D departure, after RATVU, UT35 AYT then as filed, runway 35L, climb 5,000 feet, squawk 6412."
			If the pilot doesn't understand, type it out.

			{{DEFAULTSORT
			}}