Tord

Hi guys! Getting back to the wonderful CL650 in XP12 I was curious of which Simbrief OFP layout that best matches the CL650´s FMC? I´m normally using the LIDO layout with KG units. What got me wondering was the fields I´ve marked in bold below, in the PLANNED FUEL section. I belive they match some FMC model where these fields are to be filled with that specific data? They just aid in adding up the various fields in the Planned Fuel section. I´ve cut out the sections from the LIDO flightplan that I´m using for the PERF INIT page, which is pretty un-complicated. I´m usually adding the ZFW from the line "ESTIMATED ... ZFW 13090" in the example below, and then DELETE the CALC FUEL to get SENSED(?) FUEL values after giving the system time to "settle" after the fueling process is finished. Are there more parts of the FMC that can be used with the OFP data? [ OFP ] -------------------------------------------------------------------- SETHA 09JAN2023 ESSB-ENGM CL60 SETHA RELEASE 1012 09JAN23 OFP 4 BROMMA-GARDERMOEN WX PROG 0909 0912 0915 OBS 0906 0906 0906 ATC C/S SETHA ESSB/BMA ENGM/OSL CRZ SYS M80 09JAN2023 SETHA 1010/1030 1114/1122 GND DIST 277 CHALLENGER 650 / CF34-3B STA 1125 AIR DIST 280 CTOT:.... G/C DIST 213 AVG WIND 201/035 MAXIMUM TOW 21863 LAW 17237 ZFW 14515 AVG W/C M003 ESTIMATED TOW 15603 LAW 14853 ZFW 13090 AVG ISA M009 AVG FF KGS/HR 1008 FUEL BIAS P00.0 ALTN EKYT TKOF ALTN ESIB FL STEPS ESSB/0360/ -------------------------------------------------------------------- -------------------------------------------------------------------- PLANNED FUEL --------------------------------- FUEL ARPT FUEL TIME --------------------------------- TRIP OSL 750 0044 CONT 15 MIN 252 0015 ALTN AAL 614 0041 FINRES 397 0030 --------------------------------- MINIMUM T/OFF FUEL 2013 0211 --------------------------------- EXTRA 500 0033 --------------------------------- T/OFF FUEL 2513 0244 TAXI BMA 136 0020 --------------------------------- BLOCK FUEL BMA 2649 PIC EXTRA ..... TOTAL FUEL ..... REASON FOR PIC EXTRA ............ -------------------------------------------------------------------- FMC INFO: FINRES+ALTN 1011 TRIP+TAXI 886 -------------------------------------------------------------------- -------------------------------------------------------------------- WEIGHTS ------- EST MAX ACTUAL PAX 6 ...... CARGO 0.1 ...... PAYLOAD 0.5 ...... ZFW 13.1 14.5 ...... FUEL 2.6 5.0 ...... POSS EXTRA 2.4 TOW 15.6 18.0 LDG...... STAB TRIM ...... LAW 14.9 17.2 ...... --------------------------------------------------------------------

Ah, VNav as a modifier makes what I see happening make a lot more sense! As you say I was thinking of it being VNav OR FLC, but in fact I should think of it as FLC OR VS with VNav enabled OR Disabled. Thanks!

I think this should help? https://youtu.be/GODF3B7odTE

I´m very sure I´m doing something wrong and would appreciate some advice from you with good knowledge. Scenario 1. Descent when only following a VNAV path according to a STAR. Let´s assume that I´m nearing an airport and have added a STAR and Approach in the FMC. The path has a couple of AT OR ABOVE, AT OR BELOW and AT altitude restrictions with final approach altitude for the ILS at 2500 ft. a) I set 2500 as selected altitude prior to TOD. Actually I´d set the altitude to match any STAR altitude restrictions during the descent, but let´s be lazy here. NAV and VNAV are the active modes. (I´m hoping I use the correct names as much as possible). ATS is on and showing SPEED at this time. b) When reaching the TOD I do no button pushing. The autopilot will initiate the descent, ATS goes to DESCENT if I remember correctly. The VNAV PATH will be followed and the various restrictions will be met. At a suitable point I press APPR which sets LOC and GS as selected modes, and they activate upon catching the LOC and GS respectively. c) During the descent I manage speed to achieve whatever speed is needed during the approach/arrival. Scenario 2 Descent initially following a VNAV path according to a STAR, but ATC comes with altitude instructions. a) Setup and initialization as above. While inbound to a waypoint with an altitude restriction of AT OR ABOVE FL180 I get the instruction to descend to FL110. b) What I´ve done here is to set FL110 as selected altitude, then press FLCH. However, and I haven´t done a lot of trials, if we reach FL180 the AP seems to level off and not proceed to FL110? I then start mashing buttons trying to select VS or FLCH but the descent becomes very messy and I have no real control of what I should select. I guess my question here is, how do I transition from VNAV to "manual" AP modes? c) What should I di to stay in VNAV for this scenario? Do I need to DELETE any altitude restrictions on LEGS that are above the ATC instructed atitude? If I do that I´m guessing that VNAV path will calculate the descent for whatever the next lower alt restriction in LEGS is, and my selected altitude of FL110 will mean that the VNAV descent will stop at FL110? Scenario 3. Non-VNAV method. What is the best practise of using AP modes if I don´t want to use VNAV/VPATH?