chemgeek
En-Route
- Joined
- Dec 5, 2009
- Messages
- 3,111
- Display Name
Display name:
chemgeek
If you are going to fly IFR in potential IMC conditions, you should ALWAYS be both proficient and prepared to fly approaches to minimums. The weather forecast doesn't care what your personal minimums are. Personal minimums are for planning and risk mitigation, not hard stops about what you are competent to fly.
For any IFR flight, you are never committed to arrive at your planned destination. If weather conditions change and become untenable, one seeks nearest VFR or simply lands at an appropriate alternate airport with workable weather for an approach. The easiest way to get into trouble is to commit to arriving at your destination come hell or high water. Sometimes the forecast weather doesn't cooperate. On my first IFR trip after getting the rating, I flew on a fall business trip at near max range on a lovely late summer/early fall day. What was forecast to be a trip in severely VFR conditions started to go sideways when an afternoon squall line 75-100 miles west started drawing cool, moisture-laden air inland from the Atlantic, causing ceilings to drop to MVFR conditions quickly with a solid, thick undercast along the coast. I wound up being #4 or 5 on the ILS to BHB on a forecast VFR day. I had plenty of outs and PIREPS to monitor actual weather, and it was no big deal if I was late the the meeting by a few hours or even a day. But you never know what will happen en route, so you should always be prepared when filing IFR.
In a simple light single with no icing protection, the typical use of the IR is to take the uncertainty, stress, and safety compromise out of flying in MVFR conditions. A typical IFR trip for me is departing in MVFR conditions with uncomfortably low ceilings for VFR XC, popping out on top or between layers for cruise and a smooth ride, and making an IFR descent through the cloud deck at the destination. Occasionally, you get to actually fly an approach. If significant icing is suspected or expected in the IFR climb or descent it is normally a deal-killer. BTDT, unintentionally, during an IPC, and not that much fun. (A good education, though. Lake effect clouds can ice you up in one big hurry.)
For any IFR flight, you are never committed to arrive at your planned destination. If weather conditions change and become untenable, one seeks nearest VFR or simply lands at an appropriate alternate airport with workable weather for an approach. The easiest way to get into trouble is to commit to arriving at your destination come hell or high water. Sometimes the forecast weather doesn't cooperate. On my first IFR trip after getting the rating, I flew on a fall business trip at near max range on a lovely late summer/early fall day. What was forecast to be a trip in severely VFR conditions started to go sideways when an afternoon squall line 75-100 miles west started drawing cool, moisture-laden air inland from the Atlantic, causing ceilings to drop to MVFR conditions quickly with a solid, thick undercast along the coast. I wound up being #4 or 5 on the ILS to BHB on a forecast VFR day. I had plenty of outs and PIREPS to monitor actual weather, and it was no big deal if I was late the the meeting by a few hours or even a day. But you never know what will happen en route, so you should always be prepared when filing IFR.
In a simple light single with no icing protection, the typical use of the IR is to take the uncertainty, stress, and safety compromise out of flying in MVFR conditions. A typical IFR trip for me is departing in MVFR conditions with uncomfortably low ceilings for VFR XC, popping out on top or between layers for cruise and a smooth ride, and making an IFR descent through the cloud deck at the destination. Occasionally, you get to actually fly an approach. If significant icing is suspected or expected in the IFR climb or descent it is normally a deal-killer. BTDT, unintentionally, during an IPC, and not that much fun. (A good education, though. Lake effect clouds can ice you up in one big hurry.)
Last edited: