Project FMC simplified for Project Airbus

[The320Pilot]

The PA A320 FD-FMC beta v0.80 works pretty good. And, finally, I have to retract the spoilers after touchdown, just like in real life! Now, I have two questions:

1. When can we expect the English manual? Please...
2. Is it possible to add the "Minimums" callout? And, perhaps, also the V1, Vr and V2 callouts?

Thanks!

[The320Pilot]

My wingtip lights do not work! Neither the red or green navigation lights, nor the strobe lights.

[wulfbindewald]

My wingtip lights do not work! Neither the red or green navigation lights, nor the strobe lights.

Just made a crosscheck examplary in the A320 CFM beta 0,8. The nav lights and callouts V1, VR, V2 are working well.

I recommend to delete the panel folder and to copy the beta 0,8 panel again and crosscheck the aircraft.cfg.
For safety reasons I have only used the new aircraft.cfg and added further aircraft repaints after to be sure it generally works.
Also I propose to crosscheck the effects+gauges files....

Does the callout prob remain after the crosschecks? Is the corresponding CALLOUT_FD folder included in the FSX/sound folder acc. to instructions?

Wulf

[The320Pilot]

My wingtip lights do not work! Neither the red or green navigation lights, nor the strobe lights.

Just made a crosscheck examplary in the A320 CFM beta 0,8. The nav lights and callouts V1, VR, V2 are working well.

I recommend to delete the panel folder and to copy the beta 0,8 panel again and crosscheck the aircraft.cfg.
For safety reasons I have only used the new aircraft.cfg and added further aircraft repaints after to be sure it generally works.
Also I propose to crosscheck the effects+gauges files....

Does the callout prob remain after the crosschecks? Is the corresponding CALLOUT_FD folder included in the FSX/sound folder acc. to instructions?

Wulf

I'll do that. Thanks!

[The320Pilot]

I have the following effects in the Effects folder:

