BoldPilot

BoldPilot

There are old pilots... there are bold pilots...

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ztl:ctr3 [2025/04/09 17:30] – zackztl:ctr3 [2025/04/09 17:48] (current) – zack
Line 68: Line 68:
 So the fourth line entry for deviations start with D........ and then, we go from there. I'm sure you can guess what the D is for.\\ So the fourth line entry for deviations start with D........ and then, we go from there. I'm sure you can guess what the D is for.\\
 After the D comes the restriction... if we're telling someone //deviation north approved//, we would append "N" after the D... so the 4th line on the datablock would read DN, meaning **d**eviation **n**orth. D20R would indicate that the aircraft is **D**eviating **20** degrees **R**ight.\\ After the D comes the restriction... if we're telling someone //deviation north approved//, we would append "N" after the D... so the 4th line on the datablock would read DN, meaning **d**eviation **n**orth. D20R would indicate that the aircraft is **D**eviating **20** degrees **R**ight.\\
-    Well, in some of our previous examples, we gave the aircraft instructions to rejoin the route. Sometimes, planes wont be able to rejoin the route. So... surely there must be a way to differentiate that, right?+    Well, in some of our previous examples, we gave the aircraft instructions to rejoin the route.  
 +    Sometimes, planes wont be able to rejoin the route. So... surely there must be a way to differentiate that, right?
 Correct. The syntax for the entry gets longer the more time we talk on frequency. So D20L means the aircraft was only instructed to deviate 20 degrees to the left. That's it. No instructions to resume the filed route or go direct some waypoint down yonder.\\ Correct. The syntax for the entry gets longer the more time we talk on frequency. So D20L means the aircraft was only instructed to deviate 20 degrees to the left. That's it. No instructions to resume the filed route or go direct some waypoint down yonder.\\
 Soooooooo **D20R/JONZE** would indicate that an aircraft is deviating 20R, and will go direct JONZE whenever they're clear of the weather. If they're going to return to the next waypoint in their filed route, we'd put /F.\\ Soooooooo **D20R/JONZE** would indicate that an aircraft is deviating 20R, and will go direct JONZE whenever they're clear of the weather. If they're going to return to the next waypoint in their filed route, we'd put /F.\\
Line 80: Line 81:
  
 **STANDARDS TO ACHIEVE** / __Altitude Changes__:\\ **STANDARDS TO ACHIEVE** / __Altitude Changes__:\\
-Define and compute basic descent math to ensure aircraft meet crossing restrictions\\+1. [[https://boldpilot.hartlantair.com/doku.php?id=ztl:ctr2#:~:text=STANDARDS%20TO%20ACHIEVE%20/%20Altitude%20Changes|Define and compute basic descent math to ensure aircraft meet crossing restrictions]] - We're back to this shit, eh? Lol. Done deal. [[ztl:ctr2|]]
  
 **STANDARDS TO ACHIEVE** / __En-Route Control__:\\ **STANDARDS TO ACHIEVE** / __En-Route Control__:\\
-Utilize prescribed phraseology to alert crossing traffic of each other\\+1. Utilize prescribed phraseology to alert crossing traffic of each other\\ 
 +Okay that's kinda adifferent... so this is getting at merging target procedures. Remember those from your S3 days?\\ 
 +The easy part is that if we have two targets that are going to be separated by only the minimum vertical separation((i.e. horizontal is less than 5 miles, except where 3 miles is authorized...)), we need to advise both targets with enough time that they can request a vector to "miss" the other airplane.\\ 
 +Instead of making two separate traffic calls, you can actually simplify it in some cases. For example, \\