Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Jeremy Peterson

Pages: 1 ... 7 8 [9] 10 11
121
Events / Re: May The 4th Be With You FNO
« on: May 05, 2018, 08:44:38 AM »
Here is a time lapse of my flight analysis. It starts overhead the JHAWK intersection on the edge of the MCI TRACON at 8:15PM, and ends at 9:45PM. The video was compressed 128x in the sim, and an additional 8x in post editing. The total time from JHAWK to touchdown was about 1hr and 30mins

Link to time lapse: https://gyazo.com/b466bd2660d6f91c3aaac6af76fc4dd5

Nice little time lapse!

I noticed on VATSPY at one point I counted 51 arrivals in a 30 minute period. Real world AAR rate for that airport is 52/hr. So basically the airport saw double the capacity of what it can handle in the RW.

You might want to check your math. If you got 51 arrivals in 30 minutes and then none in the following 30 minutes, you’ve achieved a total arrival rate of 51. If you had 51 arrivals in both periods, then it would be double the real world rate. It’s a small discrepancy but worth mentioning.

122
The Control Room Floor / Re: Metering on the Network
« on: March 21, 2018, 07:54:45 AM »
I want to thank everyone for their input, I hope the discussion continues.

Maius has been an absolute boss at doing the website end for ZMP, and he decided this TMU project was something that was doable. Here's an idea of how deep of a discussion we went into about this:

I were looking at stats from our last event and found the busiest 30 minute period, which we all agreed was beyond our max (factoring in network lag and bad pilots). So we figured a max, took 20% off of it, and decided that it's the "AAR" than we can use to shoot for during events. We just have to figure out the different rates for the other runway configs.

Holy crap we're dorks.

MSP Rates:
http://www.fly.faa.gov/Information/west/zmp/msp/frames.htm

Also, I'm very interested in your TGUI you made for MSP! PM me please, I'd like to know more!

123
The Control Room Floor / Re: Metering on the Network
« on: March 18, 2018, 09:48:39 AM »
It's important to remember that TMU is a process, not just a function. It takes planning, familiarity of airspace, open lines of communication, and collaboration. I remember for the PHL FNO a few months back, I was TMU for that event, I made sure to be cognizant of what could go wrong before it actually hit us.

The constraining factors for this event were staffing levels and high anticipated volume. I anticipated two possible scenarios and proposed workarounds to their constraints. Here's the first possible scenario:



This scenario features heavy ZBW flow on J121 in combination with high DC Metro (PCT) volume. The solutions were pretty straightforward: (1) BOS ground stop for 1 hour and then a PCT ground stop about 15 minutes after, to end at the same time as the BOS one to stabilize demand; or (2) extensive MIT with ZNY, ZDC, and ZBW.

This is the 2nd scenario and it actually came to fruition:



Here, we have heavy ATL volume with little room to accommodate flows from ZOB or ZNY66 (flights from/through ZBW). Unfortunately, there is little coordination we do with ZTL (a major pitfall for ZNY since there's so much traffic between the 2 ARTCCs) so we would have to heavily rely on ZDC. The best possible action would have been an ATL ground stop for no more than an hour to clear the airspace and reaccommodate capacity to allow for that flow. Once it was released, we would implement MIT for ZDC overflights landing PHL (i.e., the ATL departures). Option 2 was to stop DC Metro departures and place ZBW on CFR with ZNY_TMU in order to optimize the arrival streams. The last option was to reroute aircraft through ZOB (which we ended up doing) to help out ZDC with the MIT. This required coordination with ZDC, ZTL, ZID, ZOB, and ZNY and was the least desirable option; we only used it because we were unable to get ATL to give us the ~40 MIT we needed to accommodate other arrival streams in time.

124
The Control Room Floor / Re: Metering on the Network
« on: March 17, 2018, 03:16:24 PM »
Another suggestion: Could TMU be used for Call-for-Release procedures? I'm not talking in getting the release from the TRACON, but in particular for the featured airport for FNO, could the local controller not only get the release from the TRACON (for the TRACON's airspace), but for the release for the aircraft going to the FNO airport and get the window for their departure? Sorta like combining metering with calling up for oceanic clearance, and getting the expected window for when they should reach the sector in question.

