Are you going to do more videos?
On 3/16/17, Jordan Gallacher <jordanandseptember@xxxxxxxxx> wrote:
I am using RC4, and I am thinking I started the approach checklist too lateBlind and Visually impaired Pilots mailinglist
because I was at 2000ft 12 miles out and should have captured the
glideslope. I was running the Approach checklist right when Michelle said
to do it at right about 10 miles out. A quick this bit about RC4, look in
the controller options. You will find a box in there for your approach
altitude. It is often too high. For example I flew into KNID, and RC4
wanted me at 7600ft. Knowing this was not right, I changed it to 4600ft and
landed just fine. Also with RC4, always follow ATC's instructions including
speed. You will have a much more successful flight, and if you are already
running the Approach checklist, this is the only time you want to ignore any
speed changes RC4 tells you because at this point Michele is handling the
speeds. In high traffic areas and airports, this is especially nice since
it keeps the spacing correct, and landing is much easier and more fluid.
Jordan
Sent from my iPhone
On Mar 16, 2017, at 7:58 PM, Joshua Tubbs <orin8722@xxxxxxxxx> wrote:Blind and Visually impaired Pilots mailinglist
What ATC are you using, Jordan? Do you have to descend to capture the
glideslope? MSATC is the most simple but it also has serious problems
in high traffic. PF3 handles the coms for me, so I'm going to try
flight five now and see if I have better luck landing. I'll ignore all
airspeed requests, attempt to be at the right altitude for
approach--since PF3 or Radar Contact doesn't actually end your descent
there like MSATC does, which is about the only plus I can think of for
MSATC. Everything else about it sucks, like not being able to
acknowledge instructions while traffic is radioing in. Every other ATC
addon eliminates that.
On 3/16/17, Jordan Gallacher <jordanandseptember@xxxxxxxxx> wrote:Blind and Visually impaired Pilots mailinglist
I had a similar issue flying into KSAN last night. Going to try again
tonight but try a higher approach altitude. It appears that I hit
terrain
as I was descending through 1800ft. My approach altitude was 2000ft.
Jordan
-----Original Message-----
From: bvipilots-bounce@xxxxxxxxxxxxx
[mailto:bvipilots-bounce@xxxxxxxxxxxxx]
On Behalf Of Joshua Tubbs
Sent: Thursday, March 16, 2017 12:58 PM
To: bvipilots@xxxxxxxxxxxxx
Subject: [bvipilots] Obsticle at CYOW?
Hi all,
Unfortunately I missed the Glideslope on this video--not sure if I did
the
approach checklist too late, but I do the approach checklist after they
clear me for the runway and to contact tower when established, etc. Most
times, when I do the approach checklist when IYP tells me to, PF3 will
continue to nag at me to stay at my current altitude as IYP starts
landing,
or Mike locks onto the localizer, making me unable to follow the rest of
ATC
vector instructions.
If anyone knows of a way to make PF3 instructions consistent with the
way
IYP does things, it would be greatly appreciated. I know there's a ton
of
options in PF3, I'm just not sure what to set. It would be nice if PF3
would
tell me to descend to a suitable altitude for capturing the glideslope,
and
I don't know if the option is available already.
Also, I did eventually land visual, or tried to, at least, on the runway
32,
but I crashed into... something. I tried looking on airnav at CYOW to see
if
it'd tell me any navigational obsticles, but I couldn't find any.
Well, live and learn, I guess. Here's the video. It was a success in
Worldwide Virtual's Acars system, so I won't have to log the flight
again.
https://www.youtube.com/watch?v=NniRNhWjy4g
Blind and Visually impaired Pilots mailinglist
//www.freelists.org/list/bvipilots
To post a message to the list, send a message to bvipilots@xxxxxxxxxxxxx
To
unsubscribe, send a message to bvipilots-request@xxxxxxxxxxxxx and put
the
word unsubscribe in the subject of your message.
For other options such as digest, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject of
your
message.
Blind and Visually impaired Pilots mailinglist
//www.freelists.org/list/bvipilots
To post a message to the list, send a message to
bvipilots@xxxxxxxxxxxxx
To unsubscribe, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in the
subject
of your message.
For other options such as digest, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject of
your
message.
//www.freelists.org/list/bvipilots
To post a message to the list, send a message to
bvipilots@xxxxxxxxxxxxx
To unsubscribe, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in the
subject of your message.
For other options such as digest, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject of
your message.
//www.freelists.org/list/bvipilots
To post a message to the list, send a message to
bvipilots@xxxxxxxxxxxxx
To unsubscribe, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in the subject
of your message.
For other options such as digest, send a message to
bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject of your
message.
