- Joined
- May 11, 2010
- Messages
- 20,740
- Location
- Charlotte, NC
- Display Name
Display name:
Snorting his way across the USA
Flying IFR in CAVU hardly keeps you proficient. You're just flying VFR on a prescribed route.
There are two parts to being proficient at flying IFR. One of them is flying the airplane by reference to instruments, the other is being proficient in using the system. You can most definitely maintain the use of the system proficiency by filing IFR in VMC.Flying IFR in CAVU hardly keeps you proficient. You're just flying VFR on a prescribed route.
I'd prefer to transit at 1500 min altitude, more time to devise a solution if the engine quit. However, my home drome sites under a 1500 B shelf, so I transit the 5.7 nm at ~1300MSL to get to the practice area, which is an additional 8.3nm to get out of the B airspace. You'd be legal VFR in your scenario to go at 900, but it's a risk left to pilot discretion.
I have found that at some large airports (ie KLAS), they seem to be a bit "confused" on how to handle VFR traffic. From my experience, VFR traffic is told to "go away" more often. For example, I was coming into LAS and was told that there would be a "90 minute delay" for VFR arrivals. WTH!?
Ceilings 2400 BKN. Flight distance 10nm. Forecast to break up by noon. Flight time 0915a. Not worried about the extra time in route. More concerned about delays. Field elevation 1000. Descending toward destination. Visibility 10nm.
Everybody has an opinion, lets hear it!
So we're all agreed that VFR is ok and this is not technically scud running - can we all agree that flying at 2500'MSL with ground level between 600 and 1000' and a cloud deck at 3000' leaving you anywhere from 1900 - 1500 of space beneath you is not the safest VFR evolution in the event of engine malfunction -
Assume that I'm traversing the distance at about 135-140knots IAS from gear up to level off at my destination, I'm light at about 2400lbs - so - I'll buy some distance slowing from 140kts to 75 or so which is Vg in the event of engine failure so I have maybe 2 minutes to find a place to land . . .
Thats scud running in my book - when you have 2 minutes to set up a place to land in the event of engine failure means you have no options essentially.
We can play a technical name game all we want - but if you have 120 seconds [and likely less] to find a place to land in the event of loss of engine power - you have significantly lowered your safety margin in the Los Angeles basin.
10 miles between airports? That's practically overlapping traffic patterns!
it all about risk tolerance. I have more than a thousand hours flying traffic reporters over the DC area at about 1200 AGL. Flying low was necessary for the airspace, as well as giving the reporter a good opportunity to see the traffic. As such, I maintained a mental database of potential landing spots. I disagree about having no options...you always have options--some are just better than others. The key is to find the survivable ones.
And remember, unless you take off from two mile long runways in the middle of the desert, there's always some point were you're going to be low with few options in the event of engine failure.
Regarding scud running, I consider that a situation where the clouds push you lower and lower. Here you had plenty of outs and a airport never more than five miles away.
So, how high would you have gone - for a 10nm flight - if clouds were no factor?
The only reason I would file IFR, is that it is the LA basin. And, although I've flow there numerous times, I am not THAT familiar with the area. Filing IFR is just a lot easier.
Put new numbers in the box.......do what you've done a thousand time before.
It is a 10 mile flight............ One traffic pattern overlaps the other one..
if thats the case . . . . some people need to understand a pattern!
in general you're right, but the spreading cancer of windmill farms is a double edged sword. On the one hand they're an obstacle you need to avoid. On the other hand there are so many of them and they are so easy to see, you can use them to navigate visually in some pretty poor conditions.This might not be anywhere near as dangerous in Kansas or Nebraska, Iowa or Illinois where there are open fields everywhere...
So we're all agreed that VFR is ok and this is not technically scud running - can we all agree that flying at 2500'MSL with ground level between 600 and 1000' and a cloud deck at 3000' leaving you anywhere from 1900 - 1500 of space beneath you is not the safest VFR evolution in the event of engine malfunction -
Assume that I'm traversing the distance at about 135-140knots IAS from gear up to level off at my destination, I'm light at about 2400lbs - so - I'll buy some distance slowing from 140kts to 75 or so which is Vg in the event of engine failure so I have maybe 2 minutes to find a place to land . . .
Thats scud running in my book - when you have 2 minutes to set up a place to land in the event of engine failure means you have no options essentially.
We can play a technical name game all we want - but if you have 120 seconds [and likely less] to find a place to land in the event of loss of engine power - you have significantly lowered your safety margin in the Los Angeles basin.
This might not be anywhere near as dangerous in Kansas or Nebraska, Iowa or Illinois where there are open fields everywhere - but being at such a low altitude adds significantly to the risk and why I refer to it as scud running - the risk is from the lack of a place to land safely not from the low cloud level - but the combination of MVFR and lack of places to land . . .
if thats the case . . . . some people need to understand a pattern!
Were you flying:
A - C182
B - C206
C- Turbine Helo?
If the answer is C - your MTBF is a lot higher than any fixed wing piston powered aircraft . . .