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
ztl:ctr3 [2025/04/09 17:35] zackztl:ctr3 [2025/04/09 17:48] (current) zack
Line 81: 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, \\