My error, guys.

 

Regarding the TOD an FMC/FMS calculates TOD based on the destination airport elevation for a constant descent unless you insert a hard altitude in the LEGS page of the CDU. RC calculates its TOD based on a hard altitude of the crossing restriction at about 40 nm out.

 

My preference is to used the range ring method and modify V/S on the MCP of the aircraft and slow IAS if necessary. I try to maintain an idle descent as much as possible. The reason I prefer the range ring is if necessary the path changes which might require a different FIX at the 40 nm mark.

 

In cockpit videos I have of the B737, B738, and B763 many crews at a certain point will prefer to use MCP control for descent rate. They also use a 30 nm range ring to indicate in general the airport traffic area where pattern entry occurs.

 

I looked at a log of a B737 from KLAX to KATL and when still in ATC center they did have some descents of up to 2,600 fpm. I used flightaware.com. Do a flight search (flight name unknown) and enter the origin airport and then the destination airport and a list of flights by flight ident and aircraft type will be shown. Choose one that states Arrived and right click on the flight number and a page will open with the route and other information. Click on Track Log. Here's an extract of an Airtran log on that route:

 

11:09 34.3558 -86.0592 103° East 553 636 28,300 -1,020  Atlanta Center

11:10 34.3192 -85.8772 104° East 553 636 27,300 -1,140  Atlanta Center

11:11 34.2819 -85.6956 104° East 548 631 26,100 -2,100  Atlanta Center

11:12 34.2425 -85.5039 104° East 540 621 23,200 -2,940  Atlanta Center

11:13 34.2069 -85.3347 104° East 519 597 20,300 -2,700  Atlanta Center

11:14 34.1731 -85.1711 104° East 508 585 17,800 -2,820  Atlanta Center

11:15 34.1075 -85.0472 123° Southeast 447 514 14,700 -1,920  Atlanta Center

11:16 34.0267 -84.9461 134° Southeast 431 496 14,000 -420  Atlanta Center

11:17 33.9461 -84.8428 133° Southeast 419 482 13,900 -180  Atlanta Center

11:18 33.8736 -84.7519 134° Southeast 392 451 13,700 -480  Atlanta Center

11:19 33.8167 -84.6667 129° Southeast 322 371 13,000 -660  Atlanta TRACON

11:20 33.7500 -84.6000 140° Southeast 286 329 12,500 -840  Atlanta TRACON

11:21 33.7333 -84.5167 104° East 298 343 11,400 -1,200  Atlanta TRACON

11:22 33.7333 -84.4167 90° East 298 343 10,100 -1,320  Atlanta TRACON

11:23 33.7333 -84.3333 90° East 277 319 8,800 -1,320  Atlanta TRACON

 

Here the max is almost 3,000 FPM at 540 knots TAS or ground speed, not IAS which would be a false indication if in MACH range at FL234. The route was:

KLAX HOLTZ9 TRM NABOB J231 ACH PNH J6 IRW FSM MEM ERLIN1 KATL

 

BTW: I paste this into FS Builder to generate an FMC and FS9 plan applying a couple of ident mods if necessary.

 

The same flight yesterday had similar descent rates.

 

A caution when using some airlines on flightaware.com. Some airlines use the same flight number on a multi-leg trip. Once you open a flight it may show a different leg with different departure and destination information so always check the airports after opening the flight.

 

For the occasional steep descent plan ahead to use an airspeed that will allow spoiler/air brake use.

 

A point of information about logged flights through September in FAA territories. Because of temporary budget cuts, the ATC staff has been reduced by 10% for any shift. In high traffic areas this has caused more congestion than usual and some flights are delayed and maybe typical operating patterns modified.

 

Back to the flight log: Notice that sampling is at a one minute interval so peaks and minimums might be missed.

 

 

 

 

 

 

 

Thanks Ray.

 

I'm about to takeoff at my home airport EGGP and was wondering how when editing flight plan in fsx I can make a waypoint a certain altitude

 

Ronzie,

 

Thanks awesome!

 

I'm looking at some of the flights now..

