So the other day as I was flying, I started to wonder:
All pilots should be familiar with basic VFR cloud clearance requirements in 14 CFR 91.155 (and if not, then go study now!). When flying piston airplanes, we probably spend most of our time in the Class E below 10,000 ft. arena:
This is great and all, but how can we actually determine how far away we are (especially vertically)?
I thought about using a sextant and some "simple math":
Unfortunately, I need to know my actual distance TO the cloud as well as my angle... A quick Google search found one of these, but I'm not so sure how it will work with a cloud:
In all seriousness though, how can we stay legal and safe when operating VFR in the vicinity of clouds?
While distances are hard for many people to estimate, time is much easier for many people to estimate. Pull out your trusty E6B, and work out the distance in terms of seconds.
For example, at a cruising speed of 110Kts (typical for many small GA student planes),
So if you cannot see where you'll be in 1:30, visibility is too low.
If you can fly to a cloud in less than 10 seconds, you're too close.
The answer, as best I can discern it from my training & my own experience, is "You can't!" -- every instructor I've flown with has said that cloud clearances are the most inadvertently-busted regulation, even when pilots are doing their best to obey the requirements.
Our eyes and brain are really good at judging distance relative to landmarks and objects of known size (that's how we can tell we're on a "3 mile final" or "8 miles out"), but without known references our ability to estimate distance quickly falls apart, and there simply aren't that many useful landmarks in the sky.
Judging lateral distance to clouds is, at least in my experience, generally easier than vertical distance - as long as you're a fair distance away from the cloud anyway.
You can roughly estimate the ground position of a cloud pretty easily (and if you can't you can always use its shadow and be pretty close). You can also usually find features on the ground of known size (runways, for example: You can get the length of the longest runway at a field from your handy VFR sectional), and figure out how many of those are between you and the cloud's ground position.
Also if you're doing this whole pilotage-and-navigation thing right you know where you are on the chart, and you can visually estimate the ground position of a cloud pretty easily (again if all else fails use its shadow and you'll be close). Break out your plotter and you can figure out how many miles away you are from the cloud (but inside about 3 miles this is going to get pretty difficult, and with your head in the cockpit mucking about with the chart and plotter you may wind up inside the cloud by the time you're done working up your estimate!).
A final close-in technique for clouds at your altitude is to use your wing. You know your aircraft's wingspan, and you can also say that roughly half that value is the length of one wing. Figure out how many "wings away" the cloud is, and do the math -- of course if you're at a distance where you can do that kind of visual estimation you're likely to be close to the cloud clearance limits.
Judging vertical distance is harder. The usual advice if you're below the clouds is to get the cloud heights from a local airports ATIS or AWOS and use that as a guide. If you're above the clouds PIREPs for cloud tops serve the same purpose.
Visually if you're above the cloud the same skills you use to judge your height above a runway will work. The catch is those skills really only work when you're within about 1000 to 2000 feet (i.e. "By the time you can really judge the distance you may already be too close!").
Coming up from below a cloud you're basically relying on judging your closing speed to an object of unknown / nebulous size: As you approach the cloud it's going to get bigger, but you don't really know how big it's going to get before you wind up inside it.
As a final visual cue in any direction, remember that clouds aren't clearly-defined boundaries - Often you'll see little wispy streaks of cloud around you as you're getting closer to the cloud you're trying to avoid (particularly when approaching from below). This is a pretty definitive indication that you're probably closer to the cloud than you should be, and you should start heading away from the cloud before you wind up inside it.
I think the best bottom-line practical advice I've ever gotten on cloud clearances, loosely paraphrased from a couple of the local CFIs: "Just stay way the heck away from clouds until you're instrument rated and on an IFR flight plan." and "If you think you might be too close to a cloud, get further away!" -- the latter probably being what the FAA is getting at with their statutory distance requirements.
So the other day as I was flying, I started to wonder: All pilots should be familiar with basic VFR cloud clearance requirements in 14 CFR 91.155 (and if not, then go study now!). When flying piston airplanes, we probably spend most of our time in the Class E below 10,000 ft. arena: This is great and all, but how can we actually determine how far away we are (especially vertically)? I... sure how it will work with a cloud: In all seriousness though, how can we stay legal and safe when operating VFR in the vicinity of clouds?
StallSpin's answer on the recent question about VFR traffic patterns has got me thinking about the "Remarks" section of the Airport/Facility Directory. We are all taught in training to review the AFD entry for airports we intend to visit (part of FAR 91.103's "become familiar with all available information" requirement), and to comply with any restrictions noted - typically things like "no touch-and-go landings", "Standard traffic pattern required of all aircraft", "Prior Permission Required for jet aircraft", etc. Aside from it being The Right Thing To Do, and avoiding the possibility
I hope this is a relevant place for me to ask a math question regarding aircraft design. I am trying to understand how one would implement a controller to control the pitch angle of an airplane for a small exercise. I understand the control part and its implementation. What I do not grasp is how one acquires the longitudinal equations of motions (which are then used for the control part) which serves as the starting point. What is the starting point or what are the principles used to derive these equations? If I know how to derive these equations for a very simple case, then I know I have
In Did this aircraft illegally exceed 250kts below 10,000ft? it was mentioned that unlike here in the US, EASA does not have a 250 kt. speed limit below 10,000 ft. So does this mean that are we allowed to go as fast as we want? Mach 8? ;-) What is the maximum indicated airspeed specified by EASA when operating in the European Union?
Something that just popped into my head: I've been on a few easyJet and Ryanair flights where a lot of passengers clap and cheer on touchdown. Would the pilots be able to hear this? Here's an example I found by searching YouTube: It seems pretty commonplace... but can the pilots hear them? I guess it would be distracting. Just something I was wondering!
I was looking at potential experimental projects when I read this fascinating website about a tiny aerobatic-capable twin-engine airplane. It's light enough to be an ultralight, but much too fast: Aside from the obvious fun of flying this little plane, I wondered whether: I'd be able to log time in the Cri-Cri as multi-time? My guess is yes. Assuming I'm MEL-IFR, could I log multi-IFR with a two-way radio, altimeter, Dynon-type AI, HI and at least one cert. VOR & glide slope? An approach cert. GPS setup would be too heavy I assume. My guess is this is wishful thinking...
the ground so the previous turn won't be able to intercept it. I could either omit the CD part or insert another CR (course to radial) before the CD leg but then I'm not doing what the map says, I improvise. So my question is am I conceiving this wrong, or the IAC is ambiguous in this particular point? ...I am building my own ATC simulator and for that purpose I need to include several instrument procedures. I have a problem with that particular one: My problem is on KEA transition, the leg between
Non-precision instrument approaches generally have altitude restrictions which get lower when you get closer to the airport. I always figured these restrictions were AMSL using the current altimeter... ground level. Although I don't see any obstructions that high during this segment of the approach, as far as I know instrument approaches are supposed to guarantee a 500 ft obstacle clearance, do... actually are (or, as most pilots prefer to think, you're lower than what your altimeter reads) Have a look at this VOR approach into Newark Most altitude restrictions are a minimum level, so
I've noticed that on some airlines (I may have seen it on SAS) the cabin crew had a small touchscreen at the front of the plane which they were using to select recorded audio messages etc, in both their language, and English. Searching the internet, I found out it's called a Flight Attendant Panel — here are some photos I found: So I gather they can control the lighting, and movies; but what else can these panels do? I also found a FAP trainer, which says: This virtual training environment generates a realistic FAP representation including OBRM, CAM and PRAM What
I was looking through my virtual radar logs one of the days and found this "glitchy" ADS-B behavior. I am almost 100% sure that this is not due to my antenna or setup since two independent different... is the "skew" at seemingly same angle? Is that anything? In light of MH370, does this happen often, how reliable is that GPS data? Tail # N657UA Boeing 767-300 Typical route between EGLL and KORD Time of occurrence is approximately: 3/16/2014 6:09pm CST I have also verified FlightAware is ALSO showing the same weird glitch. See below "yellow" highlighted airplane: Same A/C from FlightRadar24