Even though this thread is dated, I love all the valuable info everyone has given. I am new to the 727 and this thread (and others) help me understand the ins and outs of this lovely bird.

Manfred

Could you comment on technique for localizer capture. I try to fly an accurate localizer intercept, say from a DME arc, but this ends in a nearly ninety degree intercept which has me overshooting the LOC and by the time I get back on the LOC the glideslope is below. Should one add a couple of miles to the DME arc to allow some distance for making the intercept at a finer angle

Just try and fly a traffic pattern. Fly downwind about 5 or 6 miles from the airport. Let's say the runway is north / south and you are landing on runway 36 (north). Fly a no wind heading of 180 degrees and have the plane level around 3,000 feet above ground level with flaps 15 degrees and around 160 KTS.

Tune the OM NDB to the frequency listed in the MAP pull-down. You can get all the information you need for the airport and runway by mouse over on the MAP pull-down located at the top left menu bar under the heading WORLD. Get all the nav aids set-up in advance so there is no rushing during the approach. If your airport does not have a NDB in the OM, find one that does.

Use the NDB indicator to see where you are in reference to the OM. Flip the paddle to NDB on the RMI card this will give you magnetic bearing to the OM as you fly the traffic pattern. As you fly abeam the OM for your runway the RMI/NDB will point 90 degrees to the left (if you are flying a left hand traffic pattern). Fly past the OM for a few minutes. The needle is now pointing to the 8 o'clock position on the RMI/NDB.

Start a left turn to 090 degrees and when on the 090 heading look at the NDB needle. It should be pointing at around 10 o'clock on the NDB indicator. You are landing on runway 36 and the RMI/NDB should show you about 020 degree bearing to the station (OM). You should be at flaps 15 and 160 KTS. and 3,000 feet AGL. As the RMI/NDB starts to show 15 to 10 degrees, start a left turn towards the runway. If you are 5 miles outside the OM this should give you ample time to intercept the LOC. Keep an eye on the RMI/NDB needle as it nears the bearing of 005 degrees the LOC should be coming alive. Fly all of this on the autopilot so you can see what is happening.

If you want to cheat you can have the GPS open in it's own window to see your progress, but the 727-100's rarely had a GPS so we learned to fly using VOR/DME and NDB. Use the heading select to turn (vector) the plane and intercept the LOC. Five miles outside the OM you should be below the G/S and you are now ready for the approach. While tracking the LOC, as the G/S comes alive put the gear down. When the G/S is one dot from intercept select flaps 30 degrees. Steer the plane in heading select and you can use the pitch knob on the autopilot to pitch down to follow the G/S. If this is too hard, you can select AUTO G/S before the G/S comes alive and just adjust the power to keep the approach speed as you descend. If you are around 125,000 pounds for landing a speed of 125 to 130 KTS should be OK. Look for a FF (fuel flow) of around 2,500 pounds per engine. Adjust as needed to keep the speed.

Let me know if this helps...

Lou

Hi Antonio.

I also had the problem, which is why I asked Lou the questions, but I no longer have them. Some things which might help either prevent, or get through, the loss of avionics power.

1. Create a keyboard command for the Avionics Master (on/off). I use CTRL+SHIFT+A. Use the keyboard command to turn the avionics on when needed.
2. If you have a registered version of FSUIPC, you can give infinite battery life to your aircraft by going to Miscellaneous > Extend battery life (indefinitely if value equals 0, else by factor). Set it to 0
3. Add the line electric_always_available=1 to the [electrical] section of the aircraft.cfg

Any of these should solve your problem.

Quote:

I rarely used CTRL+SHIFT+A for the ADF, so I simply use it for the Avionics Master (on/off).
You can use whatever Key Combination you want. There are plenty of others that are not in use, I simply chose the one that was originally used for the ADF. Here is how:


Settings > Controls > Buttons/Keys
Then set the Event category: to Radios (1)
Highlight Avionics master (on/off) (2)
Click on New Assignment  (3)
Press CTRL + SHIFT + A (or whatever Key Combination you want), then click on OK.
Your done.

Quote:

I don't know what I did to make it disappear.

Originally, I used the electric_always_available=1, to stop it happening.
Next. I used CTRL+SHIFT+A to turn the avionics back on when they turned off.
Then I used FSUIPC to Extend battery life (indefinitely if value equals 0, else by factor), by setting the value to 0.

One other thing I used to do to get the avionics back and working, was to press CTRL+E, the default for engine start, because it turned the avionics back on and they never disappeared again during the flight. This did not cause the engines to be shut down and then restart either, it only turned the avionics back on. So it was another work-around.

All of these worked as a way of getting around the avionics turning OFF after about 10 to 15 minutes. I do not use any of these fixes any more. A few weeks after I asked Lou those questions, and got his reply, everything was working like it should. I honestly think I was missing something that eventually allowed the avionics to turn OFF after 10 or 15 minutes, but to this day, I don't know what I was missing that caused it.

You're welcome.

One good thing about the APU in the CS727, is that it doesn't consume fuel.

ajandrade wrote on Sep 19^th, 2013 at 10:18pm:

Unfortunately not. I have no idea as to when the next update might be.

Note: I am not a member of the Captain Sim staff, so I do not know what their plans are in regards to the updates for the 727 (or any other product).