New member - some questions
Posted: Sun Dec 16, 2012 6:06 pm
Hello,
I just joined recently and have a couple questions.
1. If I understand correctly, we're free to use our own weather engines while flying in PilotEdge. However, does this mean we can set up our weather to be perfectly calm, clear and sunny, even though in the real world there might be strong winds, overcast skies, and a torrential downpour at the moment? Can we fly VFR in PilotEdge even though the conditions may be IFR in the real world? Or how about slightly less extreme - let's say they're VFR, but the winds are a bit strong - can I set up the wind to be calm in my sim?
2. Since everyone uses their own weather engine, the ATIS code that one pilot hears in their sim will be different than the one I hear in mine. Do controllers simply ignore the ATIS code I give them? However, I should give them the code anyway so they know I have the weather, right? (Also, are there plans to have some sort of a centralized system in the future so our ATIS codes are consistent?)
3. Are there any rules about pausing or disconnecting mid-flight?
4. I'm aware that in the real world, pretty much the only purpose in filing a VFR flight plan is so that they start looking for you if they haven't heard from you within a certain time. Is there any purpose in filing a VFR flight plan in PilotEdge? Are we encouraged/discouraged from doing so?
5. This one is a bit longer - it's about a rather strange experience I had during my first real attempt at a flight today:
I took off from Mojave (MHV), intending to make a short 20-mile trip to General Fox (WJF). I intended for this to be a fairly straightforward flight, just to get myself familiar with the service, talking to controllers, etc. I practiced the flight on my own first, before connecting to PilotEdge, and it went smoothly. I tried it on PilotEdge, and oddly enough, after taking off from Mojave and climbing about 1,000 feet, my engine failed. What's strange is I didn't configure any failures to occur in my sim (FSX) -- and I've never had this or any kind of failure happen unexpectedly, unless I've specifically configured it to occur. I briefly considered whether I should declare an emergency to ATC, or attempt to turn back and make an emergency landing - but I decided this wasn't the purpose of the flight at all, and I wasn't even sure if this kind of thing is allowed in PilotEdge, so I just disconnected.
The cause of the unexpected engine failure is a complete mystery to me. There aren't any settings in the PilotEdge client related to system failures, are there? I didn't find any by looking through the options or searching online, so I have no reason to believe PilotEdge is to blame. It's just really strange - I didn't do anything differently between my practice flight and my actual flight using PilotEdge. It's possible that my weather engine (REX) may have had something to do with it. I've had cases before where REX would have no wind at one altitude, then suddenly 25-knot winds at another altitude, with no smooth transition in between, which caused me to stall unexpectedly - but never an actual engine failure. But anyways - should something like this happen again, are we allowed to practice actual emergency procedures, including off-field landings, in PilotEdge?
That's all I have. Looking forward to flying in PilotEdge - it promises to be a great tool for practicing cross-country flight planning and communicating with ATC. Hopefully, my future experiences won't be quite as terrifying as today's flight!
I just joined recently and have a couple questions.
1. If I understand correctly, we're free to use our own weather engines while flying in PilotEdge. However, does this mean we can set up our weather to be perfectly calm, clear and sunny, even though in the real world there might be strong winds, overcast skies, and a torrential downpour at the moment? Can we fly VFR in PilotEdge even though the conditions may be IFR in the real world? Or how about slightly less extreme - let's say they're VFR, but the winds are a bit strong - can I set up the wind to be calm in my sim?
2. Since everyone uses their own weather engine, the ATIS code that one pilot hears in their sim will be different than the one I hear in mine. Do controllers simply ignore the ATIS code I give them? However, I should give them the code anyway so they know I have the weather, right? (Also, are there plans to have some sort of a centralized system in the future so our ATIS codes are consistent?)
3. Are there any rules about pausing or disconnecting mid-flight?
4. I'm aware that in the real world, pretty much the only purpose in filing a VFR flight plan is so that they start looking for you if they haven't heard from you within a certain time. Is there any purpose in filing a VFR flight plan in PilotEdge? Are we encouraged/discouraged from doing so?
5. This one is a bit longer - it's about a rather strange experience I had during my first real attempt at a flight today:
I took off from Mojave (MHV), intending to make a short 20-mile trip to General Fox (WJF). I intended for this to be a fairly straightforward flight, just to get myself familiar with the service, talking to controllers, etc. I practiced the flight on my own first, before connecting to PilotEdge, and it went smoothly. I tried it on PilotEdge, and oddly enough, after taking off from Mojave and climbing about 1,000 feet, my engine failed. What's strange is I didn't configure any failures to occur in my sim (FSX) -- and I've never had this or any kind of failure happen unexpectedly, unless I've specifically configured it to occur. I briefly considered whether I should declare an emergency to ATC, or attempt to turn back and make an emergency landing - but I decided this wasn't the purpose of the flight at all, and I wasn't even sure if this kind of thing is allowed in PilotEdge, so I just disconnected.
The cause of the unexpected engine failure is a complete mystery to me. There aren't any settings in the PilotEdge client related to system failures, are there? I didn't find any by looking through the options or searching online, so I have no reason to believe PilotEdge is to blame. It's just really strange - I didn't do anything differently between my practice flight and my actual flight using PilotEdge. It's possible that my weather engine (REX) may have had something to do with it. I've had cases before where REX would have no wind at one altitude, then suddenly 25-knot winds at another altitude, with no smooth transition in between, which caused me to stall unexpectedly - but never an actual engine failure. But anyways - should something like this happen again, are we allowed to practice actual emergency procedures, including off-field landings, in PilotEdge?
That's all I have. Looking forward to flying in PilotEdge - it promises to be a great tool for practicing cross-country flight planning and communicating with ATC. Hopefully, my future experiences won't be quite as terrifying as today's flight!