PilotEdge Forums

Hello,

I've chosen ORBX for Airport models, OpusFSX for Weather models, and FEX for Clouds, Sky and Water. I'm going through the manuals of each product and I've come across several questions related to their use with PilotEdge.

Opus uses NOAA weather data to create what it calls a "Dynamic Weather Region" of 912km by 912km and a "Detailed Weather Region" of 500km by 500km. Using Opus Live Weather Updates, its engine will download METAR data from various MET Stations along your intended route depending on the ICAO of your destination and en route alternates. In addition, Opus also injects Winds into the simulation for both Surface and Aloft based on METAR and/or GRIB data. With just this information alone, you can see several questions that need to be asked:

1) What happens to my Wind information coming from Opus, when I'm flying through PilotEdge airspace? If Opus is showing me "Winds 234/24" at my destination airport, will I get the same exact wind information by calling PilotEdge ATC at the destination airport?[/b]

2) What happens to my Wind information coming from Opus, if I've decided to customize my Wind data using the Opus Engine while flying through PilotEdge airspace? At this level, how can PilotEdge know anything about the winds being blown around in my simulator, unless it can read data coming from my simulator environment. Shouldn't I get completely different wind information when calling PilotEdge ATC in this case?

The assumption here, is that not all PilotEdge users will also be OpusFSX users (...REX users, etc.). So, if PilotEdge users are flying with differing weather models in their respective flight simulator environments, how do PilotEdge controllers handle such situations. The other questions have to do with AI visibility for the third-party weather engine user who also uses PilotEdge.

3) If Opus generates a "partial" cloud cover condition that places the base of the clouds at say, 700 feet agl, and I'm shooting a precision approach into an airport with other PilotEdge users who are operating in bright and sunny VFR conditions with no overcast above the airport for them, will I still see their PilotEdge generated AI aircraft in the pattern once I arrive at the 700 foot level punching down through "partial" cloud cover? In other words, how does PilotEdge render other AI traffic as seen on the screen of those using third-party Weather Engines such as OpusFSX?

I'm trying to work this out so that I know what to expect before getting started with PilotEdge.

Thanks.

PilotEdge controllers will furnish you with the current real world weather. Therefore, if your sim is pulling real world weather, then the conditions reported by our controllers should be in sync with what you're seeing in the sim, by pure coincidence.

Yes, if you alter your local weather (which would be fine for training purposes, that's the whole basis of most simulator training sessions, in fact, it's very rare to use real weather in a structure training environment), then PE ATC won't be in sync. In those cases, your best bet is to inform the controller that you "have the numbers" when you call for taxi, or check in with the final approach controller. Otherwise, they're going to read the real world weather to you, and it's not going to be relevant to your sim.

We could technically extract that data from your sim (in some cases) and have the controller read that out, but that has its own drawbacks and we're not going to do that.

So, the answer is simple...PilotEdge controllers read the real world weather conditions, period.

When we indicate in our flightplan notes that we are simulating adverse weather at our end, does it get noticed by the controllers when they see the flight plan? I am almost always testing something new or atypical so I regularly post notes (so controllers know I'm not ignoring them, just distracted by some new toy or app).

How much do the notes get taken into consideration on a flightplan?

Yes, we see them if we drill down into the detail level on the strip. There aren't too many occasions to do that, though. That doesn't stop us from reading the weather out, though, unless you point out verbally that you have the numbers. Otherwise, we end up with recordings where PE looks like it's dropping the ball by not issuing the weather to arriving aircraft.

Naw, that's all good to read the weather. I usually use real-weather just because SoCal's weather is already so diverse (at least compared to Arizona's).

So requesting a specific tec route in the notes field doesn't work well?

The TEC route you're going to get is set in stone. If you'd like to FILE a specific TEC route, go for it, that saves us some time. However, putting the TEC code in the remarks doesn't do much either way.

The one time we do drill down into the strip is during the clearance delivery phase, so that's when we're most likely to see the remarks. Once you're enroute, the likelihood of the enroute controllers seeing the remarks is reduced, depending on their controlling technique.

So when I file I post the enroute waypoints for the tec route, and list the tec route name in the comments. Should I be inserting the name of the tec route in the ENROUTE field instead of waypoints? If I am trying to request a specific departure or tec route?

You can file the entire route (most helpful since we don't have a route processing system, unlike the FAA) with a note in the remarks as to which TEC route ID that represents, or you can just file the TEC route ID as the route itself.

Bear in mind, there is no "TEC route which you'd like to fly." There is only ever ONE applicable TEC route for the aircraft classification and current weather conditions enroute (ie, the route selection is often affected by LAX and SNA direction of operations).

" or you can just file the TEC route ID as the route itself"
That I'll have to try. Does it reduce the readback when I call for clearance?


"There is only ever ONE applicable TEC route"
To be more specific; TEC routes, approaches, departures. Essentially I am trying to file a flight plan so complete that the controller just says "as filed". Can you file for specific departure, tec route, and approach by entering them into the ENROUTE line?

A controller will never say "as filed" for the routing if it includes a SID. The SID _must_ be stated by the controller.

As long as you file the TEC route (either the code or the full route), you're going to get a pretty short clearance from the controller. There are some local IFR departure instructions which can't be entered into the route anyway, such as the one at SMO: "after departure fly runway heading until crossing the LAX 315 radial, then turn right heading 250 without delay, radar vectors Santa Monica..."

Just file the TEC route (either the full route or the code) and you're doing great.