OnCourse Software

OK, I have read the relevant parts of the pdf more than once, and I know I am probably being dense, but why is the Oceanic Airspace option greyed out for most of my flight plans which cross the Atlantic? I recently flew Bogota to Madrid, and that was fine: the OA option is still available for that flight, but all the other transatlantic flight plans I have tried have no OA option in the main PF3 window.

The only comment I can find here (by Dave M) is this:

Quote:

If the option is greyed out it means you have already created an Oceanic flight plan that contains Gander and Shanwick. If the flight plan does not contain Gander and Shanwick it is not an Oceanic flight plan and the option becomes available to give you the choice to make it such

but I don't understand what it means. Sorry! How do I now define OA for EGLL-KBOS? The only flight plan for which I have designated Oceanic Airpspace was that SKBO-LEMD flight (and that went nowwhere near Gander/Shanwick airspace). Is there something I have to reset?

Thanks...

If the option is greyed out it means PF3 recognises it is already an Oceanic plan. There is no need to define it as such. Just fly your plan and at Gander/Shanwick the OP will kick in.

So, assuming I've now understood correctly, all North Atlantic crossings are going to be greyed out, as PF3 recognises that they are Oceanic Airspace. Whereas all crossings from South America (or, from North America to, say, South Africa/vice versa) are entered manually.

Thanks for the clarification.

martinlest wrote:

So, assuming I've now understood correctly, all North Atlantic crossings are going to be greyed out, as PF3 recognises that they are Oceanic Airspace. Whereas all crossings from South America (or, from North America to, say, South Africa/vice versa) are entered manually.

Thanks for the clarification.

It is a bit contra-intuitive I agree. Perhaps Dave could add a pop-up to remind the user that the fpl has been recognised as NATS.

Hi Martin,
did your flightplan have waypoints like N5750,N5740 etc in it or was just the std type of lettering like SHA for Shannon and such like?

I copied a real-world BA flight plan for EGLL-KBOS, but a few of the waypoints there don't exist in FSNavigator (e.g 'VIXUN'), so I had to change it a little, substituting nearby waypoints.

The plan contains both named waypoints and VORs, and also standard 'co-ordinate' waypoints like N5140, and so on. This is it, in fact:

waypoint.0=EGLL, A, N51* 28.65', W0* 27.56', +000078.74,
waypoint.1=WOD, N, N51* 27.17', W0* 52.73', +000000.00,
waypoint.2=CPT, V, N51* 29.50', W1* 13.18', +000000.00,
waypoint.3=DIKAS, I, N51* 46.62', W3* 15.55', +000000.00,
waypoint.4=STU, V, N51* 59.68', W5* 2.42', +000000.00,
waypoint.5=CRK, V, N51* 50.44', W8* 29.66', +000000.00,
waypoint.6=ADARA, I, N51* 30.00', W15* 0.00', +000000.00,
waypoint.7=5120N, I, N51* 0.00', W20* 0.00', +000000.00,
waypoint.8=5130N, I, N51* 0.00', W30* 0.00', +000000.00,
waypoint.9=5140N, I, N51* 0.00', W40* 0.00', +000000.00,
waypoint.10=4950N, I, N49* 0.00', W50* 0.00', +000000.00,
waypoint.11=LIBEK, I, N48* 5.91', W54* 6.37', +000000.00,
waypoint.12=YQY, V, N46* 9.20', W60* 3.35', +000000.00,
waypoint.13=YHZ, V, N44* 55.38', W63* 24.12', +000000.00,
waypoint.14=TUSKY, I, N43* 33.90', W67* 0.00', +000000.00,
waypoint.15=SCUPP, I, N42* 36.18', W70* 13.82', +000000.00,
waypoint.16=KBOS, A, N42* 21.91', W71* 0.42', +000016.40,