Position and Hold

[Brian Doney 127]

Hello all.Quite frequently, I've been given instructions to line up and wait with landing traffic on short final, in as close as 3 miles for an earlier flight today.Usually when this happens, and depending on what aircraft I'm in, I'll just wait for the arrival to land before I enter the runway. Typically, I'm in something heavy, with simply no possibility of getting lined up, cleared for T/O, and airborne in such a short time, so as not to cause a go around.Today I was in an MD-80, and figured I'd give it a shot. I lined up as fast as I reasonably could, got T/O clearance almost immediately after aligning, and as soon as the clearance was out of the controller's mouth, I was rolling. I had no chance, and though I expected it to happen this way, having an RA almost immediately after lift off as the landing aircraft climbed out over the top of me left me wondering:Any way to maybe prevent this from happening ? Some sort of limit to apply ? Even a, "Position and hold after the landing XXX on X mile final" would be great.This is with the new test version, just FYI.

[Ray Proudfoot 8,928]

Hi Brian,Was everything okay before the new version? Are you running FSUIPC v3.617? Have you rebuilt your scenery database?The check that you're clear to line up is well tested and reliable so I'm surprised your having these problems.If the problem persists please create a log and send it to JD.launch rcv4click debugload the .plnclick start rcOnce you're cleared to "line up and wait" stop RC, zip up the log and send it.Cheers,

[Guest Douglas Thompson]

That parameter can be opened up a bit quite easily. We'll do so if we see enough flak about this. Also, "...immediate takeoff..." will be a part of RC in v5.

[Guest realm174]

Good morning,I experience the same behaviour as described above. The only difference being that I rarely fly heavies, but there has been more than one instance where i've been just about landed on.FSUIPS 3.617RC: 4.01 (4.0.3737)thank you,realm174

[iainsmith 9]

>Hello all.>>Quite frequently, I've been given instructions to line up and>wait with landing traffic on short final, in as close as 3>miles for an earlier flight today.Just been reading in "Airports" magazine about the work of the ATC tower at London Gatwick, the world's busiest single runway airport. At busy times clearance to t/off with incomers 3 miles out is the norm. They prefer 6 miles but have to work down to 3 to handle the volume!Iain

[Guest jboweruk]

Boy that requires some quick reactions by the pilots taking off..... That's a disaster waiting to happen.

[ronzie 21]

For complex aircraft one pilot (as is usually the case with FS) has quite a load to handle. Trying to set up all parameters while taxiing and doing a checklist and comm while rolling past the hold point and lining up is quite a load. It is true that RC provides some assistance with autoreply and other stuff with the PNF but for some people this introduces other problems.Therefore just a bit more clearance in the seperation on final to let you line up and give it the gas may be necessary. There are a few cheats I use such as turning on the transponder early and landing lights on at the hold point. Using the mouse to set parameters and turn things on for a quick rolling take-off is a pain.I control final seperation with AISmooth.To insure I'm set up to go when taxiing and told to contact tower I just ack and then contact when I'm ready to go whether or not I'm rolling. I keep an eye on final traffic with TCAS so I know what to expect.We are talking heavies but close in final spacing also happens with GA mixed with small commercial at smaller "independent" outlying and feeder airports.The point is to be in full take-off config before entering the runway and if you are not ready refuse to line up but not acking.

[Brian Doney 127]

Ron,I would never take the runway without being ready to go now.If I could receive take off clearance from the hold point I'd be fine with that.I also use AISmooth.I've done everything I possibly could to get on and off the runway as quickly as possible.I guess the point is:"I keep an eye on final traffic with TCAS so I know what to expect."This I have no problem with, I'm usually mode C just before reaching the hold, but, when I actually have to disobey instructions to avoid letting RC put me into a situation like this, that kinda bugs me a little.Especially as it happens so often, not every flight, but, often enough.After using RC for a bit now, I guess I'd like to see, not really more features in AI handling, but more transparency. The only time I am reminded of the man behind the curtain, in terms of RC, is whenever there's AI involved. Be it the situation we are talking about here, or the "parting of the sea" feeling when enroute. Just some thoughts.

[Ray Proudfoot 8,928]

Hi Brian,Edited for spelling.I agree with Ron in that you should be fully configured for take-off once you've been given clearance to line up / taxi into position.The only things I do as I line up are switch on the landing and strobe lights and select LNav on the MCP. All other controls are set.We had a lot of discussion during testing on this issue. If you allow too much of a gap between inbounds then you could be waiting ages especially if you're in a queue at a busy airport. So whilst 3 miles is a bit tight providing you don't dawdle once cleared you should be okay. If an inbound is within 3 miles and you've been given clearance then wait until he's cleared the active. You're still number 1 as far as RC is concerned. Just watch out for other Ai if there's a holding point on the other side of the active as they may push in ahead of you. 27L at Heathrow is an example.We hope to include an 'immediate' departure command in a future release. Probably only when an inbound is within 4 miles although that distance will be supplied by a r/w controller.Cheers,

