A weekly award for high controller staffing on VATSIM
By Mark Richards 811451
#510853 Congratulations to:

Tower

Image

Code: Select allTop 20 Iron Mic Winners (TWR scoring, 1 pph per facil)
From: 2017-02-13 00:00:01    /    Until: 2017-02-19 23:59:59
============================================================
 #   ID      Facility (airport) name          Uptime    Up %
--   -----   ---------------------------   ---------   -----
 1   EDDF    Frankfurt                      67:35:11   40.2%
 2   CYYZ    Toronto-Pearson                62:03:04   36.9%
 3   EGNX    East Midlands                  46:25:04   27.6%
 4   PDX     Portland Intl OR               37:48:04   22.5%
 5   PHX     Phoenix Sky Harbor Intl AZ     36:07:41   21.5%
 6   LIRF    Roma-Fiumicino                 34:42:41   20.7%
 7   ENBR    Bergen                         34:04:52   20.3%
 8   EGKK    London-Gatwick                 32:19:22   19.2%
 9   SAN     San Diego Intl-Lindbergh Fi    28:32:08   17.0%
10   SFO     San Francisco Intl CA          28:10:22   16.8%
11   SY      Sydney Intl                    27:30:25   16.4%
12   ESSA    Stockholm-Arlanda              24:34:28   14.6%
13   UKBB    Kyiv (Boryspil)                23:50:46   14.2%
14   ML      Melbourne Intl                 23:17:00   13.9%
15   EGLL    London-Heathrow                23:09:14   13.8%
16   WSSS    Singapore-Changi               22:06:26   13.2%
17   EDDT    Berlin                         21:18:45   12.7%
18   LPPT    Lisbon                         21:10:04   12.6%
19   EGGP    Liverpool                      20:53:02   12.4%
20   EGSS    London-Stansted                20:23:07   12.1%
============================================================



Approach

Image

Code: Select allTop 20 Iron Mic Winners (APP/DEP scoring, 1 pph per facil)
From: 2017-02-13 00:00:01    /    Until: 2017-02-19 23:59:59
============================================================
 #   ID      Facility (airport) name          Uptime    Up %
--   -----   ---------------------------   ---------   -----
 1   KJFK    New York Kennedy Intl NY       63:59:04   38.1%
 2   ATL     Atlanta Hartsfield Intl GA     61:03:39   36.3%
 3   UGTB    Tbilisi (Lochini)              45:29:57   27.1%
 4   CYYZ    Toronto-Pearson                40:49:57   24.3%
 5   ESSA    Stockholm-Arlanda              35:47:30   21.3%
 6   ENGM    Oslo-Gardermoen                33:57:10   20.2%
 7   EGKK    London-Gatwick                 33:49:44   20.1%
 8   LROP    Bucuresti-Otopeni              28:53:03   17.2%
 9   EIDW    Dublin                         28:24:40   16.9%
10   KPHL    Philadelphia Intl PA           26:09:31   15.6%
11   KLGA    New York La Guardia NY         25:26:04   15.1%
12   SEA     Seattle-Tacoma Intl WA         25:18:21   15.1%
13   SAN     San Diego Intl-Lindbergh Fi    24:07:34   14.4%
14   EGBB    Birmingham                     22:52:38   13.6%
15   EDDH    Hamburg                        21:36:51   12.9%
16   REG     Dallas-Fort Worth Intl TX      21:25:25   12.8%
17   MCO     Orlando Intl FL                20:15:33   12.1%
18   EDDF    Frankfurt                      19:51:35   11.8%
19   EGLL    London-Heathrow                18:41:53   11.1%
20   BOS     Boston Logan Intl MA           18:29:36   11.0%
============================================================


Center

Image

Code: Select allTop 20 Iron Mic Winners (CTR scoring)
From: 2017-02-13 00:00:01    /    Until: 2017-02-19 23:59:59
============================================================
 #     ID   ARTCC/FIR name                    Uptime    Up %
--   ----   ----------------------------   ---------   -----
 1   LQSB   Sarajevo Radar                  90:18:28   53.8%
 2   ESAA   Sweden (Suecia) Low             46:57:00   27.9%
 3   EFES   Tampere                         38:03:04   22.6%
 4   PAZA   Anchorage                       35:22:13   21.1%
 5   KZTL   Atlanta                         33:37:04   20.0%
 6   KZBW   Boston                          33:12:37   19.8%
 7   EKDK   Kobenhavn                       32:03:14   19.1%
 8   KZAB   Albuquerque                     31:39:22   18.8%
 9   KZOA   Oakland                         31:02:55   18.5%
