Jump to content

Ian's flight scores


Ian Pearse

Recommended Posts

I am really annoyed - FSFS disconnected on me 3 times during the flight for no readily apparent reason. My final score ended up with no takeoff and marked down because Autopilot was in use - having switched it on once I got to cruise altitude. The final score was as follows:

Ian piloting Beech King Air 350 Paint3 ended 13 April 2011 at 21:28

FSFlyingSchool 2011 (Jan 21 2011)

Using: FSX

Visibility: 62.14 Miles Wind: 7 Knots

Aircraft: BEECH ID: G-IANP Airline: Flight:

Flight plan: EAFS TO LFPO Paris:Orly NAV1: OLW

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:00 Hours 45 Mins 04 Secs

Landing Score:25.27

Autopilot used.

Landing was successful in the following areas:

  • Good alignment with runway on ILS approach. [80%]
  • Gentle touchdown. [367 FPM]
  • Good landing speed - not too fast. [98 KIAS]
  • Wings were level.
  • Landed on runway surface.
  • Glideslope held until flare.
  • Good pitch control after touchdown.
  • With flaps - good job.
  • Heading aligned with runway.
  • Throttle(s) idle.
  • Good controlled final descent to touchdown.

    • Poor glideslope on ILS approach - you can do better. [0%]
    • Distance from runway threshold (visual approach): [-784 feet] (short)
    • Nose down too low - you need to land on your main gear.
    • Poor steering after landing - stay on the centre line.


      Flight Score:0.00 (Flight did not include take off...)
      Autopilot used.

      Flight commended in the following areas:

      • Smooth turns.
      • Nice banking.
      • Correct matching of flaps to speeds.
      • Gear deployment at safe speed.
      • Comfortable G forces.
      • Smooth pitch control.
      • Flown within aircraft's maximum speed limit.
      • Gentle taxi turns.
      • Appropriate position of flaps during taxi.
      • Safe taxi speed.
      • Smooth braking during taxi.
      • Wings level near ground.
      • Well coordinated turns.
      • No stalls.
      • Pitch not too high.
      • Pitch not too low.
      • Flaps down on time.
      • Approach speed not too fast.
      • Low altitude speeds not too fast.
      • Good clearance of obstacles.

    Flight included the following problems:

Airspeed too low - you are risking stalls.Rapid descent - dangerous and uncomfortable.
Definite room for improvement...
Link to comment
Share on other sites

I am really annoyed - FSFS disconnected on me 3 times during the flight for no readily apparent reason. My final score ended up with no takeoff and marked down because Autopilot was in use - having switched it on once I got to cruise altitude. The final score was as follows:

Ian piloting Beech King Air 350 Paint3 ended 13 April 2011 at 21:28

FSFlyingSchool 2011 (Jan 21 2011)

Using: FSX

Visibility: 62.14 Miles Wind: 7 Knots

Aircraft: BEECH ID: G-IANP Airline: Flight:

Flight plan: EAFS TO LFPO Paris:Orly NAV1: OLW

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:00 Hours 45 Mins 04 Secs

Landing Score:25.27

Autopilot used.

Flight Score:0.00 (Flight did not include take off...)

Autopilot used.

Ian...

What did you do that could have made FSFS disconnect? It never ever disconnects on me. BUT if you use Slew mode it will, if you change time it will, if you change aircraft it will, and if you move your aircraft too fast up or down (like you can in slew mode) These are reasons that makes FSFS disconnect at once. Apart from that, I have never heard of disconnects in flight.

As for the no flight score. Well if you disconnect from FSFS you HAVE to fly from scratch again, as a re-connection will start from the point you are at - ai in the air, hence leaving you with a no-take-off verdict.

Autopilot: Remember that TWO things have to be in place for you to use AP. You have to be ABOVE 1000 feet in a light aircraft, or 5000 feet in a heavy. AND (IMPORTANT) you have to be in Cruise mode. NOT in take-off mode, and not in landing-mode.

Link to comment
Share on other sites

Hi Ole, I did none of those things that might make FSFS disconnect - I was very careful to avoid doing anything out of the ordinary. The autopilot bit happened, I presume, because I reconnected after the disconnects - as I was already in the cruise with the AP on I presume it picked that up. The AP didn't go on until FL200. I did have some turbulence on the way - the aircraft was bucking about a bit, do you think that could have caused the disconnects?

Link to comment
Share on other sites

I'll fly the leg again and see what happens. I'll pick a higher cruise altitude in case it was the turbulence that did it. A real pain.....dry.gif