[Brian Doney 127]

I was trying to avoid going over the insinuation that this is a fault on my end..And ya know what, I'm not going to argue about it now.10 years of this and 2000 VATSIM hours have taught me how to be ready.In each and every instance I have been, as ready, if not more so, than you.Since you like to challenge my preparedness, there's one back at ya.I would not have brought this up otherwise.No matter who you are, and how, "ready" you think you can be, if cleared into position in a heavy PMDG744 with traffic on 3 mile final, you will cause a go around if you try it, and there is no "good" reason to keep it this way.Period.I am a little irritated now, won't deny it, not by RC funnily enough, but by the responses I've received here.I guess I'll just drop it since you two know better than I do.

[Guest mmcevilley]

>No matter who you are, and how, "ready" you think you can be,>if cleared into position in a heavy PMDG744 with traffic on 3>mile final, you will cause a go around if you try it, and>there is no "good" reason to keep it this way.>>Period.Brian,From another perspective, your point is well-taken. You are correct that regardless of how "ready" the individual is (regardless of a/c flown), the fact of the matter is that RC *may* take a bit of time to clear you for takeoff - that coupled with a short final AI, and "who-knows-what" criteria used by FS to trigger the go-around, often result in a go-around for that AI. I have had what you report happen to me (moreso in the PMDG 744 because of its taxiing difficulty - less so with the LDS 767) Quite frankly - I don't care (about the AI). If ATC clears me on the runway - then the runway is MINE! Let the AI go-around! ;-) In the real world, such would not happen - you would be cleared for immediate t/o BEFORE taking the active. Doug has mentioned that this capability will be in V5.Yes - we have tested this capability and the current "position and hold" logic represents a reasonable balance between efficiently getting you off the ground, and allowing AI to land in front of you (of course, while still holding in position at the hold line!!!! ;-) )I have had cases where an AI on 5 mile final resulted in me waiting for him to land, other cases an AI on 3 mile final will get me position and hold. I figure its a timing thing, considering all the ground and air traffic interaction going on when TWR is working landings and departures.JD and Doug take all comments and issues to heart. It will be addressed, but perhaps more likely as part of the V5 logic design and development.Hope this helps ...-michael

[Ray Proudfoot 8,928]

Hi Brian,I'm sorry that you feel irritated by the replies (presumably including mine) that you've received to your original post. It was certainly not my intention to irritate you.If you feel so inclined press the Debug button each time you start RC4 and if you do receive what you consider to be a unreasonable command to line up then post JD the log and it can be looked into.Cheers,

[Brian Doney 127]

Ray, Michael,My post was a bit inappropriate, and for that I do sincerely apologize.I just got the impression that you weren't actually listening(reading) to what I was trying to say. I know that I am doing everything I can already to minimize the issue, and to only be told that I'm not doing enough, well, rubbed me wrong. Again, sorry for that.I want to reiterate what I've said in the past, RC has completely revolutionized my sim experience, I haven't looked back since my CD arrived.My orignal post wasn't really looking for a fix, as I don't really see this issue as a true "bug", I just think it's an area that could use a bit more work. You've stated that v5 will address the issue to some extent, and that is good enough for me.

[ronzie 21]

My post was wordy but sometimes for the "edification" of others not familar with r/w demands I could put in something the original poster would know just to be sure he/she knows where I am coming from.There are three things I would like to clarify that are already in this thread:There was a bug introduced two versions ago in FSUIPC where AI on approach were not seen and premature runway clearance was granted even though you were not #1 in the takeoff queue.I do not like runway clearance when I am still quite a way from the holding point. My workaround was to ack (7) when told to contact tower and then when I am holding or approaching the holding point contact tower (1). This workaround lets RC take a fresh look at AI on final before giving runway clearance.My comment on mouse clicks while taxiing referred to covering the view out the window with an overhead pop-up to operate landing and system devices as necessary. Blind taxiing including onto the runway is kind of difficult.I was not commenting on your proficiency but just describing some non-r/w tactics I use to work around these limitations of the computer environment.

[Guest Douglas Thompson]

My guess at this point is we'll use 4m-3m for immediate, and anything greater for normal. Who knows. Two things for sure... 1, the betas will hold our feet to the fire at to whether it's acceptable or not :-) (and thank goodness for our betas!), and 2, we'll never please everyone.I was riding 'jump' on an L1011 from KMIA-KATL years ago. In the interest of fuel conservation, the captain did't call for #3 to be lit until he was clr'd into position (and quickly) clr'd for T/O. I was very uncomfortable with several things I saw in that cockpit that day. We made it to KATL though.