FSX Piper Warrior II PA28-161

Piper Warrior II PA28-161 Version for FSX with SP2. A Gmax model that features animations, virtual cockpit with semi-transparent yoke, doors that open, two different size 2D panels, versions with and without wheel fairings and more. The PH-SVG is owned by the Rotterdam Flying Club. By Rien Cornelissen.

​This is Warriorc.zip for FS X with SP 2 which, of course, has many features of the Pipers for FS 2004 and FSX-SP2 that were released already.

Installation: unzip Warriorc.zip to your Microsoft Flight Simulator X folder. Make sure the option "use directories" is active, (it usually is) for the directory structure is contained within the .zipfile.

The textures are dxt mipmapped .dds files. The exterior model contains LOD's: Levels-Of-Dilution; when the aircraft gets more remote, less detail is shown, requiring less processing time.
I made LOD 400, 150, 50, 15 and 5. In LOD 400 everything is present; in LOD 5 there are only flat, unanimated and untextured silhouette of fuselage, wings and tail.

The model with animations was made using GMax and the FS X-SP2 sdk. Many parts could be borrowed from other members I made of the Piper family for FS 2004 and FS X-SP2.

In the virtual cockpit I left out the pilot and the head rests of the front seats, in order to facilitate looking around.
Also, the yoke is semi-transparent in the vc.

The door will open using . First the door latch will open together with the storm window, a small window within
the window directly to the pilot's left, and then the door itself.
The bagage door will open by , followed bij <2>. The ribbon to keep this door in the open position
is represented too.

The gear has suspension, as can be seen when moving on uneven ground. The wheels will spin while taxiing.

Like in the real Warrior the trim surface at the trailing end of the elevator wil move extra as the elevator is moved.

Choices can be made between Warriors with a '16x9' and a '4x3' panel, and with or without the wheel fairings installed.
The '16x9' panel is for wide screen monitors.

Without fairings the aircraft will be about 5 kt slower.

The gauges that are specific to the Warrior were made in xml.

The directional gyro has the usual random drift, but I added an extra drift in steep turns; its absolute value is proportional
to the rate-of-turn-squared. The gyro can be reset pressing the key, but also, more realistically, by turning the knob using the mouse.

The subscale of the altimeter was changed to read both hPa (=mBar) and inches of mercury. The tanks will contain 25 Gal. each, and the fuel gauges will indicate "full" at that amount.

The annunciator panel is functional, as is the audio panel, on which sound of markers, nav 1 and 2, and ADF can be switched on and off.
The cockpit light and the navlights are toggled by left clicking the thumb wheel directly to the left left of the main power switch.
When turning the thumb wheel in the real PA28T, there will first be a click switching the nav lights on, and the rest of the travel it will be a rheostat for the cockpit panel light.

The instruments were put in place using FS Panel Studio.

About the P-effect:

I placed the engine slightly to the right of the midline in the flight dynamics to simulate the P-factor:

In the real aircraft the propeller turns clockwise as seen from the pilot's seat.
Therefore, the propwash will take a spiraling trajectory along the fuselage. It will collide with the vertical fin, pushing it to the right,
thus causing the aircraft to turn left.
Moreover, a propeller blade that goes down will generate more thrust than one going upward because the former will have a higher speed
with respect to the air and will have a larger angle-of-attack, caused by the propeller axis being more pitch-up than the aircraft path.
This, too, adds to a tendency to turn left.

This so-called P-factor is compensated for cruise speed in the Cessna 172 with a bent strip of metal at the trailing end of the rudder;
in the Arrow by the rudder trim, but the degree of correction will depend upon airspeed.
In situations in which engine power is high with respect to airspeed (takeoff, climb, recovery from stall)
the pilot has to apply "right rudder".

This is the case in almost all single engine propeller aircraft; most engines (but not all) turn clockwise.

The P-factor adds to realism, but there are a few prerequisites:

1. The simpilot must have rudder pedals.
2. The pedal mechanism should have no mechanical play: its potentiometer should exactly follow the feet's movements.
3. In the settings menu the null zone for the rudder pedals must be set to zero. If the software that comes with the
pedals allows for a null zone, it should be set to zero too.

Still, if you don't like the P-factor, open aircraft.cfg, find

[GeneralEngineData]
engine_type= 0
Engine.0= 4.000, 0.800, 0.000
fuel_flow_scalar= 1.000
min_throttle_limit=0.000000

and change it to read

[GeneralEngineData]
engine_type= 0
Engine.0= 4.000, 0.000, 0.000
fuel_flow_scalar= 1.000
min_throttle_limit=0.000000

which will place the engine in the midline.

The real Piper Warrior-II PH-SVG is owned by the Rotterdam Flying Club in the Netherlands of which I am a member,
being a private-pilot-with-an-instrument-rating. I use this computer model to help me stay current. From time to time, from all over the world I am getting mail from (student) pilots using it to the same purpose.

All of my files are public domain; you are allowed to do with them whatever you please without permission,
though I do appreciate to be notified of major changes.

For those that are interested the model and gauge source codes are available at my email address.

Rien Cornelissen

Adam McEnroe

Adam McEnroe is a flight sim enthusiast who has been simming since the days of FS95. Adam writes all of the download section editorials after testing each of the files. Adam has extensive knowledge using various flight simulator packages and thoroughly tests the files before writing about them. Adam also like to fly real-world aircraft in his spare time and is training for his PPL.

Should you wish, you can contact Adam via email at adam@flyawaysimulation.com.

Leave a comment