Jump to content

Alex Ying

  • Content Count

  • Joined

  • Last visited

Everything posted by Alex Ying

  1. I updated to 1.2.5 and the HTTP version check and server loading is resolved, but I run into audio issues now. No matter which device or audio mode I choose, all audio was choppy and cutting in and out. I tried restarting VRC and my computer as well with no resolution. I reverted back to version 1.2.4 and the audio issues were immediately resolved.
  2. This topic has come up before on the VATUSA forums before as well, not much agreement there in the discussions I've seen. The main issue I see is that how much more helpful is it if you see *_EH_CTR vs *_7_CTR? Sure, if your'e coming from the east, you'll probably want to call *_EH_CTR, but what about if you're coming from the south? Where's the E/W cutoff line? Also, high-low splits vary depending on the area and sector. A high sector may have a floor of FL210 in one part and FL240 in another part, and so on. Same goes for approach. Sometimes you'll see more descriptive subsector name
  3. To echo what Don said, VATSIM isn't anyone's job. We all do what we do and contribute to this shared community because we like to and want to. Sometimes other commitments to family or work or school come up and VATSIM gets pushed to the background. ZNY is quite active and both the ATM and DATM are great people but also busy people. Sometimes things just take a bit longer than expected and it's nothing out of the ordinary. As an aside, ZNY is one of the largest ARTCCs in VATUSA so sometimes things take longer on the administrative side. That's just a fact of how many people there are.
  4. To echo what Steven said, in the US, STARs may or may not be runway dependent, depending on which airport you're flying to. In general though, STARs are designed for and used on arrivals from specific directions. At Kennedy (KJFK), arrivals from the west use the LENDY6, south use the CAMRN4, and north/east use the IGN1, ROBER2, or PARCH2. SIDs are often similar where they're names after the exit fix that they lead to. The US also has SIDs named for the airport such as the Kennedy 3 Departure (JFK3) which is a general SID that applies to all runways and most if not all exit fixes available from
  5. I wouldn't say any particular subject or cl[Mod - Happy Thoughts] is "the most important." What's important are various skills that can be applied to the task of air traffic control. ATC is about maintaining safety and efficiency in a 4 dimensional environment (latitude, longitude, altitude, and time). Therefore, spatial reasoning ability is critical. You can't maintain separation if you can't form a coherent mental picture of what the airspace looks like and how the aircraft are moving through it. Understanding some basic physics and meteorology wouldn't hurt. A good understanding of arit
  6. Depends on the airport and airspace layout. KEWR departures climb up to 10000 or 11000 in a small rectangular airspace near the airport above arrivals at 7000 flying in a loop farther out around the airport. I think KLGA departure generally climb above arrivals. KJFK on the other hand has a arrivals and departures crossing above or below each other depending on the particular configuration and departure or arrival fix. There are cases where a departure goes under an arrival flow and then over the same arrival flow in a different location and vice versa. For example, on the 31s, arrivals fr
  7. If you're flying in the US and looking for actual routes themselves, the FAA and FlightAware are good resources FAA Preferred Route Database FllightAware IFR Route Database
  8. For routes, you can also search the for routes in the FAA Preferred Route Database (PRD). Some ARTCC also have their own PRDs which are modified versions of the RW FAA database (for example ZNY's PRD)
  9. Another source of US charts that I use is http://www.airnav.com/airports/ Not quite as pretty as SkyVector but I've found it easier to find a particular chart in the list format rather than the thumbnails on SkyVector's airport pages.
  10. 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/headquarters_offices/ato/service_units/air_traffic_services/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 prim
  11. Personally (and I'm biased since I'm a ZNY controller), I think it makes sense for the large consolidated US TRACONs to count all the primary sectors as one. Tower hours obviously are tied to an airport and center hours are not. For approach/departure, it's a little less obvious because approach certification varies greatly across all the different TRACONs (or approach facilities outside the US) due to airspace and whatnot. It seems to me that for approach, if a sector from that facility is staffed, then it should count for the facility, not the individual airport, since the TRACON isn't tied
  12. I had this happen to me today. I was controlling KEWR, and then about an hour in, vATIS crashes for me, but not for KLGA who was also online. I can start it and fetch the D-ATIS offline, but if I fetch the D-ATIS while connected to VATSIM, it crashes. I noticed that the VATSIM weather also stopped updating for me while vATIS was unusable (about an hour and a half to 2 hours). After that, the weather on VATSIM updated, and vATIS started working again.
  • Create New...