dvis3yzawwgr9p4du4g7rcqsie1vi7

Legal Alternate Airports (And the “3 Rs”)!

Published on

in

A common problem on all flight tests, but especially for the instrument rating and CFI-I evaluation, is understanding the need for alternate airports, and how to analyze conditions for their suitability. The basic premise behind all the FAA regulations is that every “pilot in command” is required to research and plan an alternate airport. That is for all VFR flights “not in the vicinity” but especially IFR (with limited allowable exceptions).

Alternate airport means an airport at which an aircraft may land if a landing at the intended airport becomes inadvisable.

§91.103 (that preflight “all available information” reg.) requires alternates for all flights; VFR “not in the vicinity” and in controlled airspace under IFR (except in certain exceptions):

This information must include —  For a flight under IFR or a flight not in the vicinity of an airport, weather reports and forecasts, fuel requirements, alternatives available if the planned flight cannot be completed, and any known traffic delays of which the pilot in command has been advised by ATC;

Basically, in §91.103, the FAA is requiring due diligence on all the popular ways to kill yourself in an aircraft. Every well-trained pilot should pay attention and comply with this basic guidance. But DPEs still get applicants showing up for flight tests without calculating their take-off and landing performance – and sometimes they have never done it ever. A recent flight test candidate for an instrument rating had over 200 take-offs and landings at his “home field” and did not even know the length of the runway – guessed 3K when it was actually over 5K! (“I thought I only needed that was just for the private test…”)

IFR Alternate Requirements

For planning an IFR flight in controlled airspace, a flight plan is required under §91.169 and an alternate must be specified (except with limited allowable conditions).

§91.169 IFR flight plan: Information required.

(a) Information required. Unless otherwise authorized by ATC, each person filing an IFR flight plan must include in it the following information:

(1) Information required under §91.153(a) of this part;

(2) Except as provided in paragraph (b) of this section, an alternate airport.

The default FAA position for IFR planning (just like VFR “not in the vicinity”) is to research and select a suitable alternate airport. In IFR regulations, relief is found in §61.169 (c): “IFR alternate airport weather minima.” If weather forecasts predict a pilot can descend from the MEA in forecast VFR weather conditions – no alternate airport (or even instrument approach procedure) is required.  Also if the airport of intended landing is forecasting “pretty good MVFR conditions” (that famous 1-2-3 guide), no alternate needs to be filed. But how do we know what the weather will be down the road an hour or two from now? What are the “legal forecasts” for my destination and for my alternate airports?

Legal Weather For IFR Planning

Certainly, if it is “clear blue sky” at the destination and an official weather product says so, you are legal (and safe) to proceed. But if the weather is low and crappy with widespread instrument conditions forecast, a Terminal Area Forecast (TAF) is required and/or a pilot must plan a legal alternate (depending on conditions). (For Part 91 operations, the newer MOS is legally acceptable for your weather decision also). Remember, you do not have to fly to your filed alternate, this is a required “escape plan” for the IFR flight plan. Traditional area forecasts, do not go below a 1000 ft ceiling, so forecast IFR conditions at your destination with no TAF require an alternate! MOS data, properly derived and interpreted, can provide a legal remedy for Part 91 operators in these cases. Remember, the FAA default position for filing IFR is the specification of an alternate airport (this also means extra fuel; see this FAA Legal Opinion on what those 45 minutes include, Also NTSB).

Don’t Be Fooled By EFB

ForeFlight (and many other EFBs) are very helpful in providing an amazing array of weather products. But it is a serious mistake to assume that because you see a TAF listed on the app this is legal for your flight planning (check TAF limitations). In the example below, KMMU is 13 miles from KEWR. If the weather in the area is forecast to be IFR, the TAF you see on your app. is not legal for determining an alternate (no TAF at KMMU, no way to determine 1-2-3). Using traditional weather products, an IFR alternate is required, and that planned alternate airport also needs some way to determine legal weather, with acceptable conditions for the IFR runway in use. (and watch for alternate “NA” and non-standard alternate minimums). More on LAMP/MOS and the newer GFA below.

Flight test applicants (even CFI-I candidates) really struggle with “legal weather” for IFR. Merely pointing to the EFB and parroting “800/2 or 600/2” is not really enough (you will not be safe in the clouds). Also assuming any mobile app is correctly importing and displaying LAMP data may be hazardous. (there are many different algorithms at work here). Without a reliable weather forecast at your destination in forecast IFR conditions, it’s a good idea to pick a pretty big airport (usually a Delta with a TAF) for your planned alternate. You want to reliably determine the required 600/2 800/2 and you also want some “big city” services (see “3Rs” below)

TAF vs “MOS Magic”

