Guidelines for submitting Regional Airline Schedules


Best if you print this document.

If you have information, including schedules, on a Regional Airline anywhere in the world that flew DC-3s we invite you to add its schedule to this webpage.

Here are the guidelines for submitting a new Regional Airline. Although it looks like a lot of steps, after doing one flight you will zip through them in no time at all.

  1. Tell us briefly about your Regional Airline, including a URL if possible, before starting any work. Although unlikely, we don't want two pilots submitting information on the same Regional Airline.

    We define a Regional Airline as one that has about ten to thirty one-way flights.

  2. Once approved, we request four items:

We will work with you if any of these present difficulties. Our goal is to post additional Regional Airline Schedules, not to put roadblocks in your path.

FSNavigator Flight Plans
  1. When selecting airports try to avoid the behemoth, International airports with their 10,000 ft. parallel runways. Airports of that size did not exist during the era of the DC-3.

    Using FSNavigator search the area of the selected city for a suitable airport. Airports with the designation "Municipal" are frequently the original airport that served a city and make a good choice.

    I usually start at the MS Aircraft directory and do a city search, jotting down all the airports with an ICAO Code that begins with the letter "K" ... for the US. Then I check out each of them for suitability.

    There are rare occasions where the best airport is not a "K" code (T27 for El Paso, Texas, for example), so keep your eyes open when in FSNavigator doing the airport search.

  2. Start and end the FSN Plan at the AIRPORT, not at a Runway. Do this by clicking on the small brown dot in the aircraft diagram in FSN then clicking "To Flight Plan." See "Tips" below.

    We avoid designating runways since so many pilots now use "Real Weather" which will dictate the correct runway. Others may choose whichever runway is optimum.

  3. Try to minimize the use of VORs which were only becoming popular towards the end of the DC-3's career.

  4. If an NDB is past the destination airport, select the NDB and send it to the Flight Plan. Then, in the Flight-plan" section of FSN at the top of the screen, right-click that NDB and designate it as a "bearing point." This provides the directional information that the pilot must fly, and you would still select the airport with FSN which will provide the distance information.

    Place the Bearing Point in the FSN plan immediately before the destination airport. Once you give this a try you will see how it works.

  5. Take note of the range of the Navaids as you designate them. In FS2002 and FS2004, most NDBs have a range of 38nm, although some are higher.

    It's perfectly OK to designate Navaids farther apart than their range. For example, two NDBs could be 60nm apart. The pilot would then fly from NDB "A" towards NDB "B" using Dead Reckoning until "B" was received. More on this in the "Flight Description" section below.
FSNavigator Tips

Here are some FSN techniques that I use which greatly speed-up creating flight plans. They are best shown by working through an example flight.

  1. Create a flight where your DC-3 is at 10,000 ft altitude.
  1. Locate airports of interest using FSN. Let's look for "KPVC" in Provincetown, Massachusetts, and "KHFD" in Hartford, Connecticut, for our proposed route of flight.
  1. Select appropriate Navaids.
  1. Altitude Information
The Written Flight Description

You're on the home-stretch, now. Two examples and you'll be ready to go. If you have Microsoft Excel you will find it easiest to prepare the written flight descriptions because of its natural rows and columns needed for tables.

Set the page-setup to "Landscape" to print across the wide dimension of your paper.

We will begin with a very simple flight from Phoenix, Arizona, KIWA; to Tucson, Arizona, KRYN. All NDBs are within range of the one before it and the last NDB is on the landing field. We will leave it up to the pilot to determine the best cruise altitude.

SW_XXX_01 76 Phoenix Tucson Dep Phoenix 145deg to AVQ NDB, 245.0; to RYN NDB, 338.0; on Field, Land Tucson. KIWA-KRYN

The details:

The second example will be for the flight that we created above, Provincetown to Hartford. We will assume a 4500 ft cruise altitude, also.

SW_XXX_02 117 Provincetown Hartford Dep Provincetown 280deg DR to IHM NDB, 220.0; and climb to 4500 ft; DR 266deg to HF NDB, 244.0; then 004deg for 6nm, Land Hartford. KIWA-KRYN

Additional Description Details

Return to top of document