Skip to content

Commit

Permalink
Add content structure
Browse files Browse the repository at this point in the history
  • Loading branch information
mattkelly4 committed Sep 29, 2023
1 parent 7370b4e commit bf5f865
Show file tree
Hide file tree
Showing 25 changed files with 467 additions and 23 deletions.
23 changes: 23 additions & 0 deletions docs/airspace/cta.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,26 @@

--8<-- "includes/abbreviations.md"

## Airways Clearances
- Requirement to obtain a clearance prior to entering CTA
- Airways clearance to enter CTA when already airborne
- Airways clearance when departing from CTA aerodrome

## Controlled Aerodromes
- Class C
- Class D
- Class D Metro

## Pilot Tracking/Level Requests
- Amended levels
- Weather (and other) deviations
- Tracking for different waypoints
- Requests for airwork or to operate in a certain area

## Separation Standards
- Different classes of airspace and what separation services are provided by ATC (e.g. class C - IFR sep from all, VFR sep from IFR, VFR traffic info on VFR)
- Visual separation (by pilot)

## Class E Airspace
- Requirement for IFR to obtain clearance
- Requirement for VFR to maintain listening watch
19 changes: 19 additions & 0 deletions docs/airspace/ifrocta.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,22 @@

--8<-- "includes/abbreviations.md"

## Taxi at Uncontrolled Aerodrome
- Radio call to be made (link to radio page)
- Requirement to update ATS if departure delay encountered (and expectation that ATS will set ops normal time with you)
- Radio setup (COM1: CTR, COM2: CTAF/unicom)
- Expectation of airways clearance on the ground if departing OCTA aerodrome close to CTA LL

## Airways Clearance after Departure
- Requirement to remain OCTA until in receipt of clearance (set APA to CTA LL)
- Handling of clearance

## Cruise OCTA
- Requirement to inform ATS prior to change of level or track (but no clearance required)
- Use of Area QNH
- Enroute IFR traffic and appropriate actions

## Arrival at Uncontrolled Aerodrome
- Clearance to leave CTA descending
- Traffic statement and appropriate actions (e.g. maintaining 1000ft sep with aircraft on opposing tracks)
- Cancelling SARWATCH (including whilst airborne where VHF coverage is limited)
7 changes: 7 additions & 0 deletions docs/airspace/lanesofentry.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,10 @@

--8<-- "includes/abbreviations.md"

## Navigating via Lanes of Entry
- Finding them on VTC charts
- Airways clearance requirements (some require ATC approval - e.g. Hope Valley route in Adelaide)
- General rules:
- Stay to the right
- Remain above safe altitude over terrain/built up areas
- Make broadcast on designated frequency or area frequency if none
13 changes: 13 additions & 0 deletions docs/airspace/prds.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,16 @@

--8<-- "includes/abbreviations.md"

## Danger Areas
- How to find details in ERSA
- Replanning to avoid
- Using appropriately designated danger areas (like training areas) to conduct predictable flight training/manoeuvres

## Restricted Areas
- How to find details in ERSA
- RA status and what that means from a flight planning perspective
- How to remain clear laterally and vertically (i.e. boundary level between PRD and other airspace takes on designation of least restrictive airspace type)
- Military restricted airspace and potential civil releases

## Prohibited Areas
- Not sure if we still have one in Aus or if it was downgraded to RA3
15 changes: 10 additions & 5 deletions docs/airspace/rulesofflight.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,13 @@

--8<-- "includes/abbreviations.md"

*Open to a better name*
- minimum height rule
- right of way
- other items from VFRG
- etc
## Altitude Requirements
- Minimum height rule (500ft AGL, 1000ft over populated areas)
- Remaining clear of CTA/PRD (boundary level takes form of least restrictive airspace type)

## Right of Way
- Give way to the right
- Circuit right of way
- Takeoff/landing separation minima OCTA

**Other VFRG rules**
16 changes: 12 additions & 4 deletions docs/airspace/vatsimoperations.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,15 @@

--8<-- "includes/abbreviations.md"