This is usually how we do it for ZNY. Either the EC or dedicated TMU will make sure the appropriate lines of communication are open for release time coordination. For example, during the Eastbound CTP, I was working with the ZBW TMU to coordinate releases that weren't initially scheduled through the official booking channels. ZBW had heavy enroute volume and departures from EWR or PHL bound to Europe were on CFR. EWR Tower would relay me flight info they were requesting to release and I would call ZBW TMU and ask them for a specific wheels-up time. EWR Tower would be responsible for getting that flight of the ground within 2 minutes prior to 1 minute after that time or a new release would have to be coordinated.

In the real world, CFR isn't always involving the ARTCC (or for N90, the TRACON) TMU; sometimes the tower only has to pick up the phone (unless they have a shout line or something) to the TRACON or ARTCC controller above them and request a specific release. However, other times TMU or specific TMU personnel are aware of the CFR procedures being in effect and participate in coordinating the releases so that controllers can focus on more immediate things.

125
The Control Room Floor / Re: Metering on the Network
« on: March 17, 2018, 09:37:54 AM »
Sometimes what we do in New York is Call-for-Release (CFR). If I’m the TMU for the event, I’ll usually be asking ZBW—or at the very least, BOS—for CFR for all flights coming to the designated airport. That way, I can look for appropriate gaps in enroute/arrival flow to fit in aircraft. Downstream centers can do this too; for instance, often times we get a heavy arrival stream from ATL at some point during the event. ZTL is a tier 2 center and admittedly, we have very little infrastructure to communicate with them so we ask ZDC to have them either provide MIT, reroutes, or ideally, CFR to either our TRACON, Center, or just between them (ZTL to ZDC).

Additionally, we have implemented CFR for ZOB and CZY, where Toronto traffic is heavy.

CFR is pretty much as close as we can get to using all available arrival capacity efficiently without creating excessive delay through ground stops and holding. All that has to happen is the tower calls either an enroute controller or the TMU requesting CFR and asks for a release time. They have 2 minutes before the time and 1 minute after the time to release that aircraft or else they will have to ask for another time.

Alternatively, if you know the demand before an event (like through signups where you have a flight list), you can construct a ground delay program to schedule aircraft. This is the most effective method of controlling your arrival rate because it restricts it to a certain number. You break each hour into segments and schedule aircraft to each block leaving a certain number of slots empty to account for unscheduled traffic (pop ups). Unfortunately, while often being the most effective method of controlling your arrival rate, it is the most time consuming and relies on a high level of controller-controller and controller-pilot cooperation and rarely ever suits events in VATSIM due to the lack of that cooperation.

Finally, for short term periods of excess demand, a ground stop is usually sufficient. The scope is important here and must be determined before implementing the GS. If there is excess demand for MSP and much of the future traffic isn’t airborne yet and originated from ORD, MDW, and MCI, then a tier 1 ground stop would suffice. If you have a heavy arrival stream from DEN and there are 28 more departures not yet airborne, bound to MSP, then a single-airport (for DEN) is all that’s needed and anything more than that would generate excess delay. If there is excess demand from many ARTCCs, all scheduled into MSP and not yet airborne, then an ALL+Canada GS might be most effective.

Oh, and for reference, there have been times where 40 MIT for ZTL to ZDC wasn’t even enough for spacing LGA arrivals and we had to seek other solutions. One thing we did was implement a mandatory reroute from the FAA Playbook that swapped the arrivals to come through ZOB and this alleviated congestion some. ZDC also did a great job in creating space for us while that was happening. If I remember correctly, BOS didn’t have a whole lot of traffic coming in so nothing was necessary with them, though if it were a problem, I would’ve had them on CFR.

