Jump to content

atc-discussion New Oceanic Spreadsheet


Andre Almeida

Recommended Posts

Andre Almeida

Hello,

I would like to share a spreadsheet with you that has initially been developed for Santa Maria by some Portuguese Controllers, and has recently been adapted to also accommodate Shanwick & Gander operations.

A template of the spreadsheet can be found here: https://docs.google.com/spreadsheets/d/1XEjfxRV5F-OqIZgraakljMwgmMghuEOsizHaAE4_ta8/edit?usp=sharing.

It is non editable, as it is supposed to remain in an empty and clean format. If you'd like to use it, go to "File -> Make a Copy".

Let me explain a bit about the spreadsheet and what differentiates it from any other sheet you may have.

The spreadsheet works, at this time, for 106 aircraft, allowing for three different positions to be simultaneously manned (Delivery, Shanwick and Gander). There are four pages which will be of use:

  • Clearance;
  • Position Report 1;
  • Position Report 2;
  • Route.

There are a few more hidden pages, that should not be touched, unless you'd like to risk messing up some of the spreadsheets functionalities.

To avoid this post becoming too long, a small document explaining the four pages is available here: https://docs.google.com/document/d/1na5it03PeA2GDgx03z-wBJj5ocJRb7nZ2r99Dg7koBk/edit?usp=sharing.

But, why this spreadsheet and not any of the others floating around?

First of all, this one checks for conflicts. If the separation between two aircraft at the same flight level inbound the same waypoint falls below 10 minutes and the preceding aircraft is not faster than the succeeding aircraft following the rules below then the spreadsheet will alert you of a conflict by highlighting their callsigns in red.

image.png.52d754d9dfa009651313c983565a08b3.png 

This happens on all pages, be it the Clearance or either of the two Position Report pages.

It's not all though. In my opinion it reduces the workload a lot, since most things are prefilled. During a position report all that has to be done is select the next waypoint in the drop down box, and write the two reported times in their corresponding cells. If the pilot is /t, a quick copy-paste of the last column is all that is needed. Information can be quickly shared with the next controller without the need of copy-pasting information from one sheet to the other, all that has to be done is click a checkbox, further reducing the workload.

If anyone happens to use the sheet, we would love to receive some feedback, be it to tell us that everything worked as expected, or that something did not work, or even to request something that has been forgotten.

Even though the spreadsheet has been tested plenty there may still be some errors that have not yet been found. Feel free to trust the sheet whilst controlling, as it hasn't let me down yet, but don't forget to double check things yourself whenever you have time. Trust, but verify. 

