by SAX775 » Sun Jun 29, 2008 1:07 am
I don't think I understand the penalty or bonus that is associated with on time arrivals. I have read the Ops Manual and this thread and while it states that you use an on time arrival formula it does not specify what actions are taken for early or late arrivals.
I use Activesky X for my weather and RadarContact 4 for my ATC. In RC4 I have ATC and weather delays turned on. This means that if ATC detects (or randomly generates a delay) into the holding pattern I go. This happen last night on my return from KDEC to KSTL. ATC randomly generated a delay into KSTL and into the holding patterns at TOY I went. Once you get that close to an airport there is no more wiggle room to make up time so I had to just eat the delay totaling 0.3. After release from TOY I flew the B190 to its maximum performance but there was no making up time. (Real torque limit is 86% for 1700 RPM and 94% at 1500 RPM and that was my limit. You have a 5 minute 100% torque take off limit, but I use that for take-off and when required during single engine ops.)
In the real world I have experienced enroute and arrivals delays plenty of times. It seems that they never occur when we are out training, but always when passengers are in the back. All you can do is explain to the passengers the situation and let them know you are doing everything you can to make up for lost time.
I think RC4 or even VATSIM to a lesser degree, offers this very likely real scenario and because it does happen in real world I chose to accept the flight. Now I wonder what I need to do as far as pay the piper. In the real world if someone would ask, usually rare unless someone very important was in the back, I just had to provide a verbal; ATC delay, weather, departure delay, passenger delay (I have had passengers arrive late and still expect an on time arrival), ect.
Ken Goodpaster
SAX 775