OnCourse Software

Hi Team,

I am on the latest BETA and have flown 2 flights where the same issue occurred.

My airways clearance provided the initial altitude of FL100.

On contact with Departures cleared to FL100.

Approaching FL100, not provided with an onwards climb to a higher altitude.

Levelled off and maintained FL100 and then instructed to maintain 4,000ft even though I had never been provided with a clearance to 4,000ft.

I had to H9 out of the situation to recommence climb.

I don't believe i missed a call / clearance on either occasion however off apologies in advance if it is a user error!

SID altitude holds are quite uncommon in Australia and usually (IRL) we do not have any restrictions from getting airborne to being cleared to the ATS plan initial cruise altitude.

Kind regards,

Mark

Looks like you might have restarted PF3 immediately after your last flight because the log is almost empty. Please send me the old_debug_monitor.log which 'should' be the correct one for your last flight

Hi Dave,

I did not realise that opening PF3 would override the last flight log. As I have flown since the report, that old debug monitor log will be gone for the flight in question and I have H9’d subsequent flights to avoid a level off.

I see the new .75 and a change to SID management which could have been my experience so I will do a few flights with the new version and see how I go.

Thank you and all the best for the season and new year!

Kind regards,

Mark

Hi Mark,

PF3 doesn't overwrite the debug log when you start it. But under certain circumstances, of which I've yet to recreate and fix, when closing PF3 it will close the log and then suddenly want to write something else to it and consequently opens another. Thus making your current and relevant log the old one. Bit confusing and thankfully only happens occasional. I might have a look into that issue again today.