Hello!
I started my radar training about a week ago and I feel like I need a bit more practice so I’ve started this thread with My trainer, @Jinco , approval.
Few notes:
-
No light aircraft accepted at this time. For the purposes of IF, “light” aircraft are defined as the C172, SR22, XCub, Spitfire Mk VIII and P38
-
Airport, runways, and other information will be announced 1 day ahead of the session
-
You can spawn at any airport within 65nm of the opened airport but not too close like directly under the approach cone of the runway in use.
-
Request any approach type
-
You can file STARs and/or approach procedures to your flight plan
-
These are the recommended speeds during your approach:
- Downwind [ 220 - 200 IAS ]
- Base [ 180-200 IAS ]
Though it is speed at your discretion until I give you a speed restriction (But don’t be speeding on final lol)
Feedback
- Terrain bust: Must remain above 1,000ft AGL when you aren’t cleared for approach. You can take avoiding action if you’re about to face plant into a mountain
- Separation bust: Must have a 3nm lateral, and 1,000ft vertical separation between other aircraft when you’re not established for the approach yet.
- Issue intercepting the ILS: If you didn’t get the localizer with the vectors I gave you, above the GlideSlope or overshot the localizer. If any of these occur(except overshooting the LOC, that I will have to correct myself) announce a missed approach so that I can bring you around to retry the approach.
- Inefficiency: If you believe you could’ve got to the runway significantly quicker or had a problem with my sequencing. Or if their are large gaps(>7nm) that could be avoided.
- Any improvements: If you have any quality of life changes that I should take note of whether small or big.
Ping List
This thread is heavily inspired by JeppyG’s Radar Tracking Thread [Closed @ NA]
Still planning for the airport I want to control:)