What weather engine are you using, ASE, REX, Open Clouds, default?

Instead of flying higher [where the winds are stronger,] try flying lower >10,000 <20,000 feet.

Link to comment
Share on other sites

Hi Ole, I did none of those things that might make FSFS disconnect - I was very careful to avoid doing anything out of the ordinary. The autopilot bit happened, I presume, because I reconnected after the disconnects - as I was already in the cruise with the AP on I presume it picked that up. The AP didn't go on until FL200. I did have some turbulence on the way - the aircraft was bucking about a bit, do you think that could have caused the disconnects?

The program is made to sustain turbulence, so It should not be enough to disconnect FSFS. You did not, by any chance, use a chat program while flying? When I flew my first round-the-world-trip (Called the WWT (World Wide Tour)) I flew offline, but me and my Friend, with whom I flew the WWT, often MSN chatted during flights - and sometimes - just sometimes, when one of asked a question that required a yes or no - and we had made some course change for instance, in FSX, and had forgotten to click the MSN window - we then typed a Y (beginning of a YES - right?) and that unfortunately is the slew key in FSX, and THAT disconnected us.I ended up changing the Slew keypress to another key than Y....

And regarding Autopilot. When I said 1000/5000 feet - its Above GROUND level - not MSL - just to make that clear.smile.gif

Link to comment
Share on other sites

Hi Ian

I have had FSFlying school for some time and upgraded to 2011 when it came out at the end of last year.

So I don't know if I can be much help- the only thing I could think of was time compression?

Kind Regards

Chompski

Link to comment
Share on other sites

Hi Chompski, Nope, no time compression. And no chat either. All I had running was FSX, FSFS, Navigraph, Plan-G and TrackIR. No chat, no Squawkwin or anything. I will redo the leg and try and take more notice of what is happening. One possibility, triggered by your comment Ole, is that, having gone to Plan-G or Navigraph to look at something, I didn't properly switch back into FSX, but I don't tend to do keyboard entries except for radio tuning once I'm in the cruise. The other keyboard entry I do from time to time is F10, to freeze the TrackIR for a while.

Link to comment
Share on other sites

OK, that was much better. I had 2 disconnects while still on the ground, but hadn't done much till then so not a major problem. I flew this time without Plan-G, as the new version wasn't connecting to FSX properly. All seemed to go OK. Scores on the doors:

Ian piloting Beech King Air 350 Paint3 ended 14 April 2011 at 20:20

Aircraft: BEECH ID: G-IANP Airline: Flight:

Flight plan: EAFS TO LFPO Paris:Orly NAV1: OLN

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:01 Hours 32 Mins 49 Secs

Landing Score:69.66

Autopilot used.

Landing was successful in the following areas:

* Good glideslope on ILS approach. [60%]

* Good alignment with runway on ILS approach. [70%]

* Gentle touchdown. [89 FPM]

* Good landing speed - not too fast. [102 KIAS]

* Wings were level.

* Landed on runway surface.

* Glideslope held until flare.

* Good pitch control after touchdown.

* With flaps - good job.

* Heading aligned with runway.

* Throttle(s) idle.

* Good steering after landing.

* Nicely handled crosswind.

Landing included the following problems:

* Nose down too low - you need to land on your main gear.

* Ballooning during landing - needs practice.

Definite room for improvement...

Flight Score:75.91

Autopilot used.

Flight commended in the following areas:

* Smooth turns.

* Nice banking.

* Correct matching of flaps to speeds.

* Gear deployment at safe speed.

* Comfortable G forces.

* Smooth pitch control.

* Flown within aircraft's maximum speed limit.

* Gentle taxi turns.

* Good take off steering.

* Rotation was not late.

* Appropriate position of flaps during taxi.

* Safe taxi speed.

* Smooth braking during taxi.

* Wings level near ground.

* Well coordinated turns.

* No stalls.

* Smooth comfortable descent rate.

* Pitch not too high.

* Pitch not too low.

* Flaps down on time.

* Approach speed not too fast.

* Low altitude speeds not too fast.

* Good clearance of obstacles.

Flight included the following problems:

* Loss of altitude during takeoff - climb smoothly.

* Airspeed too low - you are risking stalls.

Definite room for improvement...

Autopilot was switched in at 25000 at the start of the cruise, and disconnected at 4000 prior to final approach. Much better following the ILS this time but still need to fine-tune my speed control. My flare was a bit slow, hence the nose low warning. I did bounce a bit too.... I like this pacakge, shows what I need to practice on. Gonna set up for Leg 2 now.

