After another flight I found a couple more points worthy of mentioning (IMHO). I'd appreciate it if someone from the team would actually comment on this list and on my other post "My observations"Anyway, here it goes:- There seems to be a discrepancy between the "Fuel used" indication on the undocked engine display and the docked display! On one the indication remained constant throughout the flight at 0.83. The other display showed the correct value. I'm using the metric system.- The background noise is only activated after switching off the Stby power and reactivating it. I assume it should be running the entire time when you load the panel.- I wonder what the logic is behind the FREQ DISAGREE message you get when you have a VOR tuned and try to access the APP mode. Should it be generated based on the tuned frequency or does it really check if the tuned radio is an ILS? When no signal is recieved, or the ILS is out of range, the system will assume it's a VOR.- Could you maybe update the ADF reciever so you can tune NDB's with a .5 frequency?- When arming the autopilot for approach, and the G/S not being recieved (only the localizer), the current pitch command will be replaced by G/S and the aircraft will go into a steep dive. Not very funny :-)- When the autopilot intercepts the G/S from below, in level flight, the aircraft will start a climb and then rapidly pitches down. I doubt the passengers clapped that landing :-)- When a VOR is tuned to a DME, the VOR pointer will show north. I assume that the VOR pointer is inhibited in such a case. (On the ND)- Again, descending on the G/S with 1200 fpm @ 200 kts @ 2200 ft RA, the GPWS terrain alert was activated.- How do you activate the marker sounds on the panel?- In final approach, after activating both wipers, the APU suddenly started automatically and I couldn't deactivate it.- It seems at night with night-lighting on (SHIFT+L), the flap handle doesn't move. At least for me.- I couldn't dissengage the autobrakes by pressing the joystick's brake button.- The spoilers didn't extend after having been armed. Thrust levers were at idle.Regards,Mark

Exactly the same here...and those buttons are hard to use either in cycling and single click operationsjos

>- When the autopilot intercepts the G/S from below, in level flight, the aircraft will start a climb and then rapidly pitches down.Just to make sure I understand, the G/S was a few dots above when you hit APP mode and the a/c climbed? Could you provide further specifics (airport, r/w, time of day).>I couldn't dissengage the autobrakes by pressing the joystick's brake button.The autobrakes will automactically disengage (I am not at home right now, but I believe it is when you move the throttle foward from idle).>The spoilers didn't extend after having been armed. Thrust levers were at idle.I have had this happen, but everytime it was due to not having the lever exactly in the ARM detent. Are you sure the lever was in the proper position?Thx,George

"Just to make sure I understand, the G/S was a few dots above when you hit APP mode and the a/c climbed? Could you provide further specifics (airport, r/w, time of day)."Not exactly. The G/S was well above when I armed the APP mode. It was just that as the G/S was coming down, the G/S mode engaged with the G/S still being slightly above and the aircraft started a climb.I took a look at the G indicator (SHIFT + Z) and I had 0 G's for half a second. The aircraft should maintain level flight and then start a gradual descent to capture the G/S nicely."The autobrakes will automactically disengage (I am not at home right now, but I believe it is when you move the throttle foward from idle"Yes, but you should also be able to disengage them by braking manually."I have had this happen, but everytime it was due to not having the lever exactly in the ARM detent. Are you sure the lever was in the proper position?"Well I armed them by pressing "SHIFT /" which arms the spoilers directly.I would also like to say that it is pretty annoying that so many buttons and functions are "laggy". I mean entering the DEST ICAO code takes a second and basically all FMC inputs require a long time until you see that a field has changed. Same with the A/T.Another bug:Flying a SINGLE CH ILS approach, if you deactivate the flight director, you will lose the APP mode even with the autopilot engaged!I'm not sure about this one:Is it realistic that you can select modes on the MCP without a F/D NOR an autopilot engaged?I'm not talking of the TO/GA mode as that can be activated when the button is 'armed'. Pressing the ALT HLD on the MCP without a F/D or A/P engaged will result in ALT HLD engaging, without neither F/D bar nor the AP engaging. Could be a feature, I'm not sure. Just thought it was worthy of reporting as neither the 744 nor the 757/767 have this feature.Regards,Mark