* When you approach your destination & want listen to ATIS from 300-250NM you have to keep pressing TEST in the RTP the new thing is Press "TEST+OFF" till the RTP turns off then remove ur fingers and you will be able to listen to the ATIS with your hands free!!
* Another thing I discovered with the FMS but still yet have no idea what we can get useful from it, on the RTE page type the word "ORGN" instead of your departure airport 4 letters code and the FMS will accept it & if u turn your ND to the PLAN View you will see the word & airport of departure in the same exact place with the title ORGN
Hope you guys have more to share
Last edited by cpt_shawky; 17th Sep 2009 at 09:42.
If you think a weather diversion could be likely, you can type in the route from your destination to your alternate at the bottom of the current plan on the ROUTE page. You won't be able to finish with the alternate runway or STAR/Approach, so just put in the four letter ICAO code. This will allow you to view the route on the route page for orientation should the diversion become actually necessary, and any "direct" clearances can be seen as the route legs are already on the LEGS list.
If you think an instant diversion is necessary, think "RALFIE". R for Route - change the destination on the ROUTE page to your new airport. A - ARRIVAL select the runway and ILS likely die to winds or ATC information on the ARR page. L - LEGS get to the bottom of the legs page, and bring the new ILS initial fix to the top. F - FIX place the airport identifier in th eFIX page, with a 25 mile circle to remind you of terrain etc. I - INIT/REF hit the init ref page to select the Vref, and see the ILS frequency, ILS course and runway length displayed so you can tune them up. For the -700 an appropriate autobrake setting is (9 - [number of 1000 feet of runway] ) E - Elevation - go to INDEX>NAV DATA>Airport enter the airport identifier and you will see the info page giving the Elevation. Set this in the pressurisation window, and if you like add 200 feet for a rough ILS minima. 20 seconds work gives you everything you need to put the aircraft on the ground at an "unknown" airport.
If you have an older update, you can access the Alternate and Nearest airports page (if your company hasn't paid for them anyway) by placing a random offset in the offset page, then pressing the "erase" line select key on both CDUs simultaneously.
You can define a waypoint by describing two intersecting tracks, and having the FMC work out where the intersection is. Useful when, say a vector leg has been planned before an ILS, and you would rather have an intersection. The format is [the first point][the outbound track]/[second point][second point outbound track] i.e.: AAA065/BBB350 in the legs page will place a point where the 065 radial from AAA intersects the BBB 350 radial.
Place two equal sized circles around two airports on the fix page, big enough to overlap. Looking at the map - if you join the two intersection points (mentally) together you will gat a line that is half way between the two airports and perpendicular to them. Where this mental line crosses your track is the nil wind critical (or equal-time) point. You can adjust this for wind - but while easy to do, the explaination is too long for me to type. If you adjust the circles until the intersection point is on your track, you can use the intersection feature from the fix page to add the fix tou your route. If you want to be fancy, you can define a better name for the point on the NAV DATA page.
You can set up a free standing way point by placing any random point at the bottom of your LEGS page, adding the point you want to be a free standing way point under that, and then deleting the first random way point. This sets up a deliberate route discontinuity, and the free-standing waypoint then exists by itself. It is good if you don't want to use up your fix pages to define points (more useful when there were only two fix pages) You can also form a holding pattern on the point - useful for setting up engine out procedure holding points before departure etc.
I've got a few more, but that's enough for my typing for now
-- Seeing as the aircraft cost so much, they are not advertised well - in all of the cockpit, the word "Boeing" only appears in three place. See if you can find all three on the next few sectors!
Oh dear, but I guess we were all a bit impressed the first time we discovered the Test+Off button! Is there a way to stop the annoying 5 seconds of "Test" when you press the button to see if the ATIS is coming in and discover its not?!
I'm not that long on the 737 myself, can't think of much else except:
Some people think running 1 Pack in Auto and one off on the ground saves fuel, but obviously the logic will make it run in high flow which burns more APU fuel than both in auto. Check out the MAINT/APU page and look at the instant fuel flow in the different configurations.
I think everyone knows the abeam point in the legs page, just put the point on top, then the point below on top of that and execute it.
The FMC info is always interesting, would be interested to hear any other little tricks.
Perhaps, also of interest, are somethings NOT to do. I've seen smart arse SFI's teaching cadets on TQ courses to do some overly slick things, but tell only half the story.
Climbing out above TA; use 2 fingers and select STD and cancel MFRA (baro setting) at the same time. They then did the same when descending through TL to select QNH. Except this time they also deselected the DA (baro setting). The SOP, on a NPA, is to select a DA rounded up to nearest 100 and the MCP altitude to the same. They did not get" +100 or minimums", but the a/c levelled off. This was all that saved them. However, in another previous airline they set MCP to MAA and descended in V/S. There would have been no call of "+100 or MINS" and they would have got very close to terra firma if not crashed.
Very often it is NOT a good idea to use 2 fingers to execute 2 switches at the same time, especially in the air.
For, perhaps something useful to do with the FMC, and this applies to all such equiped a/c, and is very helpful to ATC.
Often we ask ATC to avoid weather by left/rigfht 15/20 etc. degrees. Yes, but for how long??? ATC need to know. Go to RTE OFFSET and enter left/right XX nm until the route bypasses the weather. You can then tell ATC how many NM's you need to deviate and for how many nm's down route. Another way is to enter the active, or relvant, wpt into DCT TO and then in lower RT corner enter a guessed INCPT CRS TO. You wil then see a dotted track into the waypoint. Alter this until it bypassess the Wx. You can now advise ATC you need to deviate HDG XYZ and can track ABC into the WPT. That way they have a picture and can manage traffic well in advance. It ain't a wackily clever trick; it is just using the box in a way it was designed to do and to be helpful to your mate at the other end of the microphone. It's better than throwing a curve ball to who knows where.
I'm not flying airliners, but I enjoy reading this. Our avionic mechanics also have some tricks on certain instruments and the FMC, to test them. Test displays are often called up by pressing multiple switches at once. I remember a three letter code being entered on the FMC maint page to unlock a lot of company related presettings. Anybody tried a ctrl-alt-del in flight?
Location: Tweet Rob_Benham Famous author. Well, slightly famous.
You may be astonished just how many people had not the faintest idea what the squelch did. Those that had a rough idea often thought that it worked the other way round.
It doesn't hurt to have these little memory joggers from time to time, but shawky, get the hang of spreading the word with a modest subtly. In my day, the captain would reach across and belt anyone that he thought was trying to tell him something. Think yourself lucky you're in the modern world!
I come from an era in aviation when it was the Captain's "sacred duty" to ensure that the following generations of Captains were better than they were themselves. Ideally this came about by the following generation's application of their own skills, PLUS the collective wisdom of the preceding generations which had been dutifully passed on.
I hope that, as I am now one of the older generation, that I have performed my "sacred duty". I think that I have, but it is not for me to judge, it is up to the current generation of Captains and First Officers whom I influenced to make that judgement.
Aviation is an information intensive industry, the more knowledge that we share, the better we all are for it. As an old fart now, I'm finding that the younger generation has more than a little good information to share with me. Why should someone be "put down" simply because in his/her relative inexperience they are sharing something which, in all good faith, they believed to be unknown to most? Young dogs CAN and DO teach old dogs new tricks every day. Encourage them, don't put them down.
h3dxb, you quoted I like to show planedriver how little they know about their aircrafts. Why? If you are an experienced professional as you claim to be, what 'kick' do you get out of belittling someone? As an experienced professional (your claim), would it not be more appropriate to enlighten them and contribute towards their overall worth, both as a pilot and a fellow human being? You, sir, are delinquent in your "sacred duty".
I wish that PPRuNe had been around when I was a young pilot. The CONSTRUCTIVE inputs of the numerous TRUE professionals who lurk these pages would have accelerated my learning experience considerably.