There is a new forecast option (but only legal for Part 91) called the Localized Aviation MOS Program (LAMP) point forecast. Many of you might be familiar with the Model Output Statistics (MOS) seen on ForeFlight and other EFBs.  Since the FAA does not specify which forecast you must use to determine the conditions in 91.169, you can pick your options. The FAA requirement is only to obtain “appropriate weather reports and forecasts, or a combination of them” for naming your destinations and determining an alternate (not available to Part 135 and 121 yet). Computational models are valid and have a pretty good level of detail to determine the local weather accurately. The ceilings and viz, as currently specified, need a little massaging to align with FAA requirements but GFAs are updated hourly and very accurate. But just like any single source news, too much reliance on one data stream may be dangerous. Always start with the larger synoptic picture and build a thorough weather picture for safety.

LAMP forecasts are computationally derived (no human hands) and recently became available on the 1800wxbrief website from over 1800 locations. By contrast, there are only 750 airports with TAFs. Studies have indicated that LAMP forecasts are more accurate than human-developed TAFs. IT seems TAFs tend to err more frequently on the side of caution due to human intervention. But maybe there is an advantage to the many years of meteorological experience behind every TAF. MOS forecasts are more frequent and prolific but are not approved yet for Part 135/121 operations  (barely out of “clinical trials.”)  Another current issue you may detect is that each mobile App might import computational data differently. Raw LAMP data direct from the NWS will be more accurate until a standard algorithm is decided for mobile app.  imports.

What are the “3 Rs” for Alternate Planning?

@safepilots (IG)

I tell my flight students that realistically (and in the interest of safety) a required alternate airport should meet the “3 R” rule. Remember a miss in low IFR for a GA pilot is “almost an emergency” and you really did not want to end up at this alternate. Your “sure bet alternate” should have Radar, Restaurant, and Rental Cars (in addition to those legal weather requirements)! “Big-city services” are essential for your personal (and passenger) comfort. I am continually amazed that pilots pick some small part-time rural airports, with a non-precision approach and no weather forecasting as a viable alternate airport when they are flight planning. What exactly are you going to do now that you (maybe) successfully landed (the family or customers in the back are *not* going to be happy)? Fly safely out there (and often)!


See “SAFE SOCIAL WALL” For more Resources

Join SAFE and get great benefits. You get 1/3 off ForeFlight and your membership supports our mission of increasing aviation safety by promoting excellence in education.  Our FREE SAFE Toolkit App puts required pilot endorsements and experience requirements right on your smartphone and facilitates CFI+DPE teamwork. Our newly reformulated Mentoring Program is open to every CFI (and those working on the rating) Join our new Mentoring FaceBook Group.

