Re: [Flightgear-devel] Presets menu
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.11.18 15:47]: > I created a /sim/presets area in the property manager which is where > all the FDM initial conditions can be batched up. Things like: > runway (i.e. 1R) Woohoo! That's been on my wishlist[1] from when I first started using FG. Nice work, Curt. [1] http://unbeatenpath.net/software/fgfs/Wishlist.html -- Cameron Moore / Just think how much deeper the ocean \ \ would be if sponges didn't live there / ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: AW: [Flightgear-devel] Flying Tutorial
Carsten Höfer writes: > Thanks for the checklist, David. Now it's in the document!! Great. I'll send the emergency checklists another time, when I feel like more typing. The weight and balance data and performance tables are also needed for flight planning. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
AW: [Flightgear-devel] Flying Tutorial
Thanks for the checklist, David. Now it's in the document!! Carsten -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Im Auftrag von David Megginson Gesendet: Montag, 18. November 2002 03:50 An: [EMAIL PROTECTED] Betreff: re: [Flightgear-devel] Flying Tutorial Carsten Höfer writes: > As You will see it's only the structure of the tutorial, but it should > give You the idea behind it. I would like You to read it and tell me > Your opinion. Did I miss something? Is there a better order? Is anyone > out there to write one of the sections? It looks interesting -- I'll try to find time to read it in more detail. In the meantime, you asked for checklists. Fortunately, I'm a fast typist, so here are the checklists for normal procedures in the 1981 C172P, straight out of the POH (forgive any typos): PREFLIGHT INSPECTION (1) Cabin 1. Pilot's Operating Handbook -- AVAILABLE IN THE AIRPLANE. 2. Control Wheel Lock -- REMOVE. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Presets menu
On Mon, 2002-11-18 at 14:41, David Megginson wrote: > Curtis L. Olson writes: > > > BTW, Andy, how hard would it be to accept an initial airspeed for the > > YASim models so we can do in-air starts with those? > > Andy's concern has been the obfuscation around velocities. We have > > - calibrated airspeed in knots (forward from the nose of the plane) > - mach number (ditto) > - UVW wind/body speeds (u/v/w) > - NED speeds > > The NED *should* be the ones we save and restore, since they are the > only independent ones (we don't have to set the orientation first); > however, because of problems with LaRCsim, we had to make UVW > canonical quite a while back. It would be nice to fix that and make > NED canonical first, then twist Andy's arm until he supports them in > YASim. > > There's also more to the problem. If we're restoring a saved flight > then everything's fine, since all of the FDM state is already valid. > If, on the other hand, we're starting in the air, then we need a > general trimming routine like the one Tony wrote for JSBSim and > LaRCsim to avoid violent oscillations at startup. For the record, I did not write a trimming routine for LaRCsim. > > > All the best, > > > David -- Tony Peden <[EMAIL PROTECTED]> ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Presets menu
On Mon, 2002-11-18 at 14:17, Andy Ross wrote: > Curtis L. Olson wrote: > > BTW, Andy, how hard would it be to accept an initial airspeed for > > the YASim models so we can do in-air starts with those? > > Not hard at all. The only reason it doesn't is that, heh, I got > really confused about how to figure out the units and precedence > rules. Speed can be set in about a zillion ways (roll/pitch/heading > vs. x/y/z vs. north/east/down coordinates, IAS, TAS, knots, m/s, mach, > etc...), and it seemed like the FDM is responsible for figuring out > what goes where. > > If you can point me at a property to read for an authoritative > velocity source, I'm there. :) > > A slightly harder problem is getting the aircraft trimmed for the > selected environment. A really annoying property of most (all?) sims Almost all professional sims have a trimming routine. They are not only useful for the instructor, but also very helpful when using a motion base and control loaders. > is that they start you out at the right point, but way out of trim and > you wreck the setup trying to get stabilized. I can probably > canibalize some of the solver code for that. It is not a terribly hard problem to solve, but does require some patience in discovering and covering most situations. > > Andy -- Tony Peden <[EMAIL PROTECTED]> ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Presets menu
Curtis L. Olson writes: > BTW, Andy, how hard would it be to accept an initial airspeed for the > YASim models so we can do in-air starts with those? Andy's concern has been the obfuscation around velocities. We have - calibrated airspeed in knots (forward from the nose of the plane) - mach number (ditto) - UVW wind/body speeds (u/v/w) - NED speeds The NED *should* be the ones we save and restore, since they are the only independent ones (we don't have to set the orientation first); however, because of problems with LaRCsim, we had to make UVW canonical quite a while back. It would be nice to fix that and make NED canonical first, then twist Andy's arm until he supports them in YASim. There's also more to the problem. If we're restoring a saved flight then everything's fine, since all of the FDM state is already valid. If, on the other hand, we're starting in the air, then we need a general trimming routine like the one Tony wrote for JSBSim and LaRCsim to avoid violent oscillations at startup. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Presets menu
Curtis L. Olson wrote: > BTW, Andy, how hard would it be to accept an initial airspeed for > the YASim models so we can do in-air starts with those? Not hard at all. The only reason it doesn't is that, heh, I got really confused about how to figure out the units and precedence rules. Speed can be set in about a zillion ways (roll/pitch/heading vs. x/y/z vs. north/east/down coordinates, IAS, TAS, knots, m/s, mach, etc...), and it seemed like the FDM is responsible for figuring out what goes where. If you can point me at a property to read for an authoritative velocity source, I'm there. :) A slightly harder problem is getting the aircraft trimmed for the selected environment. A really annoying property of most (all?) sims is that they start you out at the right point, but way out of trim and you wreck the setup trying to get stabilized. I can probably canibalize some of the solver code for that. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Presets menu
I have been working a bit over the weekend on the intialization infrastructure, especially as it relates to providing initial conditions to the FDM's. I created a /sim/presets area in the property manager which is where all the FDM initial conditions can be batched up. Things like: airport-id (i.e. KSFO) runway (i.e. 1R) offset-distance (i.e. 7 miles out) altitude(i.e. 2000') glideslope (i.e. on a 3 degree glide slope) airspeed(i.e. 90 kts) You can set any or all of these and when you are satisfied, choose the Presets->Commit menu option. The menu is a little clumsy and doesn't expose the entire interface. Ideally, someone will come along and build a sensible dialog box, or "Reposition Wizard" or something along those lines. I won't claim it is all perfect yet, but it doesn't seem to seg fault so I committed my changes. BTW, Andy, how hard would it be to accept an initial airspeed for the YASim models so we can do in-air starts with those? Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-users] Error making SimGear 0.2.0...
On Wed, 13 Nov 2002 21:33:56 -0500 "Norman Vine" <[EMAIL PROTECTED]> wrote: > > I realize that Patrick needed to change the > #ifdef WIN32 to #ifdef __CYGWIN__ > but this should not be necessary in that WIN32 should be > being #defined by our configure script and as it is written > this works on both Cygwin and MingW32 > Actually WIN32 gets defined by the configure script but config.h/simgear_config.h isn't included in all files. Changes to FlightGear: - Index: src/ATC/AIEntity.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/ATC/AIEntity.cxx,v retrieving revision 1.2 diff -r1.2 AIEntity.cxx 28a29,34 > > #ifdef HAVE_CONFIG_H > # include > #endif > > #include Index: src/ATC/AILocalTraffic.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/ATC/AILocalTraffic.cxx,v retrieving revision 1.3 diff -r1.3 AILocalTraffic.cxx 21a22,27 > > #ifdef HAVE_CONFIG_H > # include > #endif > > #include Index: src/Cockpit/hud.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Cockpit/hud.cxx,v retrieving revision 1.1.1.1 diff -r1.1.1.1 hud.cxx 22a23,26 > #ifdef HAVE_CONFIG_H > # include > #endif > Index: src/FDM/ADA.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/ADA.cxx,v retrieving revision 1.1.1.1 diff -r1.1.1.1 ADA.cxx 20a21,25 > #ifdef HAVE_CONFIG_H > # include > #endif > > #include Index: src/FDM/Balloon.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/Balloon.cxx,v retrieving revision 1.2 diff -r1.2 Balloon.cxx 39a40,43 > #ifdef HAVE_CONFIG_H > # include > #endif > Index: src/FDM/NullFDM.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/NullFDM.cxx,v retrieving revision 1.1.1.1 diff -r1.1.1.1 NullFDM.cxx 23a24,29 > #ifdef HAVE_CONFIG_H > # include > #endif > > #include > Index: src/FDM/flight.hxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/flight.hxx,v retrieving revision 1.4 diff -r1.4 flight.hxx 83a84,87 > #ifdef HAVE_CONFIG_H > # include > #endif > Index: src/FDM/JSBSim/JSBSim.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/JSBSim/JSBSim.cxx,v retrieving revision 1.5 diff -r1.5 JSBSim.cxx 23a24,27 > #ifdef HAVE_CONFIG_H > # include > #endif > Index: src/FDM/UIUCModel/uiuc_wrapper.cpp === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/UIUCModel/uiuc_wrapper.cpp,v retrieving revision 1.5 diff -r1.5 uiuc_wrapper.cpp 77a78,82 > #ifdef HAVE_CONFIG_H > # include > #endif > > #include - Changes to SimGear: - Index: simgear/bucket/newbucket.cxx === RCS file: /var/cvs/SimGear-0.3/SimGear/simgear/bucket/newbucket.cxx,v retrieving revision 1.1.1.1 diff -r1.1.1.1 newbucket.cxx 25a26,28 > #ifdef HAVE_CONFIG_H > # include > #endif Index: simgear/io/sg_binobj.cxx === RCS file: /var/cvs/SimGear-0.3/SimGear/simgear/io/sg_binobj.cxx,v retrieving revision 1.1.1.1 diff -r1.1.1.1 sg_binobj.cxx 23a24,26 > #ifdef HAVE_CONFIG_H > # include > #endif - With the patch from Norman in <014101c28f0c$271e4570$ad37ba8c@sfdev3> applied, FlightGear compiles without errors on my cygwin/gcc (there are a lot of warnings though but most are related to new stl headers in gcc 3.x). Patrick -- Patrick Stählin <[EMAIL PROTECTED]> ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 737
Once upon a time, you were sitting and writing: > "Roel Michiels" writes: > > When you start modelling the B737, here's an excellent site by on of > > the Captains I flew with at Sabena. This man is highly proficient > > and also a simulation enthousiast. You will find lots of info > > concerning the real-life B737 and it's caracteristics. Hold on to > > this link !! It'll be very useful once you start on the B737 ! > > Greetings, Roel > > > > http://users.pandora.be/guy.daems/fs-how.html > > A 737 would be a nice plane to have... Anybody thinking of modeling > one? Dave Culp fly those... and I guess we could all just benefit from this fact ;) All the best, Elady. ~ ___ Elad (elady)_@__ ___ ( \ J. Yarkoni .-'`-. / ) ( \_ / (O O) \ _/ ) (`-( ) )-') ( _\ \/ /_ ) (__/ `-..-' \__) "Elady" for friends or "Oh my God... - It's Him !" for fans (or turbofans). [EMAIL PROTECTED]| http://www.ee.bgu.ac.il/~elady| .---. ECE. BGU, Beer-Sheva,Israel' ___ ' 972-8-6472417 84105-' .-. '- _' '-' '_ ''-|---|/ \==][^',_m_,'^][==/ \|---|-'' \__/~\__/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cygwin build problem with sprintf
[EMAIL PROTECTED] writes: > Norman Vine wote: > > > > > > ! #ifdef _WIN32 > > #define snprintf _snprintf > > #endif > > > > --- 66,72 > > > > ! #if defined(_WIN32) && !defined(__CYGWIN__) > > #define snprintf _snprintf > > #endif > > To Norman: Good fix. > > To Curt (etc.): Shouldn't this go in instead of > in every source file that uses it? I thought it already was there ... Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cygwin build problem with sprintf
Norman Vine wote: > > > ! #ifdef _WIN32 > #define snprintf _snprintf > #endif > > --- 66,72 > > ! #if defined(_WIN32) && !defined(__CYGWIN__) > #define snprintf _snprintf > #endif To Norman: Good fix. To Curt (etc.): Shouldn't this go in instead of in every source file that uses it? - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Flying Tutorial
[EMAIL PROTECTED] writes: > Maybe a silly question: Should'nt companies like Cessna or Raytheon > have an interest in supporting programers of flight sims? Does it > have a chance to ask them directly for information? Or is this > thought a little bit naiv? They toyed around with that for a while -- MSFS had some official Cessna sponsorship, and Fly! claimed to have aero data direct from Cessna and Piper. In the end, though, I doubt it matters much. If there's any buyer prejudice at all, it's probably towards the type of plane you trained in rather than the typed you used in a sim -- they'd be best to concentrate on the flying schools. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Flying Tutorial
Maybe a silly question: Should'nt companies like Cessna or Raytheon have an interest in supporting programers of flight sims? Does it have a chance to ask them directly for information? Or is this thought a little bit naiv? Carsten David Megginson schrieb: > Michael Basler writes: > > > Unfortunately you are right, I should have checked > before. I thought they > > would provide manual + checklist if they write manual > + checklist :-( > > > > It still might be helpful for what Carsten wants to > do, though. > > I've noticed POH's and IM's (generic POH's) popping up on > eBay for ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Flying Tutorial
Michael Basler writes: > Unfortunately you are right, I should have checked before. I thought they > would provide manual + checklist if they write manual + checklist :-( > > It still might be helpful for what Carsten wants to do, though. I've noticed POH's and IM's (generic POH's) popping up on eBay for around USD 10.00. That's the place to go. I've already ordered a 172R and a 182. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Flying Tutorial
David, > These are short checklist collections for FS2000/2002. You mentioned > that there were actual scanned POH's available somewhere. What I'm > most interested in are the POH performance tables for various Unfortunately you are right, I should have checked before. I thought they would provide manual + checklist if they write manual + checklist :-( It still might be helpful for what Carsten wants to do, though. Sorry, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cygwin build problem with sprintf
Jon Berndt writes: > Here's the sprintf problem again in a recent build attempt for > fg_init.cxx. Is there a fix for this for CygWin? > > Jon > > > > g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/us > r/local/include -DPKGLIBDIR=\"/usr/local/lib/FlightGear\" -c -o fg_init.o > `test -f 'fg_init.cxx' || echo './'`fg_init.cxx > fg_init.cxx: In function `bool fgSetPosFromAirportIDandRwy(const string &, > const string &)': > fg_init.cxx:823: implicit declaration of function `int _snprintf(...)' > make[2]: *** [fg_init.o] Error 1 > This seems to clear things up Norman $ cvs diff -c FGTrim.h 2>&1 | tee diffs Index: FGTrim.h === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/FDM/JSBSim/FGTrim.h,v retrieving revision 1.2 diff -c -r1.2 FGTrim.h *** FGTrim.h22 Sep 2002 15:31:09 - 1.2 --- FGTrim.h18 Nov 2002 14:06:56 - *** *** 66,72 tCustom, tNone, tTurn } TrimMode; ! #ifdef _WIN32 #define snprintf _snprintf #endif --- 66,72 tCustom, tNone, tTurn } TrimMode; ! #if defined(_WIN32) && !defined(__CYGWIN__) #define snprintf _snprintf #endif ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Flying Tutorial
Michael Basler writes: > > Thanks. I took a look, but couldn't find anything except > > FS2000/FS2002 checklists. Where are the actual Cessna ones on the > > The file names are > > manc310.zip, manc185,zip, manc172 and so on, depending which you > are looking for. I entered "cessna" and "manual" into the search > routine to find them. These are short checklist collections for FS2000/2002. You mentioned that there were actual scanned POH's available somewhere. What I'm most interested in are the POH performance tables for various aircraft. Thanks, and all the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: re: [Flightgear-devel] No rule to make target `new_gui.cxx
> Martin Spott writes: > > make[2]: *** No rule to make target `new_gui.cxx', needed by `new_gui.o'. Stop. > Somethings not rebuilding properly. Make sure you have a fresh CVS > checkout, [...] I was absolutely shure I did - but I forgot to uncomment a line in my build-script that updates the according build-directory :-/ Sorry about that, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Cygwin build problem with sprintf
Here's the sprintf problem again in a recent build attempt for fg_init.cxx. Is there a fix for this for CygWin? Jon g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/us r/local/include -DPKGLIBDIR=\"/usr/local/lib/FlightGear\" -c -o fg_init.o `test -f 'fg_init.cxx' || echo './'`fg_init.cxx fg_init.cxx: In function `bool fgSetPosFromAirportIDandRwy(const string &, const string &)': fg_init.cxx:823: implicit declaration of function `int _snprintf(...)' make[2]: *** [fg_init.o] Error 1 smime.p7s Description: application/pkcs7-signature
RE: [Flightgear-devel] Flying Tutorial
David, > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David > Megginson > Thanks. I took a look, but couldn't find anything except > FS2000/FS2002 checklists. Where are the actual Cessna ones on the The file names are manc310.zip, manc185,zip, manc172 and so on, depending which you are looking for. I entered "cessna" and "manual" into the search routine to find them. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Flying Tutorial
Michael Basler writes: > There are several checklists available (intended for use with MSFS, but > these are the real ones), including for Cessnas, from > > http://www.flightsim.com/login.htm > > Besides, they have complete manuals for several aircraft available > (including Cessnas, as I just checked, too). Obviously the makers don't > object against scanning them (or don't know about it...). Thanks. I took a look, but couldn't find anything except FS2000/FS2002 checklists. Where are the actual Cessna ones on the site? Thanks, and all the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Flying Tutorial
Sorry for the full quote... just happened. Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Flying Tutorial
Carsten, David > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David > It looks interesting -- I'll try to find time to read it in more > detail. If Carsten manages to get this written with time (and I am sure it will need time) this will be a great addition to FlightGear and might buy us quite a number of customers. The outline is quite promising, IMHO. It might be usefeul if "real pilots" (no, I am not one, although I might help, too) have a look into it from time to time. > In the meantime, you asked for checklists. Fortunately, I'm > a fast typist, so here are the checklists for normal procedures in the > 1981 C172P, straight out of the POH (forgive any typos): There are several checklists available (intended for use with MSFS, but these are the real ones), including for Cessnas, from http://www.flightsim.com/login.htm Besides, they have complete manuals for several aircraft available (including Cessnas, as I just checked, too). Obviously the makers don't object against scanning them (or don't know about it...). Beware: Despite the login/password thingy, basic use of the site is free. However, if you're not a premium member (I am) you may need several attempts to login at US peak use times. Carsten, if you run into trouble, just mail me what you need and I can download it for you. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David > Megginson > Sent: Monday, November 18, 2002 3:50 AM > To: [EMAIL PROTECTED] > Subject: re: [Flightgear-devel] Flying Tutorial > > > Carsten Höfer writes: > > > As You will see it's only the structure of the tutorial, but it should > > give You the idea behind it. I would like You to read it and tell me > > Your opinion. Did I miss something? Is there a better order? Is anyone > > out there to write one of the sections? > > It looks interesting -- I'll try to find time to read it in more > detail. In the meantime, you asked for checklists. Fortunately, I'm > a fast typist, so here are the checklists for normal procedures in the > 1981 C172P, straight out of the POH (forgive any typos): > > > PREFLIGHT INSPECTION > > (1) Cabin > > 1. Pilot's Operating Handbook -- AVAILABLE IN THE AIRPLANE. > 2. Control Wheel Lock -- REMOVE. > 3. Ignition Switch -- OFF. > 4. Avionics Power Switch -- OFF. > 5. Master Switch -- ON. > 6. Fuel Quantity Indicators -- CHECK QUANTITY. > 7. Avionics Cooling Fan -- CHECK AUDIBLY FOR OPERATION. > 8. Master Switch -- OFF. > 9. Static Pressure Alternate Source Value (if installed) -- OFF. > 10. Baggage Door -- CHECK, lock with key if child's seat is to be > occupied. > > > (2) Empennage > > 1. Rudder Gust Lock -- REMOVE. > 2. Tail Tie-Down -- DISCONNECT. > 3. Control Surfaces -- CHECK freedom of movement and security. > > > (3) Right Wing Trailing Edge > > 1. Aileron -- CHECK freedom of movement and security. > > > (4) Right Wing > > 1. Wing Tie-Down -- DISCONNECT. > 2. Main Wheel tire -- CHECK for proper inflation. > 3. Before the first flight of the day and after each refueling, use >sampler cup and drain small quantity of fuel from fuel tank sump >quick-drain valve to check for water, sediment, and proper fuel >grade. > 4. Fuel Quantity -- CHECK VISUALLY for desired level. > 5. Fuel Filler Cap -- SECURE. > > > (5) Nose > > 1. Engine Oil Level -- CHECK, do not operate with less than five >quarts. Fill to seven quarts for extended flight. > 2. Before first flight of the day, and after each refueling, pull out >strainer drain knob for about four seconds to clear fuel strainer >of possible water and sediment. Check strainer drain closed. If >water is observed, the fuel system may contain additional water, >and further draining of the system at the strainer, fuel tank >sumps, and fuel selector value drain plug will be necessary. > 3. Propeller and Spinner -- CHECK for nicks and security. > 4. Landing Light(s) -- CHECK for condition and cleanliness. > 5. Carburetor Air Filter -- CHECK for restrictions by dust or other >foreign matter. > 6. Nose Wheel Strut and Tire -- CHECK for proper inflation. > 7. Nose Tie-Down -- DISCONNECT. > 8. Static Source Opening (left side of fuselage) -- CHECK for >stoppage. > > > (6) Left Wing > > 1. Main Wheel Tire -- CHECK for proper inflation. > 2. Before first flight of the day and after each refueling, use >sampler cup and drain small quantity of fuel from fuel tank sump >quick-drain value to check for water, sediment, and proper fuel >grade. > 3. Fuel Quantity -- CHECK VISUALLY for desired level. > 4. Fuel Filler Cap -- SECURE. > > > (7) Left Wing Leading Edge > > 1. Pitot Tue Cover -- REMOVE and check opening for stoppage. > 2. Fuel Tank Vent Opening -- CHECK for stoppage. > 3. Stall Warning Opening -- CHECK for stoppage. To check the syste
