Der Michel

I tried to get the correct versions. I can rule out any P4 or non Honeywell references.

That’s why I wrote empty FMS. It’s hard to get reference material. So I have to take what I get.

According my knowledge it’s possible to uplink such data in A320 and A330/340. It’s airline policy what they uplink and what not. I have no info what the majority of airlines is doing. Maybe ini can give us an option to select what to uplink and store it in the livery settings.

Not for the old Honeywell P3 system.

And the same error as always: 1. The speed at the departure is the V1 !!!! If it's not entered it has to be dashed! 2. The from wpt TIME and SPEED has to be large font

All sim-images on Ground: 1. dashes have to be white 2. UTC has to be TIME on ground 3. no : between dashes 4. LSK1R and 3R Time is only computed in cruise phase, otherwise it is dashed. 5. LSK5R refference WPT with / has to be moved 1 column left

1. dashed lines are missplaced 2. LSK3R has a format error

1. LSK3L remove the space behind ILS

1. LSK4L has to be large font ---° /----.- 2. LSK6L has only to show one decimal 3. Line 6 ACCUR has to be right alligned 4. Dashes for LSK6R have to be large font 5. LSK3L UPDATE AT is missing

1. LSK5R large font dashes

1. Keep LSK1L, 2L, 3L empty for an empty FMS, no dashes 2. LSK5L large font dashes

1. LSK4R should have a large font minus 2. LSK5R is missing STEP ALTS>

1. LSK2R is missing small white font [M]_ or [FT] in front of the dashes 2. LSK2R the dashes have to be 1 column right

1. Layout of page is wrong, as already stated For correct layout: 2. The page is only populated with Line 1 and 2, LSK4R prior engine start!! The rest has to be dashed. 3. FOB has to be green, as it's a not editable by FCMC computed value in P3 4. JETGW has a blue [ .] 5. When CRZ ALT is reached, the CRZ TEMP has to be dashed The FCMCs : ‐ Measure the fuel quantity and indicate it on the ECAM. ‐ Calculate the aircraft's Gross Weight and Center of gravity, based on the Zero Fuel Weight and the CG entered by the crew.

1. As long as long as no Radio is tuned at RAD NAV (will happen after alignment of IRS), - no FREQ has to be displayed at SEL NAVAIDS (just keep blank). - no FREQ has to be displayed at ND (just keep blank). - no MORA has to be displayed at ND. 2. SEL NAVAIDS: frq has to be 1 column left 3. SEL NAVAIDS: AUTO has to be 1 column right 4. SEL NAVAIDS: Display LSK1-4 only, if something related is tuned.

1. keep page dashed as long as ADIRS are OFF. The GPS signal is routed through them. 2. The GPS position is not instant avail with ADIRS ON, it requires some time. For IRS INIT page it is stated <1min that GPS pos is avail. 3. Indicate the mode of ops at LSK3R and 6R

1. move titel 3 columns right

1. Dashes have to be ALWAYS !!! white (large font) and the correct format is: ----.--/-----.-- 2. LSK6R: SEL has to be in small font 3. Line 5: OFF, ALIGN, NAV x.x has to be in small font 4. LSK3L label depends on availability of GPS

1. Only 2 pages, not 4 2. P3 doesn't support RADIUS, so remove it. Edit: This report assumes that ini is doing a Honeywell P3. With 1.02 they changed several pages including IRS INIT from P4 to P3. So it‘s a pre Release1A standard.

1. VIA and AVAILABLE label are not in line with the columns/matrix structure 2. Runway length is too far right (keep it in same colun) 3. Runway unit has to be small font 4. ident/freq is too far right 5. NONE has to be at the end of the list, if it exists in reality (I have no source) 6. ERASE also with <-- 7. display NONE at LSK2R if there are no TRANS and keep the list empty. 8. Refference is from SEC, so no yellow items. 9. VIA page should have a RETURN and no ERASE/INSERT 10. selecting any LSK1-3L item should directly switch back to ARRIVAL page. 11. NO VIA has to be at the end of the list

1. AVAILABLE RUNWAYS is not correct arranged in the column/line matrix 2. dashes for SID and TRANS are both missing an additional one 3. CRS has to be moved 4. length unit has to be small font 5. ILS has to be large font 6. END is missing 7. NONE has to be at the end of the list, if it really exists (have no source) 8. EOSID NONE is missing 9. ERASE has an <-- and no * 10. just a another refference

There will maybe follow more posts to this topic. 1. LSK5L is missing <ALTN page access

Please enable MCDU 3 so we can use it for AOC/ACARS operations, just like it's done in reality.

This will now be a longer post, as the F-PLN has many issues. Maybe I will do follow on post in future. 1. at LSK1R show only 5 dashes ----- and move 1 column right 2. removed 3. Line 1 is missing TIME 0000 4. LSK1R is missing the airport refference altitude rounded to tenth 5. for the leg length the unit NM does only appear at line 2 6. all dashes have to be large font 7. the color and size of the / is always defined by the following text or numbers (just a general remark) 8. LSK1L is missing the label for the SID name 9. The CA leg is indicated wrong. Already mentioned in the A350 topics. An CA leg is somehow a "pseudo" constraint. For the VNAV it'S mandatory to met it, therefor the position is adjusted along the track according climb performance. Initial there is a assumed distance and when performance calculations are avail, that position is refined. But: It's not indicated as magenta constraint in F-PLN, ND or VERT REV page! Also there can never be a missed or match asterix next to it. This also relevant for FA (in the reference photo) and VA legs. 10. We see here 2 magenta asterix without predictions avail. that cant be! Also there a no alt CSTR, so for what are they there? The speeds 230 and 250 are constraints, they have to be magenta. 11. Also the arrival airport is missing the altitude 12. And as already mentioned in the A350 topics. The ALTN F-PLN is missing the destination of the active F-PLN as origin for itself. Without that it's not possible to built a ALTN F-PLN. 13. If there is a window alt constraint in F-PLN, display WINDOW in F-PLN 14. The arrival altitude has to be green. 15. The GS intcpt altitude has to be green 16. TRK and BRG are missing the ° 17. HOLD SPD has to be in the TIME column and different spelling 18. place the HOLD speed value in the speed column, but it's not in line with the other speeds

1. The LSK2L and 2R have to be blue, as the values can be edited by pilot. 2. Whne LSK1R is pressed, the values have to vanish 3. The logic need to be adapted. The ini A340 has GPS, so this logic has to be implemented: "The preferred way of initializing the ADIRS is to use the GPS position, because this does not require any flight crew intervention. Less than 1 min after setting the ADIRS to NAV, the INIT page displays the GPS position without displaying the ALIGN IRS prompt. If the flight crew enters a CO RTE or FROM/TO, the INIT page displays the departure airport reference-point coordinates, and the ALIGN IRS prompt appears. If this prompt key is not pressed, the ADIRS is initialized to the GPS position at the end of the alignment time. At any time during the alignment, the flight crew can manually adjust the coordinates displayed on the INIT page. The ALIGN IRS prompt reappears. If the ALIGN IRS prompt key is pressed, the coordinates displayed on the INIT page are sent to the ADIRS for initialization. This is the alternate method for ADIRS initialization, when the GPS position is not available. A normal alignment takes between 5 and 10 min (depending on the local latitude). At latitudes between 73° and 82° (North or South), the alignment takes about 17 min. The ADIRS cannot be aligned beyond 82° (North or South). A fast alignment takes about 30 s, and it is used for improving the ADIRS initial position accuracy, when time is limited."