RC4 will not use altitudes in the flight plan. For certain phases all you can do is request higher or lower. During initial departure and final arrival you can get RC to not command your altitude or at least command them but relax monitoring. Check out NOTAMS, IAP, Departure with Altitude Restrictions and Departure without Altitude Restrictions in the RC43 manual. For the enroute phase RC will always choose the immediate altitudes for climb and descent to your chosen cruise altitude which is available in your FSX plan as:

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KMIA to KJFK</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>35000</CruisingAlt>
        <DepartureID>KMIA</DepartureID>
        <DepartureLLA>N25° 47' 43.00" , W80° 17' 24.00",</DepartureLLA>
        <DestinationID>KJFK</DestinationID>
        <DestinationLLA>N40° 38' 23.00" , W73° 46' 44.00",</DestinationLLA>
        <Descr>KMIA, KJFK</Descr>
        <DeparturePosition>13L</DeparturePosition>
        <DepartureName>MIAMI_INTL</DepartureName>
        <DestinationName>JOHN_F.KENNEDY_INTL</DestinationName>

 

You can also modify the cruising altitude on the Controller Page preflight in RC.
 

Within those ranges you can set the on your LEGS page for your aircraft to follow. Depending on your aircraft model it may import them from a proprietary format output by a flight planner.

 

That's my FS9 experience. I gave up on the FS flight planners a long time ago as too limiting and also because in those you are limited to the navaid and intersection databases in FS making it difficult to use current real world flight plans.

 

While I am on FS9, I do respond to some FSX items because RC behavior is the same for both.

 

For PMDG FMC plans, the .rte and .rt2 formats can include altitudes if you use an accommodating planner and set that option when exporting.

Thanks Ray.

 

I'm about to takeoff at my home airport EGGP and was wondering how when editing flight plan in fsx I can make a waypoint a certain altitude

 

Ronzie,

 

Thanks awesome!

 

I'm looking at some of the flights now..

 

Hi Deeb,

 

Do you live near Liverpool? I'm near EGCC as you can see from my sig.

 

As Ron said you can't specify an altitude for a waypoint in a flight plan, only the cruise altitude.

 

If you fly a 3rd party aircraft that has a CDU you use the FIX option to create a circle 40 miles around your destination airport. You can then vary your descent rate manually to ensure you cross that circle at the altitude RC has ordered when you hear "I need you down in 30 miles or less". The alternative is to create a waypoint using that FIX and hard code a speed and altitude into the CDU.

 

Then, using VNAV the MCP will vary the descent rate to meet the crossing restriction. It will usually be around 2,000fpm.

 

It probably sounds more complex than it is. If you post a plan here that you are having problems with it will help me understand what's going on.

Yeah I live on the Wirral so 5 mins from Liverpool.

 

I currently use the POSKY Boeing 737-800 but I'm looki at getting the PMDG series so might hold off until I get that.

 

Didn't have time to do the flight today however I'll try slowing right down before destination and if I still struggle I'll post a flight plan im using however I am using default ones fsx loads

Ah, the posh part of Merseyside! :wink:

 

Your EGGP-EGAA flight has a cruise level of 240. That should work okay. The Posky a/p doesn't have a CDU but the PMDG series does so that will make life easier.

 

Make sure your descent speed stays around 280kts.

EGGP-EGAA worked fine with a descent speed of 240kts with speedbrake at -2400 fpm.

 

I then wanted to practise descending from FL300 therefore I slowed right down about 80mi from airport, at 75mi was told to descent to FL280 from FL350 and i did so (I added a VOR to flight plan at 75mi from airport)

 

At FL270 I was told to come down to FL110 and that they needed be down in 30mi or less, I was then descending at -3100fpm with speedbrake at 250kts and I made it!!

 

I'm now editing all my flight plans and would like to thank you all loads for all the help

Glad it worked for you Deeb. If you were at FL300 for EGAA-EGGP that is too high which is why you didn't have much time to get down and had to use the speedbrake.

 

One of my test flights is EGCC-EIDW and cruise is FL180. EGCC-EGLL is FL210. Any higher and I would struggle to meet the crossing restriction.

No I did an international flight at FL300 in America I test on the flight plan that was failing last time and its working!!

 

Again, thanks guys