Jump to content

ontheair

Members
  • Posts

    190
  • Joined

  • Last visited

Posts posted by ontheair

  1. Hi dear Travis,

     

    Thanks for contributing once again.

     

    I did fly the VOR-DME rwy 11 approach with Concorde X (track 102° CZM VOR - 2000' ASL) coming from Panama/MPTO.

     

    That's true the proc. turn involved (302° radial outbd CZM/102° track inbd ) places the CZM before the rwy . That's the way I understood the EFB/Navigraph chart. As you know what seems to be incorrect is the mentionned approach course 259° (for both rwys).

     

    Amicalement

     

    Jean-Louis

  2. Bonjour,

     

    Something rather strange with some Cozumel approach charts :

     

    VOR/DME rwy 11 (CZM) 112,6 apch course 259° !! Instead I would say 102° as charted (offset 14°)

     

    VOR/DME rwy 29 (CZM) 112,6 apch course 259° !! Would say 305° (offset 9°)

     

    Please tell me if I'm wrong

     

    Guess it's not on Aivlasoft side but Navigraph's

     

    Jean-Louis

  3. Hello Urs,

     

    Would you please check what's wrong with LSGS departures ?

     

    SID overview gives S and W departures : GOLEB is one of the W departs but when selecting a SID, none of the rwys are available !!!

     

    On the other hand, when trying to modify an ATS route description (mine : LSGS DCT BERAR GOLEB CBY 4543N00514E 4544N00507E DCT LFLL) the GOLEB SIDs are available when taking off from 25 but the plotted departure route for GOLEB1W is rather strange with a "ghost" wypt located near Cairo VOR !!!

     

    Thanks to have a look. Best regards

     

    Jean-Louis

     

    below a copy of my Runways.txt related to LSGS :

     

    LSGS 07 07L

    LSGS 25 25R

    LSGS 08L 08L

    LSGS 26R 26R

     

    PS just noticed there is no STAR available at LSGS ?? What about the ILS/DME 108,35 ISI 246° LLZ offset via SANET ? Is that normal ?

  4. Hi Vic,

     

    As I can see Travis just gave you the only and right answer to your problem

     

    Quoting you "I will try and do what you suggested. In the meantime. What I don't understand is how do you pick/pair those numbers like..."

     

    May I suggest you to read the manual again and again and again as most of us did ? I know it looks like boring to read all that stuff many times but pretty useful believe me.

     

    Regards

     

    Jean-Louis

  5. Good investigation/job Urs !

     

    "As a workaround I can only suggest to rename CLE to CLE99...."

     

    Found fix CLE coords N41°38,40168 E002°38,002 located :

     

    E:/Program Files (x86)/Microsoft Games/Microsoft Simulator X/AivlaSoft/SIDSTARS

     

    made the change CLE to CLE99, choose STAR PUMAT3T and the vanishing issue is still there !

     

    Did I select the correct file ?

     

    Regards

     

    Jean-Louis

  6. Thanks Travis !! Glad to know I didn't do anything wrong...

     

    I confirm this issue is linked with some LEBL STARs. I just make some STAR change tries and I came to the following conclusions :

     

    AIRAC 10/08 -

     

    25R north arrivals LEBL

     

    - BISB2V OK everything fine

    - BIS2Y "

    - ALBET1T "vanishing" issue is occuring everytime

    - PUMAT3T "

     

    Any possibility to fix it ?

     

    Best regards

     

    Jean-Louis

  7. Hello Urs,

     

    What did I do wrong ? Don't know ?? but all selected charts-objects (VOR, airports, fixes, compass rose, etc...) and the aircraft symbol (while enabled) are missing on both local and remote DUs !!

     

    Tried but no way to make them visible again. AFAIK I didn't make any change in my DU settings.The a/c symbol was visible on ground at EBBR but disappeared just after takeoff on the CIV7D SID ?? Except my planned route and rivers the France and Spain charts are desperately empty.

     

    EBBR DCT CIV MEDIL UQ237 DISAK UN857 DIRMO UN855 PPG ALBER DCT LEBL

     

    Any idea ?

     

    Regards

     

    Jean-Louis

  8. How can I make the difference between a VOR/DME and a DME with the chart legend ?

     

    Example : near CYQT/Thunder Bay

     

    Thunder Bay VOR/DME : YQT/114.1 noted D (H) + coords

    Mickay Thunder Bay DME : UAU/112.5 noted D (H) + coords

     

    BTW what do D and (H) stand for ? (I should know that...)

     

    Merci d'avance

     

    Jean-Louis

  9. Thank you Urs !

     

    I just provided the above comment not to underline any EFB dysfunction but to explain why the flight progress changes that quickly from dep to enroute chart as soon as the first enroute wypt is the last SID wypt.

     

    By removing this wypt from enroute, deleting and reconstructing the proper SID, the chart change is normal, it just occurs when it's planned to occur, and that's fine !

     

    Best regards

     

    Jean-Louis

  10. Hello Urs,

     

    Just found what might be the beginning of an explanation....

     

    - Let's enter the following ATS route description and activate it :

     

    EHAM DCT LEKKO UN872 MEDIL UN872 KOVIN UY317 RESMI UN857 LMG UN10 ENSAC UP181 MAGEC DCT LFBZ

     

    - let's choose the SID rwy 24 EHAM South depart : LEKO1S and activate, the corresponding SID is included in the route setup

     

    Now observe the route setup window : LEKKO is the last wypt of LEKOS1S SID. The first following wypt is LARAS on UN872.

     

    Now let's modify the route : LEKKO is still an enroute wypt instead of being the last wypt of LEKO1S SID !!

     

    That means if I don't remove LEKKO as an enroute wypt and reconstruct the full LEKO1S SID, the flight progress change from departure to enroute chart will take place well before LEKKO.... CQFD/QED.

     

    Same problem concerning the LFBZ North STARs : MAGE3B, MAGE3L, MAGE3V. MAGEC won't be part of the choosen STAR except you don't remove it from enroute wypts and reconstruct the STAR.

     

    What do you think about ?

     

    Best regards

     

    Jean-Louis

  11. Bonjour Urs,

     

    Thanks very much for your crystal-clear answer to my question.

     

    "....within a range of approx 2,5 miles from a wypt then this wypt changes to passed..."

     

    Yes "approx" is the word, except the range of 2,5 miles might become much much greater !!

     

    Just flew the WAL1R departure from EGCC : the last depart wypt WAL is 34NM from EGCC but depart chart changes to enroute well before reaching the 2,5 NM range to/from WAL !

     

    Is there a way in EFB program to make sure the distance of 2.5 NM minimum between a/c and wypt is the main criteria to make the flight progress changing from departure to enroute ?

     

    Thank you

     

    Jean-Louis

  12. Hello Urs,

     

    From EFB manual section 6 page 3 of 4 :

     

    "When the last Departure waypoint or the 1st Enroute waypoint has been passed Progress changes from the Departure chart to the Enroute chart"

     

    Well, but it happens from time to time that the progress change between departure and enroute charts occurs well before the last departure wypt and in this case there is no way to go back to departure when enroute is active.

     

    How can I change that to keep the dep chart activated till the last wypt ? Maybe in the settings but i don't know which ones needs to be corrected.

     

    Best regards

     

    Jean-Louis

  13. Hello Urs,

     

    Just made the following change in my Runways.txt file :

     

    LTBS 01 01L

    LTBS 19 19R

     

    after pressing "Reset airport data cache" and "get airport data" I got :

     

    EFB Dispaly Unit LTBS rwys : 01L 19 instead of 01L 19R

     

    what's wrong ?

     

    Airac cycle 1006

     

    Merci

     

    Jean-Louis

  14. Hello Urs,

     

    The title is self-explaining : how can I do that ?

     

    Of course, instead of saving my own checklist I spent many hours to build, I have the possibility to export it and to restore it via the import function.

     

    AFAIK the export/import functions were designed to share checklist rather than to save/restore them.

     

    Don't you think a "Restore" button (that is missing) would do the job far better ?

     

    Thanks

     

    Jean-Louis

  15. Hello Urs,

     

    Would you please have a look on LFSB charts :

     

    - the SID overview gives many departures to N, E, S and W

    - the SID selection provides also many departures but only from rwy 26. Departures from different rwys than 26 are just not available ? (longest LFSB rwy is 15-33)

     

    how can you explain such an incoherence ? Could it be related to Navdata ?

     

    A runway correction concerning LFSB was made some days ago into my runways.txt file. Here it is :

     

    LFSB 08 08

    LFSB 26 26

    LFSB 16 15

    LFSB 34 33

    LFSB 16R 15R

    LFSB 34R 33R

     

    Merci beaucoup and let me tell you once again I really appreciate the great job you've done with EFB that is now "a must"

     

    Jean-Louis :):)

×
×
  • Create New...