Jump to content

igorbischi

Members
  • Content Count

    133
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by igorbischi

  1. Ok, this is the flight plan (in fs2004 format). This is the first time I send an attachment, so I hope I did it right. The original name was LIRP-LIME.pln. I made it with fsbuild 2.2. The cruise fligth level is 220. For the flight I used the plane Pilatus PC12 by flight one, and for LIME I used the freeware ISD-Project airport, with the afcad by alessandro mozzi (lime-afcad-1.0.zip in avsim file library).Thank you.Igor
  2. Ok for msa over 400 then approach=6000 feet. The problem could be I was vectored to intecept the LOC too close to the airport (13 miles).About the 115 heading You are right. It wasn't 115 but 015, I made a mistake when I wrote it down. Now I am away from home. When I'll be home again this evening (italy local time) I'll send you the flight plan.Thank you.Igor>Hi Igor,>>The 6000 feet is because the msa for LIRE is over 4000 feet,>so that sounds about right.>>However the vectors can't be as you describe. If you were 30>miles S of the airport and vectored to 115 that would have>taken you further away from the airport.>>Could you post your entire flight plan so we can get a better>idea of what might have happened.>>All the best,>>John
  3. I did hear the call to descend to FL120. I made all the crossing restrictions as usually, and I switched to qnh only when I heard altimeter check.Igor>Hi Igor,>>Did you hear a call for you to descend to either FL120 or>FL110? If so that means you need to be down to that Flight>Level (still on STD pressure) 40 miles from LIME. If you were>given a 90 degree heading before reaching FL120 or FL110 it>means you didn't make the crossing restriction. You'll have>that confirmed in the critique at the end of the flight.>>Fly it again paying particular attention to making that>crossing restriction and ensure you stay on STD pressure until>you hear "Altimeter check". At that point tune to QNH>pressure.>>Hope that helps.
  4. I had a problem with a flight from LIRP to LIME. At about 30 miles S from lime I was vectored by approach to 115. At 13 miles SE from LIME I was vectored to 315, to intercept the localizer runway 29. I was told to mantain 6000 feet (I was at 6000 yet, qnh = 1000). The problem is that at 13 miles from the airport, 6000 feet, is too late to intercept the ILS descent path; indeed the needle of the glide slope was at the bottom of the navigation display. To be sure i didn't make any mistake I did the flight twice, but the result was the same. I am afraid it is a bug (I am sorry for my english).Igor Bischi
  5. After I land, when I press key 1 to contact ground at egll (any rwy) I have a CTD (atc.dll error). I use uk2000 egll scenery. could it be a wrong ground freq? A conflit with default fs9 atc? I tried to switch off all afcad in the area, flying with default cessna, no other add-on except fsuipc, but the result is the same. Only if I eliminate uk2000 scenery the crash doesn't happen. Do you have any idea?Thanks.Igor Bischi
  6. I'm sorry if the following aspect has been discussed yet:Airport at see level; fmc reduction clmb-1 thrust, fmc clmb thrust at 1500 feet; flaps 5 t/o, lnav engaged, mcp altitude selector at 10000 ft. If I engage a/p between 400 agl and 1500 agl flight level change engages too, and I red N1 in the a/t modes of the flight mode annunciator, so I presume the plane enters climb thrust before reaching 1500 ft. Is this correct? For me in this configuration the best way to t/o is: starting flaps retraction at 1500 ft, engaging a/p at 3000 (with flaps up) and then flight level change or vnav. Is there a right way to engage a/p earlier in the t/o phase?Thanks.Igor
×
×
  • Create New...