fx_navgre320pa.fx
fx_navred320pa.fx
fx_navwhi320pa.fx (Note: the tail's white nav light works flawlessly.)
fx_strobe320pa.fx
fx_strobe2320pa.fx

And some others, but these are the ones I am probably interested in.

With regards to the callouts, I found the problem. I was using an old version of the CALLOUT_FD. I was missing everything but the callouts from 2500' to 10', the "ding" sound and the fuel low warning sound. Now, every callout works --except for the minimums one; it should be included with a .xml or something to attach the sound to the MDA or DH set for the approach.

[fdd_fr]

Hi,

I am sorry to change the panel files name, but I had to do that, for a better organisation, and for the next FMC's adaptation to the other aircrafts.

With the panel 0.80, you have the definitive organisation of the panel files and you must delete your old panel folder and use the new panel folder provided in the beta 0.80. And now, the FMC gauge files are grouped in a .CAB file,that must be placed in your fsx\Gauges\" folder.

You must use the Aircraft.cfg file provided with the beta 0.80, because some changes in the aircraft flight dynamics and the panel declaration change in the [FltSim.x] sections : (panel=A320CFM and Panel=A320IAE).

You must use the new panel.cfg files of the 0.80, because I renamed many files, to separate common files to all Aircraft FMC version and files that are dedicated to a specific version.

About the callout "Minimum", it works. If you it dosen't work on your computer, check if you have copied the all the files of the 0.80 panel and the panel.cfg file.

I will upload tonight, on my website, the last "Callout_FD" folder, and all the effects files used by the aircraft.


About the english translation of the aircraft manual, Sean works on it, but that requires many works (manual has more than 100 pages). When Sean will be completed the translation, I will publish the final version of the Aircraft of the AVSIM library.

The next airports, that I will upload next weekend will be :

- ELLX - Luxembourg
- OMDB - Dubai
- KGEG - Spokane ( in north Rocky Mountains) USA
- and maybe SPIM - Lima - Peru

Also, LSZH Zurich - Switzerland , to fix a bug in one STAR.

After, I will work on UUDD - Moscow (but I need a little time, because charts are complex), WMKK Kuala Lumpur and VHHH Hong Kong.

Francois

[fdd_fr]

You can download the "Callout_FD" sounds pack and the "Effects" pack used by my panels here : http://freenavdbgroup.com/?page_id=159


You must have in your Aircraft.cfg file the following [Lights] section (they are different for CFM and IARE, because CFM has Flex wings and wings lights are hard coded in the MDL file):

For the A320 CFM version :
[LIGHTS]
light.1=2, -69.70, 0.00, 4.70, fx_strobe2320pa ,
light.2=1, 6.8, 0.00, -5.80, fx_beacon320pa ,
light.3=1, 3.83, 0.00, 8.47, fx_beacon320pa ,
light.4=4, 46.50, 0.00, 3.00, fx_vclight , //cokpit Night ligthing
light.5=5, 11.570000, -10.48, -5.81, fx_PAland , // fdd = light.9=5, 12.00, -10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.6=5, 11.570000, 10.48, -5.81, fx_PAland , // fdd = light.10=5, 12.00, 10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.7=7, 49.25, -1.00, 2.90, fx_vclight , // VC day lighting by francois Dore

For the A320 IAE version :

[LIGHTS]
light.1=2, -69.70, 0.00, 4.70, fx_strobe2320pa ,
light.2=1, 6.8, 0.00, -5.80, fx_beacon320pa ,
light.3=1, 3.83, 0.00, 8.47, fx_beacon320pa ,
light.4=4, 47.00, 0.00, 3.00, fx_vclight , //cokpit Night ligthing
light.5=5, 11.570000, -10.48, -5.81, fx_PAland , // fdd = light.9=5, 12.00, -10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.6=5, 11.570000, 10.48, -5.81, fx_PAland , // fdd = light.10=5, 12.00, 10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.7=7, 49.25, -1.00, 2.90, fx_vclight , // VC day lighting by francois Dore
light.8=3, -13.70, -55.25, 2.45, fx_navred320pa //-13.90, -55.25, 2.45, fx_navred320pa
light.9=3, -13.70, 55.25, 2.45, fx_navgre320pa //-13.90, 55.25, 2.45, fx_navgre320pa
light.10=2, -13.95, -55.25, 2.45, fx_strobe320pa
light.11=2, -13.95, 55.25, 2.45, fx_strobe320pa

For the effets, they are the same for 2 version :

[EFFECTS]
wake=fx_wake
water=fx_spray
dirt=fx_tchdrt
concrete=fx_sparks
touchdown=fx_tchdwn,1
enginefire=fx_engFire
startup=fx_engstrt
EngineDamage=fx_engsmoke
WheelWetSpray=fx_wheelwetspray
WheelSnowSpray=fx_wheelsnowspray
windshield_rain_effect_available = 1
SnowEngineWash=fx_SnowEngineWash
WetEngineWash=fx_WetEngineWash

Francois

[The320Pilot]

Still my lights do not work.

EDIT: I haven't downloaded the Effects package yet. Will try again to see if the lights work.

[fdd_fr]

That's work ?

Today, 3 new airports and one update :

http://freenavdbgroup.com/

- ELLX - Luxembourg (realised by Jean-Pierre Varnier
- KGEG - Spokane Intl - USA (Washington) fully compatible with FTX/ORBX NRM Scenery
- OMDB - Dubai Intl - United Arab Emirates - fully compatible with Fly tampa Addon Scenery


Airports Updated :

- LSZH - Zurich - Switzerland (by Jean-Pierre varnier) V 4.01 (STAR and Approaches fix)

AIRAC updated : version 01242015

Francois

[wulfbindewald]

Hi Francois,

some feedback for Your attention:

FD_FMC airports pack V4 01242015 feedback regarding CYYJ and KJAC STARs

-- CYYJ - formal correction request


-- KJAC - the descent phase 300 to 220 knts from the selected star is too abrupt and an earlier speed reduction to 220 or 250 might be helpfull for the following steeper approach phase. Otherwise major spoiler use is nec. The altitude steps are ok. TOD manual corrections due to shorter hops <200nm are already regarded in advance and not the driving issue.


-- Panel A320 beta 0,8 - In the shortened checklist Information area of the upper ECAM there is a QNH-to-press-button indication too.
Shortly before (AUTO / ILS) landing the QNH button must be pressed....ok, but the indication is flickering and does not show this and remains red due to an internal conflict.

Wulf

[fdd_fr]

Hi Wulf,

Thanks for your report.

I will fix CYYJ runway name, and I will add a decelerate step for KJAC STAR.


About the QNH button, it is not a gauge bug. Sometimes, i have the same problem, and I think that is a bug from external weather software. I don't know which weather soft you use, but I use Active Sky 2012, and sometimes during STAR and approaches, QNH value changes every seconds for just a little decimal and I have to push the button often. I think that it is because the weather engine receive QNH data from several closest stations, with a little difference in the QNH value (minus than one millibar) . That's requires to push the button several times. But generally, this phenomenon disappears when you approach of the airport.

As QNH changes are very small, you can adjust your QNH just before landing, when your are in final approach, because, if the QNH value change of 1 millibar, the QNH reading becomes red.

I can add a tolerance area in QNH value check, but I am afraid that occurs problems whit autolanding.

But I can say that is not a gauge bug.

Weathe engines have many bugs (Active SKY); If you do several flight without quit and launch again Active SKY, weather will be false and data will be not updated. For each flight, I must qui and launch again Active Sky.

Regards

François

[fdd_fr]

I will post next saturday the fixed CYYJ and KJAC, because I have began WMKK Kuala Lumpur and it is a huge Airport, with many procedures and I proceed some final settings on the FMC on the model PA A330-300 and I hope post a video with it.

[Airbus Fan]

Just a question about an a330.. Will it have same looking FMC as in a32x? Or a realistic one? ( I don't care that much how it looks, it's good if it does what it's function).

[fdd_fr]

It is the same. I adapt only the logic and the code for the A330 performances. I have many difficulties with the Gravity center (according the fuel quantity) , but I have found solutions to many problems this last weekend.

I had to find new calculation to set N1 thrust, Flex to Temp, and pitch control during climb and descent. I work seriously on it since 3 weeks. And first the first time, this weekend, I have completed a perfect flight (ELLX to OMDB).

With the A330, it will be necessary to set the trim between +1.5 to +2.5, according your take-off weight, before take-off.

As the A330 original VC is not yet ready, I use the A321 VC model, but I have edited the MDL file to change the position of the VC in the aircraft (because A330 is very more longer than A321), to be at the right place.
That's works, but it is a little too high, but good location in the lenght. This is because MDLconvertX can change the relative position of a VC, but in the 2 direction with ony the same coefficient. So, to set the VC at the right place in the front, It is a little to high.

I will post a video during this week.

Francois

[Henrique]

Hello!
First, Thank´s for your project. All your hard work, for free, it´s something not normal this days...
Second, I would like to know, if the A330 FMC can it work on Thomas ruth A330/40 vc.
Thanks in advance

[fdd_fr]

Hi Henrique,

Yes, It can works, but for use the Tom Ruth's VC, I must change all the gauges code, because his VC has not the same coordinates areas (dispalys, button, switches) that the MS A321 VC. Possible, but requires many work because all the XML code must be adapted. And I think that his VC has an overhead with no all functions (bleeds, hydrualics, ADIRS...).

In this case, the most simply solution is to use my adapation of the MS FSX A321 VC; In this case, there si only to change the aircraft.cfg file data and the AIR file.

Francois

[Henrique]

Thank´s for the quick answer.
So maybe i´ll wait for the PA vc.

[fdd_fr]

I will try to post a video tonight of the PA A330-300 with FD-FMC and the A321 VC merge.

[fdd_fr]

Test of FD-FMC with modified A321VC on the Project Airbus A330-300 model in video :

First video : Startup engines and systems initialisation : PA 330-300 beta test FD-FMC HD video

Excuse me for the head movement, but I test in the same time the Track IR and I have some difficulties

Next video will be take-off and inital climb

[fdd_fr]

next :

PA 330-300 beta test FD-FMC HD video Part 2 : Take-off and initial climb

You can see, just after take-off that the aircraft go up too. I have to improve the code during the first segment of the climb, when the aircraft is in SRS mode and has to capture the 15° of initial climb angle.

[The320Pilot]

You can download the "Callout_FD" sounds pack and the "Effects" pack used by my panels here : http://freenavdbgroup.com/?page_id=159


You must have in your Aircraft.cfg file the following [Lights] section (they are different for CFM and IARE, because CFM has Flex wings and wings lights are hard coded in the MDL file):

For the A320 CFM version :
[LIGHTS]
light.1=2, -69.70, 0.00, 4.70, fx_strobe2320pa ,
light.2=1, 6.8, 0.00, -5.80, fx_beacon320pa ,
light.3=1, 3.83, 0.00, 8.47, fx_beacon320pa ,
light.4=4, 46.50, 0.00, 3.00, fx_vclight , //cokpit Night ligthing
light.5=5, 11.570000, -10.48, -5.81, fx_PAland , // fdd = light.9=5, 12.00, -10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.6=5, 11.570000, 10.48, -5.81, fx_PAland , // fdd = light.10=5, 12.00, 10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.7=7, 49.25, -1.00, 2.90, fx_vclight , // VC day lighting by francois Dore

For the A320 IAE version :

[LIGHTS]
light.1=2, -69.70, 0.00, 4.70, fx_strobe2320pa ,
light.2=1, 6.8, 0.00, -5.80, fx_beacon320pa ,
light.3=1, 3.83, 0.00, 8.47, fx_beacon320pa ,
light.4=4, 47.00, 0.00, 3.00, fx_vclight , //cokpit Night ligthing
light.5=5, 11.570000, -10.48, -5.81, fx_PAland , // fdd = light.9=5, 12.00, -10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.6=5, 11.570000, 10.48, -5.81, fx_PAland , // fdd = light.10=5, 12.00, 10.00, -6.20, fx_PAland , //3-01-2012 halo fuselage des feux landing fdd
light.7=7, 49.25, -1.00, 2.90, fx_vclight , // VC day lighting by francois Dore
light.8=3, -13.70, -55.25, 2.45, fx_navred320pa //-13.90, -55.25, 2.45, fx_navred320pa
light.9=3, -13.70, 55.25, 2.45, fx_navgre320pa //-13.90, 55.25, 2.45, fx_navgre320pa
light.10=2, -13.95, -55.25, 2.45, fx_strobe320pa
light.11=2, -13.95, 55.25, 2.45, fx_strobe320pa

For the effets, they are the same for 2 version :

[EFFECTS]
wake=fx_wake
water=fx_spray
dirt=fx_tchdrt
concrete=fx_sparks
touchdown=fx_tchdwn,1
enginefire=fx_engFire
startup=fx_engstrt
EngineDamage=fx_engsmoke
WheelWetSpray=fx_wheelwetspray
WheelSnowSpray=fx_wheelsnowspray
windshield_rain_effect_available = 1
SnowEngineWash=fx_SnowEngineWash
WetEngineWash=fx_WetEngineWash

Francois

Can't make those lights work in the A320 CFM. They work correctly in the A320 IAE, though.

[fdd_fr]

CFM model has wing lights hardcoded in the model, because flexwings. Check if you have the right CFM model (FSX version).

Francois

[wulfbindewald]

Hi Francois,

the STAR defintion at Ketchikan PAKT may be corrected as the intersection for
all defined RWY11 approaches are related to the VOR ANN located in the south.
May be the STAR intersection waypoint DOOZI will be better for the entry from
the N and W .... I guess VOR LVD is too far away.
For Your attention.

Wulf

[fdd_fr]

Hi Wulf,

I will test your suggest . This was a difficulty to create STAR at PAKT, because there is no official STAR. Only all arrivals must pass by VOR ANN.

I am finishing WMKK Kuala Lumpur (the most difficult airport than I make, because there are many procedures and approaches and each STAR can have several ends with different approaches..

I will publish at the same time updates for KJAC adn CYYJ.

Francois

[The320Pilot]

SKCL is almost finished. I promised to send it to fdd_fr by the end of January but I've been busy. I expect it to be done in a couple of weeks.

[fdd_fr]

Hi A320Pilot,

No Problemo ! Take your time; This is great that you join us to create airports !

Today, just one new Airport (It take me many times, because vry complex procedures) :

http://freenavdbgroup.com/?p=542

- WMKK - Kulala Lumpur - Malaysia

Please, read the airprot information file, via the ARRIVAL page of the FMC, during STAR and approaches, because, there are some specials procedure in some case (mandatory holding pattern, or priority runway to land).
This airport requires that you download from the AVSIM library, an update of the AFCAD, realized by Ray Smith, because, runway 15-33 are missing in FSX stock Airport (and Ray Smith added the second terninal) . The link to download is in the install file, in the WMKK directory. AVSIM requires to create a free account to download;

You can use this airport, without update your AFCAD, but in this case, don't use Runway 15-33 Procedures (SID and approaches).

I have updated CYYJ (wrong runway declaration inn STAR) and KJAC (add speed constraints in some STAR); Thanks to Wulf to report me these bugs.


But Wulf, about PAKT, I can't change the ANN arrivals, because I respected the charts :



Final A320 version will have a new GO-AROUND procedure, that will work like the take-off procedure, with a pitch control by the FMC, at 15° until safety altitude is reached.

Fix some small bugs also.

Final edition will be in 2 weeks max, I had the confirmation of Sean that the english translation of the manual will be ready.

Have a good day.

Francois

[wulfbindewald]

Hi Francois,

PAKT: Ok, then as a consequence an approach from W or N to RWY11 should be traditional w/o STAR.
PAJN: Did You already considered the official updated transition SEYMAR (STVNS already included) from RNP RNAV RWY26,
which makes transitions from the west more feasible?

Any further airport creation plans?
Otherwise KMRY Monterey , KRDD Redding and PAHO Homer Alaska would be nice

Wulf

[Zamir]

Hi A320Pilot,

No Problemo ! Take your time; This is great that you join us to create airports !

Today, just one new Airport (It take me many times, because vry complex procedures) :

http://freenavdbgroup.com/?p=542

- WMKK - Kulala Lumpur - Malaysia

Please, read the airprot information file, via the ARRIVAL page of the FMC, during STAR and approaches, because, there are some specials procedure in some case (mandatory holding pattern, or priority runway to land).
This airport requires that you download from the AVSIM library, an update of the AFCAD, realized by Ray Smith, because, runway 15-33 are missing in FSX stock Airport (and Ray Smith added the second terninal) . The link to download is in the install file, in the WMKK directory. AVSIM requires to create a free account to download;

You can use this airport, without update your AFCAD, but in this case, don't use Runway 15-33 Procedures (SID and approaches).

I have updated CYYJ (wrong runway declaration inn STAR) and KJAC (add speed constraints in some STAR); Thanks to Wulf to report me these bugs.


But Wulf, about PAKT, I can't change the ANN arrivals, because I respected the charts :



Final A320 version will have a new GO-AROUND procedure, that will work like the take-off procedure, with a pitch control by the FMC, at 15° until safety altitude is reached.

Fix some small bugs also.

Final edition will be in 2 weeks max, I had the confirmation of Sean that the english translation of the manual will be ready.

Have a good day.

Francois

Will start testing WMKK, thanks !

[fdd_fr]

Hi Francois,

PAKT: Ok, then as a consequence an approach from W or N to RWY11 should be traditional w/o STAR.
PAJN: Did You already considered the official updated transition SEYMAR (STVNS already included) from RNP RNAV RWY26,
which makes transitions from the west more feasible?

Any further airport creation plans?
Otherwise KMRY Monterey , KRDD Redding and PAHO Homer Alaska would be nice

Wulf

Hi Wulf,

You request difficult airports, because in the most case, these airports have no procedure except approaches.

PAHO has no SID or STAR.

I realized KMRY that I am testing. I will post it this tomorrow, with LOWS (realized by Georges) and VHHH (Hong Kong new airport).

As the final aircraft will be ready in one or two weeks, I would add some airports in other countries, for all world users. Asia has nothing for the moment, we will work on some airports in other world countries.

I work now on VHHX - Kai Tak, Hong Kong old airport that it was one of the most difficult approach of the world. You will love it (and I recommend to buy the fantastic Fly Tampa scenery about this airport.

I think also at SPIM - Lima, and La PAZ, the higher airport in the world and some japan and corean airport (there is a guy who has realized fanstastic freeware scenery of 6 Korean airports).

I will publish also this weekend an update of the airport creation toolkit, with a complete database of all the actual waypoint used today in the world by the airlines companies; these database will allow to create airport files very more quickly, because when a waypoint is missing in FSX, you have just to do a copy/paste of this waypoint from this database.

You would join us to create airport, wulf, this is a interesting job !

About PAJN, I will try to add your approach this weekend also.


Edit : About your PAKT appraoch, think that you can add waypoint at any moment, during the flight, with FD-FMC; When you loaded PAKT STAR, display the Arrival page, and you can enter one or several waypoints before "ANN" VOR to get the trajectory of your choice.
People forget than FD-FMC allow to enter waypoints, VOR, NDB in the flight plan as you want.
The only thing, is to not insert waypoint into a SID, a STAR or an Approach. You must enter yours waypoints between the SID and the STAR or before load SID and STAR.


Francois

[fdd_fr]

It seems that there is maybe a problem with the Ray SMith update AFCAD of WMKK.

In FSX, all runways threshold have are marked by a waypoint that FD-FMC use as the final waypoint of an approach.

THis waypoint has always the same structure in the FSX database; Its name is always built with the following syntax :

- waypoint type "R",
- ICAO regional code
- Airport ICAO name
- Name of the runway.

E.g :

The runway threshold waypoint name in the FSX GPS, of the 14L of WMKK is : RWMWMKKRW14L

But it seems that with the Ray Smith AFCAD, these threshold waypoints don't exist, and when you load an approach, the final waypoint of the approach is always the point that define the airport location in FSX (near terminal 1).

This phenomenon is not important for an ILS or LOC approach, but It can be boring with a RNAV approach.

I must check, by desactivate the Ray Smith addon Scenery, if the problem comes form the stock FSX AFCAD or if it comes of the Ray Smith AFCAD.

In all case, if someone is a specialist of Airport Design Editor (ADE) and know how repair this AFCAD and add this markup runways waypoints, please contact me.

Otherwise, I will update WMKK files by add a user fix for each Runway threshold.

Thanks

Francois

[wulfbindewald]

Hi Francois,

thanks again for your effort for the PAJN update and the new KMRY.

If You intend to create airports in other countries e.g. Southamerica I suggest besides Lima and La Paz
- SEQM new Quito airport in Ecuador, deep valley location, offset landing
- SCEL Santiago de Chile, hub
- SPZO Cuzco Peru; high altitude, challenging between mountains and even more challenging than KJAC;
LAN Peru is flying many times per day with A319 from Lima(!) to Cuzco

I tried to make an airport but I failed ... too complex.

Wulf

[fdd_fr]

I added SEYMR IAF at PAJN with 3 arrival gates, according a new Alaska Airlines charts that I have fouond. I will after a good night.

Francois

[fdd_fr]

Hi,

Good news, there is no problem with the Ray Smith WMKK scenery. Runways threshold are available for FD-FMC. All works fine.


3 New airports uploaded :

- LOWS - Salzburg - Austria - realized by Georges
- KMRY - Monterey - USA (California)
- VHHH - Hong Kong New Airport (Chek Lap Kok) - China

Updates :

- PAJN - Juneau - USA (Alaska) v4.11, with the second RNAV RNP Rwy approach via SEYMR transition ( Alaska Airlines Porecedures). Charts can be downloaded on the website page.



Link : http://freenavdbgroup.com/?p=550

Think to read always the airport information page, via the Arrival page of FD-FMC, about Arrivals and special procedure for each airport.

Good flight

Francois

[wulfbindewald]

Hi Francois,
could You please update the new complete AIRAC file pack, as usual, in the freenavdbgroup too. Thanks!
The 2 new RNP RNAV26 approach maps from PAJN seem to be identical.

Wulf

[fdd_fr]

Excuse me, wrong manipulation.

All is ok now.

Francois

[wulfbindewald]

Hi Francois,

FD_FMC airports pack V4 02142015: 2 probs found in KPSP Palm Springs for Your attention, :

STAR... RNAV TRM ok
STAR... RNAV BALDI does not work and corrupts the basic flightplan
STAR... RNAV PSP adopts input from BALDI, but not intended here

Approach RNAV-Y for RWY31L:
The waypoints HIXOV-RIYOC-TECUV are defined with altitudes 6000-4000-4000 ft.
I suggest to use 6000-5000-4000 instead.
In fltpln this altitude step is defined in one step from 6000 to 4000 ft, but in one turn of 180°.
As the approach leg is (logically) splitted with the intermediate waypoint RIYOC
I consider to adopt the 5000 as already defined and done for the other similar approaches.

Wulf

[fdd_fr]

ok wulf, I will check KPSP.

Francois

[fdd_fr]

Hi Francois,

FD_FMC airports pack V4 02142015: 2 probs found in KPSP Palm Springs for Your attention, :

STAR... RNAV TRM ok
STAR... RNAV BALDI does not work and corrupts the basic flightplan
STAR... RNAV PSP adopts input from BALDI, but not intended here

Approach RNAV-Y for RWY31L:
The waypoints HIXOV-RIYOC-TECUV are defined with altitudes 6000-4000-4000 ft.
I suggest to use 6000-5000-4000 instead.
In fltpln this altitude step is defined in one step from 6000 to 4000 ft, but in one turn of 180°.
As the approach leg is (logically) splitted with the intermediate waypoint RIYOC
I consider to adopt the 5000 as already defined and done for the other similar approaches.

Wulf

HI wulf,

I have fixed the KPSP errors.
- RIYOC has now a altitude constraint of 5000ft, duriong RNAV-Y RWY 31L approach
- I changed the name of the 3 RNAV STARs by the following syntax : "RNAV TRANSITION.IAF", so now "RNAV BALDI" is called "RNAV BALDI.PSP" (and there are 2 "RNAV BALDI.PSP", according your arrival direction;
- old RNAV BALDI had a bug in the file (missing deleted commas) : bug fixed : STAR works now.


I have updated also PASI, with new minimum speed constraints at some waypoints of some approaches.


These 2 updated airports can be downloaed by using the "Download Airports" : ICAO x to x" pages of the menu Airport Database. version are v4.01.

I havn't updated the pack "full pack database files", so this is the reason why you must download these 2 airports, individually by the ICAO pages

I will do it, with the next update of the AIRAC and when I will add new airport, next weekend probably.

Thanks for the reports

François

[wulfbindewald]

Hi Francois,

thanks for the KPSP STAR updates. It works.

only formular:
You wrote "......now "RNAV BALDI" is called "RNAV BALDI.PSP" (and there are 2 "RNAV BALDI.PSP", according your arrival direction......"
This a bit confusing when selecting the RNAV. Why not to adopt the transition point FIVUT to STAR FIVUT.PSP instead of BALDI.PSP again?
The incoming directions are different and correctly defined: NW for "FIVUT".PSP and SW for BALDI.PSP.

Wulf

[fdd_fr]

Hi Wulf,

I have checked quickly KPSP, because I am working on RJTT - Tokyo Haneda, which is a very complex airport (many differents approaches, with new approach which I not knew : LDA approaches) and I have many difficulties to work on 2 things on the same time. When you work on an airport, you must have a globlal vision of all the maps, to understand some details.

And to check an airport, I must take all the charts of this airport and put them on a table and think.

Let me finish RJTT and I will re-work totally KPSP; I need to hold all the maps in the hand.

When I will finish RJTT, I will recommend that you test the rwy 22-23 LDA approaches; It seams that they are very difficult, at very low altitude, with a final 90° turn before landing, by hand.

François

[The320Pilot]

I think SKCL is ready. I'll send it today to François. Enjoy--and tell any bugs you might find (if there are any).

[fdd_fr]

great !

you 're welcome

[fdd_fr]

I do a last test and I post :

- SKCL, by A320Pilot !
- RJTT Tokyo
- NWWW Noumea New Caledonia

[fdd_fr]

New airports added on the website, with the updated AIRAC :

- SKCL - ALFONSO BONILLA ARAGÓN – CALI – COLOMBIA ; realized by Carlos Mario Díaz (The320Pilot) - You're welcome to the group^!
- RJTT - TOKYO HANEDA Intl – JAPAN
- NWWW – NOUMEA LA TONTOUTA – NEW CALEDONIA


Links : http://freenavdbgroup.com/

Francois

[fdd_fr]

Hi Francois,

thanks for the KPSP STAR updates. It works.

only formular:
You wrote "......now "RNAV BALDI" is called "RNAV BALDI.PSP" (and there are 2 "RNAV BALDI.PSP", according your arrival direction......"
This a bit confusing when selecting the RNAV. Why not to adopt the transition point FIVUT to STAR FIVUT.PSP instead of BALDI.PSP again?
The incoming directions are different and correctly defined: NW for "FIVUT".PSP and SW for BALDI.PSP.

Wulf

Hi wulf,

I am not sure to understand all your request, but I think that all is ok in the last KPSP version (4.01). NW STAR has "FIVUT.PSP" name.

Can you confirm to me if all is ok, and if it is waht you mean ?

Thanks

Francois

[wulfbindewald]

Hi Francois,

the new Version KPSP 4.01 embedded in "FD_FMC airports pack V4 02212015" does not rename the RNAV adress,
please see the screen pic below. As usual for Your attention.

Wulf

[fdd_fr]

oh sorry. I have forgotten;

Files modified, you can download KPSP fixed.

Francois

[fdd_fr]

Hi,

A member of "Pilote-virtuel.com" has found an error in the approaches files of VHHH Hong Kong, where the waypoint "STELA" has a wrong altitude (200ft then the real value is 2000ft).

I have uploaded the new version of VHHH (4.01) on the Freenav website, and updated also the "full airport pack".

Sorry for the error.

Francois

[wulfbindewald]

Hi Francois,

- A320 panel beta 0,8:
When using the speed brakes during appproach (AP and FMC activated) the speed brakes will fully extend. I have read in a another forum that the speed brakes in real A319/320 aircraft only extend 1/2 in AP mode, not fully extended. Is this limitation adoptable to your A319/320 panel during AP mode?

- FD_FMC airport pack for KPSP 4.01 now works.
My experience: The approaches from BALDI and FIVUT need extensive use of speed brakes during descent.
This can be managed a) with an earlier TOD and speed reduction in time before transition at 13000ft or b) a hold pattern at waypoint VOR PSP to come down to ~7000 ft.

Wulf

[fdd_fr]

About speedbrakes, you are right. My Airbus FCOM is old and this features is a change on the A319/A320; Not present on original aircraft;

I will see if I can add this features, but with you, aircraft will not never completed wulf !

About KPSP, TOD calculation is very complex and I don't want change the actual code. Think that you can engage your descent before the TOD; the only condition is that your aircraft is at less than 200 Nm of the airport (real Airbus feature). I think that this feature is for these special cases.

To engage your descent before the TOD, pull the alt button and sselect an lower altitude, and after push the alt button. If the aircraft is at less than 200 Nm of the airport, this action will engage the descent processus.

Francois