- top down rule
- who to contact
- enroute sector extensions
- etc
## Radio Communication Differences
- Unicom instead of CTAF
- Text and voice where text pilots known to operate in the area
- Allowance for non-standard winds/weather requiring use of reciprocal runways, etc

## Top Down Rule
- Identifying who to contact
- Use of controller ATIS to determine who is providing control services for aerodrome

## Enroute Sector Extensions
- Use of controller ATIS and VATPAC website airspace map to determine sector ownership
- Being told to contact a frequency which isn't displayed in pilot client (most foreign pilots get confused by this)
14 changes: 14 additions & 0 deletions docs/airspace/vfrflightfollowing.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,17 @@

--8<-- "includes/abbreviations.md"

## Use of Flight Following
- Provided surveillence service including traffic and area QNH updates
- Useful if intending to enter CTA at some point along your route

## Initiating Flight Following
- Initial listening watch, then radio call to request service
- Actions if service is unavailable

## Flight Plan Amendments
- Advising ATS of amended tracking or level

## Cancelling Flight Following
- Radio call to cancel service
- Service terminated by ATS due workload
21 changes: 21 additions & 0 deletions docs/flight-planning/alternaterequirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,24 @@

--8<-- "includes/abbreviations.md"

## Alternate due Weather
Link to Met section to interpret TAF

### Day VFR
- Simple VFR alternate minima (different for fixed and rotary wing)

### Night VFR
- GNSS/navaid or alternate within 1hr (double check)

