Various structural changes

docs/flight-planning/flightplansubmission.md

@@ -8,8 +8,10 @@
 
 ## Equipment Codes
 
-## Unusual Callsigns
-- Include in remarks as 'RTF/QANTAS'
+## Callsigns
+- Note to use ICAO not IATA codes
+- Use of VH- for international flights only, otherwise just 3 character rego identifier
+- Include unusual callsigns in remarks as 'RTF/QANTAS'
 - List of approved callsigns (mirror what we have in the SOPs under Controller Skills)
 
 ## Airwork and Planned Delays

docs/flight-planning/routeselection.md

@@ -92,6 +92,6 @@ Flight planning can be greatly simplified through the use of the many available
 
 VATPAC's [Pilot Assist](https://vatpac.org/membership-hub/tools/pilot){target=new} tool can be helpful for generating weather forecasts and accessing charts for your planned flight. The system can also be used to generate a route which complies with the ERSA FPR.
 
-Some aerodromes and terminal areas feature specific procedures for pilots to comply with. These procedures have been summarised in [Local Procedures](../local-procedures/), where you'll find flight planning advice as well as in-flight procedural guidelines.
+Some aerodromes and terminal areas feature specific procedures for pilots to comply with. These procedures have been summarised in [Local Procedures](../../local-procedures/), where you'll find flight planning advice as well as in-flight procedural guidelines.
 
 Applications like Navigraph allow pilots to plot out their intended flight plan on appropriate maps and charts. For those without a subscription, the free [SkyVector](https://skyvector.com){target=new} provides similar functionality. Be aware that the system is primarily designed for use in the USA and whilst Australian coverage is generally good, the VFR mapping system is lacking compared to other options.

docs/local-procedures/sydney.md

@@ -4,6 +4,36 @@
 
 --8<-- "includes/abbreviations.md"
 
+## Sydney Airport Procedures
+### Standard Taxi Routes
+- Description and SOPs diagram
+
+### Preferred Runway Exits
+- Description and reference to Airport Efficiency Procedures
+
+### Runway 16L/34R Procedures
+- Transfer to Tower turning onto B10 (directed or self initiated)
+- No taxi instructions issued after landing 34R to get yourself onto Lima
+
+### Sydney Director
+- What to say to Director
+
+### YSSY STAR Route Discontinuities
+- Requirement to leave discontinuity in FMC as per STAR chart (e.g. RIVET STAR)
+
+### Independent Visual Approaches (IVAs)
+- Requirement to report the runway in sight, or visual if on LOC
+- Expectation of traffic information if within 1nm
+- Advice to use ILS
+- Missed approach
+
+### VFR Helicopter Routes
+- Clearance requirements from ATS
+- Definition of each route
+- Bondi 5 procedure
+- Expectation of being processed via a different inbound route when approaching from CAPS or MRBR due YSSY runway config and traffic requirements
+- Expectation of requirement to report airborne/on the ground, not issued a takeoff/landing clearance (unless using H1)
+
 ## VFR Scenic Flights
 ### Harbour Scenic Flights
 - Flight planning advice
@@ -33,33 +63,6 @@
 - Clearance requirements from ATS
 - Definition of clearances (e.g. Manly Sector, South Harbour Sector)
 
-## Sydney Airport Procedures
-### Standard Taxi Routes
-- Description and SOPs diagram
-
-### Preferred Runway Exits
-- Description and reference to Airport Efficiency Procedures
-
-### Runway 16L/34R Procedures
-- Transfer to Tower turning onto B10 (directed or self initiated)
-- No taxi instructions issued after landing 34R to get yourself onto Lima
-
-### YSSY STAR Route Discontinuities
-- Requirement to leave discontinuity in FMC as per STAR chart (e.g. RIVET STAR)
-
-### Independent Visual Approaches (IVAs)
-- Requirement to report the runway in sight, or visual if on LOC
-- Expectation of traffic information if within 1nm
-- Advice to use ILS
-- Missed approach
-
-### VFR Helicopter Routes
-- Clearance requirements from ATS
-- Definition of each route
-- Bondi 5 procedure
-- Expectation of being processed via a different inbound route when approaching from CAPS or MRBR due YSSY runway config and traffic requirements
-- Expectation of requirement to report airborne/on the ground, not issued a takeoff/landing clearance (unless using H1)
-
 ## Class D RNP Approaches
 ### YSCN RNP Approach
 - Traffic statement by SY CTR