Rndmtrvlr
Pre-takeoff checklist
I attribute my bacon being saved to his training on a couple of occasions.
And since I've grown particularly fond of my bacon . . .
I attribute my bacon being saved to his training on a couple of occasions.
I don't teach students to go below MDA with the hood on period. If their hood is on and they hit MDA they better be going missed.Wow we must all have the same Satan! He sure gets around!
If we're not in actual, mine prohibits me from ever taking off the foggles from simulated zero-zero takeoffs to, 'oh the MDA/DH is 769, go to 300ft' (150ft above rwy elevation) and then take them off and land
There is some value in doing some of the training with the full panel, else you won't know how to do it in the real world and truly use all the resources you have.and we are always partial paneled in some way.
I'm with Jesse. Folks need to be in the habit of going to MDA and staying there, not continuing down. Not to say that one might not set a lower-than-published MDA/DA for a specific purpose (or higher, for that matter, say, when arriving in good VMC for a circling approach with other aircraft in the pattern), but it will be established before commencing the approach, and if the hood is still on when the MAP is reached, the missed approach had better be initiated.I don't teach students to go below MDA with the hood on period. If their hood is on and they hit MDA they better be going missed.
That's a better way of wording what I intended. My wording almost implies that I meant the moment you hit MDA you go missed. What I meant is that you don't go below it period with the hood on.I'm with Jesse. Folks need to be in the habit of going to MDA and staying there, not continuing down
I'm with Jesse. Folks need to be in the habit of going to MDA and staying there, not continuing down. Not to say that one might not set a lower-than-published MDA/DA for a specific purpose (or higher, for that matter, say, when arriving in good VMC for a circling approach with other aircraft in the pattern), but it will be established before commencing the approach, and if the hood is still on when the MAP is reached, the missed approach had better be initiated.
And I don't teach zero-zero takeoffs, either. The hood may go on right after liftoff, but not until the aircraft is airborne. No earthly reason for practicing blind runway tracking, and a whole lot of risk (including to the instructor's ticket) if something goes wrong.
I agree and I think that demonstrating/teaching a simulated zero/zero takeoff is stupid even if there was no risk in that it might give the student the false impression that the real thing is acceptable.And I don't teach zero-zero takeoffs, either. The hood may go on right after liftoff, but not until the aircraft is airborne. No earthly reason for practicing blind runway tracking, and a whole lot of risk (including to the instructor's ticket) if something goes wrong.
IR student (still). A 0-0 takeoff is not in the cards in my book. If something went wrong, how do you plan on getting back to the field?
I don't teach students to go below MDA with the hood on period. If their hood is on and they hit MDA they better be going missed.
There is some value in doing some of the training with the full panel, else you won't know how to do it in the real world and truly use all the resources you have.
Just what significant aircraft control skills are built by doing a takeoff under the hood that aren't built by looking out at the runway centerline?Second, We do them as an exercise in accuracy in controlling the aircraft.
Only if the approach light system is already in sight, and if the hood is still on, the ALS is not in sight.Fourth, In reality, as you know, going below MDA finding the runway environment 100ft above TDZE is legal,
Just what significant aircraft control skills are built by doing a takeoff under the hood that aren't built by looking out at the runway centerline?
Only if the approach light system is already in sight, and if the hood is still on, the ALS is not in sight.
Fourth, In reality, as you know, going below MDA finding the runway environment 100ft above TDZE is legal, not that I would fly to that descent point at this time in my experience (or ever for that matter) BUT the point being, that should I NEED to in an event in which the safety of flight has been compromised, it's not an exercise for which I have never had the opportunity to practice. I didn't say that every approach goes below MDA/DH.
Lighten up and give some people credit here folks.
91.175 (c) (2)paraphrasing: as long as the flight visibility is not less than the visibility prescribed in the SIAP being used and (3) (i) approach light system and (ii) through (x) describe various runway environment identifiers for visual references (including and in addition to the runway lighting system, but not the runway lighting system exclusively) to the intended runway as being distinctly identifiable and to the pilot...allows the pilot to go down to 100 feet above the TDZE.
Ron: as you know, the approach light system in 91.175 is one of the allowed circumstances (91.175) (3) (i) Read part (91.175) (3) over: "At least one of the following visual references for the intended runway is distinctly visible and identifiable to the pilot" then it goes on to list (i) through (x).
Bottom line. its a practice exercise in being able, if necessary, to fly to 100ft above TDZE and land the plane safely. Doesn't mean anything more than that.
As far as zero-zero takeoffs, well Ron, what can I say, its another environment in which to be able to control the aircraft in an unusual circumstance, and pay real close attention to airspeed and climb rate and pegging the DG bug to the runway heading while flying a departure procedure. YMMV
91.175 (c) (2)paraphrasing: as long as the flight visibility is not less than the visibility prescribed in the SIAP being used and (3) (i) approach light system and (ii) through (x) describe various runway environment identifiers for visual references (including and in addition to the runway lighting system, but not the runway lighting system exclusively) to the intended runway as being distinctly identifiable and to the pilot...allows the pilot to go down to 100 feet above the TDZE.
Ron: as you know, the approach light system in 91.175 is one of the allowed circumstances (91.175) (3) (i) Read part (91.175) (3) over: "At least one of the following visual references for the intended runway is distinctly visible and identifiable to the pilot" then it goes on to list (i) through (x).
Bottom line. its a practice exercise in being able, if necessary, to fly to 100ft above TDZE and land the plane safely. Doesn't mean anything more than that.
As far as zero-zero takeoffs, well Ron, what can I say, its another environment in which to be able to control the aircraft in an unusual circumstance, and pay real close attention to airspeed and climb rate and pegging the DG bug to the runway heading while flying a departure procedure. YMMV
If you're finding the runway environment at 100' you've already descended without having it in sight. Perhaps you meant to say "going below MDA ONCE finding the runway environment 100ft above TDZE is legal,"?going below MDA finding the runway environment 100ft above TDZE is legal,
OK -- big difference between that and making the trainee do the takeoff from brake release with no external references at all, which is something I've heard of some instructors doing, and which I flat won't do.For me, I was still looking out ahead, just through the restricted vis of the foggles.
Right -- but at least one must be visible, and if the hood is still on, none of them are.91.175 (c) (2)paraphrasing: as long as the flight visibility is not less than the visibility prescribed in the SIAP being used and (3) (i) approach light system and (ii) through (x) describe various runway environment identifiers for visual references (including and in addition to the runway lighting system, but not the runway lighting system exclusively) to the intended runway as being distinctly identifiable and to the pilot...allows the pilot to go down to 100 feet above the TDZE.
Ron: as you know, the approach light system in 91.175 is one of the allowed circumstances (91.175) (3) (i) Read part (91.175) (3) over: "At least one of the following visual references for the intended runway is distinctly visible and identifiable to the pilot" then it goes on to list (i) through (x).
That's fine if you have at least one of those things in sight, but I don't see the point of teaching people to go below MDA without one of them in sight.Bottom line. its a practice exercise in being able, if necessary, to fly to 100ft above TDZE and land the plane safely. Doesn't mean anything more than that.
Pretty darn unusual when you can't even see one runway centerline stripe/light in front of you, and in that circumstance, I think you'd have to be either crazy or under attack by the Hovitos Indians to try it.As far as zero-zero takeoffs, well Ron, what can I say, its another environment in which to be able to control the aircraft in an unusual circumstance
That works fine for me as long as the hood doesn't go down until after you're airborne, or at least after rotation when you'd lose sight of the runway centerline in a low vis takeoff anyway., and pay real close attention to airspeed and climb rate and pegging the DG bug to the runway heading while flying a departure procedure.
...which is why I like JeppShades -- I can from the right seat pop them up to simulate breaking out, and push them back down to simulate entry/re-entry into the clouds, and the trainee doesn't have to do a thing or pull the device off/put it back on -- just like the real thing. I can just tell the trainee that as long as the shades are down you're in the goo, if they go up you can see, and to react appropriately. The only thing it can't simulate is restricted visibility below the clouds, but there's no way to do that outside the sim anyway.As for looking up from under the hood at MDA/DH to land, nothing wrong with that, really...as long as you can see well enough to land. It just saves you the step of ripping off the hood and putting it back on again 60 seconds later.
The biggest problem with a 0/0 takeoff is not getting back in, it's finding the runway from which to take off. The second biggest problem is staying on the runway until you take off.Problem with a 0/0 take off is you can't get back in.
If I want to do that, I'll do it in the sim. That way, if we go off the runway, nobody gets hurt, no metal gets bent, and I keep my ticket. Otherwise, I don't see the likelihood of that occuring as being large enough to cover the risk of something going wrong.The value in a simulated 0/0 takeoff is getting the student to realize that if they ever for some reason lose visual reference during their takeoff roll it is very possible to maintain control and stay on the runway using the DG. Without them seeing this during training ts not likely they'd know what to do.
Honestly, I don't see it as being a bigger risk then some of the first takeoffs I do with private students. Those can be way more...exciting. I'm not saying the risk / benefit make sense, but to some instructors it may.If I want to do that, I'll do it in the sim. That way, if we go off the runway, nobody gets hurt, no metal gets bent, and I keep my ticket. Otherwise, I don't see the likelihood of that occuring as being large enough to cover the risk of something going wrong.
If I want to do that, I'll do it in the sim. That way, if we go off the runway, nobody gets hurt, no metal gets bent, and I keep my ticket. Otherwise, I don't see the likelihood of that occuring as being large enough to cover the risk of something going wrong.
When I do that with a brand new primary trainee, my feet are usually resting on and often blocking the rudder pedals, and I'm talking a constant stream. We do that over and over until the trainee has it because it has to be done. If once you become an instructor you want to do that on most every takeoff with your trainees during IR training (because it will take quite a few to get it right and usually there aren't that many takeoffs in IR training), go ahead. But since I hope none of my trainess will actually be doing zero-zero takeoffs, I'd much rather use those takeoffs work on the transition from visual to instruments after takeoff which a) they will do a lot, and b) too often kills people.You don't have rudder pedals in front of you? You're actually in clear VMC, You can see the runway to correct, the student can't.
Heading control - plain & simple.Just what significant aircraft control skills are built by doing a takeoff under the hood that aren't built by looking out at the runway centerline?
I've done a zero-zero take off. Well, more like 0-20. It had been a clear night, and it was a perfectly clear morning without a cloud in the October sky. I had my sunglasses on for the drive to the airport. Get to the airport...fog. Only at the airport. 1/4 mile in any direction, nothing. But at the airport, no visibility at all. Heard guys on the CTAF flying over "Only the airport is fogged in, everything else is fine."
Climbed in the plane, taxied out, couldn't even see the next stripe on the runway as I was on my takeoff roll. Less than 2 seconds after Vr, clear and a bazillion. Flying around the only places that still had fog were rivers (one wraps around the airport) and small lakes and ponds. Would have been stuck there for another 2 hours had I waited for it to burn off.
It's not a rating you need, it's testicles the size of cannon balls, and based on a number of Ed's posts, I believe he has them.What rating do I need to obtain to be able to do THAT?
Note the sarcastic tone
I said "a number of," not "the number of."Hmmm......and you have 2100 more than Ed...what are you trying to say, Ron.
I said "a number of," not "the number of."