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 - Roger Curtiss

Pages: [1] 2
NOTAMs / Re: RIP Curley Bryant
« on: February 11, 2023, 04:36:32 PM »
This is a shame.  I worked with Curley at ZOB and he was a delightful presence with a huge dedication to VATSIM.

Events / Re: ZDC Presents: Cherry Blossom [28MAR2020 2330z-0330z]
« on: March 28, 2020, 11:22:59 PM »
I flew in this event within its first 2 hours-it was busy and well managed.  I took a look 4 hours later and it is still going strong-83 arrivals in the queue and a full load of controllers still "personning" the scopes.  Great job by all involved.  I tried leaving a note in the ZDC Feedback option but it wanted a specific controller and all who participated are worthy of mention.

General Discussion / Event Times
« on: March 01, 2020, 04:32:08 PM »
It can be rather frustrating to see practically every VATUSA event scheduled to occur in the same time frame 2359z-0400z.  While no doubt highly convenient for East Coast/Midwest USA members it is very much less so for those (apparently few) members logging on from the western side of the country.

I am curious as to how this came to be and whether:
a) the times chosen have been determined by analysis of user data (are the majority of pilots actually operating from an EST/EDT time zone?)

b) if the answer to 'a' is "no", could such a study be conducted or a poll taken to determine if indeed this is the overwhelmingly optimum time period?

c) there have been attempts to correlate event times to the actual time zones of the locations where the events are centered? i.e.,west coast events starting at 0300z?

Events / Re: [1/26/2020 2100z-2359z] Staff It Up Sunday: Featuring KJAX
« on: January 25, 2020, 11:33:10 AM »
Discrepancy in the posted times...2100z or 2200z start time?

Events / Re: [19 JAN 2359-0400Z] Escape to The Desert
« on: January 19, 2019, 02:27:00 PM »
While your instructions are clear you also contradicted yourself.

You say to report your present altitude not the altitude you are assigned or leaving but then in the example the pilot is saying, "FL190 descending 12,000...".

I would also argue that one's present altitude is also the altitude leaving but that may be a philosophical discussion better suited for another time.

Albu-turkey....good one! ;D

The Control Room Floor / Re: Shortcuts
« on: February 25, 2018, 11:05:23 PM »
LOAs are usually in effect for adjacent ARTCCs so that is about as far as seems practicable

Events / Re: Bring Don Home! [25 FEB 2200-0400z]
« on: February 25, 2018, 10:59:56 PM »
It was a pleasure to fly in this event today.  I taxied out to 17L @ KOKC and was #11 with 7 aircraft eventually behind me.  It took 40 minutes to get rolling on the runway! This was the most impressive traffic queue I have ever experienced.  Traffic was strong throughout the trip east though unfortunately I was unable to make the conclusion in KBOS.  I was running low on fuel midway and had to divert to KIAD.

What I noticed throughout the flight was the remarkable work of all the controllers who kept it calm and sorted out the potential confusion by sending the occasional aircraft on a vector to provide spacing.  Everyone was as professional as could be-the controllers were on top of their game and the pilots were quick to respond with great radio etiquette.

The performance of the participants matched that of the honoree for whom the event was created.  Don was smack dab in the middle of the traffic line as USAIR and I hope he had as good a time as the rest of us.

Kudos to all VATSIM members who were part of this event-you all done the network proud today.

General Discussion / Re: "SWA1321 With you@FL330"
« on: February 23, 2016, 04:27:29 PM »
I have posted a topic in Pilot Talk about this issue and I will be taking it up with the PTD as some good suggestions have been presented to try to reduce if not eliminate this communication area.

General Discussion / Re: "SWA1321 With you@FL330"
« on: February 23, 2016, 12:54:24 PM »
Granted, this is not a problem most of the time-which is why it never prompted me to comment on it before, however, I was mainly referring to large most definitely was a problem briefly for me last Friday as I was trying to make things orderly and I thought this sort of challenge might be prevalent.

General Discussion / "SWA1321 With you@FL330"
« on: February 22, 2016, 07:31:13 PM »
How many times, especially as a CTR controller and even more so during a large event such as FNO, have you received such a message from a pop-up target?

I worked FNO last week in an H_CTR position and it was a real problem.  I am guessing it occurs with some regularity at every major event and it may be a matter of inadequate pilot knowledge.

I honestly do not know if: a) this is as big a problem as I believe it to be or b)if there is an easy way to remedy it
but I offer the following as a suggestion-

Perhaps it would be feasible to include with the event posting a line in the description reminding pilots that handoffs require checking in only with callsign and altitude but that first transmissions when airborne to a controller at other times necessitate callsign, altitude AND position.

My thought was to gear the events to local times.  Just as LUA has center positions lighting up at local noon currently.  The point is to try an arrange coverage so that, in the example of PDT, there are more options to fly, even if it is only in the western region of the country.

Ideally, running from 1200 to 2200 would be preferred, however, it may not be practical to staff many ARTCCs for that length of time.  In which case, a later start would be good.

I think what I am saying is, if possible, pick a date, tell the ATMs/Event managers "we are considering holding this event between 1200-2200", let the ARTCCs determine what sort of staffing levels they believe they can muster and THEN set the time for the event.   A bit extra work on the planning end but it might result in greater participation through the entire day.

From what I observed today, LUA was, with only a few exceptions, a great success.  However, this-like many USA events, was a bit prejudicial toward west coast members.  Running an event until 1800 local offers very little for those of us who either cannot make it to a daytime event or prefer to fly in the evening.
As I write this it is 1955PDT and the only areas lit up are KZLC, KZLA and PHZH in the west and KZAU elsewhere.  I can understand that the controllers have put in a long day but that long day started and ended too early for those of us on Pacific time.

The same thing happens during most FNOs as well- they are over before it is FN for us (including when they are hosted in Pacific time zone locations).

So-how about trying to extend the hours of LUA to 2000 or even better, 2200 local time?

Also-in addition to lighting up America once a year, what about trying to have an entire ARTCC staffed either at a few locations for a very long time or at as many airports in the ARTCC as possible for a few hours?

I am not trying to say that LUA was not a rousing success...there were 700+ online users shortly after it started...just that we should do something along these lines more often and cater it to cover more of the day.

Virtual Airlines / Southwest Virtual is looking for ACTIVE pilots!
« on: April 01, 2010, 12:32:27 AM »
As Mike wrote:
Dear all,

"Well now is your chance to be apart of Southwest Virtual! Southwest Virtual is HIRING, yes, I said HIRING ACTIVE Pilots! At Southwest Virtual, we keep nothing but our friendly reputation going! Whether your West Coast, East Coast or digging for some High Plains or Desert Southwest, Southwest Virtual is the place for YOU!"

What a difference a space can make.  Rather than this being "a chance to be apart of Southwest Virtual..." (which apparently many pilots have already opted to do) it actually is a chance to be a part of Southwest Virtual.

And I also happen to believe it is a very good VA.  Which is why I am SWA4173 with over 83 flights in my SWA logbook.

Pages: [1] 2