10   CZYZ   Toronto                         29:48:14   17.7%
11   EDGG   Langen Radar                    29:36:37   17.6%
12   GMMM   Casablanca                      27:27:41   16.3%
13   KZNY   New York                        26:42:03   15.9%
14   LECB   Barcelona                       25:41:04   15.3%
15   YSNO   Melbourne (Snowy)               25:14:48   15.0%
16   SVZM   Maiquetia                       24:38:32   14.7%
17   KZLA   Los Angeles                     23:08:09   13.8%
18   EURW   Eurocontrol West                22:59:55   13.7%
19   EDWW   Bremen                          22:45:50   13.5%
20   ENOS   Oslo                            20:29:28   12.2%
============================================================


Disqualified: UNATTENDED CONNECTION
  • NIL
By Nicholas Watkins 1259602
#511494 Hi Mark;

Can you help me understand how New York approach hours add up to 63? We track all VATSIM stats as does many other places, and based on my data and data available at other sources I cannot get 63 hours for them without combining multiple approaches, for example HRD_APP & CAM_APP are counted as one Tracon, which in my mind is no different than Atlanta counting Charlotte Tracon Hours as Atlanta Tracon hours. I see that some of the approaches are on at the same time and it appears that those hours aren't being counted, however I don't feel the combined approach should account for a singular position, as they are not.
By Michael Mund-Hoym 1038942
#511496 It is my understanding that hours counted towards the JFK part of N90 Tracon are callsigns NY_CAM_APP and NY_KEN_DEP. For the EWR part they would be NY_ARD_APP and NY_NWK_DEP, and for the LGA part NY_HRP_APP and NY_LSO_DEP. This is certainly not an official statement though.
By Mark Richards 811451
#511497
Nicholas Watkins 1259602 wrote:Hi Mark;

Can you help me understand how New York approach hours add up to 63? We track all VATSIM stats as does many other places, and based on my data and data available at other sources I cannot get 63 hours for them without combining multiple approaches, for example HRD_APP & CAM_APP are counted as one Tracon, which in my mind is no different than Atlanta counting Charlotte Tracon Hours as Atlanta Tracon hours. I see that some of the approaches are on at the same time and it appears that those hours aren't being counted, however I don't feel the combined approach should account for a singular position, as they are not.

In a word, not simply. The stats are provided to me in a raw format and I run a perl script to process them. I don't know how that script works but I shall make enquiries but I think Michael might have the explanation.

It's also important to know that this information is coming directly from the FSD server and not from the stats server that is publicly available so if that was down for any time, these figures accurate whereas the third party ones cannot be.

Mark
By William Anderson 1210226
#511721 Where I am confused is to where NY APP can have several approach up, controlling different airports, but still be counted as one in terms of Iron Mic. For example, NY_ARD may be LGA and NY_CAM may be JFK but they are two different facilities. I am under the impression that the iron mic only counted for one airport/facility.

If we continue to use this system, wouldn't we have to count other connections under a major TRACON, but controlling different fields? For example, SOCAL Controls LAX, SAN among others. If they were to log on as SCT_LAX_APP and SCT_SAN_APP, would we have to include them even though they are two different fields under the same TRACON?

If this is the way it is done, it is discouraging for me to attempt to earn Iron Mic because I have been on day in and day out, keeping an eye on the different facilities that are online, and when I keep getting beat when I know they were not on as long or as often is very disheartening.

Just an observation I think should be noted for the future.
By Michael Mund-Hoym 1038942
#511736 The facility for which the hours are counted at the N90 Tracon is based on call sign.

I.e. NY_ARD_APP, though it could to my understanding cover service for more (also major) airports than just EWR, only counts towards the EWR section of N90 in the Iron Mic competition. Some VATUSA ARTCCs, such as ZLA and ZOA, use a call sign indicating that the position is working the combined major approach facility. When that call sign is used, the combined approach facility hours are tracked for Iron Mic.
By Ira Robinson 1100092
#511762 [quote="Nicholas Watkins 1259602"]Hi Mark;

Can you help me understand how New York approach hours add up to 63? We track all VATSIM stats as does many other places, and based on my data and data available at other sources I cannot get 63 hours for them without combining multiple approaches, for example HRD_APP & CAM_APP are counted as one Tracon, which in my mind is no different than Atlanta counting Charlotte Tracon Hours as Atlanta Tracon hours. I see that some of the approaches are on at the same time and it appears that those hours aren't being counted, however I don't feel the combined approach should account for a singular position, as they are not.[/quote]

