![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Jim,
If the instructor spent more than an hour on showing how the autopilot coupling system works, then something is wrong. I think you got that wrong. What could be better than to learn about autopilot use from an instructor. Would you prefer to have the student figure it out on his own? Why? Students aren't encouraged to use coupled autopilots during training are they? As I said: The FAA's attitude on that has changed, and rightly so, IMHO. They adapt to the fact that more and more GA planes have autopilots, and that many accidents could be prevented if only the pilots knew how to use them beyond "hold the plane straight and level" mode. The Kennedy accident comes to mind as a perfect example. So, to answer your question: Yes, in a current training environment, students are encouraged to ALSO use coupled autopilots during training, if the aircraft is so equipped. I said "also", as in: in addition to hand flying. The FAA requires you to be able to use all eqipment in the aircraft and the PTS calls for a focus on autopilot usage if the plane is so equipped. IFR flying is not a macho contest about who can fly in the soup with the fewest instruments... FWIW, here in Germany, single pilot IFR requires an operational two-axis autopilot. One of the few country-specific regulations here that make sense to me. -- Thomas Borchert (EDDH) |
#2
|
|||
|
|||
![]()
Tom, et al,
I'm not advocating against autopilots at all, but I am suggesting that the student should not learn to rely on an autopilot. A check ride should test the student's ability to handle emergency situations. If the student can handle the emergency by demonstrating proper understanding, technique, and execution of the procedures you can rest assured he or she can handle the tasks when everything is spinning properly. I would be surprised if it took more than an hour in the aircraft to demonstrate the proper procedures for using an autopilot, hence my statement about it taking more than an hour. An autopilot is one of those things where a lot of classroom work and mockup work can be done to really reduce the time spent in the aircraft. I have never been in favor of a student making extensive use of autopilots during training because it relieves them of a lot of the multitasking work. Practicing workload management when things aren't all there to help the student is one of the benefits of having an instructor in the other seat. Learning instrument flying by spending more than just a little time coupled to the box is not the best use of the student's time or the instructor's skills. I don't agree with Germany's regulations on single-pilot IFR operations, but those decisions are often made for political expediencies. Single-pilot IFR is not an unmanageable task if the pilot understands his or her limitations, the limitations of the equipment being used, and has a reasonable set of personal minimums. Taking these decisions away from the pilot by mandating use of a 2-axis autopilot may be popular, but should not be necessary. Demonstrating that a student can fly a typically one-hour check ride by hand is not a macho task. There will typically not be more than one or two holds, three or four approaches, and some partial panel unusual attitudes. Although a typical instrument flight won't involve all of these elements in a one-hour period, this scenario is still very real world. -----Original Message----- From: Thomas Borchert ] Posted At: Wednesday, November 29, 2006 8:26 AM Posted To: rec.aviation.ifr Conversation: Instrument Check Ride - What navigation equipment can I use ? Subject: Instrument Check Ride - What navigation equipment can I use ? Jim, If the instructor spent more than an hour on showing how the autopilot coupling system works, then something is wrong. I think you got that wrong. What could be better than to learn about autopilot use from an instructor. Would you prefer to have the student figure it out on his own? Why? Students aren't encouraged to use coupled autopilots during training are they? As I said: The FAA's attitude on that has changed, and rightly so, IMHO. They adapt to the fact that more and more GA planes have autopilots, and that many accidents could be prevented if only the pilots knew how to use them beyond "hold the plane straight and level" mode. The Kennedy accident comes to mind as a perfect example. So, to answer your question: Yes, in a current training environment, students are encouraged to ALSO use coupled autopilots during training, if the aircraft is so equipped. I said "also", as in: in addition to hand flying. The FAA requires you to be able to use all eqipment in the aircraft and the PTS calls for a focus on autopilot usage if the plane is so equipped. IFR flying is not a macho contest about who can fly in the soup with the fewest instruments... FWIW, here in Germany, single pilot IFR requires an operational two-axis autopilot. One of the few country-specific regulations here that make sense to me. -- Thomas Borchert (EDDH) |
#3
|
|||
|
|||
![]()
Jim Carter writes:
Demonstrating that a student can fly a typically one-hour check ride by hand is not a macho task. There will typically not be more than one or two holds, three or four approaches, and some partial panel unusual attitudes. Although a typical instrument flight won't involve all of these elements in a one-hour period, this scenario is still very real world. One could argue that any IFR flight without an operational autopilot is an emergency, in which case the only type of IFR flight that one would need to verify without autopilot would be landing at the nearest airport. Although it apparently is not done this way in most jurisdictions now, I can see the logic in doing so. Essentially it would amount to little more than increasing the number of functional instruments required for IFR flight. I don't personally agree with legislating this, but basing testing on this assumption isn't necessarily unreasonable. -- Transpose mxsmanic and gmail to reach me by e-mail. |
#4
|
|||
|
|||
![]() -----Original Message----- From: Mxsmanic ] Posted At: Wednesday, November 29, 2006 6:23 PM Posted To: rec.aviation.ifr Conversation: Instrument Check Ride - What navigation equipment can I use ? Subject: Instrument Check Ride - What navigation equipment can I use ? Jim Carter writes: Demonstrating that a student can fly a typically one-hour check ride by hand is not a macho task. There will typically not be more than one or two holds, three or four approaches, and some partial panel unusual attitudes. Although a typical instrument flight won't involve all of these elements in a one-hour period, this scenario is still very real world. One could argue that any IFR flight without an operational autopilot is an emergency, in which case the only type of IFR flight that one would need to verify without autopilot would be landing at the nearest airport. Although it apparently is not done this way in most jurisdictions now, I can see the logic in doing so. One could argue that posting opinions of IFR requirements should require significant real, IFR experience too. It amuses me that so much of what was done 30 years ago, with less accurate technical toys is today seen as macho and Herculean. Single nav radio holds? Full ADF approach? Cross country without a moving map or GPS? Single-engine, night IFR? There are way too many opinions about the lack of safety of these practices by people who have little or no experience with them. Of course everyone must know their personal and equipment limitations. I just have a problem with setting the limits based on the least competent -- sort of like my problem with our public schools teaching to the lowest common denominator rather than expecting excellence as the standard. I'm really going to upset the apple cart now when I suggest that landing at the nearest airport isn't always the best choice in any situation. Even with a blown piston or swallowed valve, the engine can often get you someplace better than the closest airport. It always makes more sense to plan and execute a solution rather than just jumping to conclusions based on what the least skilled have decided we should do. An autopilot may be on someone's personal list of minimum equipment for IFR, but that doesn't mean it should be a mandate for all of us. -- Transpose mxsmanic and gmail to reach me by e-mail. |
#5
|
|||
|
|||
![]()
Jim Carter writes:
It amuses me that so much of what was done 30 years ago, with less accurate technical toys is today seen as macho and Herculean. Single nav radio holds? Full ADF approach? Cross country without a moving map or GPS? Single-engine, night IFR? There are way too many opinions about the lack of safety of these practices by people who have little or no experience with them. It's not so much that they are unsafe as that they are unnecessary. Maybe you could fly a 747 across the country with just a compass and a map. I don't see any technical obstacle to it offhand. But would you really want to, when there are so many technical aids to safe navigation? If all the fancy gadgets fail, is it better to cancel the flight until the gadgets are fixed, or press on with just the compass? People lived with simpler instrumentation. But more of them died, too. Why take the risk? Indeed, you don't really _need_ IFR. People used to fly without it. They used to fly without ATC. A lot of the time they survived. Sometimes they didn't. The current opinion, though, is that the losses were unacceptably high in those days, and so the risks that were accepted then cannot be accepted now. I'm really going to upset the apple cart now when I suggest that landing at the nearest airport isn't always the best choice in any situation. Even with a blown piston or swallowed valve, the engine can often get you someplace better than the closest airport. Better in what sense? With a failing engine, how could a distant airport be better than a nearby airport? A lot of pilots die because they want someplace "better" than the nearest airport, and then their luck runs out before they find that ideal spot. It always makes more sense to plan and execute a solution rather than just jumping to conclusions based on what the least skilled have decided we should do. I try to follow the path of least risk. Or more specifically, I try to manage the risk/benefit ratio. It's hard to see the benefit of staying in the air with a bad engine. What's wrong with landing and fixing the problem? An autopilot may be on someone's personal list of minimum equipment for IFR, but that doesn't mean it should be a mandate for all of us. I don't think anyone should be compelled to use an autopilot if he's flyingon his own. However, I would want an autopilot for IFR flight, otherwise--at least in my estimation--the aircraft really isn't suitable for IFR flight. -- Transpose mxsmanic and gmail to reach me by e-mail. |
#6
|
|||
|
|||
![]() -----Original Message----- From: Mxsmanic ] Posted At: Wednesday, November 29, 2006 7:06 PM Posted To: rec.aviation.ifr Conversation: Instrument Check Ride - What navigation equipment can I use ? Subject: Instrument Check Ride - What navigation equipment can I use ? .... I'm really going to upset the apple cart now when I suggest that landing at the nearest airport isn't always the best choice in any situation. Even with a blown piston or swallowed valve, the engine can often get you someplace better than the closest airport. Better in what sense? With a failing engine, how could a distant airport be better than a nearby airport? A lot of pilots die because they want someplace "better" than the nearest airport, and then their luck runs out before they find that ideal spot. Better facilities, paved surface, closer to civilization, lots of reasons. It always makes more sense to plan and execute a solution rather than just jumping to conclusions based on what the least skilled have decided we should do. I try to follow the path of least risk. Or more specifically, I try to manage the risk/benefit ratio. It's hard to see the benefit of staying in the air with a bad engine. What's wrong with landing and fixing the problem? There's nothing wrong with landing and fixing the problem. Your premise however was that without an autopilot, every IFR flight was an emergency and if the autopilot failed the flight should land immediately at the nearest airport. That's just not the case. An autopilot may be on someone's personal list of minimum equipment for IFR, but that doesn't mean it should be a mandate for all of us. I don't think anyone should be compelled to use an autopilot if he's flyingon his own. However, I would want an autopilot for IFR flight, otherwise--at least in my estimation--the aircraft really isn't suitable for IFR flight. That's the point: in your estimation. If we've bred a generation of pilots that can't or won't fly IFR without an autopilot then why not just fly commercial and have a drink? |
#7
|
|||
|
|||
![]()
Jim Carter wrote:
Mxsmanic stuff snipped That's the point: in your estimation. If we've bred a generation of pilots that can't or won't fly IFR without an autopilot then why not just fly commercial and have a drink? Don't worry, he's not part of any generation of pilots. He doesn't fly, with or without an A/P, and has no intention of ever doing so. |
#8
|
|||
|
|||
![]()
"Jim Carter" wrote in news:000901c7141a$5c8da380
$8202a8c0@omnibook6100: It amuses me that so much of what was done 30 years ago, with less accurate technical toys is today seen as macho and Herculean. Single nav radio holds? Full ADF approach? Cross country without a moving map or GPS? Single-engine, night IFR? There are way too many opinions about the lack of safety of these practices by people who have little or no experience with them. It's not the equipment that's the weak link in the safety factor MOST of the time..... It's the human factor addressing the extra workload and undivided attention that's the weak link in the safety of single engine, night IFR, or hard IFR operations. I have done both hard IFR with and without an IFR certified GPS. Obviously a successful outcome for both situations, but given my druthers, GPS direct sure is easier then flying VOR to VOR. Of course everyone must know their personal and equipment limitations. And this is where lies the safety of IFR or any type of flying we do. Equipment failures happen, but more often then not, it's the human error that bites us in the rear end. I'm really going to upset the apple cart now when I suggest that landing at the nearest airport isn't always the best choice in any situation. Even with a blown piston or swallowed valve, the engine can often get you someplace better than the closest airport. I'd have to respectfully disagree with the above having been through a partial engine failure. First, the suddeness of onset catches you off guard. AVIATING, going through the emergency procedures AND THEN getting the plane set up for best glide NAVIGATING evaluating whether I can make the field, getting in touch with ATC COMMUNICATING (I called into 121.50 as I was not using ATC services), You do not know what is the problem causing the severe vibration, nor do you know if the fan will stop in front of you. For me, the engine ate an exhaust valve, and my oil loss was minimal. After all my trouble shooting, I had no clue what was happening to my plane. When things go to crap like it did for me, my first look / see was for a farm field. Once I evaluated I had enough altitude and power to make it to my destination (which by the way was the nearest airport) I stuck to my decision to press on to the airport (16 LONG miles). This decision was made based on a 200 fpm loss of altitude with what little power I had, and ALWAYS keeping an off aiport site front and center of my attention should I lose everything. I was at 3,500 when things went south with the cylinder. By the time I had descend down to 3000, I had figured I had 15 minutes flying time and my GPS had 12 minutes ETE with the field elevation of a whopping 40 feet. It always makes more sense to plan and execute a solution rather than just jumping to conclusions based on what the least skilled have decided we should do. Absolutely agree with the above, but when something goes as dramatically wrong as losing one piston operating under the cowling, nearest is best. The severe vibration brought on by losing a cylinder can easily snowball into something else to catastrophically fail, and pressing on past a perfectly useable landing site is a reckless decision in my opinion. An autopilot may be on someone's personal list of minimum equipment for IFR, but that doesn't mean it should be a mandate for all of us. Agree, since I do not have autopilot and have flown 2 1/2 hours in IMC with the last hour at night. Like you said above, it's highly dependent on personal limitations AND equipment. I have my own plane, so I know what is behind the maintenance. Even with that knowledge doesn't mean the next flight will be the demise of my vacuum pump, but with the training I have had, it shouldn't be that big a deal. Been through one of those during a night flight and it was a non event. Of course, that was easy compared to IMC, but it happens. Allen |
#9
|
|||
|
|||
![]() -----Original Message----- From: A Lieberma ] Posted At: Wednesday, November 29, 2006 7:35 PM Posted To: rec.aviation.ifr Conversation: Instrument Check Ride - What navigation equipment can I use ? Subject: Instrument Check Ride - What navigation equipment can I use ? "Jim Carter" wrote in news:000901c7141a$5c8da380 $8202a8c0@omnibook6100: It amuses me that so much of what was done 30 years ago, with less accurate technical toys is today seen as macho and Herculean. Single nav radio holds? Full ADF approach? Cross country without a moving map or GPS? Single-engine, night IFR? There are way too many opinions about the lack of safety of these practices by people who have little or no experience with them. It's not the equipment that's the weak link in the safety factor MOST of the time..... It's the human factor addressing the extra workload and undivided attention that's the weak link in the safety of single engine, night IFR, or hard IFR operations. I have done both hard IFR with and without an IFR certified GPS. Obviously a successful outcome for both situations, but given my druthers, GPS direct sure is easier then flying VOR to VOR. I can't argue with you because I agree completely. My point to MXS... was that autopilots are not and should not be required on single engine piston aircraft for IFR work. There's a world of difference between mandating their use and advocating their use. His statement that without an autopilot every IFR flight was an emergency was ridiculous. I'm really going to upset the apple cart now when I suggest that landing at the nearest airport isn't always the best choice in any situation. Even with a blown piston or swallowed valve, the engine can often get you someplace better than the closest airport. I'd have to respectfully disagree with the above having been through a partial engine failure. First, the suddeness of onset catches you off guard. AVIATING, going through the emergency procedures AND THEN getting the plane set up for best glide NAVIGATING evaluating whether I can make the field, getting in touch with ATC COMMUNICATING (I called into 121.50 as I was not using ATC services), You do not know what is the problem causing the severe vibration, nor do you know if the fan will stop in front of you. For me, the engine ate an exhaust valve, and my oil loss was minimal. After all my trouble shooting, I had no clue what was happening to my plane. Had the exact same situation (ate the exhaust valve on #4 cylinder on a CAP T41). Oil loss was zero, not enough mechanical noise to be a rod or crankshaft, and vibration reduced significantly at around 1600 RPM. Dead giveaway: swallowed a value. When things go to crap like it did for me, my first look / see was for a farm field. Once I evaluated I had enough altitude and power to make it to my destination (which by the way was the nearest airport) I stuck to my decision to press on to the airport (16 LONG miles). This decision was made based on a 200 fpm loss of altitude with what little power I had, and ALWAYS keeping an off aiport site front and center of my attention should I lose everything. I was at 3,500 when things went south with the cylinder. By the time I had descend down to 3000, I had figured I had 15 minutes flying time and my GPS had 12 minutes ETE with the field elevation of a whopping 40 feet. I was luckier: IFR on top at 8000', 38 miles East of Meridian Naval Air Station, and about 1200' ceiling below the deck. Memphis gave me the option of a small grass strip less than 2 miles North of my route, or the NAS. I opted for the Navy base (they have the best O'clubs). Broke out at about 1500' right over the threshold so had to do a 360. Field made so shut it on down. It always makes more sense to plan and execute a solution rather than just jumping to conclusions based on what the least skilled have decided we should do. Absolutely agree with the above, but when something goes as dramatically wrong as losing one piston operating under the cowling, nearest is best. The severe vibration brought on by losing a cylinder can easily snowball into something else to catastrophically fail, and pressing on past a perfectly useable landing site is a reckless decision in my opinion. Ah, there's part of the point I was making: "perfectly useable landing site". I don't consider the nearest airport to always be a perfectly useable landing site based on current conditions. Again, MXS... advocated essentially declaring an emergency and landing at the nearest airport if the autopilot failed in IFR. I still disagree with that suggestion and was using the engine failure to make (stretch?) a point. An autopilot may be on someone's personal list of minimum equipment for IFR, but that doesn't mean it should be a mandate for all of us. Agree, since I do not have autopilot and have flown 2 1/2 hours in IMC with the last hour at night. Like you said above, it's highly dependent on personal limitations AND equipment. I have my own plane, so I know what is behind the maintenance. Even with that knowledge doesn't mean the next flight will be the demise of my vacuum pump, but with the training I have had, it shouldn't be that big a deal. Been through one of those during a night flight and it was a non event. Of course, that was easy compared to IMC, but it happens. Allen I think we're vehemently agreeing with each other Allen. |
#10
|
|||
|
|||
![]()
"Jim Carter" wrote in news:004701c71437$21ca6ea0
$0100007f@omnibook6100: I can't argue with you because I agree completely. My point to MXS... was that autopilots are not and should not be required on single engine piston aircraft for IFR work. There's a world of difference between mandating their use and advocating their use. His statement that without an autopilot every IFR flight was an emergency was ridiculous. Unfortunately you are dealing with a troll who won't take your replies for what they are worth.... Not sure if you have seen rec.aviation.piloting or students, but he has been disrespecting pilots treating MSFS as if it was the real deal. I think we're vehemently agreeing with each other Allen. I see that now :-) however the troll you are dealing with won't see it in the real world way. Allen |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Accuracy of GPS in Garmin 430/530 | Will | Instrument Flight Rules | 110 | May 29th 06 04:58 PM |
Instrument Rating Checkride PASSED (Very Long) | Alan Pendley | Instrument Flight Rules | 24 | December 16th 04 02:16 PM |
PC flight simulators | Bjørnar Bolsøy | Military Aviation | 178 | December 14th 03 12:14 PM |
CFI logging instrument time | Barry | Instrument Flight Rules | 21 | November 11th 03 12:23 AM |
Use of hand-held GPS on FAA check ride | Barry | Instrument Flight Rules | 1 | August 9th 03 09:25 PM |