126
Events / Re: Northeastern Corridor 2018 [19JAN 2359-0500z]
« on: January 23, 2018, 09:01:08 AM »
Event period: 19 JAN 2018/2359Z - 20 JAN 2018/0606Z
Total reported KBOS operations (to/from KJFK): 46

Source: http://stats.vatsim-germany.org/

Event period: same as above
Total reported KJFK operations (to/from KBOS): 46

Source: http://stats.vatsim-germany.org/

Seems like a low number but this is what I'm finding. It looks like DCA was the real winner this event with event operations of greater than 60 for JFK and BOS each.

127
Events / Re: Northeastern Corridor 2018 [19JAN 2359-0500z]
« on: January 22, 2018, 09:27:23 PM »
Total airborne time ranged from just under 14 minutes to just over 1 hour!
Might that one hour one have been me?  I departed KFRG at 0231z and was probably handed to Philly Approach at around 0330z.  However, I was in a DC3 making about 130 knots over the ground, so... lol.  I don't know if your stats are including only aircraft who arrived into or departed from KJFK, or those who passed through the terminal airspace.

No, JFK departures and arrivals are only captured in these stats.

128
Events / Re: Northeastern Corridor 2018 [19JAN 2359-0500z]
« on: January 22, 2018, 08:02:20 AM »
I tracked 101 departures, 92 of them went to BOS/JFK. I would say it was 60/40 JFK, so I have to agree with Cam about those stats maybe being off. Probably issues with servinfo/vatstats or something.

You’re both probably right. If VATSIM afforded us better and more frequently updated data, by all means the numbers would look better. I’m only reporting on what I could find post hoc. Thank you both for verifying my suspicions; at the very least, these numbers represent a sample of the actual system “population” during the period and are reflected proportionately.

129
Events / Re: Northeastern Corridor 2018 [19JAN 2359-0500z]
« on: January 21, 2018, 11:51:09 PM »
  • BOS: 19 arrivals/30 departures
You're saying BOS only received 19 arrivals throughout the entire event? Or just from JFK? Either way I'd check that - definitely is not correct.

From JFK. I thought this might be suspect too but those are the stats I got. If ZBW would like to run a review on their end, we could see better what happened.

130
Events / Re: Northeastern Corridor 2018 [19JAN 2359-0500z]
« on: January 20, 2018, 07:20:19 PM »
Here is the preliminary System Review for JFK.

