
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
On 3 Dec 2003 13:06:02 -0800, [EMAIL PROTECTED] (Snowbird) wrote: >"Charles Talleyrand" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... >> There must be people on the newsgroup that fly single pilot >> IFR on a regular basis. These people have a schedule to make >> and would rather not miss that schedule unless necessary. These people >> don't have the need to carry many passengers, but just themselves. >> My question is for these people ... > >> What sort of planes are you flying? > >Charles, > >I think you have two separate issues here. > >1) single pilot IFR (subsidiary issue for a low time pilot) > >2) schedule to make > >A plane which is good for 1), especially for a low time pilot, >will be stable and relatively forgiving. Something like a >C182, maybe a C182TR. > >A plane which is good for 2) will have known ice capability, >weather detection such as radar, service ceiling to climb above >some wx, and two engines. There are a couple of singles that will do this, but they cost way more than a light pressurized twin. One is the TBM-700 at a bit over 2 million (as I recall) and there is another, not quite a pretty, but very capable. It and the TBM-700 are very much alike. Single pilot, capable, reliable, long range, and speed in the 300 knot range. and in the $2 million dollar plus range. > >A plane which will allow 2) may not be good for 1), especially >for a low time pilot. I'd change that "may not be" to "most likely won't be" <:-)) It doesn't matter what they are flying, it would be a very rare low time pilot who could keep any kind of scheduled series of IFR flights.. I just don't think it'd be practical. You'll have to fix the return add due to dumb virus checkers, not spam Roger Halstead (K8RI & ARRL life member) (N833R, S# CD-2 Worlds oldest Debonair?) www.rogerhalstead.com > >A plane which will allow for 1) (especially for a low time >pilot) may not be good for 2) > >FWIW, >Sydney
| <-- __Chronological__ --> | <-- __Thread__ --> |