Hello Nicholas. The explanation that Michael gave is spot on, and your comment that you don't feel a combined approach should account for a singular position when they are not is too. And that is why your understanding of how New York works may need to be cleared up. The call signs you mention do not count as one Tracon. Each facility, JFK, LGA, EWR & PHL is covered by its own Tracon for purposes of the Iron Mic. The figures are not combined. That is why you will see on the list that Kennedy Approach totaled 63 hours, while Philadelphia had 26hours and La Guardia 25 hours.

Now what you may be confusing are the various call signs for each; i.e. CAM_APP, HRP_APP, etc. Each of those approach positions are assigned to their specific facility. The two examples given do not interact at all when it comes to counting hours. But when you see something like CAM_APP, RBR_APP and KEN_DEP I could understand the confusion, because these are combined positions for JFK. However, when it comes time to count the hours if more than one position is on at a time the hours from only one of them count toward the Iron Mic. So if Kennedy Departure is on and CAM Approach is on the hours are not combined or counted twice. We have been through this with the iron Mic folks several times over the years because of changing call signs and air space responsibilities and I can sure you that there is no overlap. However, if you are attempting to track hours then you need to get a better handle on the various call signs used at ZNY and how the airspace for each applies to which facility and Tracon.

If you wish i will be happy to look at the charts you used to count the hours and see if I can make sense of them for you.
By Alex Ying 1357036
#511778 [quote="Nicholas Watkins 1259602"]Hi Mark;

Can you help me understand how New York approach hours add up to 63? We track all VATSIM stats as does many other places, and based on my data and data available at other sources I cannot get 63 hours for them without combining multiple approaches, for example HRD_APP & CAM_APP are counted as one Tracon, which in my mind is no different than Atlanta counting Charlotte Tracon Hours as Atlanta Tracon hours. I see that some of the approaches are on at the same time and it appears that those hours aren't being counted, however I don't feel the combined approach should account for a singular position, as they are not.[/quote]

Atlanta TRACON (A80) and Charlotte ATCT aren't necessary the best comparison since those are different TRACON facilities (list of TRACONS: https://www.faa.gov/about/office_org/he ... es/tracon/). Closer to the N90 situation would be how SoCal (SCT) or NorCal (NCT) hours are counted since those are combined off-site facilities that cover multiple majors like N90. I think those are handled similarly where SCT_APP, LAX_APP (a subsector), and SAN_APP (another SCT subsector) are counted separately.

In case anyone's interested, these are the primary sector splits for N90 (all with NY_ prefixes). There are from 3 (for Kennedy) to 5 (Newark) extra subsectors that get opened for events or high traffic only. On top of that, there are Liberty (high altitude departure sector and some minor airports to the North) and Islip (minor airports on Long Island) sectors that both have multiple sector splits.

Kennedy:
KEN_DEP
CAM_APP

Laguardia:
LSO_DEP
HRP_APP

Newark:
NWK_DEP
ARD_APP

You'll occasionally see ISP_APP (the aforementioned ISP sector) or CSK_APP online if people feel like controlling minor sectors. These don't cover any of JFK, LGA, or EWR.

LBE_DEP is the primary Liberty sector that takes handoffs from KEN, LSO, and NWK DEPs and sequences them before handing them off to NY_CTR or BOS_CTR. I'm actually interested in how this gets counted for Iron Mic since it explicitly covers all 3 N90 majors.

The staffing policy at ZNY is that if you're certified on multiple N90 sectors, you can extend coverage from one callsign to other sectors. For example, it's common for someone on NY_CAM_APP who's also certed on HRP_APP to cover both Kennedy and Laguardia or someone certed on all 3 major sectors to cover all of N90 from the NY_CAM_APP callsign.
By Ira Robinson 1100092
#511783 [quote="Nicholas Watkins 1259602"]Hi Mark;

Can you help me understand how New York approach hours add up to 63? We track all VATSIM stats as does many other places, and based on my data and data available at other sources I cannot get 63 hours for them without combining multiple approaches, for example HRD_APP & CAM_APP are counted as one Tracon, which in my mind is no different than Atlanta counting Charlotte Tracon Hours as Atlanta Tracon hours. I see that some of the approaches are on at the same time and it appears that those hours aren't being counted, however I don't feel the combined approach should account for a singular position, as they are not.[/quote]


If you point me to where you found the statistics for the time frame in question I will be happy to review it with you. Because if there does happen to be an error, then we need to correct that too!

Send me a PM or email me at ira [dot] robinson [at] gmail [dot] com