Link to comment
Share on other sites

OK, that's leg 2 done. Not bad but I got penalised for poor tracking of the glideslope - given the DC-3 has no instrument for tracking the ILS I think that's a little harsh! Nice views of the sun going down on the way over - shots in the screenshot forum. The scores:

Ian piloting Douglas DC3 World Rally 2010 ended 16 April 2011 at 21:24

Aircraft: Douglas ID: G-IANP Airline: Flight:

Flight plan: LFPO TO EGLC London:London City NAV1: ILSR

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:01 Hours 22 Mins 17 Secs

Landing Score:89.95

Landing was successful in the following areas:

* Good alignment with runway on ILS approach. [100%]

* Gentle touchdown. [66 FPM]

* Good landing speed - not too fast. [73 KIAS]

* Wings were level.

* Landed on runway surface.

* Glideslope held until flare.

* Good pitch control after touchdown.

* Good pitch at landing.

* With flaps - good job.

* Heading aligned with runway.

* Throttle(s) idle.

* Good controlled final descent to touchdown.

* Good steering after landing.

Landing included the following problems:

* Poor glideslope on ILS approach - you can do better. [0%]

* Not near the centre line - you can do better.

Definite room for improvement...

Flight Score:126.48

Flight commended in the following areas:

* Smooth turns.

* Nice banking.

* Correct matching of flaps to speeds.

* Gear deployment at safe speed.

* Comfortable G forces.

* Smooth pitch control.

* Flown within aircraft's maximum speed limit.

* Good take off steering.

* Rotation was not late.

* Appropriate position of flaps during taxi.

* Safe taxi speed.

* Smooth braking during taxi.

* Smooth climb during takeoff.

* Wings level near ground.

* Well coordinated turns.

* No stalls.

* No flying dangerously close to stall speed.

* Smooth comfortable descent rate.

* Pitch not too high.

* Pitch not too low.

* Flaps down on time.

* Approach speed not too fast.

* Low altitude speeds not too fast.

* Good clearance of obstacles.

Flight included the following problems:

* Dangerous taxiing turns - these cause discomfort and stress.

Definite room for improvement...

Tne dangerous taxiing turns comment I think came from the fact that I missed a taxiway turn at Orly and had to backtrack down the runway and do a 180 to line up - needs a sharp turn to turn in the width of the runway, differential engine power and brakes... oh well, serves me right for not checking the route properly.

Link to comment
Share on other sites

Hi Ian,

I had some low points because of the lost glide slope as well. I had a look at FSFS and I think if you un-tick the box "automatic radio tuning to ILS" in the pilot tab you should be able to do a visual approach instead of the ILS one.

Link to comment
Share on other sites

Hi Ian,

I had some low points because of the lost glide slope as well. I had a look at FSFS and I think if you un-tick the box "automatic radio tuning to ILS" in the pilot tab you should be able to do a visual approach instead of the ILS one.

No need to deselect the autotuning of ILS freq. When the ILS freq is found, and tuned, You can simple turn the nav dial, to change the freq, hence deselecting the ILS signal. Problem with leg 2, is that London City´s GS is 5.5, and in FSFS the standard 3 is used. You CAN change it in the file FSFS2011.txt, in your main FSX dir (open it, search for the London Ciry ICAO - and change the "3" to 5.5) but its a little nerdy. A possibility to change the Glideslope in the FSFS program, has been suggested by - ME - and will be incorporated in a later update.

Link to comment
Share on other sites

OK, leg 3 done. No flight score for some reason, dunno why. I forgot to swich off the AP before switching to Landing mode solost points for the landing... not my day today! On to the planning for leg 4.

Ian piloting PA-34 SENECA II Andras Aviation Club ended 17 April 2011 at 18:58

Aircraft: Piper ID: G-IANP Airline: Flight:

Flight plan: EGLC TO ELLX Luxembourg:Luxembourg NAV1: LUX

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:01 Hours 54 Mins 06 Secs

Landing Score:50.52

Autopilot used.

Landing was successful in the following areas:

* Good glideslope on visual approach. [60%]

* Good alignment with runway on visual approach. [60%]

* Gentle touchdown. [295 FPM]

* Good landing speed - not too fast. [65 KIAS]

* Wings were level.

* Distance from runway threshold (visual approach): [629 feet]

* Landed on runway surface.

* Glideslope held until flare.

* Good pitch control after touchdown.

* Good pitch at landing.

* With flaps - good job.

* Heading aligned with runway.

* Throttle(s) idle.