11 responses to “Legal Alternate Airports (And the “3 Rs”)!”

  1. Roger Harris Avatar
    Roger Harris

    Notwithstanding the limitations of a TAF and just plain common sense , is there a legal interpretation that supports the statement that, lacking a TAF at your destination, you MUST file an alternate?

    1. Roger Harris Avatar
      Roger Harris

      I guess I should have added that I’m wondering about the use of other forecasting tools such as MOS, Prog charts, Forecast discussions, SkewT, GFAs etc.

    2. David St. George Avatar
      David St. George

      The FAA does not specify the weather products required to determine the weather conditions for Part 91 operators. Currently, the only FAA weather product that fulfills the requirements due to location and specificity is a Terminal Forecast. The FAA in their Letters of Interpretation (and the NTSB in their many rulings when pilots are violated) repeatedly specify a weather forecast “at the destination airport” and that is a TAF. Previously, TWEB route forecasts (long since discontinued) were accepted as a “terminal weather forecasts” also.

      To be clear, if weather is VFR, the resolution of other products meets the need and are acceptable. Only when IFR conditions are forecast in the less granular NWS products, does a TAF become necessary to achieve the level of precision in 61.169 (both for destination and determining a planned alternate). This level of detail is seldom the real problem. Pilots tend to accept anything they see on their phone as an “acceptable weather source” regardless of location and this creates a clear safety problem.

  2. DH Avatar
    DH

    Thank you for this! I’m curious though, in your example you used an airport 13 miles away. This, of course, is outside of the TAF terminal area but about about an airport 10-5 SM away? 5 or less SM? It seems that in your article you are saying that unless the TAF is located at the airport it’s unusable for IFR.

    1. David St. George Avatar
      David St. George

      A TAF is created for the airport listed obviously, but has a 5 mile effective range. Maybe KCKV (Outlaw Field)🤣

    2. David St. George Avatar
      David St. George

      And please see below on the usage of a MOS forecast. Certainly the migration of this product to the Leidos preflight briefing site is a sign that this technology is maturing. You do have the detail required to make a decision (for Part 91 operations). What you use is essentially your call….

  3. Daniel Avatar
    Daniel

    I tried to comment before but it’s not showing up. I’ll ask again. It seems like you are saying that unless the TAF is located at your airport destination or at your alternate it would be unusable. In your example you used an airport 13 miles away (outside of TAF terminal area) but what about one inside terminal area (10-5sm) or even closer (5-1sm)?

  4. Scott Snider Avatar
    Scott Snider

    I disagree TAFs are the only NWS forecasts that provide location, visibility, and ceiling specificity. LAMP/MOS forecasts provide all three.

    Raw LAMP data are made for a specific location. Codes for each location provide visibility and height ranges, .e.g., a visibility value of “4” or above indicates visibility is 2 or more miles. A “4” or higher for ceiling indicates ceilings are 1000’ or higher. The visibility ranges match with the alternate airport minimums for precision or non-precision approaches. The ceiling ranges are higher than the alternate airport minimums for both approach types which would provide a more conservative decision point.

    Some 3rd party interpolated MOS forecasts, e.g., in Foreflight, provide more granular ceiling data, e.g., ceiling of 700’; however, I haven’t investigated how those data are derived. For non-towered airports, I use the raw LAMP/MOS data.

    https://vlab.noaa.gov/web/mdl/lamp

    Scott

    1. David St. George Avatar
      David St. George

      Thanks for the comment Scott. I should have been more clear that under part 91, you can basically use whatever you want; FAR 91.167 and 91.169 just say “appropriate weather reports and forecasts, or a combination of them” for destinations and alternates (call the local airport manager?) I am more used to the very specific weather sources for Part 135 and 121 operations (required when innocent lives are at stake). MOS certainly has the advantage of many more locations ~2000 locations, whereas TAFs are only generated for 750 (usually bigger) airports. TAFs rely on human intervention and judgement rather than AI tools. I still maintain if you miss, you really want to go to a *big* airport with “big city” services.

      Ultimately, our FAA is actually very permissive for Part 91 operations and you can certainly use computer generated point forecasts if you want. The FAA tends to say “go for it” when innocent lives are not at risk (Part 91 zero-zero IFR take-offs and also shooting approaches to airfields below minimums). For Part 91 you really have to decide your level of risk. https://bit.ly/SAFE-91 Technically you can legally still dead reckon in the NAS, and I have not seen a transponder mentioned as required equipment in 91.205 for flying IFR either. So pick your tools.

      In my personal opinion (and experience flying 135 jet operations) the LAMP system (Localized Aviation MOS Program) still suffers from what we are currently seeing with the widespread deployment of other AI tools; occasional crap mixed in with some pretty amazing results. To me, it is not ready for the big time quite yet. We do not use these (yet) as approved sources in professional flying.

      From what I have seen the MOS point forecasts are pretty accurate where there are lots weather sources, but they fail badly especially where you need them most: in the worst terrain and weather. I personally value the input from a human meteorologist massaging the data in a thoughtful way based on experience. For this same reason, TAFs have been proven in studies to be wrong more often and err on the side of caution since they are written by real humans. I love the data and level of detail in the MOS, but I will file an alternate. I think this will change with some future approvals for 135/121 operations, when this tool is more completely tested and verified.

      Interestingly, the MOS system has recently moved from the “The Meteorological Development Laboratory” to the NOAA Virtual Lab

      I wrote a note to Dr. Scott Dennsteadt (with whom I have discussed this many times – he owns a Phd and a CFI-I) and maybe he will write a note here and help us all out 🤣

      1. Scott Snider Avatar
        Scott Snider

        David,

        The LAMP/MOS forecasts and TAFs can miss the mark. Many TAFs are only issued on the prescribed 6 hour schedule. The LAMP/MOS are almost always updated more frequently than TAFs depending upon which weather model is employed. This could provide better temporal forecast resolution.

        I prefer Skew-Ts for the arrival time over other sources, however, having all the tools and being able to integrate the various data points is a wonderful aspect the NWS weather data compared to what is available to pilots from other country’s meteorological services.

        I can only hope pilots use more than either TAFs or MOS (and METARs) for their weather planning. My observation is this is often not the case. Though the atmosphere is our “home” when flying, I’ve found many pilots weather knowledge is, unfortunately, lacking. I’m sure you see this during checkrides.

        As you noted, Part 121 and 135 Op Specs provide strict guidelines for most, if not all, areas of operation including weather data sourcing.

        Scott

  5. Roger Harris Avatar
    Roger Harris

    David, thanks for clarifying. I was certainly under the impression that the discussion was focused on Part 91 operations and generally think of this venue as a Part 91 hangout.

Tell us what *you* think!

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Thanks for Visiting!

Thank you for visiting the SAFE Blog. There are over 500 specifically tailored articles covering a wide range of aviation issues related to flight training both as a pilot and as a CFI. Search HERE for a specific article, and Join SAFE

Please try our new AI Tool (Chat 5.2 trained on SAFE Blog content) for your specific topics of answers to your aviation questions. SAFE crafted AI Tool


Notification Here!

Stay updated with our latest tips and other news by joining our newsletter.


Free SAFE Toolkit App

Everything a busy CFI needs at their fingertips, *plus* resources for pilot applicants: “Checkride Ready” (with all the DPE advice on how to pass your practical test) FREE Download

Discover more from Aviation Ideas and Discussion!

Subscribe now to keep reading and get access to the full archive.

Continue reading