Expand YMMB Procedures

[glennawatson]

Summary

Expand YMMB procedures to include preferred duty runways, missing inbound waypoint SHOL, and helicopter details.

Changes

Fixes:

• Duty runway preferences are 17/35 at MB

Changes:

• Cleaned sections up to read a bit clearer

Additions:

• Helicopter overview
• SHOL inbound point

[glennawatson]

Images incoming

[glennawatson]

Would like some clarification what we'd like to do with helicopters

Real life MB controller indicates they don't use the aiming points due to them infringing on the runway environment but it's in the ERSA. Do we want to follow the ERSA or MB controller or something else?

[mattkelly4]

Looks like a heap of work has gone into this, thanks as always Glenn. Just a few discussion points from my end, mainly standardisation items or queries based on my lack of experience with the aerodrome. Feel free to reach out to discuss any points if you wish!

[mattkelly4]

Would like some clarification what we'd like to do with helicopters

Real life MB controller indicates they don't use the aiming points due to them infringing on the runway environment but it's in the ERSA. Do we want to follow the ERSA or MB controller or something else?

Have replied via discord but for everyone else's visibility, I think we'll stick with what the ERSA says so that pilots and controllers are operating with a common source of information. If this becomes problematic, we can look at amending the procedure and including the changes in the Pilot Procedures site.

[glennawatson]

What's left to get this one in, doing the diagram for it today

[glennawatson]

Diagrams are in, had to fix a problem I was having with the stylesheet for the phraseology section stripping out new lines.

All feedback applied. Ready when you guys are back from the break @alphadelta332 and @mattkelly4 and anyone who can review.

[mattkelly4]

Diagrams are in, had to fix a problem I was having with the stylesheet for the phraseology section stripping out new lines.

All feedback applied. Ready when you guys are back from the break @alphadelta332 and @mattkelly4 and anyone who can review.

FYI, I reversed the stylesheet change. Really appreciate the fix but unfortunately, it would require every example on the site to be reformatted, so have left it the way it was previously. Adding the double space after each line forces a new line in example blocks (as with elsewhere).

[glennawatson]

Ready for another review round @mattkelly4 and @alphadelta332

[alphadelta332]

Thanks for your work again @glennawatson. We've made some formatting changes, tidying up and typos, things like that. We've included most of the work you've done, main thing that we've taken out is the Helicopter Arrival/Departure procedures, in order to reduce complexity and allow the freedom for the controller to handle aircraft similarly across multiple towers, given they're rated to do all towers in the country. It poses a low risk from an operational standpoint, since no separation standard needs to be applied to VFR choppers, the ATC can make their own determination for the passing of traffic information based on the arrival/departure procedure they elect to use.

Thanks for helping out

[glennawatson]

Given the mbhelidep.png file is no longer used, you may want to delete it.

[glennawatson]

I'm actually ok with the Dep going, since what was in the ERSA and what they do in real life didn't match. So there was some ambiguity there anyway.

[glennawatson]

@tylerthetiletiler @mattkelly4 @alphadelta332

Need approval again, removed the unused image file.