* Good controlled final descent to touchdown.

Landing included the following problems:

* Poor steering after landing - stay on the centre line.

Definite room for improvement...

Last aircraft was flown using data estimated by FSFlyingSchool.

If you wish to make changes to these values, go to the

Aircraft Page and click User Specified Data. Make your changes and then

click the Save User Data button.

Link to comment
Share on other sites

OK, leg 4 done. I forgot to calibrate my controls on starting FSX, so had some rocking and rolling on the final approach - at least that is what I think it was - no wind was mentioned in the Met report. Anyway, scores below, better for this flight. I know I need to work on speed and descent control on the approach - something i will get a lot of practice at on this challenge!

Ian piloting Douglas DC-3 Andras Field ROund THe World Challenge ended 18 April 2011 at 19:50

FSFlyingSchool 2011 (Jan 21 2011)

Using: FSX

Visibility: 62.14 Miles Wind: 0 Knots

Aircraft: Douglas ID: G-IANP Airline: Flight:

Flight plan: ELLX TO EHLE Lelystad:Lelystad NAV1: NID

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:01 Hours 02 Mins 30 Secs

Landing Score:117.54

Landing was successful in the following areas:

  • Good glideslope on visual approach. [50%]
  • Good alignment with runway on visual approach. [90%]
  • Gentle touchdown. [0 FPM]
  • Good landing speed - not too fast. [68 KIAS]
  • Wings were level.
  • Distance from runway threshold (visual approach): [1906 feet]
  • Landed on runway surface.
  • Glideslope held until flare.
  • Good pitch control after touchdown.
  • Good pitch at landing.
  • With flaps - good job.
  • Heading aligned with runway.
  • Throttle(s) idle.
    Landing included the following problems:
    • Ballooning during landing - needs practice.
    • Poor steering after landing - stay on the centre line.


      Flight Score:103.29

      Flight commended in the following areas:
      • Smooth turns.
      • Nice banking.
      • Gear deployment at safe speed.
      • Comfortable G forces.
      • Smooth pitch control.
      • Flown within aircraft's maximum speed limit.
      • Rotation was not late.
      • Appropriate position of flaps during taxi.
      • Smooth braking during taxi.
      • Smooth climb during takeoff.
      • Well coordinated turns.
      • No stalls.
      • No flying dangerously close to stall speed.
      • Pitch not too high.
      • Pitch not too low.
      • Flaps down on time.
      • Approach speed not too fast.
      • Low altitude speeds not too fast.
      • Good clearance of obstacles.

    Flight included the following problems:

Exceeding flap speeds - your flaps may be damaged: have them checked.Dangerous taxiing turns - these cause discomfort and stress.Poor steering during takeoff - stay in the centre of the runway.Poor elevator control during taxi in wind - danger of flipping.Poor aileron control during taxi in wind - danger of flipping.Poor attention to taxi speed - dangerous to yourself and others.Wings not level near ground - danger of clipping a wing.Rapid descent - dangerous and uncomfortable.
Definite room for improvement...
Link to comment
Share on other sites

OK, leg 5 done, and a poor landing will hit my averages a bit - off the centre line. Nice flight though - now for breakfast!

Ian piloting Beech King Air 350 Paint3 ended 22 April 2011 at 08:05

Aircraft: BEECH ID: G-IANP Airline: Flight:

Flight plan: EHLE TO EDDT Berlin:Tegel NAV1: ITLE

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:01 Hours 09 Mins 54 Secs

Landing Score:49.29

Landing was successful in the following areas:

* Good glideslope on ILS approach. [70%]

* Good alignment with runway on ILS approach. [80%]

* Gentle touchdown. [217 FPM]

* Good landing speed - not too fast. [100 KIAS]

* Wings were level.

* Landed on runway surface.

* Glideslope held until flare.

* Good pitch control after touchdown.

* Good pitch at landing.

* With flaps - good job.

* Heading aligned with runway.

* Throttle(s) idle.

* Good controlled final descent to touchdown.

Landing included the following problems:

* Not near the centre line - you can do better.

* Poor steering after landing - stay on the centre line.

Definite room for improvement...

Flight Score:106.64

Flight commended in the following areas:

* Smooth turns.

* Nice banking.

* Correct matching of flaps to speeds.

* Comfortable G forces.

* Smooth pitch control.

* Flown within aircraft's maximum speed limit.

* Good take off steering.

* Rotation was not late.

* Appropriate position of flaps during taxi.

* Safe taxi speed.

* Smooth braking during taxi.

* Smooth climb during takeoff.

