PilotEdge Forums

Anders, KCLT is Charlotte, NC. Is that where you're starting from? If so, that's well outside of our coverage area, there won't be any ATC.

The information you posted from skyvector just above, which airport is that related to?

Keith Smith wrote:Anders, KCLT is Charlotte, NC. Is that where you're starting from? If so, that's well outside of our coverage area, there won't be any ATC.

The information you posted from skyvector just above, which airport is that related to?

I believe he meant KCLR, not KCLT.

Worthwhile investigating a planning site specially for Pilotedge at http://www.myflightroute.com.
Weather briefings, frequencies and charts. Flightaware.
Then a link to Skyvector (IFR or VFR).
Then you can file your flight plan request direct into Pilotedge.

I use this site every time I fly online.

Ah very good. Yes, you'd announce your intentions on 122.90 (CTAF) then call LA Center once enroute. You can either pick your clearance on the ground via 128.60 (then swap to CTAF for takeoff, then back to center once clear of the pattern), or you could just depart VFR on 122.90 then call LA Center for the clearance when you're already in the air (that's what most people would do in real life since it's VFR 99.999% of the time there in the desert).

Also, in the real world it's unlikely you would be able to receive LA Center on the ground at KCLR. We have set up the radios to be more powerful than real world simply because the real world alternative (phone) isn't available, so we have to make the radios work

then 1 flight was done.
did try the I 1 test.
but unfortainly I failed. its a HUGE step from Vatsim. much better and professional.
I did turn to SLI before getting cleard there. so at that point I got to known that I failed. I should have kept hdg 220. and when almost on ILS. I was going to do a heading of 180 LEFT turn. but I did turn RIGHT. so ATC wasnt so happy I believe. so I have things too work on to be better, and will try again later and hope it all goes okey.

how short can a callsignal be?
I did use the N generator for this flight N172A, but can I use a shorter one?

thanks for answers.
-Anders-

Anders S wrote: How short can a callsignal be?
I did use the N generator for this flight N172A, but can I use a shorter one?

thanks for answers.
-Anders-

Read this:
https://www.faa.gov/licenses_certificat ... g_nnumber/

Anders,

There is a mantra for IFR flying, "where am I going now and where am I going next?" You should be asking and answering this question at the start of the flight and then after every course change.

"Where am I going?" refers to a heading, a fix or a radial. It's the target of your lateral navigation. So, prior to takeoff, the answer to the question would be "heading 220" and "where am I going next?" would be "vectors to Seal Beach."

So, prior to takeoff, set heading bug to 220 as a reminder and set up your navigation equipment to track SLI. After takeoff, fly heading 220 and wait for the vector. A simple takeoff briefing, visualization of the flight path and use of the mantra above should help clear up issues like this. Don't simply wait to 'get better' at doing this. Build a system which gets you thinking along the right track.

Yes thanks for info. I actually did take the test 2 hours later and I passed. Second flight was perfect. So maybe I was stressed and couldn't concentrate made me do too much errors at first time. If I didn't understand I just say can you please repeat.

I really like pilot edge so I enter the credit card information in the profile so I'm here to stay

And I did build a better system on 2 flight. Write down all frequency on paper so it's easy to read.

Welcome to the network

Keith Smith wrote:Anders,

There is a mantra for IFR flying, "where am I going now and where am I going next?" You should be asking and answering this question at the start of the flight and then after every course change.

"Where am I going?" refers to a heading, a fix or a radial. It's the target of your lateral navigation. So, prior to takeoff, the answer to the question would be "heading 220" and "where am I going next?" would be "vectors to Seal Beach."

So, prior to takeoff, set heading bug to 220 as a reminder and set up your navigation equipment to track SLI. After takeoff, fly heading 220 and wait for the vector. A simple takeoff briefing, visualization of the flight path and use of the mantra above should help clear up issues like this. Don't simply wait to 'get better' at doing this. Build a system which gets you thinking along the right track.

As a student pilot I can't believe I get the benefit of daily learning and advice like this, and the PE service itself to boot, for $20 a month. So valuable.