### IFR
- Alternate minima on AIP charts (don't bother with Part 121 ops)
- No aid alternate minima (LSALT+500 and 8km)

## Alternate due Lighting
- Arrival after or approaching last light with no:
- Standby power
- Fixed electric runway lighting
(No need for responsible person stuff)

## Alterante due Navaids
- Required to hold if single point of failure in aircraft or on the ground would cause a loss of approach capability
17 changes: 17 additions & 0 deletions docs/flight-planning/altimetry.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,20 @@

--8<-- "includes/abbreviations.md"

## Transition Layer
- Transition altitude and level
- Inability to cruise in layer
- Variable transition level due QNH

## Area QNH
- Must be set below transition layer
- Must be within 5hPa of aerodrome within 100nm
- Requesting area QNH from ATS (link flight following)

## Altimeter Setting on the Ground
- Use AWIS/ATIS to set QNH, otherwise set aerodrome elevation on altimeter to get QNH

## Instrument Approach Corrections for QNH
- Ability to reduce published minima in shaded grey boxes by 100ft with actual QNH
- Leave grey boxes as is for TAF QNH
- Add 50ft to grey boxes for Area QNH
43 changes: 43 additions & 0 deletions docs/flight-planning/fuelplanning.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,46 @@

--8<-- "includes/abbreviations.md"

## Preflight Fuel Planning
### Flight Fuel
- Determining fuel burn and enroute time to calculate fuel burn
- Add climb fuel allowance

### Reserve Fuel
- Final Reserve (ex-Fixed Reserve)
- Contingency Fuel (ex-Variable Reserve)
- Requirement to land with Final Reserve

### Instrument Approach Fuel
- Carried for arrival at destination where weather dictates
- Not required if weather is good but INTER/TEMPO indicates deterioration and INTER/TEMPO fuel carried

### Weather Holding/Alternate Fuel
- INTER/TEMPO
- PROB30/40
- If no change indicator, alternate required
- Alternate must not require its own alternate

### Traffic Holding Fuel
- Finding details in ERSA
- Carrying extra for VATSIM events (MRM, WorldFlight, etc)
- Dictate actual amounts of traffic holding fuel required for each event?

### Extra Fuel
- Fuel tankering for return leg
- Additional contingencies when flying to isolated aerodrome
- Catering for VATSIM-isms

### Example Fuel Plan
- Sample calculation for aircraft, with TAF requiring INTER/TEMPO and instrument approach

## Inflight Diversion
- Where extensive holding or other factors dictate, perform fuel calculation to determine latest divert time
- Calculate flight fuel from present position to alternate
- Cater for any holding required at alternate (weather, traffic, etc)
- Cater for instrument approach at alternate if required
- Apply conservative buffer to minimum divert fuel, then assess current fuel burn to determine latest divert time
- Advise ATC approaching and reaching divert point

### Inflight Fuel Emergencies
- MINIMUM FUEL and MAYDAY FUEL calls (link to radio page)
24 changes: 24 additions & 0 deletions docs/flight-planning/routeselection.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,27 @@

--8<-- "includes/abbreviations.md"

## ERSA Preferred Routes
- Use as starting point to exit/enter busy TMAs, then use other route planning to connect the two
- If required route is less than ideal, consider departing VFR/OCTA

## VFR Route Selection
- Frequent navigation points to assist with visual navigation
- Routes keeping aircraft clear of CTA/PRD, even if navigation isn't accurate (i.e. applying buffer to these restrictive airspace sectors)
- Considering availability of airways clearance and Plan B if clearance not available

## IFR Route Selection
- Use of ERC H or L depending on intended cruising altitude
- Awareness of grid and route LSALTs where aircraft performance may suffer in event of engine failure or icing

## Altitude Selection
- Hemispherical levels
- VFR +500ft levels

## Designated Remote Areas
- Reference to CAOs
- Requirement to carry survival equipment (not really a consideration for flight sim)

## Use of Third-Party Tools
- Warning about use of SimBrief routes
- Use of ATC Assist to generate route
10 changes: 9 additions & 1 deletion docs/local-procedures/adelaide.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,12 @@

--8<-- "includes/abbreviations.md"

- coastal flights
## VFR Scenic Flights
### Coastal Transit
- Flight planning advice
- Clearance requirements from ATS
- Expectation of being processed at 500ft and expected clearance limits

### Hope Valley VFR Route
- Flight planning advice
- Clearance requirements from ATS
5 changes: 3 additions & 2 deletions docs/local-procedures/perth.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
---
title: Sydney, NSW
title: Perth, WA
---

--8<-- "includes/abbreviations.md"

- Victor 65
- Victor 65
- Victor 66
64 changes: 53 additions & 11 deletions docs/local-procedures/sydney.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,56 @@

--8<-- "includes/abbreviations.md"

**Fixed Wing**
- Victor One
- Harbour Scenic One
- Richmond VFR Route
- Bankstown VFR Route

**Rotary Wing**
- Bondi 5
- YSSY Helicopter Routes
- Airspace block clearances (e.g. Manly Sector, South Harbour Sector)
- R405
## VFR Scenic Flights
### Harbour Scenic Flights
- Flight planning advice
- Details of Harbour Scenic One and Two
- Who to contact and how to request clearance
- Descent into Victor One South on completion of orbits

### Victor One
- Strict tracking and altitude requirements on procedure
- Broadcast requirements

### Bankstown Lane of Entry
- Tracking details and changing altitude requirements (due overlying CTA)
- Broadcast requirements

### Richmond Lane of Entry
- Flight planning advice
- Clearance requirements from ATS

### R405 (Sydney Harbour) Airspace
- Availability only to helicopters and floatplanes
- Strict altitude requirements
- Oncoming traffic risk along Parramatta River
- Broadcast requirements

### Helicopter Coded Clearances
- Clearance requirements from ATS
- Definition of clearances (e.g. Manly Sector, South Harbour Sector)

## Sydney Airport Procedures
### 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

## Class D RNP Approaches
### YSCN RNP Approach
- Traffic statement by SY CTR
- Clearance by CN TWR

### YSBK RNP Approach
- Clearance to leave/reenter by SY CTR
- Go around note with minimal buffer to SY CTA
17 changes: 17 additions & 0 deletions docs/meteorology/forecastsandreports.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,20 @@

--8<-- "includes/abbreviations.md"

## METAR vs TAF
- METAR is report
- TAF is forecast
- Can't use METAR for flight planning

## Interpreting Data
### METAR
- What each section means
- SPECI meaning

### TAF
- What each section means
- TAF3
- Link to flight planning section to apply data in an operational context

### Common Abbreviations
- See VFRG
Loading

0 comments on commit bf5f865

Please sign in to comment.