* Wings level near ground.

* Well coordinated turns.

* No stalls.

* Smooth comfortable descent rate.

* Pitch not too high.

* Pitch not too low.

* Approach speed not too fast.

* Low altitude speeds not too fast.

* Good clearance of obstacles.

Flight included the following problems:

* Exceeding gear speed - your landing gear may be damaged: have it checked.

* Dangerous taxiing turns - these cause discomfort and stress.

* Airspeed too low - you are risking stalls.

* Flaps not down on time - plan your landing next time.

Definite room for improvement...

Link to comment
Share on other sites

That's leg 6 done - but, for the second time, I didn't get a flight score - only a landing score. No disconnects, I had stopped, brakes on, engines off, the end of flight conditions, but nothing. Gutted!

Scores are:

Ian piloting Beech King Air 350 Paint3 ended 23 April 2011 at 10:51

Aircraft: BEECH ID: G-IANP Airline: Flight:

Flight plan: EDDT TO ENGM Oslo:Gardermoen NAV1: OBW

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:02 Hours 05 Mins 04 Secs

Landing Score:86.95

Landing was successful in the following areas:

* Good glideslope on ILS approach. [70%]

* Good alignment with runway on ILS approach. [80%]

* Gentle touchdown. [335 FPM]

* Good landing speed - not too fast. [100 KIAS]

* Wings were level.

* Landed on runway surface.

* Glideslope held until flare.

* Good pitch control after touchdown.

* Good pitch at landing.

* With flaps - good job.

* Heading aligned with runway.

* Throttle(s) idle.

* Good controlled final descent to touchdown.

* Good steering after landing.

A splendid landing!

And, although I got a screen shot, there are no details now showing in either log book.

Link to comment
Share on other sites

OK, that's leg.... er... 7. My worst landing for ages, due to concentrating so hard on that offset ILS I neglected things like proper speed control, arming the spoilers, and so on. After such a good start - she complimented me on my take-off and said if I could keep it up it would be a perfect flight... yeah, right! Anyway, here we are:

Ian piloting Learjet 45 Limited Edition ended 23 April 2011 at 17:13

Aircraft: BOMBARDIER ID: G-IANP Airline: Flight:

Flight plan: ENGM TO EKVG Vagar:Vagar NAV1: SF

Failure(s): None at landing

Failure Event(s) (Zulu Time): None

Failure Bonus:0% Flight Duration:01 Hours 41 Mins 36 Secs

Landing Score:34.00

Landing was successful in the following areas:

* Good glideslope on visual approach. [50%]

* Good alignment with runway on visual approach. [90%]

* Wings were level.

* Distance from runway threshold (visual approach): [490 feet]

* Landed on runway surface.

* Glideslope held until flare.

* Good pitch control after touchdown.

* With flaps - good job.

* Heading aligned with runway.

* Throttle(s) idle.

* Good controlled final descent to touchdown.

Landing included the following problems:

* Too hard - may have damaged your landing gear. [814 FPM]

* Too fast - you had to force the plane to stay down. [158 KIAS]

* Nose down too low - you need to land on your main gear.

* Without spoilers armed - arm them before landing.

* Poor steering after landing - stay on the centre line.

Definite room for improvement...

Flight Score:108.19

Flight commended in the following areas:

* Smooth turns.

* Gear deployment at safe speed.

* Flown within aircraft's maximum speed limit.

* Gentle taxi turns.

* Good take off steering.

* Rotation was not late.

* Appropriate position of flaps during taxi.

* Safe taxi speed.

* Smooth braking during taxi.

* Smooth climb during takeoff.

* Wings level near ground.

* Well coordinated turns.

* No stalls.

* No flying dangerously close to stall speed.

* Smooth comfortable descent rate.

* Flaps down on time.

* Approach speed not too fast.

* Low altitude speeds not too fast.

* Good clearance of obstacles.

Flight included the following problems:

* Steep banking - save your aerobatic flying for some other time.

* Exceeding flap speeds - your flaps may be damaged: have them checked.

* Sickening G forces - your passengers feel rather unwell.

* Rough pitch control - that flight felt like a rollercoaster.

* Nose held too high - spilt drinks and worried expressions.

* Nose held too low - we're not in combat.

Definite room for improvement...

I have to say that some of the G forces problem was due to my yoke - I suddenly found out that I was pulling back on the yoke and nothing was happening - until I got to full deflection and suddenly the nose would jump up. Not sure what was happening there... make sure to check calibration next time. This whole thing is a learning experience...:D

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use