Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Phraseology
- Radiocheck
- "Callsign, readability 5"
- If the readability is low then give a reason. "Callsign, readability 3, you are very quiet"
- Unreadable
- Readable now and then
- Readable but with difficulty
- Readable
- Perfectly readable
- Clearance
- "Callsign, (information A) cleared to Heathrow, SANBA1R departure, squawk 5055, (QNH 1005)"
- *** See my IFR clearances notes below for what to include/omit here ***
- if correct: "Callsign, correct"
- if incorrect: "Callsign, negative, squawk 5055"
- Push and Start
- "Callsign, stand 52, push and start approved face West"
- "Callsign, after the Flybe Dash 8 passes behind you left to right on G, stand 52 push and start approved face East"
- Taxi
- "Callsign, taxi holding point A1, runway 05L via G J"
- "Callsign, Behind the Flybe Dash 8 passing right to left on M, then taxi holding point A1, runway 05L via G J"
- Handoff
- "Callsign, contact Manchester Tower, 118.625"
- Other
- On first contact with an aircraft, you must identify yourself:
- "BAW123, Manchester Ground, cleared to ..."
- Also, remember that you can't say "cleared to destination". If you don't know the name of the destination, spell out the ICAO code.
- Another thing I picked up on and mentioned during the sessions was pilots callsign up without the correct details, For example:
- "TOM2H, Request Clearance To Madrid."
- "TOM2H, Report your aircraft type and ATIS letter."
- "TOM2H, Stand 202, Infomation A."
- "TOM2H, Cleared to Madrid, SANBA1R departure, Squawk 4213"
- Make sure you have all four bits of information that you need before an Aircraft is cleared.
- Aircraft Type
- Stand Number
- ATIS Letter on-board
- Current QNH (If the pilot doesn't call up with the letter, tell them the current QNH)
- Pace and Clarity
- I am a victim to this but remember, Push to talk not Push to think.
- Make sure you think about what you say before you say it, otherwise, there are umm's and ahh's on frequency. Please think about what you need to say before you tell an aircraft to standby.
- Text communications
- This wasn't covered in this session, but have a look in your euroscope documents folder:
- \Documents\EuroScope\UK\Data\Alias
- The text document inside of this folder will show all the possible auto-generated text messages that can be used to send to the aircraft.
- The main ones used for ground are:
- .rsn Report your stand number
- .rat Report your aircraft type
- .qnh QNH $altim($1)
- .ho Contact $radioname($1) ($atccallsign($1)) $freq($1)
- .uni No Further ATC available. Monitor Unicom 122.800
- .sid Cleared to $arr, $sid departure, squawk $squawk, QNH $altim($dep)
- .rc Readback correct
- .rcq Readback correct, QNH $altim($dep)
- .ready Readback correct, report ready
- .readyq Readback correct, QNH $altim($dep), report ready
- .taxi Taxi holding point $1 via $2
- .stand Taxi stand $1, via $2
- .p Push and Start approved
- .p(n,e,s,w) Push and Start approved, face (North, South, East, West)
- The $1 and $2 are place holders and can be selected with the TAB key to swtich through.
- Anything other than 1,2 or 3 have preset values that you can quickly send: For example:
- .qnh -> QNH 1002
- Incorrect Readback
- Incorrect Readback wasn’t spotted or corrected, Make sure you are listening and checking the feedback:
- "TOM2H, Request Clearance To Madrid, ATIS A, B737"
- "TOM2H, Cleared to Manchester, SANBA1R departure, Squawk 4213"
- "TOM2H, Cleared to Manchester, SANBA1R departure, Squawk 4212"
- "TOM2H, Negative Squawk 4213”
- "TOM2H, Squawk 4213”
- "TOM2H, Correct”
- Important to note Only correct them on the incorrect part.
- Communication priority
- As soon as the aircraft is free of conflicts to tell him to contact his next controller.
- Handoff
- Taxi
- Push
- Clearance
- Radio Radio
- Co-ordination
- To talk to the controllers on Teamspeak for clearances etc use their coordination name:
- GMP (Pronounced individually) - Ground Movement Planner - Manchester Delivery
- GMC (Pronounced individually) - Ground Movement Controller - Manchester Ground
- AIR One - North Tower - Manchester Tower
- AIR Two - South Tower - Manchester Tower
- INT South - South Radar - Manchester Radar
- INT North - North Radar - Manchester Radar
- INT Final - Final Radar - Manchester Radar
- Co-ordination Example:
- "AIR GMC"
- "Pass your message"
- "GABCD C172 requests circuits"
- "GABCD C172 circuits approved, clearance at the hold."
- "Thanks"
- Some controllers don’t like using TS3, note this is a minority and can cause some issues. If you need to coordinate with someone that isn't on TS3, double click on the controller in the controller list, and enter it in the text entry box in Euroscope.
- Co-ordination with TWR - departures (as necessary), VFR traffic
- Any non-standard departures have to have a prenote
- This includes VFR and IFR nonstandard departures.
- Co-ordination of non-standard practices
- As mentioned above you need to get the nonstandard departure clearance from the correct ATC unit
- SANBA Restriction:
- Westbound Ops (23'S) - When the Aircraft's takeoff weight is less than 35 tons (This is safe to assume or ask the Question to the A/C) The pilots must fly the LISTO2R departure, Using this reroute: LISTO L612 HON. If the aircraft's takeoff weight is more than 35 tones the pilots must fly on the SANBA1R departure, using this reroute: SANBA N859 HON.
- Eastbound Ops (05'S) - There is no restriction with the SANBA as the LISTO departure does not exist on 05's so pilots must fly on the SANBA1S departure, using this reroute: SANBA N859 HON.
- Flights to LTMA Restriction:
- Flights to the London Terminal Maneuvering Area, Need to go not above FL190. This is done to keep them on the Lower Airways, and to deconflict from LTMA flights into Manchester.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement