Leaderboard

Starting Jul 17, San Francisco International Airport (KSFO) will be added as a supported airport on PilotEdge. This will be supported for at least the next 4 weeks, after which an announcement will be made regarding its operation. Limitations: The support for SFO includes the approach and enroute facilities required for flights to and from the existing coverage area (LAX, LAS, etc). It does not include any other airports in the Oakland Center area. Flights can be conducted from any airport within ZLA to/from SFO. Clearances will not be issued from SFO to airports outside of the ZLA coverage area (SEA, SLC, PHX, etc). Controllers have been specifically trained in the operation of SFO, and the SIDs/STARs associated with operations to/from ZLA, but nothing more. Why SFO? 1) one of our commercial customers has an operational requirement to utilize SFO. 2) we have been wanting to add support for at least one airport outside of the existing coverage area to allow for longer distance flights by existing customers, particularly those who operate transport category aircraft such as the Boeing 737. SFO is an extremely popular airport among simulator enthusiasts and Virtual Airline pilots. Support for SFO allows for legs such as SFO-LAX, SFO-SAN, SFO-LAS, SFO-LGB, SFO-SNA, SFO-ONT and more, along with the reverse legs. Why just SFO and not the rest of Norcal? We wanted to add this support without causing undue burden on existing controllers, or adding the need for additional staffing. The compromise was to select just one airport to facilitate longer distance flights, rather than opening an entire facility. How will this work? How will the recordings work? SFO, the relevant Norcal Approach sectors, and the relevant Oakland Center sectors will typically covered by the same person working the Los Angeles Center position, expect on specific occasions where additional staffing is provided. For the most part, all interactions involving SFO will be contained within the ZLA Radar recordings. What are the operating hours for SFO? Same as the core network hours, 8am-11pm PDT.

Would've been funny if people hadn't died....

This product will be for X-Plane 10 only.

Hey!!! I did two videos with X Plane and i hope you like them Swiss RJ100 Take Off with real sound in Zurich: Swiss A330 landing in Montreal: More to come

Lasers with sharks.

The X-Aviation CRJ is not supported in 64 bit X-Plane yet. This should be resolved very shortly, we're going through final prep work to get this update out to you ASAP. Thanks for your patience.

Carenado's new C340 II in TropicalSim's new Buenos Aires: Great plane at a good airport.

Tuning the flightmodel in XP to the level we are at requires; - Very good understanding of how XP works - Very good understanding of how the real world works - Access to very hard to get information of the aircraft and engine. - Have the knowledge to understand the documents and information you have - Access to the real aircraft and a full motion simulator - Programming skills, to make up for some of XP's inaccuracy's When you have all this it's time to start calibrating. You now know where you are, where you want to be, and have the tools to get there. Then it's basically a matter of callibrating everything IN THE RIGHT ORDER. If you don't, you will be running around in circles, like someone lost in the forrest. The key word here is reverse engineering and in sim testing. Offcourse, the average designer will enter ballpark numbers into PlaneMaker and airfoils etc, and the end result will in best case be a ballpark flightmodel. Garbage in = garbage out. Getting the 3D right is offcourse important, but then maybe 10% of the work is done. We offcourse expect some people to pick apart our planemaker model and airfoils etc and analyze them and maybe find some "strange" stuff there, but that will not get you very far unless you also have our code. It's the combination of the two that make up our flightmodel in the sim, so you will have to judge the aircraft from within the sim. M