Assumptions, disclaimers, drawbacks, and sources:
The data are very coarse due to the limitations of the VATSIM data update interval (about 2 minutes at best). Furthermore, airborne-based statistics are calculated over a period starting when an aircraft enters N90 (e.g.., crossing CCC at 12000). These times were reasonably estimated through analysis of each flight's position, speed, and altitude profiles. Ground-based times are calculated either from an estimated time of pushback (i.e., a small spike in the aircraft's speed [<5kt] before a period of taxiing and before takeoff) or the start of taxi (i.e., the time when the aircraft's speed is reasonably indicative of taxiing, before takeoff). Small changes in an aircraft's speed can occur erroneously when on the ground so may not indicate when an aircraft is actually pushing back or taxiing. Finally, if there is an aircraft in the list that doesn't have any times associated with it other than a wheels up/wheels down time, then it wasn't found in the vatstats.net database and no reasonable assessment of position, altitude, or speed were made.

With that behind us, let me present some statistics and findings of these data:
  • Total airborne time (time when aircraft enters airspace - time when aircraft lands) averaged slightly over 25 minutes
  • Total airborne time ranged from just under 14 minutes to just over 1 hour!
  • Taxi time averaged almost 21 minutes and ranged between roughly 1 minute and 45 minutes
  • 15 arrivals contributed an accumulated airborne delay minutes of 328 minutes
  • The longest airborne delay experienced was 38 minutes AAL3 from BOS-JFK, landing just before 04Z. This flight cancelled approach twice and got "spun" between NY_CAM_APP (2G) and NY_KFI_APP (2A).
  • 56 departures contributed a total of 737 delay minutes on the ground at JFK (extra taxi time above an average unimpeded taxi-out time of 11 minutes)
  • Total JFK-wide delay was 1065 minutes
  • DCA: 37 arrivals/36 departures
  • BOS: 19 arrivals/30 departures
  • Other noteworthy airports: MIA (12 arrivals/0 departures); ATL (7 arrivals/5 departures); EGLL (3 arrivals/4 departures)
  • Per the most recent 2016 numbers of the cost per minute of delay ($62.55), these delays would have cost $66,615.75 in the real world

Here is the link to my spreadsheet:
https://docs.google.com/spreadsheets/d/1B1ABgrQK1EiPfC2vLwVQ4thDzCreTqt8jdJ6lAjP1fQ/edit?usp=sharing

131
The Classroom (Controller Tips) / Re: Traffic Management in VATSIM
« on: October 26, 2017, 05:33:31 AM »
By the way, if anybody has knowledge, motivation, or pre-existing traffic management or VATSIM data processing tools and want to continue developing them, vATCSCC has platforms through which this can be facilitated (i.e., Google Cloud Platform). If you would like to contribute or have a system to work in (don't have to worry about storage, have access to cloud data services, etc.), shoot me an email! We'd love to have your help.
Just to clarify:  Are you offering to fund the operations of other TM related development with your GCP account?

Well it’s more like find the platform on which you have the freedom to develop your systems through the vATCSCC system...is that makes sense. For all intents and purposes, yes.

132
The Classroom (Controller Tips) / Re: Traffic Management in VATSIM
« on: October 25, 2017, 10:34:53 PM »
By the way, if anybody has knowledge, motivation, or pre-existing traffic management or VATSIM data processing tools and want to continue developing them, vATCSCC has platforms through which this can be facilitated (i.e., Google Cloud Platform). If you would like to contribute or have a system to work in (don't have to worry about storage, have access to cloud data services, etc.), shoot me an email! We'd love to have your help.

133
The Classroom (Controller Tips) / Re: Traffic Management in VATSIM
« on: October 19, 2017, 05:46:45 AM »
I wish I could say I'm surprised that this has gotten such a negative response. Traffic management is one of those topics that is so foreign to a lot of people on this network, and I'm happy to see someone actually trying to make a difference.

Good luck with the project, I bookmarked and will be checking in!

Thanks! If you’re looking to be more involved than just the training (i.e., administration or other stuff) or know people who might be, I’d certainly appreciate the help.

134
The Classroom (Controller Tips) / Re: Traffic Management in VATSIM
« on: October 11, 2017, 09:07:01 PM »
Thank you!

135
The Classroom (Controller Tips) / Re: Traffic Management in VATSIM
« on: October 11, 2017, 06:55:36 PM »
Appreciate the response Ira. I am aware of the content that ZNY made with Alex Evins and AJ, but that information is either inaccessible or deprecated. That content was also before "my time" here with ZNY. During the time between then and now, I perceived a lull in the attention given to traffic management, so my interest in it led me to create this. Plus, I want to create this project in a fashion that I synthesized, rather than an extension of what was already created.

Due to the shear nature of the traffic management community, the materials overlap. Nonetheless, all of my content is original. Any resemblance to previously created material is simply coincidence. I have citations for any material used other than that which is easily accessible and publicly distributed content (like most pictures or videos)

I would love to see the material that ZNY had but such material is not readily available without me having to reach out to someone for the resources (which I don't want to do).

And at this point, I have no inclination of including VATUSA management on this (yet). I want to create a workable system first with material that I created. That's my take. Hope this clears some things up.

Pages: 1 ... 7 8 [9] 10 11