Unless I opt to hang a bit more decorative CV990 related wall paper here (dunno if I'll bother though) .... the following report may conclude all I want, and need, to say in relation to this project.
"SOME OF" of what's recommended below is practiceable using our currently downloadable CV990 FDE's (as appalling as these may be) .... BUT .... not entirely practiceable without the "NEW/IMPROVED" data which is yet to be released. Although these revised FDE's aren't yet publicly available there's no harm relating "a little" in regard to what's been refined .... therefore consider this information as "a preview in another form"
.
As mentioned within the above/first presentation we've now got these simulations performing "a little more" like they should .... certainly more sensibly than was previously the case .... although it always pays to bear in mind the best of anything we offer should be interpreted as "an approximation only", simply because FS (both 2004 and FSX) "can't" replicate the technical and physical aspects of R/W aviation with absolute precision (we can close to actual performances, but, absolute fidelity is outside the practicalities of the FS platforms we represent). Bearing this in mind though the latest CV990 FDE and handling conclusions we've arrived at, based on the best/most reliable reference data we can source (including an old AOM publication), are "SUPERIOR" to the data that's currently publicly downloadable here
What follows is another quick appraisal of this project, some clarifications, as well as suggestions and recommendations for flying these "revised" CV990 simulations to best advantage .... once again based on revised data and our past 2 months of testing (remember this's an FDE update only and not a 3D model, panel/gauges, texture, effects, or audio revision). Some people will do what they want irrespective of whatever we recommend (OH WELL .... we do "TRY" you know), but, everything recommended by us is based upon our own experience and intimate knowledge of what we compile given we best understand the components of everything associated with the simulations we offer
This's the basic project .... the liveries for each variation of aircraft being clearly categorized within the "CV990" section of our following-linked "CONVAIR 880/990 TEXTURE INVENTORY" ....
tonymadgehjg.proboards.com/thread/6299/hjg-cv880-cv990-texture-inventoryCV990 30-5 AMERICAN AIRLINES configuration (initial production/pre-modification version)CV990 30-6 SWISSAIR configuration (initial production/pre modification version)CV990-A 30-5 AMERICAN AIRLINES and APSA configuration (post production/modified version)CV990-A 30-6 SWISSAIR and APSA configuration (post production/modified version)CV990-A 30-8 VARIG. GARUDA, and NASA configuration (post production/modified version)Although these aircraft are referred to as airline specific configurations (with their accompanying official series nomenclature) most later went on to fly with other carriers whilst retaining the configuration references of their original operators .... a similar, but different, system to that employed by BOEING being applicable to the nomenclature of these aircraft.
Two only "V3" base pack files will continue being offered .... one for the CV990 and one for the CV990-A (as is currently and has always been the case). Each of these two base pack files will contain separate "Aircraft Base Pack's" for each corresponding sub type .... two for the CV990's and and three for the CV990-A's .... all'n'all a very, Very, "VERY EASY" system made easier by equally simple and easy to understand documentation.
In reality there were a number noticeable physical differences between initial production and modified CV990 versions, but, it's unlikely we'll be able to produce the latter .... within the foreseeable future. The physical features of our current 3D model tend to favor the original aircraft version. However .... what also stands these aircraft apart, and what "WE CAN AND HAVE" successfully achieved, is in relation updating these simulations in accordance with their correct weights, engine thrust, and fuel capacities (range) .... each of which, supported by "a number of" edited FDE parameters, result in "varying performances" between each version .... particularly in regard to airspeed as is evidenced per the following images ....
CV990 30-5 at sustained MACH 0.87 (virtual FL310 ).... CV990 30-6 at sustained MACH 0.88 (virtual FL310) .... CV990-A 30-5 at sustained MACH 0.95 (virtual FL310) .... CV990-A 30-6 & CV990A 30-8 at sustained MACH 0.96 (virtual FL310) .... there's a significant weight variation between both of these types resulting in similar performance indications ....
Should one really want to go
"BALLS TO THE WALL" each simulation is capable of slightly faster performance than is evident within the above imagery (especially following fuel burn-off during virtual flights of any prolonged duration) .... but .... the way I establish these recommended maximum airspeed performances is to set engine N1 and N2 RPM indications within about 1% of each other (N2's being the higher indication) .... and then accept the resulting performance which is also assisted by other applied FDE manipulations. How these power settings and other manipulations each conspire to impact F/F indications for the stated performances will be your surprise to have fun with later
.
"At/Near MGW" expect the T/O roll for each of these CV990's to be quite lengthy. The cited RWY/field requirement for CV990's (again "at MGW" only) is referenced as being some 9,800 FT .... subject to airport altitude, air temperature, and all of the usual dictating variables. "At MGW" .... these simulations are now demonstrating this performance quite well (remember MGW checks form the basis of our own pre-release flight testing and recommended procedures). The performance of any of our simulations improves progressively with corresponding weight reduction/s. All of our simulations load into FS with 100% fuel and payload .... not a set standard/common fuel/payload combination and which is only good for a particular virtual flight. This preference, of ours, always results in a nominal overload .... just as as should be the case. We "DO NOT EVER" assign weight in order to dictate handling and feel though. Using the FS based Fuel & Payload Adjustment facility (or aided by our flying guides) the end user is expected to reduce fuel or payload, or both, in accordance with the specific requirements of their intended virtual flight. The way we compile these/all of our simulations promotes better/more accurate flight planning .... for those whom favor doing such.
Ranging from the lightest to heaviest CV990 variants T/O V-REF (again "at MGW") is higher in comparison with that for B707's and DC-8's. Setting an engine N2 RPM minimum of 98.5%, FLAPS 27, and applying 5 units of Elevator Trim setting, I've calculated the T/O V-REF for our CV990 simulations to be in the vicinity of the following data (based on references available to us) .... given a little bit of tolerance here'n'there
....
V1 = 156 KIAS
VR = 166 KIAS
V2 = 180 KIAS
V1 = 158 KIAS
VR = 168 KIAS
V2 = 180 KIAS
T/O rotation axis/AI attitude should never exceed +7*.
The initial ROC should never be set less, or in excess of, 2,000 FPM using an engine N2 minimum of 98.5% and with FLAPS 27 extended. For these simulations maximum engine thrust, at SL, is N2 102.6% .... but if applied (procedures at some airports, at some places around the world, do require a "full power T/O"), then, power should be reduced to the engine 98.5% N2 minimum passing through 1,000 FT, after T/O, and prior commencing flap retraction .... or one might still find oneself over-accelerating and then ascending like the Space Shuttle, but, not as badly as previously
My new flying guide/s, specifically tailored for each version of these CV990 simulations, will aid good performance/s. The designed procedures have been "PROVEN" to work provided they're correctly implemented .... difficult at first (maybe), but, "A PIECE OF PISS" subject to sufficient experience gained
For each CV990 variant the post T/O climb out and clean up procedures are now in accordance with the following recommendations ....
- INITIAL CLIMB RATE = 2,000 FPM
- FLAP 27* RETRACT = 220 KIAS .... increase ROC to 2,500 FPM
- FLAP 10* RETRACT = 240 KIAS .... increase ROC to 3,200 FPM .... set climb thrust (reduce engine thrust to between 90.6% and 90.5 N2/RPM depending on CV990 weight version) and assume the following climb procedure whilst also ensuring the AI pitch attitude never exceeds +10* (+11* at the very most and only once "clean") .... or one will risk plummeting to the virtual tierra firma (stalling) with a decent "THUMP"
Getting the entire post T/O and climb out procedure right and from TO (as prescribed above) is "essential" in order to ensure airspeed doesn't increase beyond 250 KIAS below 10,000 FT following flap retraction. These CV990 simulations will only over-perform if one allows them to do so. Again getting the ROC correct, and managing power properly, is "critical" in order to realize desirable performance.
The AI pitch attitude will progressively reduce with acceleration.
A typical climb to cruising altitude (virtual FL310) is now in accordance with the following recommendations ....
- Maintain 3,200 FPM ROC until 10,000 FT - maintain approx 90.6 to 90.7 % N2 RPM
- 10,000 FT reduce ROC to 2,500 FPM - maintain approx 90.5 to 90.6 % N2 RPM
- 15,000 FT reduce ROC to 2,000 FPM - maintain approx 90.5 to 90.6 % N2 RPM
- 20,000 FT reduce ROC to 1,500 FPM - maintain approx 90.5 to 90.6 % N2 RPM
- 25,000 FT reduce ROC to 1,000 FPM - maintain approx 90.5 to 90.6 % N2 RPM
- 27,000 FT reduce ROC to 800 FPM - maintain approx 90.5 to 90.6 % N2 RPM
- 29,000 FT reduce ROC to 500 FPM - maintain approx 90.5 to 90.5 % N2 RPM
- 30,000 FT reduce ROC to 250 FPM - maintain approx 90.4 to 90.4 % N2 RPM
- 31,000 FT ALT CAPTURE - maintain approx 89.3 to 90.2 % N2 RPM
PLEASE NOTE: Actual engine N2 RPM settings during climb will once again vary in accordance with CV990 weight version). This information is stated "with precision" within the new CV990 Basic Flying Guide .... once it's released) ....
The above procedure/s guarantee good climb and airspeed performance/s .... from T/O .... all the way up to cruising altitude .... and without the over-performance/over-acceleration that previously flawed these CV990 simulations.
Once again also .... the above recommended procedures aren't guaranteed to work using the current publicly downloadable CV990 FDE's. All of the above described procedures are based on the new and yet to be released data.
Getting back down again requires the following recommend procedure ....
- 110 DME reduce engine power to N2/RPM 80% .... maintain level flight to bleed airspeed below 350 KIAS.
- 100 DME reduce engine power to N2/RPM 70% .... commence 2,500 FPM ROD not in excess of 350 KIAS.
- 20,000 FT reduce engine power to N2/RPM 65% .... maintain 2,500 FPM ROD not in excess of 350 KIAS.
- 17,500 FT DME .... reset QNH/altimeter barometric pressure setting (2991 or as required).
- 15,000 FT reduce engine power to flight idle (N2/RPM 60%) .... maintain 2,500 FPM ROD .... reducing airspeed toward 250 KIAS.
- 10,000 FT reduce ROD .... 1,000 FPM ROD .... and reduce airspeed toward/below 250 KIAS.
Do not attempt any approach to landing with in excess of 20% total fuel remaining .... doing so will adversely influence the approach to landing AI pitch attitude.
Flying an extended approach/center line of between 18 and 20 DME is also advantageous/recommended .... simply in the interest of stabilizing these simulations on the ILS/GS at the earliest opportunity.
- Downwind legue .... select FLAP 10 at 240 KIAS .... reduce airspeed toward 220 KIAS .... maintain level flight.
- Base legue ... select FLAP 27 and reduce airspeed at 220 KIAS .... reduce airspeed toward 200 KTS .... maintaining level flight.
- Final approach legue .... reduce airspeed toward 185 KIAS .... maintain level flight.
- ILS/GS intercept .... 185 KIAS
- Select gear down 180 KIAS .... reduce engine thrust .... reduce airspeed toward 149 to 144 KIAS.
- Select FLAP 36 at 170 KIAS .... reducing toward 149 to 144 KIAS.
- Select FLAP 50/FULL FLAPS at 160 KIAS .... reduce airspeed toward 149 to 144 KIAS.
- Final approach to landing airspeed with full flaps and gear down .... 149-144 KIAS.
- Disengage AP at 100 FT .... prior to landing.
- Retard engine thrust to idle at 50 FT .... prior to landing.
- Commence +5* flair to landing at 20 FT .... prior to landing.
- Landing speed - approx 129 to 124 KIAS.
- Deploy wing spoilers immediately upon main gear ground contact.
- Engage reverse thrust upon ground contact.
- Derotate to land nose gear.
- 80-60 KTS cancel reverse thrust.
- Retract wing spoilers.
- Retract flaps.
- Taxi to gate/ramp.
Again also .... the actual Landing V-REF will vary in accordance with CV990 weight version too, but, what's prescribed for each simulation "DOES" work very well .... "if properly/correctly implemented".
As is the case with all of our simulations good planning and adherence to the recommended procedures is rewarding .... despite the obvious learning curve this may temporarily impose. What we recommend is intended to aid adaption to that learning curve though and is for the ultimate benefit of end user enjoyment
Another detail we've noted using the "NEW" FDE is engine startups are now "VERY SMOOTH" .... no more surging at the point of startup ignition/combustion. The current (albeit FS2004 only customized CV990 sound pack) also appears to be running somewhat more smoothly too. At the moment no further audio upgrading or extensions are planned, but, we'll see what transpires later.
One final detail/recommendation and which is applicable to both our currently downloadable and yet to be released CV990 simulations concerns main panel to external scenery horizon line view perspectives as follows ....
The following image presents the default main panel to external scenery horizon line view and which is quite good with no further adjustment/s being necessary or recommended ....
As these are 2D panels though by the time one reaches cruising altitude the perspective of this default main panel to exterior scenery view alters considerably (the horizon line recedes naturally) to appear as follows ....
It's therefore recommended that SHIFT+ENTER key board commands (FS2004 only .... although these panels "ARE" FSX portable too the panel view adjustment keys for this FS version are different) be selected "ONCE ONLY" to reset this view as follows ....
.... or selected "TWICE ONLY" to reset this view as follows ....
.... or even selected "THRICE ONLY" to reset this view as follows ....
The4 view preference and adjustment is "entirely up to the end user"
These panel/scenery/horizon view adjustments can be applied from approximately 10,000 FT during any climb to cruising altitude. After implementing these adjustments one must also remember to reset the original default view perspectives again and per SHIFT+BACK SPACE (FS2004) key board commands an in accordance with the same increment/s of adjustment/s for a desirable landing view .... and which can be applied from approximately 20,000FT during any descent. Failure to do this will result in an improper/exaggerated view perspective (way too much foreground being visible) by the time one flies the approach to landing and after the actual landing.
The following image presents the correctly readjusted default main panel to exterior scenery horizon line view during the approach to landing ....
The following image presents default view during a +3 degree flare prior to landing. The loss of RWY visibility is only momentary .... this's perfectly normal due to the elevated nose axis ....
The following image presents the correctly readjusted default main panel to exterior scenery horizon line view after derotation and during roll out after landing .... and which approximates that of the very first RWY image above
Adjusting the panel scenery horizon line perspective per CFG.FILE adjustment/s "IS NOT" encouraged.
Adjusting the panel scenery perspective view ZOOM FACTOR "IS NOT" encouraged either.
As I said at the very start of this presentation I can't think of anything more to add (for the moment) .... unless I decide to publish more CV990 wall paper for decorative, in as much as for teasing, purposes although I doubt I'll be arsed doing so
Mark C
AKL/NZ