diff --git a/.gitignore b/.gitignore index 4efeb747..3a819c90 100644 --- a/.gitignore +++ b/.gitignore @@ -6,7 +6,7 @@ _site/ .sass-cache/ .jekyll-cache/ .jekyll-metadata - +.DS_Store # Additional Ruby/bundler ignore for when you run: bundle install /vendor diff --git a/docs/.DS_Store b/docs/.DS_Store new file mode 100644 index 00000000..0baefbfc Binary files /dev/null and b/docs/.DS_Store differ diff --git a/docs/Contributing/.DS_Store b/docs/Contributing/.DS_Store new file mode 100644 index 00000000..84743fc4 Binary files /dev/null and b/docs/Contributing/.DS_Store differ diff --git a/docs/Pilot Briefing/South Africa/fact.md b/docs/Pilot Briefing/South Africa/fact.md new file mode 100644 index 00000000..4665e6cc --- /dev/null +++ b/docs/Pilot Briefing/South Africa/fact.md @@ -0,0 +1,112 @@ +# Cape Town International Airport (FACT) + +*Pilots taking part in events that depart from or arrive at FACT should make themselves familiar with this briefing page as well as with all existing charts.* + +## Overview + +- Cape Town International Airport is the primary international airport serving the city of Cape Town, South Africa. + +- The airport has runway 19 / 01. + +## Charts + +Charts are available from the AIP [here](https://www.caa.co.za/industry-information/aeronautical-information-aeronautical-charts/). + +Chartfox charts are available [here](https://chartfox.org/FACT). + +## Frequencies + +| Position | Callsign | Frequency (MHz) | Remarks | +|-------------|--------------------|-----------------|---------| +| FACT_ATIS | Cape Town ATIS | 127.000 | - | +| FACT_DEL | Cape Town Delivery | 122.100 | - | +| FACT_GND | Cape Town Ground | 121.900 | - | +| FACT_TWR | Cape Town Tower | 118.100 | - | +| FACT_APP | Cape Town Approach | 119.700 | - | +| FACT_F_APP | Cape Town Director | 124.350 | - | +| FACA_CTR | Cape Town Area | 125.100 | - | + +## Departure Briefing + +### Clearance Delivery + +- **FACT_DEL** will be the Position responsible for issuing IFR clearances. + +- When requesting IFR clearance, please provide your Aircraft Type, Stand Number and ATIS letter. + +- When requesting IFR clearance, please provide your **Aircraft Type**, **Stand Number** and **ATIS letter.** + +### Departure Procedures + +- Comply with your assigned departure procedure and do not climb above your initial Climb Altitude unless instructed so. + +- You may be given intermediate climb instructions due to traffic. Do not climb above any assigned flight level. + +- Comply with any speed restrictions if provided. They are important to maintain adequate separation between traffic. + +- When approaching the runway, you'll be asked to report fully ready for departure. That means that when given line-up or take-off clearance, you're expected to be ready to do so without delay. If you need more time, please advise the tower. + + +### Ground Operations + + +- **FACT_GND** will be the Position responsible for providing push-back and taxiing instructions. + +- Remember to squawk **Mode C** before taxiing. + +- If told to monitor a frequency, you're expected to tune in the frequency but not to contact the controller. He will contact you when able. + +- When approaching the runway, you'll be asked to report fully ready for departure. That means that when given line-up or take-off clearance, you're expected to be ready to do so without delay. If you need more time, please advise the tower. + + +### Code F Restrictions + +- **FACT is not Code F compliant** + +### Departure Timeline + +- For Cross Africa, your slot time is represented as a **CTOT (Calculated Take off Time).** You'll be expected to push-back at **TOBT (Target Off Block Time)** between 15 and 20 minutes before **CTOT (depending on how the traffic is flowing at that time).** + +- As far as Clearance is concerned, you can request it at any time before **TOBT**, as long as you'll be ready for push-back at **TOBT.** We suggest you request your clearance at least 15 minutes before **TOBT.** + +- You should not need to connect to the network more than 60 minutes before your **CTOT.** + +## Arrival Briefing + +### Arrivals and Approaches + +- As your flight is approaching, please make yourself familiar with the arrival and approach procedures for Cape Town. + +- All pilots expect Runway 19 for landing. + +- Pilots should plan for the ILS runway 19. + +- On initial contact with Cape Town International, you will be told the landing runway and the arrival. + + +### Parking and Ground Operations + +- When landing, pilots are advised to vacate as quickly as possible to allow for smooth operation. + +## Oceanic Operations + +- For Johannesburg Oceanic flights, you will not be required to request an Oceanic Clearance. + +- You will be requested however to maintain your Flight Level and an assigned Mach Number. + +- During Oceanic En-route, you'll be able to request higher flight levels, depending on availability. + +- Position Reports will not be required. You may be requested from Oceanic Controllers to provide your ETO (Expected Time Overhead) for a specific waypoint. What the Controller is expecting is your time (as in, 1615z) at the specific waypoint. + +- Remain on your last ATC assigned squawk code until instructed otherwise. + +- CPDLC availability at Johannesburg Oceanic is at the controller’s discretion; if it is not explicitly offered, assume it is unavailable. + +- SELCAL is also available at Johannesburg Oceanic. + +- SLOP (Strategic Lateral Offset Procedure) is also available at Johannesburg Oceanic. + + +From: **[VATSSA eAIP](https://eaip2.vatssa.com/)** + +Last update: **22/02/2026 17:35Z** \ No newline at end of file