OnCourse Software

johnhinson wrote: *

Thu May 04, 2017 5:01 am

Should PF3 give "line up and wait" (or "position and hold", as was) instructions?

I was held for take off but incorrectly given clearance as soon as the incoming aircraft had touched the runway. (Iwas also given preference over another waiting aircraft). I pulled onto the runway smartly as another incoming aircraft had called in for landing. I could see the first ahead while I did take-off checks and also heard it report clear of the runway so PF3 obviously knew exactly where it was. The second arrival had to go around (pilot's decision, not the controller's, if I remember rightly) so I should really have been held for that too. My setting for "Hold for jets on final" is 6 miles (the default) but I think it was a lot closer than that.

Seems PF3 made a bit of a mess of this, not at all its normal disciplined way. Appropriate log (hopefully) attached.

John

Quote:

Should PF3 give "line up and wait

Quote:

I was also given preference over another waiting aircraft

Quote:

I pulled onto the runway smartly as another incoming aircraft had called in for landing. I could see the first ahead while I did take-off checks

Quote:

and also heard it report clear of the runway so PF3 obviously knew exactly where it was

Quote:

The second arrival had to go around (pilot's decision, not the controller's

dmarch wrote: *

Thu May 04, 2017 10:41 am

Quote:

Should PF3 give "line up and wait

Not necessarily

dmarch wrote: *

Thu May 04, 2017 10:41 am

Quote:

I was also given preference over another waiting aircraft

Do you mean they were in front of you on the taxiway?

dmarch wrote: *

Thu May 04, 2017 10:41 am

Quote:

I pulled onto the runway smartly as another incoming aircraft had called in for landing. I could see the first ahead while I did take-off checks

I think your takeoff checks should be completed before you enter the runway

dmarch wrote: *

Thu May 04, 2017 10:41 am

Quote:

The second arrival had to go around (pilot's decision, not the controller's

Again you shouldn't have been hanging around on an active runway doing takeoffchecks

dmarch wrote: *

Thu May 04, 2017 10:41 am

AI interaction in PF3 is by no means perfect but it works well 99.9% of the time. At some time in the future I will revisit AI monitoring and maybe, just maybe I might be able to improve some areas. Unfortunately it's very difficult to see exactly what AI traffic was doing just by using the log file you provided unless your debug level is set to maximum, which of course will then generate very large files. But obviously if you do get a recurring issue then by all means recreate it with your debug level set to max and let us have the log.

dmarch wrote: *

Thu May 04, 2017 10:41 am

Quote:

Should PF3 give "line up and wait

Not necessarily

Quote:

I was also given preference over another waiting aircraft

Do you mean they were in front of you on the taxiway?

Quote:

I pulled onto the runway smartly as another incoming aircraft had called in for landing. I could see the first ahead while I did take-off checks

I think your takeoff checks should be completed before you enter the runway

Hi Dave,

In the A320 there is a "long" procedure and a short checklist after the take off clearance. Of course it is shared by the two pilots, not always the case in our personal simulators .. it takes only a few seconds to perform usually while you line up for take off.

Rgrds,

Massimo

Quote:

and also heard it report clear of the runway so PF3 obviously knew exactly where it was

PF3 doesn't 'track' AI aircraft and it simply reports events after they occur

Quote:

The second arrival had to go around (pilot's decision, not the controller's

Again you shouldn't have been hanging around on an active runway doing takeoffchecks

AI interaction in PF3 is by no means perfect but it works well 99.9% of the time. At some time in the future I will revisit AI monitoring and maybe, just maybe I might be able to improve some areas. Unfortunately it's very difficult to see exactly what AI traffic was doing just by using the log file you provided unless your debug level is set to maximum, which of course will then generate very large files. But obviously if you do get a recurring issue then by all means recreate it with your debug level set to max and let us have the log.