For feedback or questions you may reach me either here on the topic, or via private message on this forum, or even via Discord (I'm on VATUK's server, so it should be fairly easy to find me, André Almeida#1125).

  • Like 2
Link to post
Share on other sites
Ben Wright

Thanks for sharing us with this Andre, we used an older variation of this during Miami Vice and feedback was very positive. The only issue we had was due to myself translating some bits from Portuguese to English😂

  • Like 1
Link to post
Share on other sites
Andre Almeida

Had completely forgotten about that. 😛 Won't happen again, just translated the words inside all the formulas to English.

Also fixed a small error in the REQ FL dropdown on the Clearance page.

Edited by Andre Almeida
Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Similar Content

    • Chris White
      By Chris White
      Just wanted to say that I thoroughly enjoyed my first event last night as a controller rather than a pilot.  Particular thanks to @Dean Benavidez, @Piers Austin-Foss and @Jake Egan for the support.  I thought we did quite well at Bristol last night! 
      I would certainly welcome more events like this one within VATUK as it gives controllers like me a chance to get involved in more events outside of CTP and MWM 🌝
    • Alvi Segovia
      By Alvi Segovia
      Is there any documentation for Cardiff or if anyone could possibly share some documents of Cardiff?
      If not, can someone point me in the right direction.
    • Leslie Channell
      By Leslie Channell
      Just wanted to say a big thank you to Lenny who was Directing Gatwick app this afternoon.
      I (EZY22LC) hit a PC snag or two after departure, along with a corruptly loaded Flight plan in the FMS.  Not very often I practice a divert in the FS Labs A320 and so I chose to have a practice by doing a return to Gatwick.  I was outbound passing FL 200 on unicom when I sent a message to the Gatwick director, who had just handed me to 122.8
      He was kind enough to turn me and get me onto a star, planning that whilst nursing the PC and aircraft was fantastically challenging, I missed the first WP but the controller kindly pushed me to the next one down the star.  Flying the star manually as systems fell, I was vectored to and joined the ILS at about 12 miles.
      With the field in sight.... boom, my PC froze leaving me frozen on the ILS with traffic behind.
      I did shout a quick 'I am logging off' before disconnecting.
      Thank you Lenny, your patience and guidance were both very welcome. Apologies for stopping on the ILS all be it momentarily.
      ...............
      I have now uninstalled the newly installed drive backup software!  I never knew was running in the background trying to clone my drive whilst I was flying... Doh!
       
    • Ben Cook
      By Ben Cook
      Hi all,
      It is with regret that I am announcing my resignation as TG Instructor for New Controller effective 31/10/2020.
      I would like to thank @Daniel Crookes, @Oliver Rhodes and the rest of the Training Department for their continuous support. I would like to especially thank my partner in crime, @Fergus Walsh, who has worked with me for the last year. We have introduced some very exciting changes to TGNC including exams and structured lessons and I am very happy to have been a part of it.
      This is certainly an experience that I will never forget, and I am grateful for the memorable times I have had in the department. I look forward to seeing where Fergus and my successor takes the TG in the future!
      Thanks,
    • Harry Sugden
      By Harry Sugden
      Back in mid-2019...
      And now it's happening!
      To bring the terminology in line with ICAO’s preference for PBN procedures, the UK has been transitioning from “RNAV” to “RNP” approaches this autumn. There has been no change to any of the procedures and how they work; just the name and associated phraseology. I thought people might be interested in where/when this change has taken place to reduce any possible confusion over the frequency if pilots have up to date charts!
      The airfields for which the RNAV approach has already been renamed as of AIRAC 2010 (Effective ALREADY!) are:
      Alderney EGJA Barra EGPR Barrow/Walney Island EGNL Belfast/Aldergrove EGAA Birmingham EGBB Blackpool EGNH Bristol EGGD Cambridge EGSC Campbeltown EGEC Cardiff EGFF Cranfield EGTC Doncaster EGCN Dundee EGPN The following airfields will have their RNAV approaches renamed to RNP as of AIRAC 2011 (Effective this Thursday, 08 October) :
      Exeter EGTE Gloucester EGBJ Guernsey EGJB Islay EGPI Jersey EGJJ Kirkwall EGPA Lands End EGHC Liverpool EGGP London/Gatwick EGKK London/Heathrow EGLL London/Stansted EGSS  
      Heathrow
      The trial for the RNP Y approach remains in place, effective 08 OCT 2020 - 06 OCT 2021. Therefore, the permanent approach must be referred to as the “RNP Zulu” approach on frequency, as on the chart, and the RNP Y as "RNP Yankee".
       
      Some General RNAV Reminders
      The QNH must be included in RNP approach clearances, even if it has been issued with an earlier descent - “cleared RNP approach runway (designator), QNH (hPa)”. (I couldn't find the Procedure Change Post for this, but there definitely was one!)
        There are 3 fix types prior to the MAPt: IAF, Initial Approach Fix; IF, Intermediate Fix; FAF, Final Approach Fix. Aircraft may only be instructed to route direct to either an IAF or IF to commence an approach, not the FAF.
        Clearing an aircraft for the RNP approach clears them to descend to the platform altitude and then further with the procedure. Sometimes, generally for either separation purposes or due to the controlled airspace base, you may need to instruct the aircraft to maintain a higher altitude even if they are direct to the IAF/IF. The following phraseology may be used: “EZY12AB, route direct OLEVI, maintain altitude 4000ft” then later “EZY12AB, cleared RNP approach runway 26L QNH (hPa)”
        Where aircraft are instructed to route direct to an IF to commence the procedure - as they would be at Gatwick, for example - the turn at the IF onto the final approach track must not exceed 45 degrees.
×
×
  • Create New...